I have been debugging and this notice.

How can I get rid of these notices.

NOTICE: wp-content/plugins/s2member/includes/classes/cache.inc.php:94 – Undefined variable: cache_needs_updating
NOTICE: wp-content/plugins/s2member/includes/classes/sc-profile-in.inc.php:67 – Undefined index: ws_plugin__s2member_profile_saved
NOTICE: wp-content/plugins/s2member/includes/classes/sc-if-conds-in.inc.php:83 – Undefined variable: logicals
NOTICE: wp-content/plugins/s2member/includes/classes/sc-if-conds-in.inc.php:89 – Undefined variable: logicals
NOTICE: wp-content/plugins/s2member/includes/classes/sc-if-conds-in.inc.php:175 – Undefined variable: condition_failed

The 1st one is on a page with the pro log in widget.
The last four are on a page that uses conditional shortcodes and also has the edit profile shortcode.

I know that if I use the php versions in a template I can get rid of the if-condition errors. But the shortcodes make it nicer. Yes I could turn off debug to but I’m debugging so…It’s the 1st one I want do deal with most as it’s filling my log file up.

Thanks for your time.

Hi Michael.

You’d have to edit the files to define those variables before they are checked in the line where you get the notice. E.g. default [hilite mono]$cache_needs_updating[/hilite] to false before the conditionals.

I hope that helps. :)

Thanks for the heads up on this thread :-)

Please see this related article.
http://www.s2member.com/forums/topic/cache-needs-updating-error/#lead-topic-41260

The solution is to put your installation of PHP and WordPress® into production mode. You are currently running in DEBUG mode; which is why you are seeing NOTICES from PHP.

Thanks Cristian I will do that so I can continue debugging what I need to and not see s2members notices.

Jason thanks for the link. In it I learned that you are fixing your code to deal with this. That is the real solution to the problem and not me having to turn off debugging when I am debugging. I feel you are saying its me not you.

Thanks Cristian I will do that so I can continue debugging what I need to and not see s2members notices.

Cool. :)

In it I learned that you are fixing your code to deal with this.

Right, the next generation of s2Member being developed will take care of these warnings.