Kasia

Thank you @juliengemaddis, this helped me. You’re a star.

All good now, thank you!

I implemented the change you provided. Now, the username retrieval form doesn’t load at all and I get the following in my error_log file:

[01-Mar-2022 21:44:32 UTC] PHP Fatal error: Uncaught Error: Call to undefined method WP_Members_Shortcodes::do_forgot_username() in /home/myaccount/public_html/wp-content/plugins/wp-members/includes/class-wp-members-shortcodes.php:860
Stack trace:
#0 /home/myaccount/public_html/wp-content/plugins/wp-members/includes/class-wp-members-shortcodes.php(153): WP_Members_Shortcodes->render_pwd_reset(NULL, ”)
#1 /home/myaccount/public_html/wp-includes/shortcodes.php(356): WP_Members_Shortcodes->forms(Array, ”, ‘wpmem_form’)
#2 [internal function]: do_shortcode_tag(Array)
#3 /home/myaccount/public_html/wp-includes/shortcodes.php(228): preg_replace_callback(‘/\\[(\\[?)(wpmem_…’, ‘do_shortcode_ta…’, ‘[wpmem_form pas…’)
#4 /home/myaccount/public_html/wp-includes/class-wp-hook.php(307): do_shortcode(‘[wpmem_form pas…’)
#5 /home/myaccount/public_html/wp-includes/plugin.php(189): WP_Hook->apply_filters(‘[wpmem_form pas…’, Array)
#6 /home/myaccount/public_html/wp-includes/post-template.php(253): apply_filters(‘the_content’, ‘[wpmem_for in /home/myaccount/public_html/wp-content/plugins/wp-members/includes/class-wp-members-shortcodes.php on line 860
[01-Mar-2022 21:44:47 UTC] PHP Fatal error: Uncaught Error: Call to undefined method WP_Members_Shortcodes::do_forgot_username() in /home/myaccount/public_html/wp-content/plugins/wp-members/includes/class-wp-members-shortcodes.php:860
Stack trace:
#0 /home/myaccount/public_html/wp-content/plugins/wp-members/includes/class-wp-members-shortcodes.php(153): WP_Members_Shortcodes->render_pwd_reset(NULL, ”)
#1 /home/myaccount/public_html/wp-includes/shortcodes.php(356): WP_Members_Shortcodes->forms(Array, ”, ‘wpmem_form’)
#2 [internal function]: do_shortcode_tag(Array)
#3 /home/myaccount/public_html/wp-includes/shortcodes.php(228): preg_replace_callback(‘/\\[(\\[?)(wpmem_…’, ‘do_shortcode_ta…’, ‘[wpmem_form pas…’)
#4 /home/myaccount/public_html/wp-includes/class-wp-hook.php(307): do_shortcode(‘[wpmem_form pas…’)
#5 /home/myaccount/public_html/wp-includes/plugin.php(189): WP_Hook->apply_filters(‘[wpmem_form pas…’, Array)
#6 /home/myaccount/public_html/wp-includes/post-template.php(253): apply_filters(‘the_content’, ‘[wpmem_for in /home/myaccount/public_html/wp-content/plugins/wp-members/includes/class-wp-members-shortcodes.php on line 860`

Thank you very much for this. I am using the Sucuri plugin to automatically update all of the default WordPress Salt hashes once a week as a security measure. I’m betting my problems with disconnection coincided with that. Hopefully adding these additional salts that aren’t being targeted by Sucuri will resolve the issue. I’ll update again if this doesn’t resolve the issue long-term.

I think the free limit is 25 but don’t quote me.

Ray,

It’s true. Google will force you to set up billing before issuing an API, mostly as a backstop in the event that your daily per project request count exceeds the limits provided by their free service.

This is not something a plugin developer can avoid when use of the API is required. I have been going through the process of issuing API keys for a number of different website projects in my portfolio that use Google API. Not once have I ever been billed for my usage because the traffic levels on my site aren’t high enough. So if you have more than 50K visitors to your site every day, you might have to worry about getting charged for API usage. Otherwise, it’s a non-issue. Hope that helps clear things up.

• This reply was modified 5 years, 11 months ago by Kasia.

It appears that a clean WordPress install running only WooCommerce and NextGEN with the TwentySeventeen theme does not throw an error. Unfortunately, the live site where the problem occurs is running on a custom theme with many other necessary supporting plugins. I did activate the TwentySeventeen theme on this site when I was trying to figure out the problem and still experienced issues, so I’m guessing that perhaps there is another plugin that might be contributing to the problem. Because the gallery is a very minor feature of this site, it would not be a good use of resources to spend a lot of time trying to determine where the conflict is. As such, I have replaced NextGEN on this website with a different photo gallery plugin that isn’t causing any conflict with WooCommerce. Thanks anyway.

Just an FYI for anyone who may also be experiencing these issues. I solved the problem by adding the following line to my site’s .htaccess file:

php_value opcache.enable 0

An update here, today everything with Sandbox appears to be working properly so I can only assume the issue was on PayPal’s side.

Yes, you are absolutely right. It is the Toolset Views plugin that is causing the conflict. I use this in combination with WooCommerce Views to do a couple of things with my site. I will bring this to their attention. Thanks.

• This reply was modified 7 years, 11 months ago by Kasia.

Just wanted to add that after the 3.0.1 update, the automated database upgrade pushed by the plugin worked fine and I no longer experienced data corruption. Still working on sorting through the new version before I go live, but glad to see this issue was solved.

Problems here as well. I had to restore my database from a pre-3.0 backup, as well as revert to the previous version of the plugin. After the upgrade, I got the white screen of death on the front end until I ran the “database upgrade” pushed by the plugin on the backend. After that, my site’s functionality was restored, but it was clear that data had become corrupted somehow. I kept getting fatal errors about exhausted memory when I tried to load my product list, and certain products had attribute and variation data that just disappeared and seemed to create bugs. The data upgrade pushed by the plugin did very bad things! I hope the next release solves this issue.

• This reply was modified 7 years, 11 months ago by Kasia.
• This reply was modified 7 years, 11 months ago by Kasia.

Using version 2.4.6 and applying the fix suggested by Nate Allen here:

https://www.ads-software.com/support/topic/post-thumbnail-editor-not-working-with-the-wordpress-update#post-8296929

worked for me.

I would suggest removing current version 2.4.7 from the repository and applying this solution to 2.4.6 and releasing that as 2.4.7. I have just spent my afternoon rolling all of my websites back to 2.4.6 and applying this fix.

Just wanted to add that I ran into this issue as well and this thread was extremely helpful. I just recently switched hosting providers, and so I am assuming that the new host does not have the mod_authz_core.c and the previous one did. I am disabling hardening and removing the associated .htaccess files until Sucuri can address this more permanently.

Disregard this, the e-mail finally showed up on my third attempt.