Forum Replies Created
-
Posts
-
Commenting out the deprecated code in /enfold/config-layerslider/LayerSlider/wp/menus.php did the trick, thank you.
Thank you, that is exactly what I was looking for. I was not able to find this thread in my initial search. Again, thanks for the assistance.
fine with the version… but still would be nice if you added a filter for the args array as mentioned above:
$args = apply_filters( 'avf_google_maps_args', $args );Update: ah, I see… just filter the source and add my own arguments… ok, that also works.
Issue resolved.exactly, so which type of event would this be?
Maybe a little example of how the event listener should be constructed?Would this be the recommended way:
(function($){ $('body').on('av-google-maps-api-loaded', my_callback() ); function my_callback(){ console.log('hey dude'); } })( jQuery );or maybe better to use the avia-google-maps-api-script-loaded event?:
$('body').on('avia-google-maps-api-script-loaded', my_second_callback() ); function my_second_callback(){ console.log('phone is ringing, dude'); }Update 1: Neither. Now using something like:
window.addEventListener('load',function(){ if(document.getElementById('av_gmap_0')){ gmap_init(); } });But again, not sure if this is the recommended method, also there is no way to provide a unique ID to the map, so we just have to check if at least one map exists.
Update 2: Nope, also not the best way.
As I understand it it’s two things.
1. A filter so that we can all hook into it with our own functions
2. A function that Ismael has made for me (thank you again)By asking if the avf_dropdown_post_query filter be added to the next release, I mean just that… will this filter be part of the next release of Enfold, or will we need to modify the core file:
config-templatebuilder/avia-template-builder/php/html-helper.class.phpeach time, defeating the purpose of this thread.Thank you for the response Günter.
I look forward hearing how best to filter the results.
All the best!Hello Nikko,
We updated the original post with the cause and solution.
Seems the file was being duplicated as newer versions of Enfold moved the file into a subfolder. Updating the theme left the original file causing the conflict.Issue can be marked as resolved.
We also experienced the JS error of the missing function. After manually adding the missing function to enfold > js > shortocdes.js this was resolved. So are we to understand that version 4.2.4 is missing a required JS function?
I also noticed the grid content element is not longer displaying correctly. Will roll back to version 4.2.1 and see if the issues go away.
Update: rolling back to version 4.2.1 resolved both issues.Just solved this issue.
This force-loading an old version of jQuery can be turned off by navigating to:
Dashboard > LayerSlider WP > Scroll to the bottom of the page > Advanced Tab
and turn off the foolish feature:
Use Google CDN version of jQuery (on/off) This option will likely solve “Old jQuery” issues.Shame on you LayerSlider WP.
Issue can be marked as resolved.Having the exact same issue.
The allocated memory is already set to 256M, and has been verified via phpinfo (see enclosed link)
Note: Images do upload, it’s only when media.php tries to generate the thumbnail images that the system is crashing.Update 1: We have verified that it is an issue with Enfold, as it works fine when we switch to Twenty-Fifteen to upload images and create thumbnails. The Out of Memory issues seems to be an ongoing thorn in the side of Enfold.
Update 2: After checking how many image sizes are registered it’s little wonder we are running out of memory. After installing Ajax Thumbnail Rebuild we see there are 19 image sizes registered! 13 are registered in the functions.php file and the rest seem to be generated by default from the avia_woocommerce_set_defaults function, although we do not have WooCommerce installed. What kind of deal is that?
I ended up having to manually re-create the page element by element.
The new page loads without issue, so this leads me to believe that something in the old page was causing the error.
Since there is no way to debug this in Avia, I guess it will forever remain a mystery.Great theme… when it works correctly.
Quick follow up: The problem seems to be related to the latest version of Yoast SEO throwing the following error:
Uncaught TypeError: jQuery(...).qtip is not a functionSo please ignore this as we go do battle with the cartoons at Yoast.
For reference, this is a known issue with Yoast SEO:
https://github.com/Yoast/wordpress-seo/issues/3552What does updating to version 3.2 have to do with this issue?
I understand that the sidebar will always apear below the last color section element. But would it not be possible to simply tell the element to be inserted before the footer, as it also spans the entire width of the screen.This issue has also been brought up on the following threads:
Unfortunately fullwidth elements such as fullwidth button, color section etc. would push sidebar below
https://kriesi.at/support/topic/content-section-before-footer/
Just wanted to verify before I start hacking the template files.
