WP 6.1.1 with Gutenberg
All plugins up to date
PHP 8.0
Hello team,
after update WP 5.8.6 to WP 6.1.1
SiteOrigin Widgets Bundle and Page Builder by SiteOrigin no longer work correctly in the backend.
The display in the frontend is o.k. as long as nothing is changed in the content in the widget or in the builder.
If something is changed and saved, the same problem as described in 2 occurs.
Already checked, but without success:
– All plugins disabled = no change
– Customizr theme replaced by WP standard themes = no change
– Changeover at the provider PHP 8.0 to 8.1 = no change
Description:
1. Used:
SiteOrigin Widget “Accordion” = display in the backend = o.k.
editing possible. Changes are not (!) saved.
Preview doesn’t work. When selected, the editing area of the widget is closed.
2. Used: “Features”
When opening the page = lines and wiget in lines are only displayed as text elements with partly cryptic characters.
Selection of the blog and editing (save works here) = line and widget are displayed. Text content is partly cryptic. Image elements are not displayed in the backend.
Example:
Hans Mustermann
job title
office for this and that
u003ch4u003eNameu003cbr /u003e
Practice child and adolescent psychotherapyu003c/h4u003e
u003cpu003eExample street 25u003cbr /u003e
12345 Musterhausenu003cbr /u003e
phone: 0 12 34 . 56 78 99u003cbr /u003e
u003ca href=u0022mailto:[email protected]@mustermann.deu003c/au003eu003c/pu003e
u003cpu003eu0026nbsp;u003c/pu003e
3. used: “Tab” = same behavior as “Features”
4. Note: The content of newly created elements remains and changes are saved.
What could be the reason?
Thank you for your effort.
Greetings
Dachs
Hi Dachs
Has your site recently been migrated from one server to another?
Hi Andrew,
thanks for your reply.
No. The site has been running since April 2021.
Hi Dachs
Thanks for the update.
The most common causes of characters displaying in unicode are storing data in a type that doesn’t support the characters, a plugin incorrectly filtering the content, or a language selected in WordPress that doesn’t match the characters output. If the issue persists with a default theme activated and all plugins except for Page Builder and the Widgets Bundle deactivated, you can perhaps try checking that your database is set to utf8.
Sorry, it took a while.
Just checked the mysql database settings.
Table shows utf8mb4_unicode_520_ci for almost all.
wpm subscribers and yoast_seo links = utf8_general_ci.
latin1_german2_ci is predefined for the collation in the Operations tab.
The character set is defined in the wp-config:
define( ‘DB_CHARSET’, ‘utf8mb4’ );
The provider explains that the data from MySql is stored encoded in UTF-8 by default, but the data between server and client is exchanged in Latin-1.
https://www.hosteurope.de/faq/webhosting/mysql-DB/mysql-und-zeichensaetze
So this could be the problem.(?)
Also for the problem that the changes in the widget cannot be saved?
Hi Dachs,
Thanks for checking. That collation is fine and means that this issue is unrelated to the database itself.
That’s possible. Can you please link me to a page on your website where I can inspect this issue?
The SiteOrigin Widgets Block stores data on save so changes aren’t always reflected during a plugin conflict test. Try disabling all non-SiteOrigin plugins and then making a change to the block affected by this. Does the issue persist? If not, try re-enabling each plugin one by one (making an edit each time) and then when it occurs again, what was the last activated plugin?
Kind regards,
Alex
Hi Alex,
I checked everything again this afternoon and tested possibilities.
I will go through all the pages again.
Duplicate the blocks with the widgets and re-enter the content.
Saving is then possible and everything is displayed correctly in the frontend.
Thanks for your effort.
I’ll report back if this path has led to success.
I hope that the next website I have to update
with the same configuration (but still with the Classic Editor)
does not show the same problems when updating to WP 6.1.1.
Best regards
Dachs
Hi Dachs,
Sounds good. Let me know if it occurs again. If it does occur again, I recommend regenerating the widget content using the instructions in my last reply as that should hopefully allow you to identify a conflict.
Kind regards,
Alex
Hi Alex,
had done the path you described before. Without a result.
I found the problem now.
I carried out the checks (text changes, saving etc. – by deactivating and reactivating the plugins) on a duplicated page (Plugin Post Duplicator).
This is causing the problem. So far I haven’t had this problem. And I usually only work in duplicates and not in the original pages.
Finally, thank you again for your kind support!
The problem is solved.
Best regards
Dagmar Nebur
Hi Dachs,
Thanks for checking. I recommend reporting this issue to the developers of that plugin as it’s likely a sign of a general issue related to duplicating data rather than a third party plugin.
Kind regards,
Alex