Forum Replies Created
-
Posts
-
@Günter Wonderful, thank you!
@edolmen Yes, in the child theme, child_folder/shortcodes/section/section.phpYou’ll want to have the shortcodes fitler setup in your child theme’s function.php as well, I believe.
add_filter('avia_load_shortcodes', 'avia_include_shortcode_template', 15, 1); function avia_include_shortcode_template($paths) { $template_url = get_stylesheet_directory(); array_unshift($paths, $template_url.'/shortcodes/'); return $paths; }Any direction on how I would make this change? I’ve tried modifying where the thumb id is defined directly in av-helper-masonry.php with the same results.
I’ve been waiting for the latest Enfold release to see this fix, and now that it’s arrived, this is still broken without that extra plugin! Was the fix actually included?
I am a freelancer people hire ;) Can you give me a hint as to where the problem is?
I am wondering how the demo was put together: https://kriesi.at/themes/enfold-2017/blog/
On the demo site, is that page defined as the Blog Posts page?
I have lots of clients who always use the demos to explain what they want but then there’s no explanation of how it was put together.It doesn’t error doing it this way, but now it’s not seen as the blog post page (with body classes and whatever other benefits come from that)? Is it not set as the blog post page in the Enfold Demo Theme example?
Thank you – that worked.
The solution was to add this to functions.phpadd_theme_support( 'deactivate_tribe_events_calendar' );Thank you – this worked for me –
I went to Performance > “Disabling of template builder elements” and switched back to “Load only used elements (recommended)”
and then in the next section down I set
“Scan Widgets for Theme Shortcodes” = “Scan widgets”
and the page no longer errors.Here is a dev site with all plugins turned off and child theme empty except for custom post type. Still happens…
Yes, but I already went through all the code and couldn’t find any issues. I literally strip the theme to nothing but the custom post type declaration and it’s still happening. Could it be something with the way the post type is configured?
