WIP: Invalid edit button in WP Editor

Browser: Chrome, Safari
OS: macOS

In WP editor, there’s a button “Edit with Bricks”. This link is “/wp-admin/post.php?post=2925&action=edit#” and gets redirected to “/wp-admin/undefined”.

The other “Edit with Bricks” button at the top calls “/{page name}/?bricks=run” and is working fine.

Hi Matthias,
Thanks so much for your report!

I can replicate the problem and have added it to the internal bug tracker. We will update this thread as soon as it is fixed.

Best regards,
timmse

Thanks!
By the way, this sample is a brand new page, no content in Gutenberg or Bricks.
Why does it say “This page is built with Bricks”?

No idea, it’s not like that for me:

Please send temporary login credentials and a link to this thread to help@bricksbuilder.io using the email address you used during the purchase.

Stefan, this test site is on my local server. I would need to open it up for external traffic to allow you accessing it. Please understand that I’m not keen to do so.
However, I started a little bit of investigation myself.

For me, the “built with Bricks” block is already shown when I just click “New Page”, even before I did enter a title or save the page.

I looked for this message in the Bricks code. In i18n.php, function get_admin_i18n, it’s assigned to bricksActiveMessage:

and then used in gutenberg.js, function handleEmptyContentCore, to create that message block in Gutenberg:

Maybe one of the conditions of the enclosing if-statement applies to my setup, but not to yours? I didn’t dig deeper here.

And here we also see the probable cause for the non-working Edit button: It’s set to ‘#’ if no builderEditLink is defined.

Addendum:
Tested on another (local) staging, also with Bricks 2.1.2. The same message box appears when creating a new page.

Out of interest, I did a quick debug of this JavaScript function, especially the if-statement’s criteria which fire the creation of the message box:

  • rootContainer is defined.
  • selector .bricks-block-editor-notice-wrapper doesn’t (yet) exist.
  • window.bricksData.renderWithBricks is 1
  • window.useDefaultEditor is undefined

I hope this helps with your investigation.

Could it be that you have created a “general” page template, i.e., a template that is applied to all pages? If so, that could be the reason why the message is displayed. However, in that case, the text would be somewhat misleading—it would be better to say something like, “This page uses a Bricks template…” or something similar.

Yes, I have a page template – for every site I manage.
And yes, if that is the cause for the message box to appear, the wording is indeed kinda misleading.

So we can rephrase this ticket to two issues:

  1. Edit button not working
  2. Unfortunate wording in the message

Thank you for your analysis.

Okay, thanks for confirming!
#1 is definitely a bug.
#2 Let’s see. I added a note to the task :v:

1 Like

In my case, it’s not about a general template. Please check the video: Posts ‹ Antz Racing — WordPress - 22 October 2025

I unchecked “post”, and the module is removed.

Sorry, but I don’t understand what you’re getting at with your video. If the post type can no longer be edited with Bricks, it makes sense that the “Edit with Bricks” block disappears, no?