Today’s Update CRASHED our whole site!

Hi @1waytoheaven

I’m sorry to hear that you are experiencing this issue.

When this update was made on the site, does any other updates have actions as well? Like:
– theme update
– other plugins updates
– WP core update

Also are you able to create a staging site and replicate the same issue and let us know about the results?

Kind Regards,
Kris

Thank you for responding Kris.

The WP core was updated to the latest last week or so.

No other plugins were in need of updating.

I use the Neve theme and it needed an update today, but I first updated Forminator alone. Then it took 45 minutes to upload the prior Forminator release from my backup. That is the longest time period our site has ever been down.

Once I’d done that I could access the site again, and then updated the Neve theme.

I do not have a testing site, and will remain on the stable version of Forminator.

I update all my plugins as soon as I’m notified in WP Updates, and have never had any other plugin crash our site.

Hi @1waytoheaven

I understand your point on this and I’m really sorry that you are experiencing the issue.

However, it’s not “as simple as that”. Due to the very “nature” of how entire WordPress “ecosystem” is built, there’s always a chance that in some particular cases “something” specific may be conflicting or even crashing at some unexpected point.

What I did just now was:

– on my clean test I’ve installed Neve theme (as you mentioned it) – the free version that I found on their official site and activated it
– then I installed and enabled 1.14.12.1 version of our Forminator (taken from here: https://www.ads-software.com/plugins/forminator/advanced/ – form at the bottom)
– then I just run a regular update

No issue, no crash.

I fully understand that this is happening to you and I’m sorry that you are experiencing it but there must be some additional reason for such crash. Usually it would be either some resource issue or some unexpected conflict with other plugin.

We’ll be more than happy to find solution, regardless whether it’s specific to your setup or it’s something that needs to be fixed in Forminator’s code but we’d need to identify it first.

Neither my colleague previously, nor I now – we couldn’t replicate that issue and we’d appreciate your help on this so we could make the plugin better and make it work for you.

I understand that you don’t have any staging/testing site and don’t want to set one specifically for this case and I’m assuming that you may not want to go through the “crash/restore” process again so maybe you would be able to e.g. look into PHP error logs and see if there are any errors logged-in around the time you performed that update?

Also, some additional information could be helpful:

– webserver
– PHP version
– PHP memory limit

that you can find on “Tools -> Site Health -> Info” page in “Server” section

and

– WP_MEMORY_LIMIT

that you can find on “Tools -> Site Health -> Info” page in “WordPress Constants” section.

Knowing a full list of active plugins on site could also be helpful if you’d be willing to share it.

All that info would help us test it way better so hopefully we could replicate the issue and that would then help us find solution.

Kind regards,
Adam

Thank you for responding and testing.

I checked the WP error_log and there haven’t been any php errors of any kind lately…

Apache Version 2.4.48
PHP Version 7.4.22

Your test of the “Neve” theme tempted me to try to update “Forminator” again…

You’ll be pleased to read it completed smoothly ??

I can think of two other factors which may have precipitated this;

1) We use the “LiteSpeed Cache” plugin, and we are on a LiteSpeed server. The server is solid, but the plugin is very sensitive, so may have baulked the Forminator plugin update.

2) I’m in the mountains of Asia using public wifi. The monsoon, and router auto-switching could have interrupted the Forminator update.

So let’s put it down to those this time.

Please bear in mind that for a plugin governing contact forms; Stability is far more important than new “features”.

Hi @1waytoheaven

I actually tested it (not on purpose, pure coincidence, but still) on a LiteSpeed server as well, though without the plugin enabled. Might be that there’s a different configuration then.

But I’d say that it’s actually quite possible that both these factors (cache and/or connection quality) could have participated in this. We do test each and every version extensively before publishing update, free Forminator is installed and active on over 200k sites and there’s additionally entire Pro branch too – and we didn’t have any such reports.

So I’d tend to believe that this was quite an unexpected “one-time glitch” caused by kind of “unfortunate circumstances” but please don’t hesitate to update us if anything like this ever happens again. This is important feedback so we always want to know about such cases.

Best regards,
Adam

Hello @1waytoheaven!

Hope you’re having a good day!

As there was no activity on this ticket for a bit, I’ll mark it as resolved for now.

If you need any further assistance, please feel free to reopen it and post here any time.

Kind regards,
Pawel