WIP: Critical error when opening some frontend-created CPT posts

Browser: Chrome 110
OS: macOS / Windows / Linux / etc.
URL: Lascia la tua Recensione • Kukushka Tours

Hi everyone,
I’m experiencing an issue on a new WordPress website built with Bricks Builder for Kukushka Tours and I’m hoping someone here might have faced something similar.

On the page “Lascia una recensione”, I created a frontend form that allows users to submit a new post assigned to a custom post type called “recensioni”. Each field in the form is mapped to an ACF field associated with that CPT (the name as post title, a text field, a textarea and a number for the year).

Everything appears to be configured correctly, and some reviews are created and displayed without any problem both on frontend and backend. However, some other reviews cause a “critical error” when I try to open them from the backend editor.

Here’s the strange part:

  • The post is created in the database
  • I can see it listed under the “Recensioni” CPT
  • But when I click “Edit” in the backend, WordPress throws a critical error screen.
  • I don’t receive any debug email from WordPress, so I have no details on the underlying error.

I’ve checked:

  • ACF field group settings
  • Bricks form “Create Post” settings
  • Different test submissions (with short text, long text, only required fields, etc.)

Yet the issue remains inconsistent: some posts open fine, others break the backend.

Has anyone encountered something similar when creating CPT posts from a Bricks frontend form mapped to ACF fields?

Any tips on what might be causing the backend crash, or how to debug it properly, would be extremely appreciated.

Thanks in advance!

Hi @alessiorealini,

I can’t replicate the issue and it never happened to me :thinking:. We will have to somehow debug this.

Can you make sure that you have debugging enabled in your wp config? Is there at least some console logs?

Best regards,
Matej

Hey Matej,

I activated now the debugging in wp config. Here the screenshot of the console log. If you wish, I can send you access to the website, let me know.

Thanks

Hi @alessiorealini,

the screenshot you sent does not help identify the issue, so it would be best if you could send temporary login credentials to your website and a link to this topic to help@bricksbuilder.io using the email address you used during the purchase, so we can take a look?

In the email, please also include the debug.log file, or it’s relevant content.

Thank you.
Matej

Hi @alessiorealini,

thank you for the email and access. Like mentioned over the email, we were able to replicate the issue, and I’ve added it to our internal bug tracker.

We will update this topic once we release a fix for it.

Thank you,
Matej

1 Like