After clicking the UPDATE button on any page that contains a Toolset Views block, I always get the "Leave site? Changes you made may not be saved" popup prompt whenever I try to navigate away from that page. Fortunately, the UPDATE button does save the content, but it's especially confusing for non-technical users, and it seems related to other documented and unresolved issues with Toolset and WP Engine (where this website is also hosted).
Also, I have been working with WP Engine support as well, and they've asked if Toolset could provide outbound IPs so that they could look into whitelisting via web rules. They think this might be related to json requests or something, but I'll admit that I'm out of my element here. Could you provide the outbound IP that they're requesting?
Hello. Thank you for contacting the Toolset support.
What if you try to whitelist all the following URLs and try to get IPs using the following URLs. You may do nslookup to get the IPs.
- toolset.com
- api.toolset.com
- d7j863fr5jhrr.cloudfront.net
I used nslookup to get the IPs, and I had WP Engine whitelist them. They were not able to whitelist the domains for some reason.
Unfortunately, the issue persists after these changes. In addition, the UPDATE button is now greyed-out and cannot be clicked after editing the content. Prior to whitelisting the IP addresses, I was able to save and update successfully, but would constantly get the "Leave site" popup when attempting to exit the page.
In that previous support thread, Waqar stated that Toolset would not be prioritizing a solution to this issue, but it seems that the problem is more common than he might have realized. Apparently, WP Engine says that they have numerous reports of Toolset not working well on their platform. In fact, there's even another WP Engine customer reporting the same issue in my previous support thread. And these other support threads seem to indicate a similar problem, and some of those threads even mention WP Engine specifically. Unfortunately, none of these threads resolved my issue, but they all seem to be related, and might provide some insight.
Either way, being that WP Engine is a very popular hosting platform, I would think it would be very important and helpful for all parties if there were a solution to this issue. It seems that WP Engine is willing to work with me (and Toolset) to resolve these issues, so I'm hoping Toolset is willing to do the same.
If that will be the case - we should be getting thousands of tickets reported but this seems to be very specific with your server permissions/rules or how its setup.
To verify - you can also try to make a test and move your site to another hosting server and check if you get the same issue which you can currently. I see there is enough time devoted before with your ticket but without much luck.
To be clear, this problem exists on EVERY website that my clients host with WP Engine (which is currently over 30 websites). In fact, I just created a brand new install on my personal WP Engine account (with only Toolset Types and Toolset Blocks installed), and Twenty Twenty-Four as the theme, and the same problem exists.
I'm not sure if this is related, but it seems that the problem *might* only exist if an image block is included in the Views block. In my latest install, I was able to update the pre-installed "Sample Page" with a Views block, but as soon as I added the Toolset Image block, I was no longer able to update the page without getting the "Leave site" warning.
I'm happy to provide login details for that install if helpful.
So, I must disagree that this is very specific to my specific server/install. I don't have a single website hosted on WP Engine where the Toolset Views block works without issue. WP Engine acknowledges the issue, but puts the "blame" on the Toolset plugin. Toolset also acknowledges the problem, but puts the "blame" on WP Engine. Ultimately, it seems that WP Engine and Toolset are not compatible. Would you disagree with that statement? If you disagree, I would love to see an example where this problem does not exists.
WP Engine seems willing to continue working with me to resolve the conflict, but we (myself and WP Engine) don't know enough about how the plugin works regarding the "saving and updating" mechanism to troubleshoot. Is Toolset willing to work with me to resolve this issue? Or at minimum, would you all be able to give us some ideas for things we can/should check regarding the server configuration?
Do you see the same request when you save add/save page or image block?
You can also share the problem URL where I can see the issue as well as admin access details so I can investigate further.
*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.
I have set the next reply to private which means only you and I have access to it.
I've escalated the issue to our next level support. They will try to dig further. I will get in touch with you as soon as I have any update to share with you.
Hi Minesh, I'm still working with WP Engine support as we continue trying to troubleshoot this issue, and they suspect (but not confirmed) that this could be due to the "long process killer" on their server. Whenever they disable the LPK, the block editor for pages with a Views block would not load, and would eventually get a 502 error. Here is the response from WP Engine support:
"Since you are on a shared plan we cannot leave this deactivated because it can effect other customers on the server.
I did disable it to try and test again however when waiting for the page to load the server load spiked so I then had to disable it again and it is still getting killed.
I just want to check if you have heard anything back from the Toolset support. The long process killer would be 60 seconds so something in the plugins is running longer than this which is why that is getting triggered.
Does the plugin require any nginx configuration to work as expected?
Any information you can provide us with would be helpful. But at the moment we can't keep the LPK disabled as it will cause errors throughout the server."
Can you comment on their observation that something with the plugin may be running loner than 60 seconds? Or anything regarding the NGINX configuration?
Our Devs will try to focus on this issue very soon and will try to improve this where possible. We have internal ticket related to this issue but please note that there is no ETA on it.
I will get in touch with you as soon as I see any update with our internal ticket.
