Hi. I noticed an interesting bug.
in version 1.9.6 the error still exists
Hi, sorry for the late reply!
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?
Best regards,
timmse
Do you have access to a play area? I have prepared an example.
You need to remove the Basic text widget, that is, just leave the Title widget
No, you would have to send me the login credentials and a link to this thread by e-mail to help@bricksbuilder.io.
I sent an email and also recorded a video
Hi @clickfusion63 ,
We are able to replicate the issue now and it will only occurs if your entire page only has 1 nested {echo:} dynamic tag in Heading element. You wouldn’t encounter this issue if you use any dynamic tag in any other element. In a live site, there should be more dynamic tags used in other elements like {post_id} etc.
However, we already recorded this into the bug tracker
Regards,
Jenn
Hi,
We’ve fixed this issue in Bricks 1.9.8 beta, now available as a manual download in your account (see changelog).
Please let us know if you are still experiencing issues.
As with any beta release, please do not use it on a production or live website. It is only meant for testing in a local or staging environment.
Hi,
thank you for the report. Does this happen for you also on a front end, or only in a builder?
Also, it’s the same if you change the inner dynamic tag, to {post_title}
for example?
Thanks,
M
Using {post_title}
in the echo function does work.
Using {query_results_count_filter:xzrqtu}
on its own also works.
Only when nesting {query_results_count_filter:xzrqtu}
in the echo function it breaks.
Hi,
ok, thank you for confirmation. As per Dynamic Data article, the echo tag does not support double quotes, and because query_results_count_filter
returns a custom element, that includes double quotes, it will not work.
Hope that clarifies the situation.
Best regards,
M
Thanks that clarifies, how would I get this to work? What I need is to parse the result from query_results_count_filter
to detremene the text output.
Could query_results_count
work for you? That one will return only the number, so I guess it should work.
And the output parses only on page load anyway?