Forum Replies Created

Viewing 30 posts - 91 through 120 (of 218 total)
  • Author
    Posts
  • in reply to: Enfold 4.7.6.2 with Child Theme Breaks Site Front End #1237010

    Yes, I’ve had errors the last 3-4 updates, and all I get is Kriesi does not know what is happening. Comforting. Kriesi, you need to step this up before you start losing customers. Please advise ASAP.

    in reply to: Enfold 4.7.6.2 with Child Theme Breaks Site Front End #1236749

    Should mention I installed it, then FTP rolled back to 4.7.6.1. Still not working.

    in reply to: Updated to 4.7.6.1 and get error? #1234866

    Yes via email after initial theme update. And every time there is an update. It does not continue and the site seems to function properly. Strange errors…

    in reply to: Updated to 4.7.6.1 and get error? #1233969

    This is the message sent to email when updating. Something like this happens every time I update your theme…

    in reply to: Upgrading to 4.7.5 threw error #1218800

    Only happens on site updates, and only seem to get one WP automated error. But it’s every time we update and multiple different Enfold files. Sites seem to be functioning correctly in spite of this. No i did not disable plugins. Oddly, our store subdomain and staging sites all work fine with the auto update in the Enfold panel…

    in reply to: Upgrading to 4.7.5 threw error #1218480

    Got this when updating live site:

    An error of type E_COMPILE_ERROR was caused in line 39 of the file /home/website/public_html/wp-content/themes/enfold/framework/avia_framework.php. Error message: require(): Failed opening required ‘php/inc-autoconfig.php’ (include_path=’.:/usr/local/php73/pear’).

    Why is it every time I update your theme, it throws errors? Are these benign, or of concern?

    in reply to: Upgrading to 4.7.5 threw error #1217749

    I can also mention that I updated our store sites through the admin link within WP, but for our main staging and live sites, I always have to manually update via FTP…

    in reply to: Upgrading to 4.7.5 threw error #1217746

    All i can give you is where it threw an error for me. Not sure what else you expect from my side. Is it something of concern, will it come back? I haven’t received another alert today…

    WordPress version 5.4.1
    Current theme: Enfold (version 4.7.5)
    Current plugin: (version )
    PHP version 7.3.16

    in reply to: Enfold and Hustle Pro Plugin #1212348

    I also use this plugin, but form input fields do not align, nor do they all look the same. It is a CSS issue between the plugin and Enfold. Just not sure which CSS to adjust….

    in reply to: Woocommerce My Account page blank?? #1208602

    It appears resolved but I had to enable the blog, which we don’t have on this site. PHP is 7.3.16.

    in reply to: Woocommerce My Account page blank?? #1208273

    A blog page needs to be enabled for it to show??

    in reply to: Background image does not parallax or scroll #1208245

    Apparently this won’t be answered?

    in reply to: Background image does not parallax or scroll #1207586

    Yes that is how I see it too. But I have it on fixed. Parallax and scroll do not work….

    in reply to: Background image does not parallax or scroll #1206571

    That section is not parallax, it is fixed. If I change it to scroll or parallax, it simply scrolls with the page like a “stationary” picture. Something seems off in the Enfold code that it is no longer working. I’m not sure what else I can do to explain this. Can you duplicate somehow on your end? Thanks…

    in reply to: Background image does not parallax or scroll #1205827

    I did in my initial message…

    in reply to: Background image does not parallax or scroll #1205508

    You are seeing fixed I believe. The others don’t work.

    in reply to: Full size header picture #1204780

    I have also tried to set background image to parallax or scroll on the bottom newsletter signup, just as the Enfold Shop example. Neither work. Only fixed. Please advise…

    in reply to: dynamic_avia making WAY too many calls #1187773

    I have added your filter exactly as you sent it (my_stamp) to a staging site to test, using Snippets (I believe it’s nearly identical to My Custom Functions when used to insert custom PHP to functions.php). Is that correct?

    in reply to: dynamic_avia making WAY too many calls #1184626

    Great. Doesn’t answer my question. Why can’t I just put it into a snippet and be done? A child theme at this point means reconfiguring all my theme customization settings. On a live site no less.

    in reply to: dynamic_avia making WAY too many calls #1184550

    So for many who don’t have child themes and can’t do that, then what? Seems to me fixing this at it’s core would be priority #1, not making your users jump through hoops to accommodate code discrepancies that aren’t being addressed. Not to mention needing to totally reconfigure the child theme to match what we already have customized in the main theme…

    in reply to: dynamic_avia making WAY too many calls #1184212

    I prefer to use a snippet if possible, since functions.php will be overwritten on every update. Is that feasible? Can i just do that, add the space to quick css, save, and be good to go?

    in reply to: dynamic_avia making WAY too many calls #1183944

    Also got this when updating the live site. Enfold seems to have more issues lately…

    An error of type E_COMPILE_ERROR was caused in line 51 of the file /home/website/public_html/wp-content/themes/enfold/functions.php. Error message: require_once(): Failed opening required ‘config-layerslider/config.php’ (include_path=’.:/usr/local/php71/pear’)

    in reply to: dynamic_avia making WAY too many calls #1183936

    For the update error, no I did not overwrite. I never do. I rename the existing Enfold folder to Enfold_old, then copy the new Enfold folder over, test, and delete Enfold_old.

    Circling back to the filter, do I just copy and paste your PHP into a snippet (don’t have a child theme)? Any changes necessary? Also, not sure what you mean when you say “If css & js file merging and compression was already enabled, then go to the Quick CSS and add a blank space to make the “save all changes” clickable and change the css in the theme to force a new file to be created when the front page is reloaded.” I get the blank space to force the save button to activate, but the part about changing the css in the theme to force a new file to be created is a bit confusing. What css am I changing to force the file to be created? Or do you just mean adding that blank space? Thanks, hopefully a more elegant, hands-off solution will be written into the next release…

    in reply to: Cannot update theme #1183675

    I believe from that version to current (4.7.3 as of today), you’ll have to FTP in and do it manually…

    in reply to: dynamic_avia making WAY too many calls #1183626

    And upon updating the test site, I now get a new error: An error of type E_COMPILE_ERROR was caused in line 177 of the file /home/website/staging/wp-content/themes/enfold/framework/php/inc-autoconfig.php. Error message: require(): Failed opening required ‘/home/website/staging/wp-content/themes/enfold/framework/php/avia_shortcodes/shortcodes.php’ (include_path=’.:/usr/local/php71/pear’).

    Cmon people…

    in reply to: dynamic_avia making WAY too many calls #1183622

    I updated to 4.7.3. Do i still need this PHP code, or does the update take care of it?

    in reply to: dynamic_avia making WAY too many calls #1182167

    This is what is in one file. Is there something wrong in here??

    in reply to: dynamic_avia making WAY too many calls #1182159

    Your answer is to disable part of your theme’s functionality and use someone else’s?? That does not instill much confidence in your theme. Seems like some error in how Enfold is merging those scripts with the most recent version. I wonder what happens if Enfold is rolled back.

    in reply to: Customize Blog page #1164097

    I think this did it, added as a Snippet to avoid it being deleted on theme updates:

    add_filter(‘avf_blog_style’,’avia_change_category_blog_layout’, 10, 2);
    function avia_change_category_blog_layout($layout, $context){
    if($context == ‘archive’) $layout = ‘blog-grid’;
    return $layout;
    }

    Thank you!

    However, I still cannot create custom category pages as suggested and get the category links to point to those, correct??

    • This reply was modified 4 years, 5 months ago by Illingco.
    in reply to: Customize Blog page #1163144

    It also creates a lot more work, especially when adding a category, as I’d then have to manually edit all those pages each time. Essentially, I just want the magazine element portion that shows category links…

Viewing 30 posts - 91 through 120 (of 218 total)