As per the subject header, the following warning message is shown
Undefined variable $image_tag in
...[extracted ] /wp-content/themes/bricks/includes/elements/image.php
on line 577
Appears to be a bug?
As per the subject header, the following warning message is shown
Undefined variable $image_tag in
...[extracted ] /wp-content/themes/bricks/includes/elements/image.php
on line 577
Appears to be a bug?
Hi Noel,
Thanks so much for your report!
Unfortunately, I cannot reproduce the issue. Would you be so kind as to provide a screencast using https://jam.dev showing and explaining what’s happening and what your setup looks like?
Best regards,
timmse
Sure, will do.
If I examine the code at image.php at line 577
I notice that $image_tag is not set, as per attached.
I have a attached a link to a screen recording of the issues.
Apologies, I should have stated that this throws up a warning, not an error.
Just to add my setup is:
Bricks,
Meta Box for custom fields
Hi Noel,
What field type are you using for the “mask field”, and what kind of file do you choose?
Hi @timmse Stefan
It’s a custom mask, so using PNG file with transparency which is being referenced by the custom field.
Custom field is a meta box image field, similar to the actual image custom field
I still can’t replicate the issue. Please send temporary login credentials and a link to this thread to help@bricksbuilder.io using the email address you used during the purchase.
@timmse have sent the details to a live server.
Any issues, please let me know
Hi @noelmcg
Thank you so much for the login details.
I am able to replicate the issue when you use the dynamic tag inside a query loop.
Already recorded this into the bug tracker.
Regards,
Jenn
That’s great Jen, thank you, appreciate your help.
If it is possible to get a quick fix (eg manually edit child theme code etc…) please let me know.
Hi Noel,
We fixed this issue in Bricks 2.0 beta, which is now available in your account.
Changelog: Bricks 2.0-beta Changelog – Bricks
Please let us know if you are still experiencing issues.
As with any pre-stable release, please do not use it on a production/live website. It is only meant for testing in a local or staging environment.