jfoster-42

No problem ?? I update support threads with solutions almost religiously. There is nothing more frustrating than finding someone who has your exact problem, and they don’t share the fix.

That said:

The conflict in AIOWPS is in the firewall settings.

If anyone else has this problem, go to WP Security > Firewall

Untick the ‘Deny bad query strings’ option, and disable the 5G firewall settings. Fixed everything for me!

All other AIOWPS settings work fine with s2member, I went through and tested each one individually.

Thanks again @kts915 for your help! I really appreciate it ??

Ok so just for the sake of being thorough, I decided to go back and check for plugin/theme conflicts. Previously, I figured it couldn’t be either of those (famous last words) since my local and subdomain copies have all the same plugins and themes running, and they work.

Still, figured I’d check before doing a clean install.

It appears that All In One WordPress Security is causing the error. Specifically, something in the .htaccess rules it adds to the site. With the plugin activated as a vanilla install, everything works. But once you restore the .htaccess rules, it all goes to crap.

I will come back and update this thread once I find the AIOWPS setting that’s causing the conflict.

Thanks so much for your help @kts915!!

Totally understand ?? Thanks for clearing that up!

Hm…I’ve never used the cPanel clone tool on this site. I always either use WP Migrate Db + manually transfer files, or I use a plugin called Updraft Plus which handles our backups, and it can do migrations as well.

I just took a full clone of the live site and tried it on my local environment. It was a fresh copy so I know everything is exactly the same, and it seems to be working fine.

I also tried adding define ('COOKIE_DOMAIN', '.example.com'); to the wp-config file, since the live one is the only version that has a subdomain. Doesn’t seem to have done anything though.

Bluehost was kinda unwilling to help, since no matter how I ask the questions it sounds like an s2member problem rather than a hosting problem ?? which kinda sucks. How were you able to determine that it was an issue with the cloning method?

Ah okay! I apologize, I thought you were an s2member employee!

WordPress seems to know I’m logged in, as I can get into the admin area just fine and all my logged in/logged out conditionals work as expected.

Again sorry for the confusion and thank you so much for your assistance ??

I contacted my hosting provider, they checked for any differences between the subdomain and the live site. There weren’t any differences. They did run a few checks and made sure all permissions were set correctly etc, no luck though.

Tried importing configuration settings from the broken site and importing to a working local environment, but everything still worked.

I found your s2-server-scanner, and ran it against the broken and working versions. The broken one came back with a checksum error. There was an error log on the broken site, once I deleted it the checksum error went away. I checked the error log, and it’s only got one entry from about 3 weeks ago, nothing related to this issue.

If you could provide any more insight into this I would much appreciate it as the site owner will soon be starting a big marketing push encouraging users to upgrade from free accounts to paid ones, and with this issue they will not be able to upgrade.

Thanks for all your help already!

Hm…what kind of a configuration error could cause that? Something in their caching?

We’re on Bluehost if that makes a difference.

Yup, I’ve tried clearing the cache and cookies (to rule out a cookie conflict like I mentioned earlier)

And yep, just tested it in Chrome and MS Edge to verify, same issue on both as with Firefox.

https://www.mysite.com to be specific, but yes. It’s the same in both the WP Address and the Site Address.

Just tested the issue on my local environment, and it seems to work fine, just like the staging site.

Looks like it’s just having trouble with the main site.

Any ideas?

Update:

Tried changing the WP Address and Site Address settings on our staging site (the subdomain) to use www, and still no change. The forms work on the subdomain but not on the live site.

Gotcha.

In the WordPress Address and Site Address settings we have www set on the live site, and the subdomain for our staging site does not use www.

Upon further reading, it sounds like it might be a cookie issue. Is that possible?

Thanks for the reply!

Hey there!

Thank you for the suggestion! It definitely improved the code and it’s almost working now.

However it appears that something is messing with the timestamp on the most recent post, as well as the next post after that. The most recent one should not have the link, and the one after it should. But WordPress seems to think that the most recent one is far older than it is (timestamp shows +3million) and the next post, which is several days old, shows as being only a few hours old.

Is there something funny in my code that’s causing this? Or could this be an oddball WP error? I’m developing on a local server right now, I know that makes WordPress do some weird stuff occasionally.

Code as of now:

//Stuff to make sure widget obeys s2member
                    $post_age = date('U') - get_post_time('U');
                    //if ( current_user_can('access_s2member_level1') && strtotime($post->post_date) > strtotime('-1 day') ) :
                    if ( current_user_is('s2member_level1') ) :
                        echo "Level 1";

                        $restrict_before = 86400; //Number of seconds per day.
                        if ( $post_age > $restrict_before ) :

                            $anchor_open = '<a href="' . get_the_permalink() . '">';
                            $anchor_close = '</a> ';

                        else :

                            $anchor_open = "";
                            $anchor_close = "";

                        endif;

                    elseif ( current_user_is('s2member_level2') || current_user_can('update_core') ) :

                    $anchor_open = '<a href="' . get_the_permalink() . '">';
                    $anchor_close = '</a> ';

                    //elseif ( current_user_can('access_s2member_level0') && strtotime($post->post_date) > strtotime('-2 days') )  :
                    elseif ( current_user_is('s2member_level0') || !is_user_logged_in() )  :
                    echo "Level 0";
                        $restrict_before = 2 * 86400; //Number of days to restrict x number of seconds per day
                        if ( $post_age > $restrict_before ) :

                            $anchor_open = '<a href="' . get_the_permalink() . '">';
                            $anchor_close = '</a> ';

                        else :

                            $anchor_open = "";
                            $anchor_close = "";

                        endif;

                    endif;

Thanks!