jaxne

Thanks John!

I appreciate the response and extra information. Thank you!

I just ran into the same problem. We are running v1.7.12 of Popup Maker and Divi 3.0.106

When I updated Popup Maker to v1.7.14, the Divi Builder would not load and displayed the Divi Builder timeout message to go to plugins and disable them to determine the conflicting plugin. Thankfully the problem appeared on our staging site. I copied the previous version 1.7.12 back to staging.

ALSO.. I was still running into the DiviBuilder timeout issue even AFTER I reinstalled the previous version. After disabling other plugins I came across this thread at SiteGround where the site was hosted in case someone else runs into this.
https://www.siteground.com/kb/divi-builder-timeout-warning/

If you are running your site there (or maybe somewhere else) and are running into this problem, this fix siteground posted which you add to your .htaccess file fixed the problem.

The cause of the problem is that the Divi builder is reaching a certain limit applied to the Apache service. In order to resolve the issue that particular limit needs to be raised. To do that you should add the following lines in the website’s .htaccess file:

<IfModule mod_substitute.c>
SubstituteMaxLineLength 10M
</IfModule>

• This reply was modified 6 years, 11 months ago by jaxne.
• This reply was modified 6 years, 11 months ago by jaxne. Reason: Added additional details

Thank you for posting this limitation and fix! We have a product that had 44 variations and we were scratching our heads why it wasn’t showing the matched variation options. Once I added your function, it worked like it should. Cheers!

Just noticed a couple of hundred emails in my inbox of backups too after updating to 4.7.0 —

How do we set ITSEC_DISABLE_CRON_TEST in our wp-config.php file?

define(ITSEC_DISABLE_CRON_TEST, ‘false’);

Thanks! I saw the same thing and found your post about it here. The site that WF flagged is also on GD MWP hosting. Cheers!

@jack McBride — Managed Wp Hosting at GoDaddy only uses SFTP.

@Ronnie-Fantastic — Thanks for chiming back in. This is a very oddball issue. Windows 10 on my DELL desktop won’t work with that site. My DELL Laptop running WIN 10 does. It doesn’t matter which browser either … FireFox, IE or Chrome on my desktop. Got a feeling it’s something tied to the OS on this machine, either with the Firewall/Anti-virus software or some other software.

If I get to the bottom of it I’ll respond here. Thanks!

I forgot to mention one other odd-ball issue with the GoDaddy servers. I had tried to edit the wp-config.php file and increase the PHP memory limit. However when I tried to SFTP into that account and upload the new wp-config.php file. FileZilla is giving me a

Network error: Software caused connection abort. File transfer failed.

I thought this may be a locked WP file that GoDaddy doesn’t allow you to modify. SO… I tried a simple small PNG file upload to the wp-content/uploads/ folder. Got the same error.

I FTP’d into the Staging WordPress site and have NO problems uploading files there. Same file, same wp-content/uploads/ folder. VERY STRANGE.

This makes me think there is either something weird with the domain name or the configuration of the live Managed WP site at GoDaddy. I tried changing transfer modes in FileZilla as a test too (passive, active and default). Doesn’t matter still the same “Network error: Software caused connection abort”.

It’ just so strange why it’s only a specific site. I can access other WP Managed hosting accounts whether it’s FTP or WP Admin on GoDaddy just fine (same theme and plugins on other site too).

GoDaddy’s Managed WP accounts don’t have a control panel like cPanel or the like to view error logs unfortunately. Not sure if this sheds any more light on the subject.

I’m running into the SAME problem with one of my Windows 10 machines. I ran Google Chrome’s Dev Tools and watched the Network tab to see what the heck wasn’t loading in the WP admin. It is the load-scripts.php file that isn’t loading the Admin in full. The connection is reste. I too was on support chat for 45 minutes with GoDaddy yesterday and they didn’t see it either from their end. I disabled all plugins and even changed the theme to standard WP 2015 theme to see if it was a theme issue. Still the same thing… WP Admin not completely loading the load-scripts.php file.

I decided to open my Laptop and try it (also Win 10) and it ran perfectly fine there. I was able to make my edits and get my site live for the client. However going back to my main dev machine I noticed McAfee acting weird. I uninstalled it and the WP Admin started working on my Dev machine. I replaced McAfee with Kapersky as I had another license for it. Everything was working great yesterday and thought problem was solved … UNTIL TODAY. Same shit again. I paused Kapersky protection and disabled their browser plugin. But load-scripts.php still won’t load!

The weird thing is that the “Staging” site I was working on loaded perfectly fine on this computer. It’s the live site that won’t load and it’s only this site. VERY STRANGE. Makes me wonder if GoDaddy has some type of Firewall on their server that is blocking some script from loading on their server and resetting the connection and we can’t see that. However, for GD to realize this will be a matter of MONTHS I feel like.

Not sure what the hell is causing this issue, but it’s driving me nuts too!

If you’ve resolved it please post back here. I will continue troubleshooting this on my end too.

THanks!

I too received a Fatal Error on a site on the checkout page as the call was to a newer WooCommerce function to grab Order ID. Line 88 gets the order ID on the thank you page WooCommerce 2.2+ uses

wc_get_order($order_id)
My store was running WC 2.1 still which uses

new WC_Order($order_id)

I made a quick change to the integration.php file on line 188 in the plugin’s includes directory and everything is working.

I posted a private support message on your ticksy support site as I’m having similar issues. When page first loads, the news ticker doesn’t display. I have to refresh the page to get it to load. I just modified the script to use the jQuery document .ready vs. window.load and it’s loading fine now. Thanks.