Gallery error

Hello @chatty-gardener. which editor are you using? Gutenberg?

Gutenberg

“TypeError: Cannot read properties of null (reading ‘isSynced’)” indicates that you are trying to access a property named “isSynced” of an object that is null. In simpler terms, you are trying to use something that doesn’t exist.

Plugin or Theme Conflict:

• Deactivate all plugins and switch to the default Twenty Twenty-Four theme to see if the error persists.?If it disappears,?then a plugin or theme conflict is likely the culprit.?Reactivate plugins one by one to identify the specific one causing the issue.
• Update all plugins and themes to ensure compatibility with the latest version of Gutenberg.

Custom Block Issue (sometimes):

• Check the code of your custom block and ensure you are properly initializing variables and handling null values.
• Make sure you are using the correct import statement for necessary components like?<code class=””>InnerBlocks.

Other Potential Causes:

• Data corruption: Try clearing your browser cache and cookies, or using a different browser.
• Javascript conflict: Check for any other scripts running on your page that might be interfering with Gutenberg.

I’ve tested the plugins and the theme and that makes no difference. Have also cleared the browser cache etc. All plugins and the theme are up to date. Afraid your other suggestions are beyond my computer skills.

I am having the exact same issue, just started yesterday.

The block editor recently started having another problem, too, where it can’t accept numbered bullet points. Loads of troubleshooting and many hours later, I discovered that tiny detail was preventing my drafts from saving or publishing…

To take above recommendations for this issue, I just opened the editor in a new browser and cleared cache, but the issue persists. (And if you don’t have any custom code blocks, that wouldn’t be an issue for your site either). Not sure when these issues will be resolved.

I’m glad it’s not just me – though that doesn’t help either of us.

I’m also having this error when trying to add a gallery. I don’t think I’ve changed anything since I made my last blog post a few days ago so I’m not sure why this would have just started from anything I did.

I think it’s working now, but I’m not sure exactly what I did / if it is a permanent fix. My steps were:

• (This didn’t seem to do anything, but maybe it did) – I reinstalled the newest version of WordPress (in updates –> reinstall 6.4.2)
• I still got the gallery error
• I created a new post
• I started a new gallery
• I re-uploaded my images directly into the gallery instead of into my media library
• It seemed to work, so I copied in all of my text from the post I was working on before.

Would love to know if there’s a permanent fix / what caused the issue in the first place.

I tried those steps and it’s worked! Thanks for the advice. Let’s hope that’s a permanent answer.

Thank you @todaywithjess!

I’ve been having the same issue for the past week or so it seems your workaround of uploading straight into the gallery UI instead of using images from your media library works.
I did not reinstall anything and did not start a new post. Just clicking that “upload” button instead of the “Media library” button was enough for it to work in my case.

Thanks for sharing – that fix worked for me, too (uploading images directly from my PC instead of from the media gallery). Glad we have this workaround but it would be nice to again have the ability to enter/modify image titles, alt text and captions in the gallery ahead of time and in bulk. Hopefully WordPress/block editor programmers are aware of this bug and can sort it out (was never a problem prior to us bringing this up).

@todaywithjess: That’s cool and all, but that’s a workaround, not a fix. I’d love for this to just work.

Just curious, but are any of you using Bluehost? I’ve seen this issue mentioned somewhere else and they also just happened to be on Bluehost. I wonder if it’s related or not.

@davince21 yes, I use Bluehost too (sorry to finally respond so late). It could possibly be related. I too hope for a true fix and not workaround.