IMPORTANT - Re-save S2Member Settings After WP 3.2 Upgrade

[rossagrant]

Hi guys,

just a quick one but remember to re-save the S2Member settings on your install after upgrading to WP 3.2.

If you don't the internal Cron Job for S2Member to check EOT's will NOT be activated until you do!

Ross

[BobTabor]

Hi Ross, thank you, I'm going to upgrade this morning. What exactly do you mean when you say:

re-save the S2Member settings

How exactly do you "re-save"? (Sorry if this is obvious, I'm still rather new to this environment.)
Thank you!
Bob

[rossagrant]

Hey Bob, just go into any menu and hit 'save' again. Just as you would if you'd changed something but you don't actually need to change anything, just hit save!

Job Done!

[BobTabor]

Awesome, doing that now ...

For the sake of my ongoing understanding, why in the world do we need to do that?!?

(I'm having an issue after upgrading to the previous version of WordPress just yesterday -- in a different post ... wondering if this is not somehow related.)

[rossagrant]

When WP upgrades the database after installing the new version it seems to strip the cron jobs from the database for S2Member. No idea why, i'll ask Jason. It keeps all of your other settings just fine but somehow the S2Member cron job which automatically looks for member's EOT's wasn't showing after I upgraded so I saved ,y settings in S2Member and voila it appeared.

[Cristián Lávaque]

Thanks for the heads up!

Do you mean saving the EOT settings (Auto-EOT Behavior) or all of them (General Options, Restrictions, etc.)?

[rossagrant]

Hey Cristian. A simple click of the save settings button under general options will do the trick. You needn't go into any menus, all options should be saved if you have the 'Deactivation safeguards' set to yes.

[Cristián Lávaque]

Got it. Thanks.