Hi @jsnowbusiness,
Thanks for posting on the forum.
Are you using Pro or free version of Membership plugin?
I didn’t find the code that you have shared in the file default.rules.php on line 630
This is a simple PHP Notice and most of the time it doesn’t affect any functionality so it is nothing to worry about!
Do you have WP_DEBUG set to true in your wp-config.php file?
If you do then please set it to false.
This will hide the warning messages and you will be able to use your site normally.
Could you please try changing the following code in your shared code to resolve the notice message?
Before Editing:
if ( $M_options['shortcodedefault'] == 'no' ) {
After Editing:
if ( isset('$M_options['shortcodedefault']') && $M_options['shortcodedefault'] == 'no' ) {
Note: You are making changes in the plugin file and these changes will be overwritten and lost when you update the plugin and you will have to make these again after plugin updation.
To find find out what is causing the issue you can just try on your development site using default WordPress theme like Twenty Thirteen and deactivating all other plugins as displayed in the following flowchart to know which theme/plugin is causing the issue if any.
http://premium.wpmudev.org/wp-content/uploads/2013/12/Support-Process-Support-Process.png
Kind Regards,
WPMU DEV
Yes it IS the pro plugin version now that I’m looking at it (the site isn’t actually mine, just doing work on it) – and no I do NOT have debug enabled in my config, that’s why this is a problem.
If I deactivate the membership plugin, going to my site with or without www. both resolve properly. With the plugin activated, if I go to my page without www. then I get this error on an otherwise blank page.
I will try the edit and see what happens. I will also try the plugin alone and with Twenty Thirteen to see if it resolves the issue. If need be, I will ask the site owner for credentials needed for Membership Premium support.
Thanks!
I tried the edit and it just made my site give 500 Internal Server Errors, so on to isolating the plugin on Twenty Thirteen.
Hi @jsnowbusiness,
We’d love to assist with this. If it hasn’t already been sorted, could you please contact us here? http://premium.wpmudev.org/contact/
Hoping that’s already resolved but if not, I’m sure we can sort it out there! 🙂
Cheers,
David