Viewing 30 posts - 31 through 60 (of 66 total)
  • Author
    Posts
  • #920485

    Hi Nick,

    Reading some of the other posts it looks like kriesi is more interested in getting us to test the problem for them rather than giving us a quick fix… quality!!

    Best Regards
    Ian

    #920499

    I get that they need this. Im happy for them to take a full copy of my site to assist their investigating, but i need to be back up and running asap. Nightmare that even the backup i did before updating appears to have failed on some of my transfers so web host looking at that SLOWLY.

    #920503

    Not the first time this has happened… must remember to take a look at this forum before I update this theme again!!

    #920507

    Been having a few issues for about a month to point where i coundn’t even post yesterday, so thought this update may help. How wrong was I?

    #920510

    Maybe I need a staging server.

    #920559

    Hi,

    We are waiting to hear from @mmaack in this thread.

    We need FTP and WP admin logins to look into the issue on each installation and it would be great if you all started your own threads.
    If you post them here, they will be visible to @mmaack as well and you would not see private content field to download version 4.2.4.

    Cheers!
    Yigit

    #920583

    I had deleted my enfold folder, and uploaded a fresh copy, but the site still delivered blank pages. My server doesn’t have direct FTP access for security reasons. Site still working fine with 4.2.2.

    #920594

    Same thing happened to me. After turning on display_errors, I saw this:

    Fatal error: Cannot use object of type WP_Error as array in D:\Users\Scott\Dropbox\SOS4Net_WebSites\Business\maglogixwp\wp-content\themes\enfold\config-templatebuilder\avia-template-builder\php\asset-manager.class.php on line 265.

    That was using WP 4.8.5 AND 4.9.4 under PHP 5.6.x. Got the same under PHP 5.4.x and an even longer error message under 7.1, but essentially the same, trying to use WP_Error object as an array in asset-manager.class.php on line 265.

    I rolled back to Enfold 4.2 and it was fine under WP 4.9.4.

    Scott

    • This reply was modified 6 years, 3 months ago by scotthco.
    #920598

    Just rinsed and repeated and now the 4.2.5 version works. Go figure. Made a backup of my 4.2.2 enfold folder as a fall-back. All seems to be well.

    I did this 3 times yesterday, with the same results.

    Worked today.

    • This reply was modified 6 years, 3 months ago by mmaack.
    #920679

    Hi mmaack,

    Great, glad you got it working and sorry for the problems.

    Best regards,
    Rikard

    • This reply was modified 6 years, 3 months ago by Rikard.
    #920712

    Can someone send me the link for 4.2.4 please? A shame they are not archived somewhere for access on this site.
    Is it just a matter of replacing the Enfold theme folder? I am using a Child theme.

    #920779

    Hi craigriches,

    Can you please check server log for error? Which version of php are you running?

    Best regards,
    Victoria

    #920783

    Hi Victoria
    Running PHP 7.1
    Managed to roll back to 4.2.4 via back up from Host. Thankfully this is on a staging site and not the live version.
    Running fine on 4.2.4
    So, can only assume it is 4.2.5 bug

    #920795

    Hi craigriches,

    Do you have any errors in the server log? That would shed some light.

    Best regards,
    Victoria

    #920847

    where would i go to find the server log?
    If you mean within cPanel there is nothing listed under Metrics=>Errors=>Last 300 Error Log messages in reverse order:

    • This reply was modified 6 years, 3 months ago by craigriches.
    #920864

    Same problem here. Back to 4.2.3.
    Waiting for the fix.

    #920898

    Hi,
    Did you update Enfold to v4.2.5 via FTP?
    This could be the issue:
    We are rewriting the elements and changing the structure in the /config-templatebuilder/ folder, and when you update via FTP some of the older files are being left in the folder at: /wp-content/themes/enfold/config-templatebuilder/
    The solution is to delete the /config-templatebuilder/ folder via FTP and re-upload from the new v4.2.5 theme.
    Please try this.

    Best regards,
    Mike

    #920992

    Hi Mike,
    The first attempt to update was from within the WP dashboard. This resulted in a success message but a blank home page but accessible backend Dashboard.
    Next I tried downloading 4.2.5 from Themforest and uploading via ftp and overwriting files. Didn’t work either.
    Then tried deleting Enfold folder and uploading latest version to Themes folder. Also didn’t work.
    Finally, rolled back to 4.2.4 from a backup and all came back fine.
    I could try your suggestion, but I am curious how this would be different to what I tried before by deleting the entire Enfold folder and uploading 4.2.5 . Would it not just be the same thing?

    #921036

    Mike I can report that your instruction to ” delete the /config-templatebuilder/ folder via FTP and re-upload from the new v4.2.5 theme.” did not work.
    Blank Homepage yet again.
    Rolled back to 4.2.4 from back up and perfectly fine.

    regards
    Craig

    #921065

    Hi,

    @craigriches
    thanks for your feedback, while this has helped some, your issue must be different. Glad your rollback worked.
    Please try creating a staging / testing site on a sub-domain with a copy of your site. This will allow you to test updates without effecting your production site, it will also allow us to help debug.
    Please open a new thread so we can assist, we will want communicate in the Private Content area, with login info, but as this is not your thread you will not see what we write, nor will your info be private. Thanks for your patience and understanding.

    Best regards,
    Mike

    #921118

    I updated from the WP dashboard. Result: blank site.
    No older files in the folder at: /wp-content/themes/enfold/config-templatebuilder/.
    As a test I installed Enfold in another wordpress site. Result in preview: blank site.


    @craigriches
    , If you can fix it, please post how you got it.
    Best regards.

    #921124

    Hi,

    @frlozano
    Please open a new thread so we can assist, we will want communicate in the Private Content area, for login info, but as this is not your thread you will not see what we write, nor will your info be private.
    Two things to look at is to try disabling your plugins, such as wordfence, and ensure your PHP is v7

    Please try creating a staging / testing site on a sub-domain with a copy of your site. This will allow you to test updates without effecting your production site, it will also allow us to help debug.

    Best regards,
    Mike

    #921130

    Is the theme incompatible with Wordfence? Or should we deactivate Wordfence only during installation?

    • This reply was modified 6 years, 3 months ago by frlozano.
    #921134

    Hi Mike
    I will start a new thread and put the login details in Pvt.
    You may not have seen my previous comments in this thread but the issue IS on my staging site. I am not prepared to apply the current update to my live site until this issue is resolved. And it doesn’t appear to be an isolated incident as it seems to be affecting quite a lot of others.
    Previous comments confirmed I am using PHP 7.1
    I can try disabling Wordfence, but I would want to continue its usage if I manage a successful update. And strange that Wordfence active does not affect 4.2.4.

    #921154

    Hi,

    @craigriches
    thank you I will look for your new thread as it being a staging site may help us isolate the issue.
    I also just came across a different site that had a .htaccess file blocking access to js files in the uploads folder, some security plugins may also be doing this.

    Best regards,
    Mike

    #921244

    Hello good day. I need help URGENTLY.
    I have updated to the latest version of the Enfold theme, after that the main site and all the pages of my site, show blank page. !!! It is a production site being the main contact of my business, so this affects me directly in sales.

    Please ask for help to solve it. I have uninstalled the theme and downloaded a new file from ThemeForest, but the error continues.

    I read that by doing downgrades everything works again. I need to please send me some file with the previous version of the theme so I can make the downgrade and my site is operational again.

    is my utimo day of support, so I urgently need support today please … !!!

    Thank you very much.!

    #921319

    Hi iteamar,

    Please open a new thread and we’ll send you the previous version of the theme there.

    Best regards,
    Rikard

    #921513

    Hi, my site breaks and is a blank page when updating the theme to 4.2.5 so I have rolled back to 4.0.5. I am using the latest version of Word Press 4.9.4 and PHP 7 with only one Plugin – All In One SEO. Please post an update here when the update is stable.

    #921688

    Hi,

    Our devs are looking into this issue, for the meantime, please refer to our temporary workaround posted here: https://kriesi.at/support/topic/disable-new-minify-merging-for-css-and-js-avia-merged-styles/#post-921266

    Best regards,
    Nikko

    #922664

    I’m reposting this because it seems that the moderators must have missed it, possibly along with the other posts that mention it. There’s a specific error message below referring to a specific line in a specific theme file.

    Same thing happened to me. After turning on display_errors, I saw this:

    Fatal error: Cannot use object of type WP_Error as array in D:\Users\Scott\Dropbox\SOS4Net_WebSites\Business\maglogixwp\wp-content\themes\enfold\config-templatebuilder\avia-template-builder\php\asset-manager.class.php on line 265.

    That was using WP 4.8.5 AND 4.9.4 under PHP 5.6.x. Got the same under PHP 5.4.x and an even longer error message under PHP 7.1, but essentially the same, trying to use WP_Error object as an array in asset-manager.class.php on line 265.

    I rolled back to Enfold 4.2 and it was fine under WP 4.9.4.

    Is anyone looking into the can’t-use-WP_Error-as-array thing???

Viewing 30 posts - 31 through 60 (of 66 total)
  • You must be logged in to reply to this topic.