Viewing 16 posts - 1 through 16 (of 16 total)
  • Author
  • #1086457

    After various performance optimizations: Front page corrupted but all other posts/pages are correct.

    Changes before error:

      httaccess > GZip compression
      httaccess > Expire headers
      Plugin > EWWW installed > all media optimized

    Tests to repair front page problem:

      delete browser cache > no change
      use various other browsers / browser-profiles > no change
      all plugins off > no change
      dropping various plugins back in > no change
      WP SuperCache off and delete cache > no change
      Enfold theme CSS file merging and compression off and delete files from UI > no change
      manually delete folder /wp-content/uploads/dynamic_avia > no change
      try various other cache settings/setting-combinations > no change
      check browser console > found that a certain avia-footer-script is missing > copied and renamed newly created footer script to old footer script name > no change


      I need help

    Hey kunxkreisi,

    Thank for you using Enfold.

    Looks like you forgot to add the site url. Please add it in the private field along with a screenshot of the home page prior to the issue. You can upload the screenshot to imgur or dropbox.

    Best regards,


    see below



    Thanks for that, it looks like you are getting 404 errors on the files in the dynamic_avia folder, could you check that the folder in question exists? If not then please try to change something in the theme options and save to regenerate it.

    Best regards,


    I agree with you that there seems to be some residual file request. However, what you are asking me to do is what I already had done before I contacted you.

    Please be so kind and try that yourself because I think it isn’t working and this may not be about the actual file but about the data base.



    Thanks for the update.

    The hash or identifier in the database doesn’t correspond with the name of the actual files. Please edit your database, look for the “aviaAsset_avia-merged-styles” and “aviaAsset_avia-footer-scripts” entries inside the _options table and then delete them. Try to check the page again afterwards.

    Best regards,


    Both are not in the database



    We reactivated the file compression settings to regenerate the database entries. Please check them again. We also noticed that there are outdated template overrides in your child theme such as the header.php file. Please get fresh copies of those files from the latest version of the parent theme and redo the modifications.

    Best regards,


    Indeed, there was a lot in there and I now use only the default child-theme files (with custom CSS styles). But the error is not corrected.

    However, I see in console that only on the front page does not load any CSS and all other pages do load it.

    Please be so kind and have another look.

    • This reply was modified 3 months, 1 week ago by  kunxkreisi.


    Thanks for the update.

    The following files are being loaded in the home page but they don’t seem to exist.

    <script type='text/javascript' src=''></script>
    <script type='text/javascript' src=''></script>

    How did you add those? We don’t see those files in the child theme.

    Best regards,


    Another good find – thank you!

    That seems to have been some residual JS by someone else. But even when I put those scripts back in, the error is not corrected. (I now took those JS out again.)

    But how could I ever load any scripts? If…

      … my functions.php is completely clean.
      … I use the default child-theme.
      … there is no hard code in the custom style.css.
      … I do not use a header/footer-script plugin.
      … I cannot find the scripts called in the database.
      … I have updated the main theme.

    I am sorry that this seems beyond the scope of your support but I am not yet completely convinced that this is not error with your theme, or the theme-based minification.


    One more thought if I may: This error only happens on the front page, all other pages are correct.

    So, could it be that there is some special theme code that is only called on “home”?



    No, there’s nothing like that in the theme and if there is, it wouldn’t break the site.
    Did you install the WP Members plugin before? The home page is loading another css file (see private field) from the plugin, but the plugin doesn’t exist in plugins directory when we check.

    Please create a backup of the site and then install this plugin to clean the database.


    Best regards,



    Did you ever get this resolved? I’m having a very similar if not exact same issue when I try to upgrade enfold to the newest version. I use enfold on about 6 different websites and some of them have the latest version of the thems with the latest version of WordPress and everything works fine, however, in one case I get very crazy stuff happening. I’ve spent 2 days now trying to troubleshoot caching at the browser, site and firewall levels and I cannot for the life of me figure this out. I too run into Console Issues with avia header scripts, avia footer scripts and I believe one other dynamically created file.

    I really need to be able to upgrade this theme and finish all updating. Any help would be greatly appreciated!



    No, this did not get solved by the support.

    I have plugin scripts loading by plugins that are not installed let alone activated. I manually cleaned the database of any code by those plugins. I deleted all caches manually and via the respective theme/plugin functions.

    Since these errors only happen on the front page I concluded that this one page is corrupted and I recreated it manually. That did solve the problems.



    @kunxkreisi: Glad to hear that it’s fixed. We’ll close this thread now. Have a nice day.

    @estleman: Please don’t hesitate to open a new thread if you need further help on this issue.

    Best regards,

Viewing 16 posts - 1 through 16 (of 16 total)

The topic ‘After various performance optimizations: front page corrupted’ is closed to new replies.