This block has encountered an error and cannot be previewed
-
Hi,
just installed the plugin and when I try to create a ticket block I have this error:
This block has encountered an error and cannot be previewed.
I’m also unable to find the ticket settings inside the page. I set in the settings the tickets to appear in my custom post type, but I’m unable to see them
-
If you cannot see the tickets area on a custom post type, have you made sure to set up a payment gateway as well? Even if you hadn’t it should still allow you to add an RSVP. I would also check the WordPress screen settings to make sure that is enabled.
The other thing I would ask is, are you using the block editor or the classic editor? And are you using any kind of page builder?
I’m trying to get some more info on where exactly that block error might be coming from, but usually this can happen when say the block editor is fighting with the classic editor, sometimes because of a page builder.
If you let me know more about your setup that would be really helpful!
Hi Truman,
thanks for the quick answer.
Here are all the details:
-I setup stripe
-RSVP block not working as well
-I’m not using any page builder, only Gutenberg with Gutenberg plugin
my theme is generatepressMy php version is 8.2.2. Latest WP version
Here is a list of plugins used:
Accordion Blocks
Advanced Custom Fields PRO
AMP
AntiSpam for Contact Form 7
BookingPress - Multi-Language Addon
BookingPress - Stripe Payment Gateway Addon
BookingPress Appointment Booking
BookingPress Pro - Appointment Booking plugin
CF7 Visited Pages URL Tracking
Contact Form 7
Cookie Notice & Compliance for GDPR / CCPA
Event Tickets
Featured Images in RSS for Mailchimp & More
FileBird Pro
Flamingo
Geolocation IP Detection
GP Premium
GTM4WP - A Google Tag Manager (GTM) plugin for WordPress
Gutenberg
Lead info with country for Contact Form 7
LiteSpeed Cache
Loco Translate
MainWP Child
ManageWP - Worker
picu
picu Pro
Polylang Pro
Redirection
Remove CPT base
Safe SVG
Schema Pro
Wordfence Security
WP Mail SMTP
Yoast Duplicate Post
Yoast SEOThanks for sharing this info with me that is very helpful! So this issue is not something I can currently recreate with just Event Tickets. In the past we have seen that same error occur because of corrupted data, and this can happen sometimes from switch editors. However just to check, you have only been using the Gutenberg editor? And never turned the classic editor on?
In this case the next step would be to have you perform a conflict test on this site: Testing Conflicts With Themes and Other Plugins | Knowledgebase I know recently I have seen some people have issues with GeneratePress theme, but it’s hard to say exactly.
The other thing I wanted to ask about is the Custom post Type, which custom post type is that exactly you are trying to attach this to? I may try to test that out on one of my sites, but as far as I have seen these should be working too. Can you let me know if that conflict test turns up anything?
Hi Truman,
since I remember I always used only Gutenberg editor in this website..but it’s hard to say, the business is quite old and I don’t remember sincerely if I switched from classic to Gutenberg…
I think we can exclude the CPT to be the issue, because I tried also for a standard page and I have the same error…
I will try disabling the plugins one by one to see if there is any conflict going on…
ok…definitely this is one of that software things that will remain a mistery…
I disabled and re-enabled some plugins and now it is appearing correctly in the backend.
But it seems is still not working fine..every time I refresh the page (obviously the draft is saved) I lose all the ticket configuration…
Hey @oceandigitals
When you refresh the page, is this still after you have saved it? Or are you referring to refreshing the page on the front end? Have you tried to just disable everything else except Event Tickets, the custom post type plugin and Gutenberg? Once you do that I would recommend creating a totally new post with new tickets, and I might even test with Gutenberg disabled in the classic editor if you can.
In the backend. I create it, save the draft and if refreshed I lose everything, the blocks shows up with no configuration.
Ok I will try to disable everything…
Alright thank you for the clarification. The other things I would check: Does creating a page and trying to add any shortcodes or something else to it create the same issue?
Are you able to add tickets to just a Page or a Post and not just the Custom Post Type?
If you use the Classic Editor does it work?
Please let us know once you are able to test that further.I hope everything is going smoothly for you. I just wanted to touch base and inquire if you had the opportunity to review Truman’s previous response as it has been some time since we last heard from you.
Hi Darian,
thanks for the follow up. Sorry, I still didn’t got a chance. Since the website is live with campaigns active I’m thinking about cloning it somewhere to make the test
That’s totally understandable, we have some easy options for setting up staging sites in this article if you need some other options. Please just let us know when you get a chance to clone that and then run a conflict test.
Hello,
I finally found the conflict, is the plugin: Remove CPT base
Hey there @oceandigitals
Thanks for getting back to us and letting us know! I took a look at the page for that Plugin, it has a description but I’m not entirely sure what exactly it is supposed to do. I would go ahead and reach out to those developers to see if they can provide a reason or workaround as why it would break the block editor.
It is supposed to remove the base slug from custom post types posts.
something like from: domain.com/post-slug/post-name
to: domain.com/post-name
I understand, however that Post type slug is pretty important for our Events, especially since our plugins rely on “pretty permalinks” across the board. Is there any way to exclude events from that plugin maybe?
Otherwise you may want to disable it, or reach out to those Developers to see if they can make an except for our post types.
- You must be logged in to reply to this topic.