Vendor product edition = conditional?

-- url of the page with the problem -- : none yet
-- HikaShop & Market versions -- : actual

Hi again,

You can tell, I've been busy over the weekend, huh? Hope you had a good rest, so you survive all my stuff...
Got more news for you, so let me split it up. This being under 'Feature requests', none is badly urgent, only friendly input.

I was thinking that vendor product edition could be sometimes 'risky', yet must and should be generally possible, of course. Only once an order for that product is in the system, it should be 'blocked', IMHO - as a security feature.

Imagine: a vendor is offering i.e. a used car (just as an example). He claims it's from 2012. Ok, someone orders it. Vendor goes and changes it to 2010... which it really is. Customer realises it sooner or later and is sure not happy. Vendor says, "not sure who told you 2012, it always said 2010."

I know, admin is getting an email if vendor edits product (and now even a dedicated one, woohoo!), but it doesn't say what was edited. I guess no other record from the past, and one could claim that even the database backup saying 2012 isn't 'real'. The stink is there. And there are just too many idiots around who cheat and steal and lie wherever a few dollars are lying around.

So again, I'm dreaming i.e. of a mechanism which lets a vendor not edit his product(s) unless they're not involved with any pending order process. Even if they mean it well and have an improved version, have them creating a new product. Technically, and in fact also legally, a feature change on a product, whichever way, makes it a different one. And who knows if "edition" always means only improving the grammar in the description...

Hmm, include at least optionally?

Thanks for reading, and even more for the briefest comment.

Wow, that new feature sounds pretty exciting! Happy version juggling!

Trust me please, it'll only be effective if vendors know of (a) the existence, and (b) the potential consequences. We want to prevent evil, not pick up the pieces when it's too late. Some might even make it a sport trying to break it or trick it out - who do you think is John Smith behind that strange IP really...
But then the world isn't THAT bad, maybe, and there's only so and so much one can do without losing the fun entirely. Fact is that it'll be a valid and good 'pro' point for a the customers of a store equipped with such feature.

Then, the second part reads more like Chinese than French to me at first glance. Looks like I'll need to seriously work on my PHP driver's license, and I'm not sure when that's going to happen. Or I just need to find someone to knit the little tool for me. Or someone else here has the need as well. And a heart. No worries, don't expect you to - you guys better focus on the new "VPM" gimmick!

Once again, thanks!

Interesting...
Jerome is this "validation of product modification" in the TO-DO for the near-far future or something close to implementation?

Like lousyfool the second part is more like Chinese than Italian to me, I would need to practice in a foolproof local server before daring to trigger anything on the live site...

Hi again,

At least in my case I'd say take your time and build a nicely working tool rather than rush-rush - as always. I wonder, if meanwhile the notification mail on product edition could be easily amended with the fields that were changed - preferably in a "before / after" format...

But then, admittedly, I haven't really thought about it, and it could as well be more difficult to realise than 'the little plugin' or even the 'VPM', haha...