Forum Replies Created
-
Posts
-
Ismael, thank you for pointing me to the Custom Layouts & Dynamic Content tutorial. VERY informative.
I have a follow-up question.
Which php file is being used when a blog post is being displayed? I thought it might have been “single.php,” but making a copy of this file and placing in the Child directory does not seem to be picked up when displaying a blog post.
Thanks!
ElliotHi Ismael,
Thanks for the detailed response and the link to the pertinent documentation.
I enabled debug mode via the Child Theme code and successfully saw the field with the short code. I made a sample edit, saved the page, re-opened the page, and the Advanced Layout Builder successfully displayed the new content. This is precisely the functionality I was looking for. Thank you.
I will also look carefully at the Custom Element Templates to see how I can take advantage of that feature, but I suspect it will be limited to elements that have already been defined on the website. Pasting in short code allows the ability to capture pages from other Enfold websites, such as installing one of the demos, capturing any desired page’s short code, then dropping the short code into another demo that has been subsequently installed.
Many thanks again.
Excellent! I knew I just didn’t understand how to set the parameters for the autoplay to work. Thanks for taking the time to show me. My site now autoplays the video as desired.
Hi Mike.
Thanks for taking the time to look into this.
Indeed, setting the Skin property to “no skin” fixed the problem. I don’t know if I ever would have tried this.
Yes, I had turned off the navigation PREV and NEXT buttons so the client wouldn’t see this issue. I’ve now turned them back on. Things are good.
Thanks again.
Hi Ismael.
Thanks for the response.
I didn’t realize this code was throwing a console error. I was following the Enfold doc to add custom code to the <head> section:
After a little bit of debugging, I determined that the code snippet provided in the documentation adds <script> and </script> commands before and after “Your code goes here.” that were causing the problem. I removed these, and the console error has been eliminated.
Thanks for alerting me to the issue. You may want to go back and change the code snippet on the doc page to remove the <script> and </script> commands,.
Thanks Rikard. Activating the Debug Field is very nice (and works!). I’ll deactivate this when the website has been completed and goes live so the client doesn’t accidentally edit this field, but during development, this is very nice to have to efficiently copy the shortcode from a page to create a derivative page. You can close this ticket.
