Forum Replies Created
-
Posts
-
Sorry that didn’t help…. can you do me a huge favor and tell me where I can find 3.5.2 to download?
I am having some major problems and need to revert unless support can fix.Thanks!
robYou may be seeing a cached page…. clear cache and try again… also try from different computer / mobile or using private browsing / incognito mode. If you deleted the old directory and uploaded the new Enfold it should solve based on what the rest of us have been through.
There are many many support threads with this exact same issue. For some inexplicable reason, there is no sticky thread on this and there is no updated version of Enfold which deletes the offending files which create this error. So we see more websites crashing day after day.
You have to delete the current Enfold folder via FTP and then upload the latest version of Enfold via FTP. If you do not delete / rename the Enfold folder, it will not work.
Good luck.
Vinay, I’m watching all these support threads for the same issue on 3.6, which I personally experienced yesterday.
Are there plans for a 3.6.1 version that deletes or overwrites the old files so people don’t have this issue with the upgrade?
Seems like a lot of unnecessary trouble for everyone, support and users alike, with all due respect.Your site does look great! Congratulations on getting it back up!
(by the way, if you want to get rid of the “theme by Kriesi” message in the footer, go to Enfold settings, then footer, then put [nolink] after the end of the copyright in the copyright box)
Unzip it to your desktop and then copy the folder over to your subdirectory… if you upload a zipped theme it will not work.
Rename the Enfold folder “Enfold Old” and upload the new Enfold folder from Themeforest.
There is a bad file in there that is not being deleted when you simply copy to that directory.. so you must get rid of it by deleting the old Enfold.Yes many of us are going through this hell today and for some reason they haven’t stopped this update.
You have to go into your site via FTP, delete the Enfold folder, and upload the new Enfold folder to your directory.
Good luck.
Happy Monday!
Actually in this case a plugin will not help because you can’t access the backend of the site when it crashes… no access to plugins or admin screen. :(
Linortek, try renaming the folder “Enfold” to “Enfold Old” and then upload Enfold to your directory.
What was strange was I updated my theme in my test environment and it worked fine… then when I copied it to the production environment it crashed the site. I think this is because one of the old files was causing the conflict and was not deleted when the staging site was migrated to production. Deleting the Enfold theme folder via FTP and uploading it fresh fixed it.
OK I am back up after a terrible 60 minutes of downtime…. Even Go Daddy’s restored backup didn’t fix the issue, which they are now researching.
I copied the Enfold new version via FTP to the themes folder and now I am back to normal.
I have updated Enfold several times and have never run into this. There is something wrong with this update version in my humble opinion.
Whew, I feel like I just had 20 cups of cappuccino!
If you take this approach, do you have to restore all the old settings in Enfold? I have Enfold Child as well….
This is a nightmare. My site has been down more than 30 minutes now.
Thanks Basilis!
Unfortunately, error also occurs when I try to access admin panel. I cannot access the back end to the site.
I am on hold right now with Go Daddy trying to restore a backup from last night.
I do not understand why the update works fine in my staging site but not in my production site when copied over. I have never had this happen before.
Any other ideas?
Thanks
RobI upgraded and my site is working fine… but I do not use Mailchimp. From the errors it seems like it might be an integration issue. Have you tried deactivating the Mailchimp plugin temporarily?
Sorry.
But here’s the deal:
This issue keeps being raised in threads every day… so perhaps create a master sticky with the latest on the solution to the HTTP error as it continues to evolve. Josue had a workaround that worked for a while (smile) and then stopped…. now this latest mod to the functions.php seems to be working… for now.
In the case of this thread, Wildwood began helping us as the mods were busy elsewhere. His proposal for the user.ini file was part of the solution as far as working with Enfold and Go Daddy.
But noted, it is your forum so of course I will of course respect your request.
Many thanks for all the help!
Code from Yigit in another thread fixed it… not sure if this is the same code Wildwood provided in post several pages back on this thread:
add_filter( ‘wp_image_editors’, ‘change_graphic_lib’ );
function change_graphic_lib($array) {return array( ‘WP_Image_Editor_GD’, ‘WP_Image_Editor_Imagick’ );}In past it has been “fixed” but then has come back. I hope this time it’s really fixed permanently. Since this issue does not impact other themes, Go Daddy just tells me to switch themes, which I do not want to do since I love Enfold.
Thanks
(for those searching who have this same issue, you have to make the mods earlier in this thread via FTP, then at the very end add this code to functions.php)
PS I just tried to upload a photo and got a new error in addition to HTTP:
“Fatal error: Maximum execution time of 30 seconds exceeded in /home/content/p3pnexwpnas08_data02/27/2854827/html/wp-includes/class-wp-image-editor-imagick.php on line 358”
You might want to join us over in this thread and see if Enfold can help us solve this problem…. and perhaps some of the fixes will work for you (they did not for me):
https://kriesi.at/support/topic/http-error-with-media-upload/
Thanks… that did not help…
Go Daddy documentation:
“Managed WordPress accounts currently cannot end their Web or PHP processes. Because of this, you cannot easily refresh your PHP settings if you use php.ini, which drives our recommendation to use .user.ini files.”
There is a lot of great info in this thread… Enfold? Any ideas?
I spoke too soon.
When I moved these mods into my production site, the problem is back.
I think I know what’s going on but I do not know how to fix it.
Go Daddy Managed WordPress uses mandatory caching — it’s built into their Managed WordPress platform — and something about Enfold / Media uploading and the Go Daddy Managed WordPress Cache is not set up correctly. This is why the above solution works on my staging site but not on the production site. Go Daddy does not use caching on the staging site.
Enfold support, can you help us figure this out? And Faye is your problem still solved – have you tried to upload 15-20 photos at once? Enfold team, if you tell me to call Go Daddy, they will say this is an issue with my theme and to go back to you…. please help!
Thanks
Thanks Faye.
I got it all working on my staging site — all HTTP errors gone!! I just did a massive upload of 30 pictures which in the past would have caused errors like crazy, and it worked like a charm ,with ALL photo sizes again working and loading.
Here’s what I did:
– Deleted Josue’s mod (above) from the functions.php
– Added Wildwood’s mod to functions.php in my child theme
– Added user.ini with above parameters from Wildwood to root directory of my staging site using Filezilla
– Added lined of code above from Wildwood in functions.phpSo far, so good in my staging site… I am going to keep using the site to make sure nothing else broke as a result of these mods and if all is OK I will push into production….
thank you so much Wildwood and Faye!!
And if anyone from Enfold is still watching this thread… please… this comes up a lot and will come up more as more and more of us move to Go Daddy Managed WordPress… put together a tutorial for people to make these changes, or perhaps figure out a different way to achieve the above result through the theme.
Thank you!! So happy this is fixed!!!
I tried the above mod in functions.php and also tried removing the earlier code from Josue:
function ava_image_sizes() {
remove_image_size(‘masonry’);
remove_image_size(‘magazine’);
remove_image_size(‘widget’);
remove_image_size(‘featured’);
remove_image_size(‘featured_large’);
remove_image_size(‘extra_large’);
remove_image_size(‘portfolio_small’);
remove_image_size(‘gallery’);
remove_image_size(‘entry_with_sidebar’);
remove_image_size(‘entry_without_sidebar’);
remove_image_size(‘square’);
}
add_action( ‘after_setup_theme’, ‘ava_image_sizes’, 11 );No luck… still HTTP error….
Does it take a while for the modified functions.php to take effect?
Hi Wildwood, I don’t think any of us expect Go Daddy to fix this… but the excellent support team have thrown out a number of options over the last few months to fix this issue. Some of them work for a while (Josue’s reduce the picture sizes in functions.php) but most did not, at least for me. The aforementioned fix has stopped working with the latest updates.
What would be great is if someone from Enfold could speak to someone from Go Daddy to help diagnose and figure out what’s going on… and then give us all a recommendation on settings, or better yet make a patch to Enfold. If that’s unrealistic, I would be happy to give someone from Enfold access to my staging environment so they could play around in a Go Daddy environment and try to find a fix that they can push out to everyone.
Still need to look at your suggested fix… When I increased the max upload time before it caused some other problems and “broke” the site so I’m a little nervous about that one.
Thanks!!
Yes, Faye, I agree… I hope Kriesi takes this one on, but I’m guessing he’s busy with all the upgrade issues… I would consider this an upgrade issue since it worsened significantly during the last upgrade.
Are you on Go Daddy Managed WordPress or just another regular plan?
I haven’t made the mods yet but I do seem to be getting a new error when trying to upload….
Fatal error: Maximum execution time of 30 seconds exceeded in /home/content/p3pnexwpnas08_data02/27/2854827/html/wp-includes/class-wp-image-editor-imagick.php on line 383
Sigh.
Wildwood, no the original code you gave a few posts ago did not make a difference… I wonder if that is because I am also using Josue’s code that stripped out some of the photo sizes? I am going nuts right now trying to get a page up so can’t try the above suggestion but will give it a little time later today. I REALLY appreciate your help!! Thanks, Rob
PS Looks like I will need to Filezilla in to try the above, right?
