Product approvals and ACL

-- HikaShop version -- : 2.5
-- HikaMarket version -- : 1.6.3

Dear Sir
1. I set the configuration of product approval to yes, after my vendor add a product, I logged in using admin count but I cant see approve button, please advice
2. is it possible to give add product privilege to vendor (so he can see all fields of the product) but do not allow him to edit those product after created , I mean if edit, only he can display the fields not edit them, this is because I do not want any vendor to change the product after I publish it
thanks

thanks for the response
1. but no approve bottom appeared even if I login by admin user (super user)
2. can you please elaborate more, do you mean to present the update and once he submit I discard the changes using onBeforeProductUpdate?

thanks
I tried to write the plugin but for certain reason its not working
I just want to unpublish the product if its been changed, I write XML file as well as the below simple code php file, install them from extension manager, enabled the plugin, still its not working

<?php
class mymall_custom_code extends JPlugin {
	function mymall_custom_code(&$subject, $config){
		parent::__construct($subject, $config);
	}
	
	function onBeforeProductUpdate(&$product, &$do) {
	$product->product_published = 0; 
 	return true;
	}
}
?>

thanks Sir
My problem is the trigger itself is not being fired on product update on the front end, cause nothing happened after I update the product, its still updating it

Update:
I installed plgHikashopDump_Events and I can see that its calling onBeforeProductUpdate but I doubt its my trigger (cause I change my trigger to onAfterProductUpdate and still not fired after updating any product) also its do not cancel the update as it suppose to do
Please advice

Dear Sir
it looks I had some problem with the plugin, I delete it and installed it again and it worked
now I noticed that the publish/unpublish icons is not appearing at the vendor front end product listing when I remove the publish privileged from the ACL , my question I still do not want the vendor to publish or unpublished the product, but at least I want to show the status of the product weather is published or no, how I can achieve that

I do not understand, when I am supposed to place this code
thanks

thanks but can you please advice where exactly ??

Hi,

I must join this thread - for two reasons:
1.) I also can not get the Main Vendor or Admin (Joomla Super User) to see unapproved products in the frontend.
2.) We should get this approval thing to work, and user "mymall" must not use (un-)publish instead.

1.)
a.) Upon installation of HikaMarket the Main Vendor was empty. Unfortunately, the documentation doesn't say anything what to do. So, I added one with same name and email as Admin (= site owner, all access rights), and made sure he doesn't inherit ACL but has all ACL boxes checked. But that doesn't cut it: when logged in as Admin into the frontend, I can't see unapproved product. I suspect the way I did it, Main Vendor and Admin are not the same? So.....
b.) I added the Admin to the Main Vendor, again making sure that all his ACL boxes are checked. Still no joy, still no unapproved products visible when logged into frontend as Admin.

What does it take? Jerome, please enlighten us...

2.)
a.) Once approval works, this is the Admin tool to "turn products on or off" (I'm avoiding other words to not confuse things). No doubt, it should always (by default) be unchecked in the vendor ACL.
b.) Publishing and unpublishing can - if desired - be granted to the vendor to make his product visible or not on the site, e.g. he can unpublish it if it's no longer available.
c.) Not mentioned here, but product deletion must also be an Admin tool. For obvious reasons, it must not be used by a vendor for the purpose to make a product "invisible". It should always (by default) be unchecked in the vendor ACL.

3.) More on approval:
I haven't even seen the approval button, and sure not used it - again, I can't see unapproved product. However, I'm hoping it is a toggle (approve <--> disapprove), because only then it makes sense: the Admin must anytime be able to use disapproval to "hide" a vendor product without interference by the vendor. Unpublishing is not an option for it, as eventually the vendor can publish it again (and, as stated, the vendor also needs a tool to "hide" his products from public view).
Needless to say, unapproved product and the approval feature/toggle MUST urgently become visible and usable in the backend. Otherwise it can lead to all sorts of awkwardness, e.g. if a vendor unpublishes an unapproved product: it would be invisible to Admin in frontend and backend, unless he used a series of tricks.....
Finally, since the addition of the approval feature (if related or not), other things like the vendor product category settings in combo with category ACL setting aren't working as expected and previously anymore - as discussed in another lengthy thread. Mysterious...


So, let's have a properly working and easy-to-use approval feature with toggle and backend use. We could all stop our horrible workarounds: mymall his/her code project, and myself the detour via hidden product categories, and who knows what tricks others are forced to come up with, yet...

Thanks Jerome!

Edit:
Ok, here's a bit of documentation on Main Vendor/Admin: www.hikashop.com/support/documentation/2...tml#tuto_your_vendor
Not that it helped me, but anyway...

Hi Jerome,

Interesting read. A bit sad to see the time spent on approvals by some - you in the first place - but the long-term view is much appreciated, plus versioning having so much more potential and additional benefits, of course... I remember it had come up some time ago when sort of "security" was the topic.

In any case, thank you for the open words. I'll think about it during the next few days, and might look at approvals from a different angle now, but that doesn't make it worse. Even though the future might still be some time away (I don't expect any statements on "when"), and even "some" approval functionality being better than none (except for workarounds), hanging on to approvals as they are could be risky considering a site aiming at hundreds of vendors, many categories, brands, quite a bit of customisation etc etc - not to mention the strain it could cause for support... it already has these past days.
Approvals as they work now may help some, indeed, and I need to find out if it's for me at the present state, and imagining it "frozen" as I wouldn't want to bug you for "beating a dead horse", haha. So, I'll see that I get approvals going at least for a few more tests on stability and practical usability, then decide. There's always the workaround with hidden categories, and possibly some other tricks..

Might sound pathetic, but as a matter of fact, whatever you guys do, you are standing behind it and the users with timely and brilliantly sufficient support. Truly amazing. So, I have all the faith in you and your future developments.

Thanks,
T