Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #1026985

    Hi!
    http://www.hotelladdict.se
    Why do I get this error when I try to update? I never had any problems before.

    Best regards
    Charlotte

    Updating Theme Enfold (1/1)
    Warning: preg_match() expects parameter 2 to be string, array given in /storage/content/09/4000509/hotelladdict.se/public_html/wp-admin/includes/class-wp-upgrader.php on line 258 Warning: file_exists() expects parameter 1 to be a valid path, array given in /storage/content/09/4000509/hotelladdict.se/public_html/wp-admin/includes/class-wp-upgrader.php on line 258 Warning: strip_tags() expects parameter 1 to be string, array given in /storage/content/09/4000509/hotelladdict.se/public_html/wp-admin/includes/class-bulk-upgrader-skin.php on line 61 Downloading update from …
    Warning: parse_url() expects parameter 1 to be string, array given in /storage/content/09/4000509/hotelladdict.se/public_html/wp-admin/includes/file.php on line 970 Warning: preg_split() expects parameter 2 to be string, array given in /storage/content/09/4000509/hotelladdict.se/public_html/wp-includes/kses.php on line 1325 Warning: strtolower() expects parameter 1 to be string, array given in /storage/content/09/4000509/hotelladdict.se/public_html/wp-includes/http.php on line 517 Warning: strtolower() expects parameter 1 to be string, array given in /storage/content/09/4000509/hotelladdict.se/public_html/wp-includes/http.php on line 517
    An error occurred while updating Enfold: Download failed. A valid URL was not provided.

    #1027046

    Hi Charlotte

    Which PHP version is your website running on?
    However, please try the following guide in order to update to Enfold v4.5.

    Update your website manually via FTP:
    1) Make a full backup of your website using a backup plugin.
    2) Safe the backup somewhere outside from the webserver of your website (e.g. on your local computer or in any cloud storage you trust).
    3) Sign out from your WordPress website.
    4) Go to your themeforest account, sign in and download the updated Enfold v4.5 to your computer. Extract it and search for the file enfold.zip. Extract this file as well to already have your folder ready to be uploaded.
    5) Sign in to FTP or SFTP using FileZilla or any other tool which is able to do that.
    6) Go to the folder ./wp-content/themes and search for “enfold”. If you want, you can download the enfold folder to your computer as well (just in case you want to restore if afterwards which is easier like that than using the whole backup).
    7) Delete the folder enfold via FTP. This may take 5-10min, depending on the server speed obviously.
    8) Wait until it is finished and the enfold folder is gone. If that is the case, upload the “new” enfold folder including v4.5 to your website in the same directory.
    9) Sign in to your WordPress website again and go to the Enfold tab (or the one from your child theme). Scroll down to the tab called Theme Update.
    10) Your current API token will not work anymore as Envato changed some stuff on their API. Therefore you need to remove your current key and generate a new private key as visible in your themeforest account under “Settings” -> “API keys”. Go to https://build.envato.com and follow the steps there. To me, https://kriesi.at/documentation/enfold/how-to-install-enfold-theme/#toggle-id-5 was also very helpful (scroll down a bit there to find out about the permissions your private API key needs in order to check for future Enfold updates). Without these permissions it will not work.
    11) Enter your generated Envato key in an incognito/private mode browser window. After revalidating your new private key within the Enfold update tab, you should see a blue rectangle saying when it could be checked for the last time.
    12) Done!

    I hope this helps!

    Best,
    Michael

    #1027221

    Hi
    I get the same bunch of errors…..I run PHP 7.0
    Thanks
    Lyse

    #1027235

    Hi,

    I have also PHP 7.0

    Enfold team! I suggest you fixed this problem so we don’t get this error when trying to update. I don’t think we should have to update through ftp. Make it work as it use to be instead!

    Best regards
    Charotte

    #1027240

    Did you go through my step by step guide?
    I guess this time the best solution is to update via FTP, because the Envato API changed and I can imagine this can’t really be fixed by Kriesi.

    If you update it via FTP this time, you will be connected to the new API afterwards and the auto update via WP dashboard will work as usual.

    #1027242

    I use quite a few themes published on Envato and all of them update just fine via the auto-update function – with Enfold being the only exception. So I guess there is a way to make this work from the theme creator’s side…;)

    • This reply was modified 6 years ago by IkariGendo.
    #1027260

    Hi Enfold,

    I think this solution through the ftp is way too complicated for many users.

    Hello Enfold upport – how are you going to fix this?
    And why didn’t you send any information about this error in the dashboard?

    Best regards
    Charlotte

    #1027261

    Hi
    I used the plugin as a fix because I have too many copies of the theme to be doing the FTP steps for all of my websites.
    I do agree with Charlotte that prior information about this upgrade should have been sent to us.
    Lyse

    #1027270

    Hi,

    @charlotteraboff
    the update to v4.5 is the fix, if you would like assistance in updating, please include a admin login & ftp access in the Private Content area.

    Best regards,
    Mike

    #1027277

    Hi Mike.

    Thanks for your email.
    Of course I can do that but I would prefer that Enfold fix the problem. There are many users like me and I don’t think is the best solution for you if you had to login and help the users like this,

    First, you need to find out why so many users have the same problem. Analyse the error message we get. What is the original problem?

    Thanks!
    Charlotte

    #1027284

    Hi,
    The problem is with the Theme Forest move away from the API to the Token system, the fix for this requires files to be replaced via ftp, so it was integrated into the v4.5 update, which is a easier solution than trying to explain which files go where.
    Luckily there is a easy plugin that updates the theme without using FTP, I see that it was posted above along with the steps to use it.
    I’m glad that you don’t need help with FTP, but we are happy to assist anyone that does need help with this one time inconvenience.
    Thank you for your patience and understanding.

    Best regards,
    Mike

Viewing 11 posts - 1 through 11 (of 11 total)
  • You must be logged in to reply to this topic.