Title: Pete Wright's Replies | WordPress.org

---

# Pete Wright

  [  ](https://wordpress.org/support/users/hekai/)

 *   [Profile](https://wordpress.org/support/users/hekai/)
 *   [Topics Started](https://wordpress.org/support/users/hekai/topics/)
 *   [Replies Created](https://wordpress.org/support/users/hekai/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/hekai/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/hekai/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/hekai/engagements/)
 *   [Favorites](https://wordpress.org/support/users/hekai/favorites/)

 Search replies:

## Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [Divi builder time out](https://wordpress.org/support/topic/divi-builder-time-out/)
 *  [Pete Wright](https://wordpress.org/support/users/hekai/)
 * (@hekai)
 * [9 years, 6 months ago](https://wordpress.org/support/topic/divi-builder-time-out/#post-8736155)
 * Hey [@finemancomm](https://wordpress.org/support/users/finemancomm/) – did you
   try my quick-fix above? Here it is again:
 * a) Open wp-content/plugins/divi-builder/includes/builder/core.php in a code editor
   
   b) Find the line that says “$third_party_plugins_active = true;” – this is around
   line #1405 in the builder plugin, or around #1525 in a similar “…/builder/core.
   php” file in the Divi Theme itself c) Comment out that line by putting “//” at
   the start of it, as follows: “// $third_party_plugins_active = true;” d) Save
   the file and re-upload it – job done.
 * That line forces the builder to report a failure for no reason. It’s supposed
   to check for potential plugin conflicts. That *would* be a good idea, but it 
   doesn’t do that. It simply allows the builder, two ET updaters and the wordpress
   importer plugin and throws the error if it sees anything else, regardless of 
   whether or not it may conflict. So it’s a worthless check that just breaks more
   than it fixes. If ET can’t come up with a *real* check for conflicts, they should
   at least disable this line.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [Divi builder time out](https://wordpress.org/support/topic/divi-builder-time-out/)
 *  [Pete Wright](https://wordpress.org/support/users/hekai/)
 * (@hekai)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/divi-builder-time-out/#post-8441923)
 * Ah, line Line #1525 if you’re using the Divi Theme, apparently (thanks to scribblevision
   on the ET forums for finding that).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [Divi builder time out](https://wordpress.org/support/topic/divi-builder-time-out/)
 *  [Pete Wright](https://wordpress.org/support/users/hekai/)
 * (@hekai)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/divi-builder-time-out/#post-8441847)
 * Sad to say the plugin seems to be coded to report all other third-party plugins
   as though the Divi Builder failed to load if the current user has the “manage_options”
   permission.
 * [https://www.elegantthemes.com/forum/viewtopic.php?f=187&t=616273&p=3402002#p3402002](https://www.elegantthemes.com/forum/viewtopic.php?f=187&t=616273&p=3402002#p3402002)
 * ET need to fix this properly, but the quick-fix is to comment out line #1405 
   in wp-content/plugins/divi-builder/includes/builder/core.php as follows:
 * // $third_party_plugins_active = true;
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Login With Ajax - Fast Logins, 2FA, Redirects] Log in Freeze](https://wordpress.org/support/topic/log-in-freeze/)
 *  [Pete Wright](https://wordpress.org/support/users/hekai/)
 * (@hekai)
 * [12 years, 1 month ago](https://wordpress.org/support/topic/log-in-freeze/#post-5010236)
 * Okay, not a generic fix I’m afraid – my host had added custom WP-specific checks
   for security purposes and told me how to work around those. So the real answer
   may well be, “Contact your host.”
 * However, that may not be exactly what has happened in your case, so these two
   fixes may be worth trying as an alternative:
 * [http://www.tipsandtricks-hq.com/apache-mod-security-update-how-to-fix-error-406-or-not-acceptable-issue-259](http://www.tipsandtricks-hq.com/apache-mod-security-update-how-to-fix-error-406-or-not-acceptable-issue-259)
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Login With Ajax - Fast Logins, 2FA, Redirects] Log in Freeze](https://wordpress.org/support/topic/log-in-freeze/)
 *  [Pete Wright](https://wordpress.org/support/users/hekai/)
 * (@hekai)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/log-in-freeze/#post-5010134)
 * Hi apixel,
 * I’ve been getting this in the past few days too, so I checked the server response.
   In my case, the server is replying with 406 Not Acceptable – the server doesn’t
   think the browser will accept its reply. That’s rare, but apparently it can happen
   when a host beefs up its security. I’ve seen a huge increase in hacking attempts
   over the past 6 months, so that sounds likely.
 * Haven’t resolved this yet, the order I’ll be trying solutions in is:
    a) Contact
   host, see if they can resolve it (on shared hosting, this may not be possible);
   b) Try other plugins that *may* send a request more like the wp-login.php one;
   c) See if the code of LWA or the alternatives can be tweaked – think we’re looking
   at sending extra ‘Accept’ headers (or maybe the developer could take a look at
   that?); d) Switch hosting.
 * I’ll post back when I have this resolved. If you manage to fix it in the meantime,
   please likewise let us all know how.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] Akismet and wordfence…](https://wordpress.org/support/topic/akismet-and-wordfence/)
 *  [Pete Wright](https://wordpress.org/support/users/hekai/)
 * (@hekai)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/akismet-and-wordfence/#post-4720164)
 * D’oh – thanks, Dion, that’ll teach me for trying to be helpful in a hurry.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] Akismet and wordfence…](https://wordpress.org/support/topic/akismet-and-wordfence/)
 *  [Pete Wright](https://wordpress.org/support/users/hekai/)
 * (@hekai)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/akismet-and-wordfence/#post-4720092)
 * Worth watching this thread as WordFence tries to get this resolved:
 * [http://wordpress.org/support/topic/you-checked-in-code-to-the-258-akismet-tag](http://wordpress.org/support/topic/you-checked-in-code-to-the-258-akismet-tag)
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [zone alarm Security suite 6 creates login problem](https://wordpress.org/support/topic/zone-alarm-security-suite-6-creates-login-problem/)
 *  [Pete Wright](https://wordpress.org/support/users/hekai/)
 * (@hekai)
 * [19 years, 11 months ago](https://wordpress.org/support/topic/zone-alarm-security-suite-6-creates-login-problem/#post-414438)
 * Try enabling referrers for the site in ZA, and clean out your cache/unwanted 
   cookies (including any related to your WP site, of course). Seems to have fixed
   this for me, in IE – though the problem was erratic, so hard to be sure.
 * Otherwise, shutting ZA down completely during login and restarting it straight
   after seems to allow logins without that palaver, for a few hours at least.
 * I don’t get this problem with WP 1.5.1, but do with 2.0.3 – which is at odds 
   with this article:
    [http://codex.wordpress.org/Enable_Sending_Referrers](http://codex.wordpress.org/Enable_Sending_Referrers)…
   but may be related to the code changed at that point.
 * Incidentally, folks, shifting blame doesn’t fix a problem. Neither ZA and WP 
   appear to be doing anything wrong here – and firewalls that allow seamless CMS
   operation are not ‘better’ if they do so by being less secure. Several weeks 
   of running my own tests last year convinced me that ZA has few peers among other
   software firewalls.

Viewing 8 replies - 1 through 8 (of 8 total)