Forum Replies Created
-
AuthorPosts
-
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!
May 2, 2016 at 4:29 pm in reply to: HTTP Error On Photo Upload With Go Daddy Managed WordPress #625903Code 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)
April 29, 2016 at 4:21 pm in reply to: HTTP Error On Photo Upload With Go Daddy Managed WordPress #624619PS 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?
I was so excited to see the code from Wildwood above since I have had this HTTP error for weeks now, and it has gotten much worse with the latest updates. Josue provided some code in another thread which eliminated most of the photo sizes, which seemed to temporarily fix the timeout issue but it is back with Go Daddy. This seems to impact photos of any file size, and at one time users were theorizing it was photos over a certain pixel width.
Right now, I have to get a page built and I am having a hard time uploading photos….. lots of HTTP Errors even though I added Josue’s code, other thread, and Wildwood’s code above, this thread, to my child theme functions.php, then cleared browser cache and Go Daddy cache.. I am so glad to see Kriesi is on this thread… I love this theme but this http error with Go Daddy is killing me.
If there’s something Go Daddy needs to do from their end, please tell me specifics and I can try that and report back.
Thanks,
RobSorry, but that is a ridiculous answer. Every time we load Amazon on mobile it works… there are not random errors on Amazon “like life”….
This problem keeps being discussed in multiple threads… Josue seems to be the expert on the “fix” which is just to remove most of the photo sizes, which is really a workaround.
Please, Enfold / Kriesi, fix this once and for all. The workaround is less than ideal and strips functionality from this theme.
April 26, 2016 at 6:57 am in reply to: Follow Up Transparent Logo not showing on Mobile News/Blog page #621929Hi – I’m receiving this same issue and the exact same error line 520…
All plugins are updated, WordPress latest version, and of course latest version of Enfold.If I clear my cache (Go Daddy Managed WordPress), the error goes away…. but then returns.
This seems to have occurred in the last 2 weeks since the last few updates.
This occurred tonight when I was trying to retrieve the Yoast sitemap for my site. It seems to also happen more in private browsing mode, where cookies are not allowed to be set / persistent.
Any ideas on what could be happening? I am seeing the error more and more, getting concerned.
Thanks!
April 22, 2016 at 10:47 pm in reply to: Mobile Header Looks Different In Private Browsing Mode in Safari on iPhone #620252Thanks for the response!
I cleared the Go Daddy cache and then reloaded the page and the error was gone… Enfold and Go Daddy seem like a fighting married couple sometimes… ha ha…. Go Daddy doesn’t let Enfold upload photos and displays these errors… I do wonder if there is some sort of cache configuration that needs to occur with Go Daddy to make it play better with Enfold? It seems like the HTTP errors (different thread you were helping me on) go away temporarily if I clear the Go Daddy cache, but then they come back about a minute later.
Thanks for your help…. I won’t worry about this since it’s just in incognito / private browsing mode and seems to go away when cache cleared.
April 22, 2016 at 9:38 pm in reply to: Mobile Header Looks Different In Private Browsing Mode in Safari on iPhone #620227Thanks Josue. I am seeing it on our other iPhone as well.
Today in “Incognito Mode” on chrome desktop I saw this error at top of page and menu froze:
“Warning: Class __PHP_Incomplete_Class has no unserializer in /home/content/p3pnexwpnas08_data02/27/2854827/html/wp-content/object-cache.php on line 520Warning: session_start(): Cannot send session cookie – headers already sent by (output started at /home/content/p3pnexwpnas08_data02/27/2854827/html/wp-content/object-cache.php:520) in /home/content/p3pnexwpnas08_data02/27/2854827/html/wp-content/plugins/optima-express/iHomefinderStateManager.php on line 35
Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /home/content/p3pnexwpnas08_data02/27/2854827/html/wp-content/object-cache.php:520) in /home/content/p3pnexwpnas08_data02/27/2854827/html/wp-content/plugins/optima-express/iHomefinderStateManager.php on line 35”
Cache cleared, all plugins updated.
Are the two related?
Everything works fine in normal mode where cookies can be set.
Thanks!
Josue etc did you have a chance to consider this solution I posted earlier on in this thread..:
“Open wp-config.php in your sites main directory via FTP (or cPanel)
Scroll to the line which reads /* That’s all, stop editing! Happy blogging. */
Add the code set_time_limit(60); above the line /* That’s all, stop editing! Happy blogging. */ text
This will override any conditions placed on your site by your host and you should now be able to upload images.””This fixed the issue but then I started getting errors (see other post) so I reverted.
If you could tell me exactly what I should ask Go Daddy to change on their side, I could call them and give it a try and then if it works post a step by step solution here to help others. Thanks
April 18, 2016 at 7:54 pm in reply to: Which slider should I use and how to I make it so it's not huge? #616757Great, I will try that, thank you!
I just have a concern about installing a 4-year old plug to manage all my media… one that is not updated regularly with security patches etc and one that is not available in the Word Press Plugin Library….
It really seems like Enfold should work with Go Daddy to at least give us some parameters of what to ask them to fix / change on their end… it almost seems like the uploads go faster than Go Daddy can handle and error out. If there were only a way to slow them down…
UPDATE:
I just found this discussion at WordPress support: https://wordpress.org/support/topic/media-files-cant-upload
This comment seemed relevant so i tried this fix on my staging site:
“This issue is being caused due to a restriction placed on your site by your web host. The reason why it appears with Minamaze and not other themes, is because Minamaze creates copied of each image you upload. The correct image size is then automatically used when needed to reduce page load speed time. As a result Minamaze needs longer to upload and create image copies.To fix this issue please speak to your webhost and ask them to increase the max_execution_time variable to 300 seconds. Alternatively, you can achieve this by editing your wp-config.php file for your domain. To do this please follow the steps below.
Open wp-config.php in your sites main directory via FTP (or cPanel)
Scroll to the line which reads /* That’s all, stop editing! Happy blogging. */
Add the code set_time_limit(60); above the line /* That’s all, stop editing! Happy blogging. */ text
This will override any conditions placed on your site by your host and you should now be able to upload images.”After modifying the wp-config.php file to 90 seconds (instead of 60) all pictures upload perfectly and it works like a charm!
HOWEVER – the bad news is that on the staging site this broke the functionality of the Full Screen Slider and those pages just display a big white box where the slider used to be. Feels like we are getting closer to a solution with the above if we can make sure nothing else is broken by increasing the timeout.
Can someone smarter than I am (most of you..) figure this out? (While the above support thread references a different theme, you’ll also see our beloved Enfold mentioned in the thread)
Thanks!
-
This reply was modified 9 years, 2 months ago by
goldengate415.
Josue, as I use the theme and continue to upload images and build pages, I am really missing some of the sizes that the above code removes… it seems like eliminating them is a workaround… is there a more permanent solution that allows me to use more of the photo sizes without http errors?
Thanks!
RobHi Ismael,
The page where this happens (with caption) on my staging site is:
http://82a.889.myftpupload.com/1292-sanderling-island-point-richmond/The page where I’ve removed the caption and where the pause actually works is on m production site at:
http://www.thomashenthorne.com/1292-sanderling-island-point-richmond/The only difference between the page that works and the page that doesn’t is I’ve removed the caption from the video in the page that works.
Does that help?
Thanks,
Rob
PS You should already have login credentials to the page that doesn’t work… they are supplied in this thread in private comments above. Thanks!April 10, 2016 at 7:57 pm in reply to: Full page video that scrolls into a text page possible with Enfold? #610814Thanks, I will try that!
One more question.. is there a way this can work not as a full screen video but just as a strip say 300 pixels high? I have tried modifying the code with lower pixels but it seems to default to full screen?
Thanks!
-
This reply was modified 9 years, 2 months ago by
-
AuthorPosts