Stephen

Let me tell you what the “real” issue is… you never informed us that a third party plugin was being installed when downloading a template.

A simple disclaimer with a check box would have been all you needed to present us when we clicked on a template.

I understand the need for supporting plugins because many themes require additional plugins to be installed to enable the theme to function properly, but those get manually installed by the Administrator so we know what they are and why they are there. If I change a theme, I can safely delete those extra plugins. No fuss!

I think it’s very wrong for you to be modifying our WordPress installations without our knowledge or permission.

In my case, it “magically” appeared on 3 websites I manage and you won’t believe the hours I have wasted trying to figure out where it came from, what it does and if I can safely delete it – time I can not bill to my clients.

You need to have a think about how this plugin gets installed and how you communicate this to us.

• This reply was modified 2 years, 4 months ago by Stephen.

Ah-hah! Thank you. That is exactly the problem.

All fixed. Thank you!

Hi. I’ve also experienced this problem many times. It always happens after updating WooCommerce and I have tried the WooCommerce Admin plugin without any success.

I don’t know what happens, but 4 or 5 days later the admin dashboard starts working again. Go figure…

It’s not browser speciffic because when it happens, it happens to multiple admins, not just to me in one browser.

All I can imagine is that there is some form of caching in the hosting that is keeping an old script running instead of launching a new one. I don’t have any caching in my site, but I know my hosting supports it at server level because I have dedicated WordPress hosting from a very big hosting company with all kinds of fancy optimizations to boost its performance.

It’s terrible advice and hardly a proper solution, but just give it a few days and see if it bounces back.

If you do come across a solution, please post it here. This glitch happens to me so often that my toes curl every time I see a WooCommerce update pending.

@corrinarusso

Loads of people use a WordPress + WooCommerce plugin for their online shop which I personally never recommend.

We had quite a stiff discussion in the office overthe best solutions.
The programmer wanted to write his own custom shop which seemed rediculous.
The boss wanted WordPress + WooCommerce because their old shop was done that way and he had no problems.
The social media guy wanted Shopify because it’s popular with his mates.
I was on the fence preferring Prestashop because it’s like having a dedicated WooCommerce without the WordPress layer.

The boss won, but I feel like it has ended up giving us the most problematic, vulnerable, high-maintenance, hosting critical, eCommerce solution of the bunch. (but to its credit, this is the most widely supported solution, espcially with third party companies like couriers)

I know this is a WordPress forum, but I’m curious what platform you prefer. I come from a graphic design background, not a programming background so I’d love your technically-driven insight. (And Pleeeeeeeaaaaase dont say Magento – it was so difficult to set up that I had to hire programmers on Fivr just to install plugins)

Thanks everyone. These have all been fantastic, understandable answers (and a special thanks for not telling me I’m just being stupid).

All features in the a2 Optimize plugin have been turned off. Both caching features in it are turned off.

A2 has confirmed that there is zero caching taking place. An off-site cache scanner (https://cache-checker.com/) also confirms that there is no caching taking place.

It is a Litespeed server because it’s intended for WordPress.

We did speak to our courier about their plug-in. They claim there’s nothing wrong with their plug-in and the problem must be coming from WooCommerce.

The process is as follows:
1 – An order is made in Woo. Checkout redirects you to the payment gateway.
2 – Payment is made in the payment gateway (nothing special soo far)
3 – You are redirected back to the Woo site and presented with a “Thank you for your business” page.
4 – The generation of this page triggers the courier’s plug-in to send the details of the order to their system.
5 – A deliverry order is created. A waybill number is generated.
6 – The waybill number is pushed back to the Woo site where it can be seen in the order notes.

During this process, our courier is receiving 2 communications which is generating 2 delivery orders each with their own waybill.

We have absolutely no caching running anywhere so it’s not a possible duplicate cached order that’s receiving payment confirmation twice. We are also running the site as lean as possible with the bare minimum of plugins so we’re practically running “Stock WooCommerce”.

We all agree that a courier should NEVER allow 2 delivers for the same order number and their system should not allow double waybills, but that’s not going to change anytime soon. They are pointing their finger at our site, not at their plugin.

Quick update to the problem. We have identified what’s going wrong, but not what’s causing it…

My hosting server is deleting the file “crp-front-tiled-layout-colorbox.php” because it is identifying the file as a virus, so every night when it performs a scan and backup, it deletes/quarantines it.

There is something in your code that an anti-virus doesn’t like – something that should concern you because it’s going to negatively affect your plugin’s reviews.