A couple of questions:
- Can you please provide me with an error log from your console? To get this, open the browser’s Developer Tools from page that you are editing. In Chrome on Windows, this would be F12 (also on a Mac), or Ctrl + Shift + I. Click on the tab that says “Console”. As you proceed through the clicks in the Wizard and get to the last step, let me know if you are seeing any errors in the “Console” when you try to insert the gallery.
- Switch from the “Visual” mode of the Classic Editor to the “Code” mode and reload the page. Then try inserting the gallery. Does this work?
Can you also please let me know what plugins are active on your site?
Option 2 does not work, unfortunately. This is the error I’m getting in the console when I hit Insert: Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
Active Plug-Ins: AdRotate Professional, Advanced Custom Fields, Advanced Database Cleaner, Ally – Web Accessibility & Usability, Classic Editor, Custom Post Type UI, Dynamic Visibility for Elementor, DynamicConditions, Elementor, Elementor Pro, Hide Admin Notices, JetBlog For Elementor, JetEngine, Members, Ninja Popups, Photonic, Prime Slider, Prime Slider Pro, Redirection, Security Optimizer, Speed Optimizer, White Label CMS, WordPress Backup & Security Plugin – BlogVault, Wp-Insert, WP-Memory-Usage, Yoast SEO
Thanks for this information. A few more questions:
- Can you please provide me with a full stack trace (you can expand on the error message in the console). I want to see which file and which call are triggering this – Chrome should give y ou the file name and other information.
- If you pick an existing gallery, are you able to edit that successfully?
- If you switch to Gutenberg / the Block Editor, are you able to create a new gallery?
Another test: can you please try this in a different browser, or in the Incognito Mode in Chrome? From what I could see, this might happen due to a bug in some Chrome extensions (unrelated to WordPress). Do you still get the error in another browser? Do you have some optimization plugins installed for Chrome?
