tisnickske
Forum Replies Created
-
Hi Micdt, see my answer in post https://ww.wp.xz.cn/support/topic/post-masonry-block-not-working-after-update-to-2-0-2/#post-15936456
I will copy the main answer here:
I resolved the issue myself, I guess. Looking at the error, it striked me that the path to the ‘missing’ resource containes a tilde (~) (../wp-content/plugins/ultimate-addons-for-gutenberg/dist/vendors~chunks/post-masonry/react-masonry-component.js). As I do have some programming experience, I thought that this might be the problem. So in the exact same location I added a folder ‘vendors-chunks’ (- instead of ~) and copied the contents of the ‘vendors~chunks’ folder to this folder. I copied the block.js file that calls the file ‘react-masonry-component.js’ in the ‘vendors~chunks’ folder as I could deduce from the second error (as a backup) and I changed the tildes (~) in the block.js file to ‘-‘ (4 cases of vendors~chunks changed to vendors-chunks). I cleared the cache and reloaded the editor page with the Post Masonry block… and all of a sudden it appears! 🙂
This was for version 2.0.2. Hoped it would have been implemented by now, however it is not, so the problems with this Post Masonry block (and others, I guess) reoccurs. I already made a ticket in which I posted the answer to the support team as well. Thumbs up that they will actually do something with my suggestion…Hello Judith,
Actually, the issue isn’t resolved, because in version 2.0.4 it seems the tilde (~) is still present in the folder I mention in my previous reply. I was hoping my solution would have been implemented in the subsequent versions of the plugin (after 2.0.2) by you guys so that it becomes persistent (at least for that part of the plugin…). However, it is not?!? Hopefully in version 2.0.5…
I resolved the issue myself, I guess. Looking at the error, it striked me that the path to the ‘missing’ resource containes a tilde (~) (../wp-content/plugins/ultimate-addons-for-gutenberg/dist/vendors~chunks/post-masonry/react-masonry-component.js). As I do have some programming experience, I thought that this might be the problem. So in the exact same location I added a folder ‘vendors-chunks’ (- instead of ~) and copied the contents of the ‘vendors~chunks’ folder to this folder. I copied the block.js file that calls the file ‘react-masonry-component.js’ in the ‘vendors~chunks’ folder as I could deduce from the second error (as a backup) and I changed the tildes (~) in the block.js file to ‘-‘ (4 cases of vendors~chunks changed to vendors-chunks). I cleared the cache and reloaded the editor page with the Post Masonry block… and all of a sudden it appears! 🙂
So what do I get in return now, solving the issue for you guys/girls 😉Hi @rajkiranb,
I did a “Empty cache and Hard reload” in the editor as you suggested, but the problem persist. I deactivated all plug-ins (except Spectra) and changed to the Twenty-twenty-two theme… problem persists. Searched Google, found this item (https://ww.wp.xz.cn/support/topic/this-block-has-encountered-an-error-and-cannot-be-previewed-20/) and this got me to look in the console (Chrome). I first cleared the console and than after I created a new Post Masonry blok, it displays some errors with react/js:
Failed to load resource: ../wp-content/plugins/ultimate-addons-for-gutenberg/dist/vendors~chunks/post-masonry/react-masonry-component.js
andChunkLoadError: Loading chunk 116 failed. (error: ../wp-content/plugins/ultimate-addons-for-gutenberg/dist/vendors~chunks/post-masonry/react-masonry-component.js) at l.e (blocks.js?ver=775908cc966c69a576f355a046fdb587:1:5598) at render.js:1:11517 at f (react.min.js?ver=17.0.1:9:2372) at os (react-dom.min.js?ver=17.0.1:9:111713) at Ur (react-dom.min.js?ver=17.0.1:9:77643) at Ir (react-dom.min.js?ver=17.0.1:9:77571) at Dr (react-dom.min.js?ver=17.0.1:9:77434) at Pr (react-dom.min.js?ver=17.0.1:9:74429) at react-dom.min.js?ver=17.0.1:9:30173 at unstable_runWithPriority (react.min.js?ver=17.0.1:9:7431) rr @ react-dom.min.js?ver=17.0.1:9I also opened a support ticket.
It seems in the meantime that the Post Masonry block is again automagically displaying in the front end (maybe the cache was killing me, although I did purge all cashes between all attempts to solve the issue). However, in the backend (Gutenberg Editor) it is still not working. Still shows the message ‘this block has encountered an error and cannot be previewed’, so I can’t change any options. Also, trying to add a new Post Masonry block from scratch (which is still possible, although deprecated) gives the same message. Duplicating via de List View > same result…
I just saw the Post Masonry block is deprecated 🙁 Is there an alternative block from Spectra that I can use? Not the Masonry block I guess as this is for images not posts. Post Grid? But will this not result in neat rows, with empty spaces when items have different heights. That was the reason for me to use the Post Masonry. Why deprecate it?
I forgot to mention: WordPress version is 6.0.1. Plugin version is 2.1.6.
Forum: Plugins
In reply to: [Companion Auto Update] CAU 3.7.1 Fatal ErrorI also get the same error message with CAU v3.7.1 installed: ‘There has been a critical error on your website. Please check your site admin email inbox for instructions.’
And yes, the dashboard seems broken by not showing all boxes.
When I use the WP plugin Rollback to install the previous version (v3.7.0) of CAU, everything is back to normal.WordPress v5.5.3