SOLVED: After the update, the editor stopped displaying the result of the Code widget

I reproduced the problem on the test domain. The site has a clean version of WordPress version 6.2 and a Bricks theme v. 1.7 - and there is nothing else. On the website using the Code widget, I use the code, and its result is visible in the editor.

After updating the theme to version 1.7.1, the result of the code is not visible in the editor:

Everything is displayed well in the frontend.

The code in the screenshot that I use:

<?php echo get_the_excerpt(); ?>

and

<?php
$category = get_the_category();
if ( ! empty( $category ) ) {
    $category_name = $category[0]->name;
    $category_link = get_category_link( $category[0]->term_id );
    echo 'Category: <a href="' . esc_url( $category_link ) . '" rel="tag">' . esc_html( $category_name ) . '</a>';
}
?>

But the result of this code is displayed in the Bricks editor:

<?php echo "Hello"; ?>

Some kind of magic))

Now I’m working with ACF, with a repeater. The situation is similar. In the Bricks 1.7.1 theme, the result is not displayed in the editor, but everything works in the 1.7 theme. From the client’s side, everything works well in both cases.

Hi Sergei,
Welcome to the forum, and thanks so much for your report!

Where exactly did you place the code element? In a template, a single post, a page, or where exactly?

Would you be so kind as to send temporary login credentials and a link to this thread to help@bricksbuilder.io using the email address you used during the purchase?

Best regards,
timmse

Hello, Stefan! Thanks for your attention! I found the problem when editing a template for a blog entry. I sent accesses to the email address you specified.

Hi Sergei,

Thanks for the login details.
Already identified the problem and it will be fixed in the next release.
Currently, the get_the_ID(), get_the_xxx is unable to use inside builder even if you have chosen the post inside Populate Content section.

Regards,
Jenn

Thanks for the answer! We are waiting for the update!

Hi Sergei,
We’ve fixed this bug in Bricks 1.7.2, now available as a one-click update in your WordPress Dashboard.

Please let us know if you are still experiencing issues.

Best regards,
timmse

1 Like