Enable/disable Advanced Custom Fields
Hi there!
As no one from the Brizy team seems to be interested in helping me with this annoying problem I’m going to ask the same question over and over again …
I need to get rid of the SoundCloud placeholder when there is no SoundCloud link in an Advanced Custom Field. As disabling fields is standard in most of the other page builders it would be great if you could tell me how I can solve this in Brizy Pro.
A similar topic occurred two years ago — hiding dynamic image placeholders.
And you still don’t have a solution for this, do you?!
Best regards.
-
Hi Nelea!
I had to set up the posts again so the errors are currently not visible. But if you check this link you will see that something is going wrong …
I assume that it is the ticket field which is causing chaos.
Kind regards.0 -
Hi KC George!
Is there any chance you could please check why the way you’ve suggested is not working the way it should? When doing so please use a post which isn’t currently visible on the homepage. Thank you!0 -
Hi Tilman,
The Ticket IDs that you are using are returning an error "Unknown ticket ID". I needed to find out how you can solve this issue.
Is it possible to have a zoom call? We can attempt to fix everything during the call
0 -
Hi KC George!
It’ s a bit more complex and not only one ticket ID is in use. That’s why there is a content element in there and not a shortcode element …
I’ve send you an email with all the details. It would be great if you could check it.
Kind regards.0 -
Hi Tilman,
From your WordPress Dashboard I had noticed that- You are pasting the event shortcode into the content area of your nw-events in Gutenberg
- In your Brizy Template, you are displaying the event details using the Brizy Content Element
I could not test this feature as I was getting the "Unknown ticket ID" error. I was seeing this error in all nw-events including the ones I was not working on. If you can help fix this error. then I can set up a few nw-events for you (following the new approach)0 -
Hi KC George!
Thanks for testing. Filling in everything by hand into a Brizy layout is quite circumstantial and not the way the page should work. That’s why I am using ACF and a template.
For me the main question is: what is causing the error when using the content element?
Kind regards0 -
Hi Tilman,
In the approach you were following earlier, you were adding nw-events content in Gutenberg and bringing it to Brizy using a blog post template. In the revised approach I am suggesting, we override the Brizy Template and add the page content directly in Brizy (instead of adding it first in Gutenberg and bringing it to Brizy later). In this approach, content that you normally add in Gutenberg must be added in Brizy. You were getting the error because you content was in Gutenberg. If your content is in Brizy, you would not get the error.
Instead of adding the even code in Gutenberg, I am suggesting that you add it in Brizy. By doing this, you are not moving a dynamic element to static. You are moving a static element from Gutenberg to Brizy.
0 -
Ok, made it like you’ve suggested.
Thank you, KC George!0
Please sign in to leave a comment.
Comments
38 comments