Forum Replies Created
-
Posts
-
Whaaat, thank you, but I swear that’s what I did and it didn’t work. That’s so bizarre but thank you for your help!
Yes I did. And that didn’t fix the issue. This is a staging site, so you can look in the theme file editor in the WP admin.
For Animated Numbers element, please go to /enfold/config-templatebuilder/avia-shortcodes/iconbox/iconbox.php in Appearance > Editor and find following on 631st line
$default = $this->sync_sc_defaults_array( $default );
and comment it out as following$default = $this->sync_sc_defaults_array( $default, ‘no_modal_item’, ‘no_content’ );
Thank you…that works….except for, it’s not in /iconbox/iconbox.php for animated numbers….it’s actually in /numbers/numbers.php :)
I’m having this exact same issue. Also tried without success disabling all plugins, deleting cache, editing the text and trying to add the object once again. Please let me know what fixes you apply.
Sorry. I had to restore a backup because from before the update because it was just too messed up. Try the info below (I kept the latest update on staging).
I actually just updated the LIVE site, and I’m now having the same issue I was having with the staging site. and now I’m also seeing the cookie consent bar showing up after I click accept (I already posted about the cookie message elsewhere though). Please help!
I’m having the same issue. I tried reloading the style.css, and nothing, cleared my cookies, still there, tried incognito, VPN, etc. and absolutely no luck.
Hi Basilis, Thank you for the response. The fonts seem fine now. Did you do something? Did you reload the fonts or something?
Hi Victoria, we use a hosting provider called Pantheon, and the error showed up on the development site dashboard when we copied down the database from the live site so we could push the theme update upstream. It’s quite nerve-wracking.
Thank you Ismael…what about the masonry shortcode on the footer? Is there another way for me to be able to display that element on the footer?
Hi Rikard,
I removed the shortcode from the second column of the footer and the issue on the footer got fixed (however, I would still like a way to be able to show the masonry as it’s always been on the footer there, any suggestions there). ALSO, the image galleries on the pages are still messed up. I added a link below, where you can scroll down the page and see how a gallery that used to be 3×2 images, it now shows as 6×1 (all happened after the same theme update).I have not made any changes. I just went in to check and was able to see the issue as it’s always been (I’m not sure why you’re not seeing anything). You can also see the same issue happening at in the middle of the page on the links I posted above (not just on the footer)… Did you scroll all the way down?
Hi, I just tried that and it didn’t work. Please feel free to go in and try anything and everything you want on the staging site to see if anything works.
I just noticed that this is happening on most pages (not just the footer. Galleries that were three columns are now one column and so on and so forth.
Also, I’ve tried the typical troubleshooting tips (deactivated plugins to see if that did it, cleared cache, etc.) and nothing has worked.
Hello, I too had this problem and used the plugin you recommended above to update and the update worked fine.
However, after the update, I noticed that my fullwidth submenus’ links no longer work and all submenus are now somewhat transparent (which I do not want), and now you can see images and text through the submenu when scrolling down. I’ve added a sample link for you to see what I’m saying.
Also, is it okay for me to now delete that plugin? Or do I need to keep it there?
Hi Victoria,
I actually removed the entire header.php from my child theme (on a staging site) just to see if that would work and the issue is still happening (yes, the window opening and the page going to the image link, which shouldn’t happen and is the issue I’ve been referring to this whole time). Can help me fix this please?
Please help me!
Hi Victoria,
Do you mind telling me what my header.php file is missing? I updated it with a fresh copy from the parent theme yesterday, so I’m not sure why it’s not updating. I just made the update again just in case I messed something up the first time, but it’s still not working. I’m running the latest version of the theme (4.4.1) and I just checked both the parent theme’s header.php and the child theme’s header.php and they’re identical except for the Google Tag Manager container on the child header.php.
One other question, I use Google Tag Manager, which is why I have to modify the child theme’s header.php. With that in mind, is there another way to add the Google Tag Manager container somewhere else that won’t require me to modify the child header.php file AND that doesn’t require a plugin (I don’t want to get a plugin for this, so I’m hoping it’s something I can do manually).
Thank you!
Hello,
The Lighbox element is also not working for me either. I followed your instructions above to do this: Can you try to go to Enfold > Performance > Disabling of template builder elements set to: Always load all elements and it didn’t work. I’ve also checked my child theme’s header.php and made sure it’s the same as the parent theme (plus my own modifications).
I’ve added admin access to my site in the private section below.
please help!
Hi Ismael,
I use Pantheon for hosting, which gives me the option of having a development site to make all and any file changes, then the code for that gets pushed up to the Test site. Once the test site is good to go, then one clones the database from the Live environment while pushing the code changes upward. We’ve never had issues, until the theme updated to 4.3.2 and then on and on after that. According to them, something within the theme itself is causing these errors to show up on the dashboard and also on the error logs. Like I mentioned before, you won’t see any errors on the actual site. However, these errors that happen due to the theme are preventing me from making any updates past the test environment because something within the theme files is preventing it. Does that make sense?
Have you ever encountered errors like the ones I mentioned above?
Hi Ismael,
You won’t see the error on the page. It shows on my hosting dashboard and on the error logs. These errors that pop up prevent me from cloning my database from the development site to the live site. These errors show up whenever I try to commit any changes to my child theme files. They first showed up during the update to 4.3.2 (I have since updated to the latest version of the theme and the errors continue to show up). I’ve contacted my hosting provider and they have confirmed that it’s something in the Enfold theme that is causing these errors to show up and prevent the database from being cloned. You can see below the exact errors that we get and how they all refer to something inside the Enfold theme.
This is exactly (copied/pasted) what shows on my website’s error logs:
PHP Notice: Trying to get property of non-object in /srv/bindings/9bed856b5f7c443f842262608ed4d5d6/code/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66
PHP Notice: Undefined variable: main_color in /srv/bindings/9bed856b5f7c443f842262608ed4d5d6/code/wp-content/themes/enfold/css/dynamic-css.php on line 35
PHP Notice: Undefined variable: primary in /srv/bindings/9bed856b5f7c443f842262608ed4d5d6/code/wp-content/themes/enfold/css/dynamic-css.php on line 47
PHP Notice: Undefined variable: primary in /srv/bindings/9bed856b5f7c443f842262608ed4d5d6/code/wp-content/themes/enfold/css/dynamic-css.php on line 52
PHP Notice: Trying to get property of non-object in /srv/bindings/9bed856b5f7c443f842262608ed4d5d6/code/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php on line 66
PHP Fatal error: Uncaught Error: Call to a member function reset_options() on null in /srv/bindings/9bed856b5f7c443f842262608ed4d5d6/code/wp-content/themes/enfold/functions-enfold.php:1566
Stack trace:
#0
/srv/bindings/9bed856b5f7c443f842262608ed4d5d6/code/wp-includes/class-wp-hook.php (286): avia_generate_stylesheet(”)#1
/srv/bindings/9bed856b5f7c443f842262608ed4d5d6/code/wp-includes/class-wp-hook.php (310): WP_Hook->apply_filters(”, Array)#2
/srv/bindings/9bed856b5f7c443f842262608ed4d5d6/code/wp-includes/plugin.php (453): WP_Hook->do_action(Array)#3
/srv/bindings/9bed856b5f7c443f842262608ed4d5d6/code/wp-content/themes/enfold/framework/php/function-set-avia-backend.php(89): do_action(‘ava_after_theme…’)#4
/srv/bindings/9bed856b5f7c443f842262608ed4d5d6/code/wp-includes/class-wp-hook.php (286): avia_update_helper->update_version(”)#5
/srv/bindings/9bed856b5f7c443f842262608ed4d5d6/code/wp-includes/class-wp-hook.php (310): WP_Hook->apply_filters(NULL, Array)#6
/srv/bindings/9bed856b5f7c443f842262608ed4d5d6/code/wp-includes in /srv/bindings/9bed856b5f7c443f842262608ed4d5d6/code/wp-content/themes/enfold/functions-enfold.php on line 1566
