ov3rfly
Forum Replies Created
-
Maybe you ran into similar issue as explained here and reported at GitHub long ago.
You did not ask anything, why should I post more? The issue is clearly described and unresolved until now.
Feel free to mark the issue as resolved after the plugin works again with WP 6.3 or after the the misleading compatibility tag in plugin description is updated.
@saudpds In your description it says:
- No cache plugins are active.
But in your System Info it says:
== Must-Use Plugins ==
Endurance Page Cache
Version: 2.3.0
Author: Mike HansenThat’s an always active cache plugin which was probably installed by your hosting company.
Your issue sounds like a cache problem so maybe removing that plugin will help. There should be an option to disable it (set to Level 0) in your WordPress General Settings. You can also remove the plugin file in wp-content/mu-plugins/ via FTP.
From what I can see, this problem was initially reported at GitHub in October 2025, an own issue for it was opened in November 2025, your developers have set it to status/evaluating on 4th of December 2025, about half a year ago. All replies since then were different users who had the same problem, and nothing happened. Let’s hope, this very easy to track down issue will be finally fixed now, it took me 2 minutes to find the real reason…
@infinitee You are currently using Elementor 4.1.0-dev1 beta version on your website. Would recommend to roll back to a stable version of Elementor which would be 4.9 at the moment.
Your current code in toggle-icon.js:
document.body.querySelector( '[aria-label="Checklist"]' ).parentElement.style.display = shouldShow ...Browser DOM in our installation:
Note the aria label is translated to other languages in DOM.
Learnings:
- Use a class name or similar to find an element.
- Check if element is found before further use.
- Test your software also in localized environments.
Your suggestions did not help, error still occurs.
Looks like a missing result validation in your code when that element is not returned as expected.
Seems also others have the same or similar problem, please add a proper check there in next relase.
@ricav So Elementor a) promotes a plugin which had a very serious “Unauthenticated SQL Injection via URL Path” vulnerability in all versions up to, and including, 4.0.3, and b) does not provide a “built-in option to remove these promotional widgets/ads from the dashboard” against WordPress Plugin Guidelines “11. Plugins should not hijack the admin dashboard“. Would suggest to reconsider this intrusive behaviour.
The described “Accessibility check” promotion widget is added to WP Dashboard by current versions of Elementor plugin, not by some other “Ally Accessibility plugin” in WP Dashboard → Plugins.
@finntown You can use e.g. this code snippet:
add_action( 'wp_dashboard_setup', function() {
remove_meta_box(
'e-dashboard-ally',
'dashboard',
'column3'
);
}, 100 );Tested with WordPress 6.9.4 and Elementor 3.35.7
See also WordPress Detailed Plugin Guidelines:
… Site wide notices or embedded dashboard widgets must be dismissible or self-dismiss when resolved. …
11. Plugins should not hijack the admin dashboard.@doni3232 A completely fresh WordPress 6.9.1 & Hello Elementor 3.4.6 & Elementor 3.35.6 installation just tested in WordPress Playground adds a Hello Theme #XX draft page and as soon as you put this page in trash and click somewhere else in admin, it creates one new draft page with higher XX id. A little bit different as your infinite case but still it should not add another one after manual deletion. Seems some onboarding process goes wrong.
Would suggest to remove the WP-Optimize plugin if that fixes the issue. There are also other reports about incompatibility of this plugin with Elementor-Caching.
Your nginx server also seems to have some additional caching enabled from looking at the HTTP headers:
x-microcache: TrueSo your general page speed should be ok also without WordPress plugins.
@mochilaalparaiso To track down the issue, you can disable WP-Optimize plugin and/or disable all Elementor Caching.
The reason for this error is a broken Elementor Accessibility promotion which was added without mentioning in changelog in 3.35.2, see also e.g. here.
The error occurs if somebody opens the WordPress main admin dashboard.
You can address the issue by either downgrading Elementor to 3.35.1 or updating to 3.35.3 or newer.
Forum: Plugins
In reply to: [WP YouTube Lyte] Error 153@sonnenschauer Thanks for the referrer hint. Had same Error 153 on a client website with WP YouTube Lyte embeds. Found that Security Headers plugin is used there and
Referrer Policyheader was set tosame-origin. Changed it tostrict-origin-when-cross-originand embeds plays fine again, no more Error 153.