reasondr

Hi @ryankienstra,

Another block has recently disappeared from the front-end of our site. Prior to addressing this latest occurrence, I’ve prepared a staging environment, where I deactivated all plugins except for Genesis Blocks Pro and Genesis Custom Blocks Pro. Additionally, I’ve removed all custom PHP and JavaScript code to try and rule out conflicts.

I can see that the missing block is still listed in the wp_posts table, confirming its existence. However, I can’t find any related metadata in the wp_postmeta table. It appears that none of the Genesis Custom Blocks store metadata in this table.

Where does Genesis Custom Blocks stores its metadata or any additional data related to the blocks? Understanding this could be really helpful in diagnosing the issue. Any guidance or further steps you could suggest for debugging this problem would be greatly appreciated.

Many thanks.

Hi @ryankienstra

Apologies for the delay in getting back to. The dissapearing blocks seems to have calmed down a little but I’m still no closer to discovering the root cause. I’ll continue to document all activity with regards to updates and rebuilding blocks etc and soon as I have any news I’ll report back.

The good news is none of the blocks I’ve rebuilt have dissapeared as yet.

Again, thanks for the support.

Hi again @ryankienstra,

I’ve lost a whole bunch of blocks today.
On the effected pages in admin, in console I have run
gcbBlocks['genesis-custom-blocks/block-name'] and it returns undefined on all blocks in question.

I also ran console.log(gcbBlocks); which returns of all my custom blocks with the exception of those that are missing / effected.

What do you think?

Thanks.

Hi @ryankienstra,

Thanks for confirming those warnings and errors are unrelated.

As soon as another block dissapears I’ll run gcbBlocks['genesis-custom-blocks/name'] and report back.

Many thanks for your help!

Hi @ryankienstra,

Thanks for getting back to me. I understand the importance of diagnosing the issue with as much detail as possible. I’ll make sure to run gcbBlocks['genesis-custom-blocks/name'] on a page where a block is currently broken at the next opportunity. Given the nature of my production site, I’ve been applying fixes immediately as issues arise, but I will report back with the results of this command as soon as another block issue occurs.

Additionally, I’ve noticed several JavaScript errors in the WordPress admin when editing Genesis Custom Blocks Pro blocks. Here are the types of errors and warnings I’ve encountered:

1. Uncaught ReferenceError: jQuery is not defined – This error appears multiple times with various post edit URLs.
2. Warning about a component changing an uncontrolled input to be controlled.
3. Warning: ReactDOM.render is no longer supported in React 18 – could indicate some of the plugin’s code might need updating to be fully compatible with React 18?

Could these errors and warnings be related to the issue of blocks randomly disappearing from the front end? It seems they might indicate broader compatibility issues or conflicts within the WordPress admin, potentially affecting how blocks are managed and rendered.

I would appreciate any insights or guidance on whether these JavaScript and React warnings could be contributing to the problem and how to address them.

Many thanks for your help.

Oh yes, multiple breakpoints would make this plugin totaly outstanding. Can’t wait to see this feature added : )