Since upgrade to most recent S2 open registration shows an error: enable javascript/cookies

Since upgrading to the most recent version of s2member 170722 on our site: http://mcm-ct.com no matter what we do or which browser we use this is the result of the open registration option. Basically can not proceed because the register form returns that javascript and cookies should be enabled. On all browsers we tested these are enabled

At a loss of what to do…

Could you take a look in the browser’s console to see if any errors are mentioned?

I’m suspecting a plugin or theme conflict. https://s2member.com/kb-article/common-troubleshooting-tips/#toc-8503e1db

Let me know how it goes. :slight_smile:

I also got your emails with the post you made here. Let’s continue the conversation here. :slight_smile:

Thank you cristian…did not want to overwhelm you

Not sure what to do about a theme conflict - using Enfold. Did not upgrade the theme only S2

Also noticed with the S2 upgrade the member level names changed,

“S2 Member Level 1” -> ”Member”
“S2 Member Level 2” -> “-“
“S2 Member Level 3” -> ”-“
“S2 Member Level 4” -> “-“

Not sure if this is relevant in any way but maybe something is not right with he upgrade to the new s2 if those were lost

here is a snapshot of the console

We disabled all the plugin’s except s2 and the problem still persists

Also, checked the configuration and removed the captcha and the error persists still…not sure what tests to do next from the thread you kindly forwarded in this post

Oh, no problem.

I see in your page several warnings in the console. Did you manage to solve/remove them all for your tests?

So you’re saying that you went back to just WordPress and s2Member in your test, no other plugin or theme than the default?

This is something I only see when there’s a JS conflict by a plugin or theme.

If you could, for a new test, create a clean installation of WP in a subdirectory, and add only s2Member, and try to reproduce the problem there.

I look forward to your update. :slight_smile:

No these warnings did not have anything to do with the problem but rather disabled plugin’s

Its just weird because everthing was working until we upgraded to the latest s2 to be compatible with wordpress 5

We did disable all plugins except s2 which brought it back to the Enfold theme and s2 as the only install

Has difficult to do these tests during the day - so will do more testing overnight. But is there anything you can recommend re these kind of conflicts as where to look specifically any php or type of err log location?

I haven’t been able to reproduce it in my installation, it seems to be particular to your installation.

Yeah, disabling plugins is harder in a production site. I think it’d be good to create a separate WP installation in a subdir (it’s pretty easy since most web hosts now have Fantastico or Softaculous). Try registration in the vanilla install. After that add s2Member and test signup again. Then add the custom profile fields and test again. https://s2member.com/kb-article/testing-in-a-clean-wordpress-installation/

This is exactly what I’d do with my site if I were having the issue you’re telling me. :slight_smile:

Hi there, did you make sure to test this with the initial WordPress theme, not your Enfold theme?
Also did you try to start fresh in a new location with only the initial WordPress theme plus S2? :slight_smile:

Since upgrading to the most recent version of s2member 170722 on our site: http://mcm-ct.com we still have problems with the registration page and also with all PayPal sign-up links.
Is it possible to downgrade the s2member version to a previous version?
Thank you

Was s2Member the only one you updated that day? Maybe it was the update of another plugin that added this weird behavior.

Yes, you can go back to an earlier release usually. It depends on what changed between them, but last ones should be fine, as far as I can tell. You just replace the s2member and s2member-pro folders in /wp-content/plugins/ dir, with the earlier versoin of each that you want to try. Pro has to be same version as Framework to become active.

You can find earlier releases here: https://s2member.com/release-archive/

I hope that helps. :slight_smile: