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!

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?

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.php

So 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!!!

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!!

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.

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,
Rob

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.

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

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, 3 months ago by goldengate415.