denrossww

Disabling ESI fixed the issue. We had 3rd party developers install and configure the LiteSpeed cache for us, so I’ll ask them if this is required to be on for any reason, if it is not then we will leave it off.

Many thanks.

That is great news. Thank you

Many thanks.

WCFM seem to know of the issue, so others may have reported it WCFM as well.

We will stick with Post Expirator 2.4.1 for the time being.

We import approx 150 products weekly using a custom import file. This also has the Post Expiry Date & Time using a custom php on the import file to ensure the products are set to private at the specific date/time. So maybe best to stick with what works for this reason too!

Thanks again.

Hi Steve

Yes, technically it is on the front end. WCFM is a vendor platform for WordPress/WooCommerce. Each of our vendors have their own unique products which are available until 5 minutes before their class starts (they sell online classes as products in conjunction with zoom).

The WCFM gives a frontend back office view so that Vendors can log in to WordPress and view their products and edit them themselves using the marketplace interface without being allowed to see the admin toolbar.

So they log in and click on a product using WCFM interface to edit the product, but because the latest code of Post Expirator is conflicting with the code for WCFM (www.wclovers.com) it causes a php error and distorts the view.

I have reverted back to Post Expirator version 2.4.1 as it works OK with WCFM’s latest version.

So I cannot disable Post Expirator for Products, because the product must expire 5 minutes before the zoom class begins because they must not be able to accept sales after the class has started and it must disappear from the website so it can’t be purchased. It is the only reason we use the plugin.

Many thanks.
Zoe

Further update: WCFM have referred me back to the developers of Post Expirator. Please could anyone advise? Thanks in advance.