Opened 3 years ago
Last modified 3 years ago
#53789 new defect (bug)
all kinds of error messages using WordPress 5.8 Widgets block editor
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Awaiting Review | Priority: | normal |
| Severity: | major | Version: | 5.8 |
| Component: | Widgets | Keywords: | reporter-feedback |
| Focuses: | javascript, administration | Cc: |
Description
After the Upgrade to WordPress 5.8, in the backend when I choose Appearance / Widgets (to edit widgets), I get error messages like these:
The "blog_subscription" block was affected by errors and may not function properly. Check the developer tools for more details.
The "google_translate_widget" block was affected by errors and may not function properly. Check the developer tools for more details.
The "recent-posts" block was affected by errors and may not function properly. Check the developer tools for more details.
The "text" block was affected by errors and may not function properly. Check the developer tools for more details.
The "nav_menu" block was affected by errors and may not function properly. Check the developer tools for more details.
The "text" block was affected by errors and may not function properly. Check the developer tools for more details.
The "text" block was affected by errors and may not function properly. Check the developer tools for more details.
The "text" block was affected by errors and may not function properly. Check the developer tools for more details.
The "text" block was affected by errors and may not function properly. Check the developer tools for more details.
The "text" block was affected by errors and may not function properly. Check the developer tools for more details.
The "bbpmmymessages" block was affected by errors and may not function properly. Check the developer tools for more details.
The "text" block was affected by errors and may not function properly. Check the developer tools for more details.
The "search" block was affected by errors and may not function properly. Check the developer tools for more details.
I installed and activated the Classic Widget Editor plugin so I could function. Later (after an update from one of the Widget providers), I deactivated the CWE plugin so I could see if this provider's widgets were now working with the 5.8 Widget block editor. (Some were fixed, some weren't). Unbelievably, though, I got more errors than before showing that widget blocks which seemed to be working before now were not working! I got a lot of Internal Error messages, whereas before I only saw one or two of these. Did switching to the Classic Widget Editor and then deactivating cause more problems? Now every time I try to access the 5.8 Widgets block editing, I get new or different errors. Very confusing and upsetting.
Attachments (6)
Change History (21)
#3
@
3 years ago
Your question: is this a live website? Answer: Yes.
Your question: what are the plugins that you have enabled? Answer:
Advanced Editor Tools (previously TinyMCE Advanced)
Akismet Anti-Spam
BackWPup
bbP private groups
bbp style pack
bbPress
bbPress - Moderation Tools
bbPress Advanced Statistics
bbPress Messages
bbPress Move Topics
bbPress WP Tweaks
Classic Editor
Classic Widgets
Code Snippets
Content Aware Sidebars
Dev4Press Updater
Display PHP Version
Document
Easy Updates Manager
Embed Any Document
Favicon by RealFaviconGenerator
GD bbPress Toolbox Pro
GD Forum Manager for bbPress
Image Upload for BBPress
Jetpack
JetPack Contact Form Success Message
Page Sidebar for Twenty Seventeen
PHP Compatibility Checker
Really Simple CAPTCHA
Really Simple SSL
Really Simple SSL pro
Stop Spammers
User Blocker
VaultPress
Widgets On Pages
Wordfence Security
WP Super Cache
WP-Members
WPForms Lite
Yoast Duplicate Post
Your question: – can you see what are the contents of the Internal Error messages? If yes they’re very useful for debugging in this ticket.
Answer: Today I only see one internal error message. It is related to a Text Widget. The title inside the text widget is "Want to post on a forum?" The text area in the widget says "You must be a registered user who is logged in." Here is the internal error message:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@… to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
Your question: – could you try and [use the Browser developer tools
https://wordpress.org/support/article/using-your-browser-to-diagnose-
javascript-errors/] to copy and paste here the errors there?
Answer: I will try to do this and put the results in another post.
Your question: - Did switching to the Classic Widget Editor and then deactivating cause more problems?
Answer: That is what I was wondering yesterday. Now I am thinking that switching back and forth is not causing a problem: Today I noticed that the variety of error messages seem to be related to which browser I am using. I get different error messages with each browser as shown below. (Note: It also seems that the browsers do not consistently show the same errors.) The following shows the errors for each browser (at least as they were when I tested each browser!):Today some of the widgets that were generating error messages yesterday appear to be okay today (example: Jetpack Google Translator). Also today I am seeing some brand new widgets showing up in addition to many from yesterday!
EDGE Browser: Error messages when using the Edge Browser:
The "recent-comments" block was affected by errors and may not function properly. Check the developer tools for more details.
The "recent-posts" block was affected by errors and may not function properly. Check the developer tools for more details.
The "categories" block was affected by errors and may not function properly. Check the developer tools for more details.
The "bbpmnewmessage" block was affected by errors and may not function properly. Check the developer tools for more details.
The "text" block was affected by errors and may not function properly. Check the developer tools for more details.
The "text" block was affected by errors and may not function properly. Check the developer tools for more details.
The "text" block was affected by errors and may not function properly. Check the developer tools for more details.
The "bbpmsearch" block was affected by errors and may not function properly. Check the developer tools for more details.
The "text" block was affected by errors and may not function properly. Check the developer tools for more details.
The "text" block was affected by errors and may not function properly. Check the developer tools for more details.
The "search" block was affected by errors and may not function properly. Check the developer tools for more details.
The "text" block was affected by errors and may not function properly. Check the developer tools for more details.
The "search" block was affected by errors and may not function properly. Check the developer tools for more details.
The GOOGLE Browser generates these error messages:
The "rss_links" block was affected by errors and may not function properly. Check the developer tools for more details.
The "search" block was affected by errors and may not function properly. Check the developer tools for more details.
The "text" block was affected by errors and may not function properly. Check the developer tools for more details.
The "recent-posts" block was affected by errors and may not function properly. Check the developer tools for more details.
The "d4p_bbw_topicsviews" block was affected by errors and may not function properly. Check the developer tools for more details.
The "widget_wpmemwidget" block was affected by errors and may not function properly. Check the developer tools for more details.
The "widget_wpmemwidget" block was affected by errors and may not function properly. Check the developer tools for more details.
The "categories" block was affected by errors and may not function properly. Check the developer tools for more details.
The "text" block was affected by errors and may not function properly. Check the developer tools for more details.
The "bbpmnewmessage" block was affected by errors and may not function properly. Check the developer tools for more details.
The "text" block was affected by errors and may not function properly. Check the developer tools for more details.
The "text" block was affected by errors and may not function properly. Check the developer tools for more details.
The "text" block was affected by errors and may not function properly. Check the developer tools for more details.
The "text" block was affected by errors and may not function properly. Check the developer tools for more details.
The "media_gallery" block was affected by errors and may not function properly. Check the developer tools for more details.
THE NEW ITERNET browser generates these errors:
The "d4p_bbw_search" block was affected by errors and may not function properly. Check the developer tools for more details.
The "pg_forums_widget" block was affected by errors and may not function properly. Check the developer tools for more details.
The "d4p_bbw_foruminfo" block was affected by errors and may not function properly. Check the developer tools for more details.
The "bbp_search_widget" block was affected by errors and may not function properly. Check the developer tools for more details.
The "text" block was affected by errors and may not function properly. Check the developer tools for more details.
The "text" block was affected by errors and may not function properly. Check the developer tools for more details.
The "text" block was affected by errors and may not function properly. Check the developer tools for more details.
The "text" block was affected by errors and may not function properly. Check the developer tools for more details.
The "nav_menu" block was affected by errors and may not function properly. Check the developer tools for more details.
The "text" block was affected by errors and may not function properly. Check the developer tools for more details.
The "bbpmmymessages" block was affected by errors and may not function properly. Check the developer tools for more details.
The "bbpmmychats" block was affected by errors and may not function properly. Check the developer tools for more details.
The "bbpmmycontacts" block was affected by errors and may not function properly. Check the developer tools for more details.
The "bbpmnewmessage" block was affected by errors and may not function properly. Check the developer tools for more details.
Here are some of the plugin widgets that seem to be involved:
JetPack blog subscriptions
JetPack blog stats
WP-Members (widget_wpmemwidget))
GD bbPress Toolbox Pro (d4p_bbw_search, d4p_bbw_topics views”)
Widgets on Pages
bbPress Messages
Also ... I don't understand this instruction related to when I give you feedback: "then remove the keyword below."
#4
@
3 years ago
As you asked, I ran Developer Tools on Edge and on Google browsers. I made screenshots of the errors generated (the Console tab). I have pasted these screenshots into two word documents. I also have individual screenshots as .png files. I can't figure out how to attach either of these, so could you please tell me what I need to do to provide you with the screenshots. Thanks.
#5
@
3 years ago
Just found this article when Googling our issue, which sounds identical to Jane's: in WP 5.8, Widgets have upgraded to a block editor version, which takes an extraordinarily long time to load, and then displays about two dozen errors (https://www.screencast.com/t/iinPQwaJUw). We're unable to edit any widgets. In Chrome, the Developer Console shows dozens of JS errors, related to widgets.php and widgets.min.js (https://www.screencast.com/t/OCEpwRAaEMv). Client reports widgets worked as expected last week.
#6
@
3 years ago
I have the same problems; I do appreciate if anybody can tell me what cause the problem and how can I solve it. first, I got the message that the "mailpoet_form" block was affected by errors…but then now I get the message form all kind of block such as "media_image" "recent_posts-widget" "top-posts" "block-widget" and…
I sort it by installing Classic Widgets and used that for the time being, hopefully they fix the problems in near future.
#7
follow-up:
↓ 8
@
3 years ago
Hi @tzohari @jamiepmg @janecarole ! Thank you for posting about the problems that you encountered. 1st I am sorry this is happening.
2nd, for all production websites if major problems appear related to blocks in widget areas the simplest way is to opt out with the available plugin Classic Widgets Editor.
In the meantime having these lists of active plugins that show errors is highly valuable for testing against them and spot if there is a common problem to resolve. Hopefully in a near minor release of WordPress we'd be able to address parts or all of the problems.
@janecarole to attach documents use the "Attach file" button near the top of this page, right under your issue's description. Make sure you are logged in 1st. And again, thank you for compiling the documents with the screenshots.
#8
in reply to:
↑ 7
;
follow-up:
↓ 9
@
3 years ago
I have uploaded 6 files. Sorry that the screenshots unnecessarily include my second monitor.
Jane
Replying to andraganescu:
Hi @tzohari @jamiepmg @janecarole ! Thank you for posting about the problems that you encountered. 1st I am sorry this is happening.
2nd, for all production websites if major problems appear related to blocks in widget areas the simplest way is to opt out with the available plugin Classic Widgets Editor.
In the meantime having these lists of active plugins that show errors is highly valuable for testing against them and spot if there is a common problem to resolve. Hopefully in a near minor release of WordPress we'd be able to address parts or all of the problems.
@janecarole to attach documents use the "Attach file" button near the top of this page, right under your issue's description. Make sure you are logged in 1st. And again, thank you for compiling the documents with the screenshots.
#9
in reply to:
↑ 8
@
3 years ago
@janecarole In your screenshots I can see you're getting HTTP 500 errors which indicate a server side issue. You should be able to find details about the error in the PHP error logs on your server. Could you find and attach it? Sometimes those logs are massive, only the most recent part would be needed. Sometimes there's PII and secrets in there, so give it a look over first to be safe.
I found this ticket because I was also getting this error in the GUI, however my HTTP error was 400. I've found the cause and workaround for that issue here #53965
#10
@
3 years ago
I, too, am having similar issues. Mine seemed to happen when I upgraded from WordPress 4.9.8 (yes, from 2018) to the current version. If I took screenshots, they'd be almost identical to the ones @jancarole took. I just downloaded the Classic Widget plugin and installed it. I am also having issues with FullCalendar. I don't write code, so I am struggling with this!
#11
@
3 years ago
Hi all,
We are experiencing the same issue on an e-commerce site and a services site. Firstly I thought it may be an issue updating to PHP.7.4 and I rolled it back, however, the same issue exists. I then updated to 7.4 again and disabled all plugins and still the. the same issue. I have had to restore the website to a previous date 3 times. I hope this gets fixed soon. Here is a list of plugins that may or may not help in your testing. Many thanks
Akismet
Classic dditor
Datafeedr API
Datafeedr product sets
Datafeedr WooCommerce importer
DX Delete attached media
Gravity forms
Health check troubleshooting
Homepage control
Jetpack
ManageWP - worker
My custom code
Quick page/redirect
Simple URL’s
STablePress
The SEO Framework
The SEO Framework - extension manager
WooCommerce
WooCommerce storefront plugins
WooSidebars
Wp Disable
WP Fastest Cache
WP-DB Manager
#12
@
3 years ago
Well, after A LOT of researching and testing, I have figured out that most of my issues are due to my theme: Blessing. I kind of inherited this site in June of this year. When I looked through the pages, plugins, etc., I realized WordPress hadn't been updated since 2018 - yes, 3 years ago. The person in charge of this was getting paid for "maintenance" up until the middle of 2020, and yet she did nothing. Now I am in charge of cleaning up her messes.
I figured all of this out by simply changing themes. Why didn't I do this first? I did, but everything stayed the same. So I did more research and found out I should add FancyBox for WordPress plugin as well as Classic Widgets plugin. I installed them, then changed themes, and...boom! Problem sorted. Maybe this will help one of you.
I am still having issues with the calendar, but hopefully, when we change themes, that will be sorted as well.
#13
@
3 years ago
- Focuses javascript added
I too can confirm the same issue is happening to me. I disabled all my plugins and the same error (403) occurred:
The "nav_menu" block was affected by errors and may not function properly. Check the developer tools for more details.
I see some are recommending to switch to classic widgets, but that defeats the whole purpose of having the nice streamlined blocks approach.
Note: I did find that when customizing the widgets via Customize, it seems to work better. However, it still pretty buggy.
Also - I tried upgrading to 5.8.1 but same issues.
#14
@
3 years ago
Just adding to the knowledge base ...
I have just upgraded from 5.7.3 to 5.8.1 on my test server and have the same issue with the widgets editor reporting errors with the calendar block. Mine was caused by MaxButtons 8.3 (an older version because of our ISP's old PHP version). Test server is on PHP7.3.
The javascript console was reporting 505 error on https://xxxxxxxxxx/wp-json/wp/v2/widget-types/calendar/encode?_locale=user
The Apache error log has PHP recoverable fatal error in wp-includes/general-templates.php on line 2202. The problem was the global $m - used at this point, conflicting with use of $m in the plugin which used it to add a do_action to an new instance of main the plugin class.
PHP Recoverable fatal error: Object of class MaxButtons\\maxButtonsPlugin could not be converted to string in /var/www/html/ecodev/wp-includes/general-template.php on line 2202,
maxButtons has fixed this in the later version (which I can't use because of PHP), but I suspect the use of something like $m as a global is always going to be a risk.
Anyone having this issue - if you are lucky and can get to the apache error log, it may help quickly pin down the problem.
For the maintainers: My problem is in the line creating an MD5 using the three globals $m, $monthnum and $year. The function is trying to concatenate the erroneous instance of the object in $m, with $monthnum and $year.
Looking at the rendering code in WPINC/blocks/calendar.php(16), it only declares globals for $monthnum and $year. I don't use calendar blocks and quick look didn't find anything that would create global $m in core files. Maybe the $m should be a '01' if creating an MD5 for the month, although $_GET\["m"\] is used in class-wp-list-table.php, so maybe that was the intent.
I did see quite a few calls to wp_reset_vars for 's' in files like wp-admin/includes/class-wp-links-list-table.php, in what looks like ajax callback handling. I wonder if translating some of these ajax query parameters to globals could be the source of many of the plugin and theme related errors.
Howdy @janecarole ! Thank you for opening this ticket this is very valuable feedback. From the ticket's content it looks like there may be some incompatible widget providing plugins active. It would be lovely if you could provide a bit more detail into the errors that you're experiencing:
Normally switching the Classic Widget Editor should NOT cause any problems no matter how many times it is switched on and off.
Thank you for supporting WordPress, looking forward for more information.