Just created a WP Staging site for my production site. This plugin works ok on the main production but blocks my identical staging site with a status 500 Server error. I assumed the problem would be in the .htaccess file so commented-out all lines added by this plugin then renamed the plugin via ftp. Now my staging loads and runs ok but with the plugin completely inactive and i really need it for the 2FA features more than any other. What lines in .htaccess could possibly be the issue in causing 500 errors in a staging site.
Thanks
]]>I came to know it can be because of security plugin so i have deactivated SSL plugin kindly let me know what can be done. Can i again activate it?
]]>PHP Fatal error: Uncaught TypeError: Argument 1 passed to Yoast\WP\SEO\Integrations\Third_Party\Zapier_Free::add_publishbox_text() must be an instance of WP_Post, string given, called in /www/wp-includes/class-wp-hook.php on line 308 and defined in /www/wp-content/plugins/wordpress-seo/src/integrations/third-party/zapier-free.php:43
To reproduce:
This is the website
[ redundant link removed ]
I have a problem with the plugin Royal Elementor Addons- I get a 500 server error when I tried to update changed in the site. after addressing to a programmer he gave me this error when debugging.
[07-Apr-2022 13:41:44 UTC] PHP Notice: Trying to get property ‘post_name’ of non-object in /home/zuzistudio/public_html/wp-content/plugins/royal-elementor-addons/classes/utilities.php on line 313
please advise how to solve this issue.
]]>I had to remove it!
]]>First of all, love your plugin. Have been using it on many sites which allowed me to stop having to create child themes.
The plugin has performed well up until now on this WPML site. I have contacted WPML first, see https://wpml.org/forums/topic/500-error-when-enabling-disabling-plugin/ but they refer to their errata https://wpml.org/errata/htaccess-is-rewritten-with-language-folder/ and tell me they have a fix on their end and now it’s up to the plugin developer to implement their fix.
If you could be so kind as to have a look at their suggestion. Both we and WPML were able to reproduce the issue.
]]>