vark

Hi,
New version compatible with php 8.1 released 4 days ago….
Best,
Vark

Hi Bob,
Thanks for the update, sorry that your customer is experiencing the issue.

When you have them, please let me know the results of the full module conflict test described above.

Best,
Vark

Hi,
The WordPress plugin team required a rewrite of the plugin, just completed.
Best,
Vark

Hi,
Thanks for letting me know about this.
Wordpress.org is currently requiring a few changes for security purposes, and I’ll put in a fix for this at the same time into v2.0.3.
Best,
Vark

Hi,
This is a PHP8 issue.

We’re in final testing for the PHP8 release.

In the meantime, suggest downgrading to PHP7+ .

Best,
Vark

Hi,

———————–

Here’s the salient details, starting in May of last year

Vark VarkTech
Thu, May 20, 2021, 10:32 PM
to Pranav

OK, let’s start from the top.

1. There are thousands of licenses in use out in the world.
You are the only customer presenting this issue.
I cannot replicate the issue in my test environment.
Therefore, I conclude that this issue is unique to your environment.

2. You’ve presented a host of issues, most of which have had to do with:
a) an external pdf plugin
– out of scope for crossouts
– I tried to suggest using a coupon to present the discount, but you did not favor that solution
b) change of order status
– should not matter

3. you have presented that in your test environment, you have deactivated all plugins except
Pricing Deals free and pro
Woo
and switched to a clean, default theme.

Excellent.

———————–

In that same email chain, I documented a complete test in my test environment, showing
That I could not replicate the issue you reported.

———————–

You then sent, in October of 2021, another report of the same issue.

Here is my response in that chain:

Vark VarkTech
Oct 13, 2021, 8:34 AM
to Pranav

Hi,
We’ve had a long email exchange on this subject entitled
“incorrect Discount Price Crossout in checkout”
with the final email sent on May 25, 2021 .

I) A test was recommended towards the end of that chain:

1. add the ‘administrator’ role to the role list in the rule
2. deactivate this plugin:
WooCommerce Shop as Customer: by cxThemes – 2.10
3. retest while logged in as administrator.

II) If you have completed that test and not successfully diagnosed the problem,
Suggest a *full module conflict test*:

To track down a module conflict, please follow these steps ** PRECISELY **:
(1) Install and activate a maintenance mode plugin (if desired)
(2) Then, DO ALL (*at the same time*):
(-) do a full site backup!
(-) deactivate ***all*** plugins except Woo, my 2 plugins (and maintenance mode plugin)
(-) ** switch to a clean default theme like “twentynineteen” **
— (This removes all other possible conflicts.)
(-) turn off all deals except the one we are examining.

(3) ** close your browser completely, retest in a fresh, clean browser session **
(4) if good, add 1 module back in. ** Retest **
(5) Repeat until conflict identified.

** This test depends on following the outlined steps fully. **

Best,
Mark

(PS – If you do have a module conflict, it will likely boil down to choosing between the 2 conflicting modules…)

———————–

And again in February 2022, you repeated your report.
My response was as follows:

Vark VarkTech
Feb 16, 2022, 9:54 PM
to Pranav

Hi,
You’re using
WooCommerce PDF Invoices & Packing Slips: by WP Overnight – 2.12.1
to create your invoices.

Pricing Deals crossouts are tested with woo-generated invoices and emails.

Suggest a *full module conflict test*: (starting with the above plugin)

To track down a module conflict, please follow these steps ** PRECISELY **:
(1) Install and activate a maintenance mode plugin (if desired)
(2) Then, DO ALL (*at the same time*):
(-) do a full site backup!
(-) deactivate ***all*** plugins except Woo, my 2 plugins (and maintenance mode plugin)
(-) ** switch to a clean default theme like “twentynineteen” **
— (This removes all other possible conflicts.)
(-) turn off all deals except the one we are examining.

(3) ** close your browser completely, retest in a fresh, clean browser session **
(4) if good, add 1 module back in. ** Retest **
(5) Repeat until conflict identified.

** This test depends on following the outlined steps fully. **

Best,
Mark`

Update – issue was due to a module conflict.