IMPLEMENTED: Add Fallback for dynamic data

Feature Requests / Improvements
21

Yes sorry, I had forgotten about the security period you took for that when I made my recent comment, my apologies. Of course we appreciate all the work you did during that stressful period of time. :relieved:

With that said, if I understand the timeline correctly, there was still nearly two weeks of the feature request idea sitting there pending approval before the security incident came to your attention. My two cents is that it should still not take that long to simply approve an idea for voting on (especially since that isn’t a commitment to doing the work, just for collecting interest details with votes). Ideally the approval time for that should be days at most, not weeks. And ideally it’d be no wait at all if we used the forum’s software for voting on ideas instead. I hope that’s taken into consideration again because there wasn’t much improvement at all since the original ideation process post unfortunately. :pensive:

Again we all very much appreciate all the work being done, this product is fantastic! But that doesn’t mean there isn’t room for improvement in processes like ideation. :relieved:

22

any news on this? we need also for media (video is not play due to low power, set a fallback image…)

23

Hi guys,

We’ve added this feature in Bricks 1.10 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/live website. It is only meant for testing in a local or staging environment.

Best regards,
M

4 Likes
24

I love that dynamic fallback has been added. How can I add dynamic data to the fallback? eg

{acf_leader_title @fallback:‘See us in {acf_location}’ }

This doesn’t seem to work as it outputs the string "{acf_leader_title @fallback:‘See us in {acf_location}’ } ".

I currently have two headings set with conditions to make this work, which gets a bit confusing.

1 Like
25

Check the syntax, there must be a space after the colon

{acf_leader_title @fallback: ‘See us in {acf_location}’ }

26

Cheers for that. I added the space, and it works if I add :plain eg …{acf_location:plain}…

acf_location is a category being pulled, so it tries to add the syntax if not using :plain. If left as {acf_location} if still fails even with the space added.

27

I’ve tested and is not working in this case:
I’ve a text field, field text is empty so I want to show a fallback → result is that dynamic data stop working

28

I just noticed that the @fallback interprets ‘0’ as empty. My use case requires the @fallback to output '1' when the field is truly empty, but the field can have values from '0' to '4'. Currently, when the field value is '0', the fallback of '1' is being output instead of the desired '0'. Is there a workaround for this behavior?

@thomas @Matej

29

Hi @emmanuelson,

yep, I can replicate the issue with dynamic tag that returns 0. {acf_number @fallback:'NO DATA'} will output “NO DATA”, even though acf_number returns “0”.

I’ll open an internal bug report about this.
Thanks!

2 Likes