Support

November 2, 2022 at 5:40 am

Hmmm, very strange.

So nothing in the code stands out for me in that Memberpress isn’t somehow triggering an EE function to display notices, however, based on the fact that the notices show the espresso-notices classes I suspect somehow memberpress has injected a bunch of details into the option used by Event Espresso to store persistent notices.

So I don’t think its a case of EE and Memberpress conflicting when running, but rather ‘something’ has happened and additional data stored in the wp option. Which means EE is then looping over all of those details expecting them to be EE notices and outputting them to the page.

Are you comfortable with PHP? I can give you a snippet to output the option so we can see if that is what is happening if so.

November 3, 2022 at 6:02 am

First, create a database backup just to be safe.

This:

var_dump(get_option('ee_pers_admin_notices', array()));

Will output the option EE uses for persistent notices.

If you can grab that content and post it here I can check it out.

Or, the other option if you have phpMyAdmin access if to check the wp_options table, search for an option name of ‘ee_pers_admin_notices’, like this:

https://monosnap.com/file/SLEgotUeJ3J0KR3iku1twz0x5fcMT1

Grab the option value from that and save it to a file.

You can then either manually set it to be a:0:{} or set an empty option using:

update_option('ee_pers_admin_notices', array());

and see if that removes the notices.

EE saves the admin notices to track them and an empty option wont break anything but make sure you backup the value first.

November 3, 2022 at 10:54 am

You’re most welcome 🙂