Hello, this plugin is causing the Divi Builder in the backend to Time Out so I am unable to edit any pages… It is definitely narrowed down to this plugin… Doesn’t interfere with the visual builder that I know of, though I don’t use the Visual all that much… To clumsy for me…
It started happening after the last Divi update… Possibly the update before, didn’t discover it right away…
I am using this plugin and your PayPal IPN for WordPress plugin together… The IPN plugin is not causing the issue, though they both may need some attention…?
Would really like to keep using these, and so hoping you will update them to the current Divi circumstances…? You can be confident of a shining review for both if you do…
- This topic was modified 4 years, 6 months ago by crzyhrse.
- This topic was modified 4 years, 6 months ago by crzyhrse.
The page I need help with: [log in to see the link]
I use WP Rocket, no CDN… As far as I know WP Rocket does’t do any caching on the backend, don’t believe any caching plugins do…?
But in any case on the test/dev site that I migrated the live site to, to explore this, when I found that short pixel was involved I deactivated all plugins but short pixel and this one… And the issue remained… So no caching involved…
Thing is, on all my Divi sites, with well over 100 plugins between all the sites, short pixel is not mixing with any other plugins to cause this issue… Not one incident… It only mixes with your plugin on this one site (now two with test/dev site) that your plugin is installed on…
I just want to see this fixed so I can keep using your plugin, am not concerned with assigning fault… This does seem to be pretty weird, and a bit varied in its behavior… The issue also does seem appear in a lot of different and varied circumstances with Divi, if one searches for it in the Divi forum… And Elegant Themes constantly updating Divi with new features and significant code changes doesn’t help, I suspect…
I believe it may be the middle of the night where the short pixel folks are, but hoping we might hear from them at some point…
Believe me, I want to get it resolved, too. On the one site where you’re having this problem, have you tried it with everything disabled except for ShortPixel? Including leaving our PayPal for Divi plugin disabled?
In my reply early on that identifies short pixel as the plugin yours is linking up with I also indicated, though maybe not explicitly enough, that “When just the two of them are active the issue occurs… When either by themselves is active it goes away…” In other words either plugin by themselves, no other plugins active, there is no issue… When both are active and no other plugins active the issue is there…
I’ve4 suggested this a couple times already and will do so again, well over a hundred active plugins spread between a dozen Divi theme sites short pixel is active on, this only occurs with your plugin… Why is this not significant to you…?
And something else I believe it is important to note here.. It is only your plugin that is coded to insert itself directly into the Divi theme, as a module that can be selected… Right in the Builder… In other words it is interacting with the Divi theme directly in some very significant ways…
Your plugin has not been updated in over ten months, and in that same period Divi has been updated and had major changes and features added to it several times, including a very significant update and features addition right before this began, and WordPress has had a ver major update since your plugin has been updated as well…
Why are you seeming to not be considering all of these past points here…?
@crzyhrse, We are certainly considering the points you have made, and we appreciate your effort finding and providing details that you have.
The issue is that we seem to be having a different experience, and this makes it difficult to troubleshoot. So let’s break down the current things that we know at this point.
– You were able to pin-point the problem seems to come from ShortPixel, and in your case it only happens with both ShortPixel and our PayPal for Divi plugin enabled at the same time.
– We were able to reproduce the problem with ShortPixel both with and without our PayPal for Divi plugin enabled.
– In our case, adding the snippet provided into htaccess seems to have resolved the issue, however, when you apply the same change it does not resolve the issue for you.
In most cases when something like this is going on the same procedures would be reproducing the same things on both ends. In this case it seems to be a bit all over the place. The only common variable we have here is ShortPixel plugin. I have yet to get a response from them, but I would imagine that’s because of the weekend / holiday. I see they typically respond quickly, so I would expect to hear back soon, and maybe they can help shed some light on this.
In the mean time I am indeed going to continue digging on our end. There is only so much I can do, though, when I cannot reproduce the problem as you have described. What I will do is put together some video of our experience so that we can provide that to both you and the ShortPixel developers.
I agree with you that it seems like our plugin would be the culprit since it’s the one interacting with Divi modules directly, however, you have confirmed that the problem doesn’t come up until ShortPixel is introduced to the equation, and again, we are able to reproduce the problem with ShortPixel alone, without our plugin involved at all.
So again, the randomness of all this is proving difficult to troubleshoot. We aren’t going to give up on it, though. I will let you know when I have more info after playing with this some more.
After playing with this some more we are finding that the issue comes up even without ShortPixel installed sometimes. Still, though, it’s all very random and we haven’t been able to track down rhyme or reason to what’s causing it. Sometimes it happens with both enabled, sometimes it happens with only ShortPixel enabled, and sometimes it’s happening with only our plugin enabled. Sometimes, though, it works great under the same various tests.
So I still don’t have an answer here, but just wanted to let you know that we are finding the problem in lots of different ways, so we’re continuing to dig to figure out what exactly is triggering the problem.
I gave short pixel access to the dev site, but before they were able to get in and see it Some interaction with my hosting seemed to fix the issue…
This error was coming up over and over in the cPanel logs:
[Sun Dec 31 06:57:43.671551 2017] [:error] [pid 861636] (12)Cannot allocate memory: [client 188.8.131.52:54037] couldn’t create child process: /opt/suphp/sbin/suphp for /home/spiritdesigns/public_html/index.php, referer: https://www.spiritdesigns.life/wp-admin/post.php?post=2&action=edit
When we turned off Mod Security rules the issue went away, and then amazingly, with mod sec rules back on the issue now remains gone on both sites… I’ve been on both for a couple days off and on, working around, and it has not come back… Backens of pahes updating properly every time… I wanted to let some time pass before letting you know, in case it were to come back…
My host owner says “by turning off and on mod security including the firewall, and restarting apache, it flushes out all old and the negative inquiries…” And that may have cleared what the plugin or plugins were interacting with…
I will watch this, no knowing know if one or both plugins in certain moments are triggering a mod sec rule…? If it happens again my host will check cloud linux and other logs, to see what caused it…. And I can turn off mod sec rules temporarily in the cPanel to see as well… Wish I’d known to do that earlier…
I am hoping some of this might be helpful to you, and so sorry for all the time we’ve all spent on this, though there has been some learning, at least for me…
@crzyhrse, I believe we have found the issue! With lots of digging we were able to pin-point the problem with the latest release of the Divi plugin, and we’ve made some adjustments to the JS cache storage that Divi uses in relation to our plugin that seems to be resolving the issue.
I don’t want to speak too soon since this has been so random and tough to troubleshoot, but we have not run into the issue again since making this adjustment. We’ll be running some more tests to ensure it doesn’t pop up again, and then we’ll get an update to our plugin released. I’ll update you again here once we’ve done that.
This is great, and wonderful to hear… And thank you so much for getting down into it…. There has been value come of all the effort… Yay…
Guys, before you close this thread, can I ask for your help: it’s been great following this thread. Especially as a small business owner who’s keen to see how others manage support issues.
But, I never actually, knowingly subscribed to this thread.
Each email I receive states “Login and visit the topic to unsubscribe from these emails”.
I’ve dove that, but still getting these updates. Can you suggest anything? I can’t find any relevant forum threads in which to ask, either.
@orchard800, I believe you made a comment previously in this thread which subscribed you to it. When you login now, on the right side, you should see an option Unsubscribe. You’re saying you already did that but you’re still getting the notifications..??
@orchard800, I don’t believe you have commented here…? I think this is a wordpress support forums issue or bug, I’ve seen it mentioned elsewhere as happening for others, more than once…
There should be an easy way to contact a forum moderator, but I don’t see one in briefly looking… There is a slack channel for wordpress moderators
but I believe one has to be invited to join…
Perhaps post in this forum,
and link to this thread for where the issue is surfacing…?
Ahhhh, I remember now… I don’t think we can delete our own comments though, doesn’t a moderator have to do it…? In any case, it’s not going to be solved here… 🙂
@orchard800 – go to the main support forum page for this plugin:
Click the “Unsubscribe from this plugin” button at the top.
- The topic ‘Causing Divi Builder in backend to Time Out’ is closed to new replies.