Peter Wooster

The issue is that the remote server is MySQL, the local server is MariaDB which doesn’t support the utf8mb4_0900_ai_ci collate. Something in your plugin is requesting that collate as it doesn’t appear in any other database tables.

I’m a backend developer, so not much more familiar than you are about using Divi. What got me interested in this was when shortcodes I wrote were not being found. I’ve asked my client to walk me through how to build a Divi template and I’ll forward it to you. What i do know is:

• open Divi Theme builder
• open Global Body Template (second on left)
• use the gear icon to get the editor.

Divi is very complex. Here’s the Elegant Themes documentation on this. https://www.elegantthemes.com/documentation/divi/the-divi-theme-builder/

I suspect any Divi template part will have the same problem and that this probably applies to any page or site builder that relies on custom post types to store its template parts.

The problem is lines 186 and 199 in shortcodes-finder-admin-display. This restricts the display to shortcodes in public post type posts. Removing the ‘public’ => ‘true’ criteria fixes the problem for Divi and probably other page builders. In Divi these posts contain author supplied content provided in the Template Builder and can contain shortcodes.

I’m not marking this as resolved since it needs an update to the plugin. Either make this an option or just remove the ‘public’ => ‘true’.

Yes, All In One SEO is a good plugin, and the free version does what we need. I’ve been recommending it to clients for a while over Yoast, and we use it in house as well. It’s just a surprise when I get a message from a client with the subject “Red Dot” and a screen shot of the plugins showing the red dot beside a plugin I didn’t recommend and that she doesn’t need. I then wasted half an hour finding where it came from. This is especially annoying when I see that the red dot is an ad telling her to purchase that plugin.

Thank you for the clarification. It seems that WordPress tolerated the old plugin until version 5.8 (new widget support?). I took a look at her plugins from SFTP and immediately removed Gutenberg as I knew it was no longer needed.

This post is for all the people who keep posting questions about this specific error and getting the usual “disable all plugins” answer. That’s hard to do if you don’t have access to the admin. Deletion using FTP or equivalent is all you can do.

I’m sure you have clients who never maintain their plugins but let their host update WordPress. I’m surprised that the host didn’t back off the update as this error breaks everything, including the admin.

• This reply was modified 3 years, 2 months ago by Peter Wooster.

One of my clients got the message “PHP Fatal error: Cannot declare class WP_Widget_Block, because the name is already in use in … wp-includes/widgets/class-wp-widget-block.php”

This was caused by the old Gutenberg plugin. Removing the plugin fixed the problem.

I will ticket about this.

I’ve released version 1.6.0 to fix the problems with WP 4.8+ and PHP 7. Please give it a test and report any problems.

I’ve just released version 1.6.0 of the Simple Access Control plugin to fix this error and support PHP 7.

I’ve added an option to produce a 404 Not Found error when a user tries to access a restricted page or post directly. Please give it a try.

/peter

I’m working on a fix for this and will release it later today.
/peter

I’m working on a fix for this plugin. I’ll release a new version shortly when I’ve tested this. Thanks to @hmabpera and @westonruter for diagnosing this problem and writing it up in ticket 41540.

You need to add a redirect near line 104. That is where the code sets the locked text for a page.

I’ve tested this on 4.7.5 and it works there.

I don’t have access to that theme. This is a very simple plugin that uses postmeta to control the access to the page. If that theme is removing postmeta, aka custom fields on page save that could cause this problem. Please check and see if the sac_locked custom field is being removed.

I have tested this plugin with HTTPS and it works on my site.