Plugins conflict after update

If you recently just updated the Display Widgets plugin, that may be the problem. Check out the forums for the Display Widgets plugin, there were some bug issues in last update… There has been a new update in the last hour that seems to fix those problems.

Display Widget plugin is not a problem for me. A lot of similar ones.
But, I could not solve conflict with Saphali Coupons. As soon as you are registered user, it gives maximum discount. Seems like some request to wpdatabase are similar to SEO Framework.
I want to use your seo plugin as I found it great. But, for now it’s deactivated, to avoid conflicts with coupons.
Do you have any idea how to solve it?

Hi @limchik,

I couldn’t find any compatibility issues with Display Widgets and The SEO Framework.

I am unable to test Saphali’s plugins, as they’re premium-only. So, I can’t report any cause for conflict.
What’s the exact name of their premium plugin, is it “WooCommerce Progressive Discounts”?

In any case, I took the liberty of sending a mail to Saphali, notifying them of this issue.

Well, I got hired as a messenger:

If the problem is with our client, then let him contact us with the screenshots of the coupon settings, as well as the system report (Woocommerce -> system report).

It’s out of my hands now, as I haven’t acquired any more information. ??

Hi Sybre,
Thanks for replays. I did contact Saphali as well. Problem is still not fixed. Hope they will do.
Last question to you. Is there any possibility to downgrade? As, previous version did work without conflicts.

Hi @limchik,

That’s possible:

1. Go to the advanced view of the plugin page.
2. Scroll down to “Previous Versions”.
3. Select the one you’d like, and hit “Download”.
4. Open your favorite FTP client, and connect to your site.
5. Go to /wp-content/plugins/autodescription/ and replace its contents with the older version.

TSF maintains a backward compatibility record for up to 2 major (x.x) versions. So, you’re safe to downgrade all the way to 2.7 ??

For completeness: This can only go wrong if the transfer settings of your FTP client have been reconfigured to send PHP files as ASCII instead of Binary (I’ve seen it happen…).

Thanks a lot??