Forum Replies Created
-
Posts
-
Hello Rikard,
Thank you for your answer.
The av-helper-masonry.php file was overridden in the child theme to fix the
PHP fatal error: Call to undefined method avia_masonry::default_args()
since version 4.8.I see the av-helper-masonry.php file in the Enfold theme now has the default_args() method, so it is now safe to remove the file in the child theme.
The error is solved, thank you!
Regards,
FrançoisHello Rikard,
Thank you for your answer.
The user was not created somehow…
I have created it again.
Regards,
FrançoisHello,
We are experiencing the same issue. Still present in version 4.8.8.1.
Got error ‘PHP message: PHP Fatal error: Uncaught Error: Call to undefined method avia_masonry::get_element_styles() in /home/aclm/www/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/masonry_entries/masonry_entries.php:682
Stack trace:
#0 /home/aclm/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-shortcode-template.php(345): avia_sc_masonry_entries->get_element_styles(Array)
#1 /home/aclm/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-post-css-management.php(940): aviaShortcodeTemplate->create_header_styles(Array, false)
#2 /home/aclm/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-post-css-management.php(975): aviaPostCssManagement->css_rules_from_shortcodes(Array)
#3 /home/aclm/www/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-post-css-management.php(874): aviaPostCssManagement->css_rules_from_shortcodes(Array, ‘file’)
#4 /home/aclm/www/wp-content/t…’Regards,
FrançoisI don’t know what to tell you. I can’t see the fix you mention : it’s in a private field.
It’s possible that the fixes I propose in the first post are not perfect. Works for me though.
(Precision : the slideshow problem occured with an “Easy Slider”).Well, the thing is that as the code is in 4.7.5, the slideshow doesn’t transition at all and the controls don’t respond to clicks. No js errors, just a stuck slideshow.
Could you please also add something to override these in config-woocommerce/config.php
# # removes the default post image from shop overview pages and replaces it with this image # add_action( 'woocommerce_before_shop_loop_item_title', 'avia_woocommerce_thumbnail', 10); remove_action( 'woocommerce_before_shop_loop_item_title', 'woocommerce_template_loop_product_thumbnail', 10);It may become very complex to customize every resource url like you wish to, and it takes time to track down every place where such urls are defined in the code. So, I would follow Yigit’s advice and use a dedicated plugin for that.
These info shouldn’t be displayed at all times, but only when the support team needs them. It would be good to have a theme option to hide them or display them only for admin users.
Anyways, to remove this “debugging info” comment from the <head>, add this to your child theme’s function.php :
// prevent enfold's debug info from being displayed in head by defining the avia_debugging_info function before enfold does. function avia_debugging_info(){}This will override (or more correctly, “define beforehand”) the avia_debugging_info function that’s located in /enfold/framework/php/function-set-avia-frontend.php, effectively preventing these info from being displayed.
Hi, sorry to step in, but : I encounter the exact same behavior with any section elements, be it color-section, grid-line, tab-section.
I believe the problem is located near the top of the “avia_new_section” function (config-templatebuilder/avia-shortcodes/section.php). The way the variable $close is set.Edit: I think I got it to work. The trick is that if there’s at least one section element in the page, everything else has to be encapsulated inside section elements.
