Expired Specials active even after being deleted and/or RED status

[RixStix]

I just realized that a few products were showing to be discounted.
Reviewing specials, those products were special but expired in 2014. Status box is RED.
Deleted the special and discounted price is still showing in red with original price struckout.

Other than that, I have done no troubleshooting.
zc1.5.4 upgraded from 1.5.3 in July 2015 by uploading the zc1.5.4 changed files after verifying no core edits to those files.

This is one where the special has been deleted
http://chainweavers (dot) com/index.php?main_page=product_info&cPath=1_13&products_id=647

Ideas? Things to check?

[Ajeh]

Is that possibly using SaleMaker on that one ...

[RixStix]

No, not in Salemaker.

Since I just noticed the issue, it could have been present prior to the upgrade from 1.5.3 to 1.5.4.

[Ajeh]

Edit that Product and check its master_categories_id ... sounds like it "thinks" it is in a SaleMaker Category ...

[RixStix]

Edited each product that is showing a Red, sale price by adding a dot to the product description.

Category ID = 13

Product has attributes but attributes do not affect pricing.
Product priced by attributes = NO

We seldom use Salemaker or Specials since most of our products are priced by attributes. We have to use coupons because of attribute pricing. That is why no one has noticed the problem (except customers who have been getting a discounted price for quite some time).

Heck, this could go back to pre-1.5.3 update which was performed Aug 2014. Specials end date was May 2014

[Ajeh]

Just to double check ... can you peek at your SaleMaker and check that none of them might include the master_categories_id that is on these Products?

[RixStix]

It'll have to wait a few minutes. There's more than that now. Got a call to rush home 'cuz every item in one master category is now being discounted that %. Wasn't like that this morning when I started the thread because there is one order that would have been discounted.

Looking through admin logs for anything strange.

[RixStix]

Whew. Back now.

OK. Looked at Salemaker. One master category was checked that was not checked yesterday, nor earlier today. If that master category had been checked, an order which was placed around 11am today would have been discounted and it was not.

Unchecked that master category and major catastrophe averted.
Unchecking that master category also removed the discount from the items which caused me to ask the original question at 9am.

AFAIK, no one has visited that particular salemaker item within the past 24 hours. Admin logs may prove me wrong. If any authorized person did it, it would be me because all other admin users are disabled from that entire admin tab. It would not be the first time, mystery checkboxes were ticked on/off.

Thank you Linda. All is well in the discounting world for now. Just think how much trouble us users could get into IF categories, products AND attributes could be put on sale or special.

Hoping to find an admin log entry of when/how that box got checked.

[Ajeh]

Maybe someone accidentally clicked one?

Maybe someone moved a Category into a SaleMaker Category? (I have not tried that one, but it is a thoughts)

Maybe you have spooks on the site ...

[RixStix]

Anything is possible. But it is really difficult for me to go through the steps which would have been

Check the one category which contained the items first described.
Then later in the day
Uncheck that category and check the master category which contains our most popular items.

And only a SuperAdmin can do that and the only SuperAdmin is ME.

Would those checkbox checks and unchecks be expected to be found in the admin activity logfile? I haven't made it that far yet. I missed Beer-thirty, so taking care of important tasks first.

You say moved. I am easily confused. Aren't there only checkboxes to include categories into salemaker sale?

I do not rule out the spooks.

Thank you for pointing me in a direction that I would not have gone because I would have bet money on that box not being checked.