-
Posts
-
This thread was originally started at: https://kriesi.at/support/topic/problem-update-4-5-failed/page/2/#post-1024353. Mike recommended that I start this new thread.
I have multiple website accounts with the Enfold them. I have uploaded and replaced the 4.4.5 theme with no problem on my local host version websites. HOWEVER, when I try to do the same to my web server hosted sites, I get an error message with no other content whatsoever. It is like the update is changing something else in the website that is preventing it from viewing.
I have followed the instructions by Mike and Gunter. I have downloaded 3 fresh versions of 4.4.5 from Evato/Themeforest site. I still get the same problem. (I’ve even replaced the so-called “corrupted file” that Gunter thought was at issue. That did not change anything.
Yesterday, I tried the specific technique that Gunter recommended: I first deleted the older version of Enfold from wp-content/themes completely, (only “enfold-child”) was left. I then uploaded the newest copy of 4.4.5 to themes. My site still crashed.
With my site now down, I then attempted to restore my website with a copy of the previous Enfold (4.4.1) that I had on my desktop (which I’d been using for my other sites before this newest update, so I’m confident it was not corrupted or anything). But for some reason, even with 4.4.1 replacing the new 4.4.5, my site remained crashed. In fact, it is still that way and I’m attempting to get my hosting service to restore my site to before all of this 4.4.5 problems.
I would very much like to see if an Enfold technician can be anymore successful in updating my theme, but on a different hosted website.
Currently, both versions of Enfold are in wp-content/themes folder: the folder “enfold” is the (working) 4.4.1 version. The “enfold-4.4.5” is the new version, but which is not working. (Note: if you rename enfold-4.4.5 to “enfold” to activate it, you will then see the error message on the live site and how it crashes).In Private is the access info and website address.
Hi,
I took a look at your site and renamed the theme folders so that the update was “enfold” and as you said, it crashed. I looked into the file & line number that was printed on the screen via the error message, and the file was missing about 100 lines of code. So I renamed the directories back and uploaded my own enfold theme to test.
This time enabling the update was successful, at least on the front end, I don’t have backend access, so please check it out and let us know.
If this is successful can you let us know how you ftp the files up?
I’m on Windows 10 using Filezilla with a explicit FTP over TLS connection.Best regards,
MikeHmm. I sent an update reply but it is not showing. Here it is again:
I found the problem per above. Envato wants a newly registered “Private Token” and not a re-generated “API Key”. Once I followed the Enfold instructions page on this I was able to (I think) get my Enfold to play nice with Envato. Thanks for your help.
Hi,
Glad to hear that this is sorted out now. I’m curious how you had been ftp’ing the files to your server that was causing the files to be corrupt?Best regards,
MikeThe FTP client that I was using is: WinSCP.
Though the setting differ a bit from what you had recommended, I changed the (default) “Encryption” setting from “no encryption” to that of: “TLS Explicit encryption”This may have been the problem all along.
Also, I’ve created a very detailed, step-by-step procedure tutorial that I’m now using for my other Enfold upgrades. So, I may be okay now.
- You must be logged in to reply to this topic.