I am using VM 2.0.20b. I have read many posts that state you can edit and save products and add new products from a frontend admin.
I have read TONS of these post and have found no solution. I have spent hours trying to figure this out.
Does anyone have a step-by-step solution?
Thank you!
I am having this problem too - I cannot save products from the front end. Using VM 2.0.22a and Joomla 2.5.14 and PHP 5.3.26. User with Joomla "administrator" permission gets the pencil icon at the front-end, and appears to be able to edit products, but when they click "save", nothing is saved, and the user is returned to the homepage.
The Joomla user is assigned to Joomla user group "administrator", but when I look at the user via Virtuemart admin > Orders & Shoppers > Shoppers, the user group says "admin" (not administrator) and this cannot be changed. Other "shoppers" still have user group "storeadmin" and this cannot be changed, and they also are unable to save product changes from the front end.
I have tried using multivendors (following the instructions I found elsewhere on the forum), but still get the same problem. I have gone back to just the original administrator as the only vendor, but still get the same problem. Cleared the server cache, cleared the browser cache, logged back in, but still the same problem.
When I add a new user via VM, and assign them Joomla user permissions of "Manager and Administrator", then go back into the Virtuemart Shoppers list, that new user still has a user group of "shopper" and I cannot change it, unless I turn on multi-vendors and select the shopper and click the vendor icon, then go into Tools > Tools & Migration > Migration and set the new store owner . Then the shopper gets a user group of "admin". But there is no user group "admin" in Joomla users. In desperation, I have tried adding an "admin" user group in Joomla with the same permissions as "administrator", but this still hasn't fixed the problem.
I am tearing my hair out over this, as the client needs to be able to update products :'(
PM me access and I'll look into.
Quote from: Maxim Pishnyak on August 08, 2013, 23:55:53 PM
PM me access and I'll look into.
Thanks, Maxim. Have pm'd you.
My bad, I didn't even see that you wrote "Frontend".
So it's probably not necessary to give me access to backend.
First of all your glossary added to the web page 2nd jquery.js. This is very bad. Resolve this issue first of all...
Quote from: Maxim Pishnyak on August 09, 2013, 13:23:47 PM
First of all your glossary added to the web page 2nd jquery.js. This is very bad. Resolve this issue first of all...
I will look into this straight away ...
Thanks!!
Quote from: Maxim Pishnyak on August 09, 2013, 13:23:47 PM
My bad, I didn't even see that you wrote "Frontend".
So it's probably not necessary to give me access to backend.
First of all your glossary added to the web page 2nd jquery.js. This is very bad. Resolve this issue first of all...
Hi Maxim
The problem persists :(
- I PM'd my back-end details to you yesterday, in case you need them.
- I deinstalled the glossary plugin, cleared the system cache and browser cache, and retested. But when I log in to the front-end even as super admin, I still have the same problem - I can edit a product (book), and click on "save", but the change I made through the editor does not save.
Can you have another look at it?
By the way, when you said "2nd jquery.js" I take that to mean that the plugin was causing a conflict by loading a second copy of jquery.js. Can I assume that deleting the plugin has fixed this?
Thanks!
You could use glossary probably, but 2nd jquery is not acceptable still.
It could be problem that your web store is placed in a folder. I turned off two options in Joomla configuration:
1. Search Engine Friendly URLs
2. Use URL rewriting
and issue is gone.
Quote from: Maxim Pishnyak on August 10, 2013, 11:44:46 AM
You could use glossary probably, but 2nd jquery is not acceptable still.
It could be problem that your web store is placed in a folder. I turned off two options in Joomla configuration:
1. Search Engine Friendly URLs
2. Use URL rewriting
and issue is gone.
Thanks, Maxim. Indeed, the problem is fixed :) But now I am left with very ugly search-engine-unfriendly urls :(
What do you mean by "your web store is placed in a folder"? Is this something I have a choice about?
Your web site url is http://********.com/s****10
s****10 - is your web site folder.
I think your temporary placed your web shop in that folder. Am I right? So it's not critical to have sef urls currently then.
BUT
You could continue developing your web site not in folder, but in subdomain.
Something like this http://s****10.********.com/
Your shared web hosting service could provide you subdomain and you can transfer your web shop from current folder to such subdomain and test your issue again.
After all why do you want to use frontend product editing?
Missy W
I found an ACL Manager that works GREAT. You basically give backend access to your client for Virtuemart ONLY! It is a great tool.
http://www.aclmanager.net/
and, the support is second to none. AMAZING!
Give it a try. Saved me tons of time!
Todd
Quote from: Maxim Pishnyak on August 11, 2013, 11:27:52 AM
Your web site url is http://********.com/s****10
s****10 - is your web site folder.
I think your temporary placed your web shop in that folder. Am I right? So it's not critical to have sef urls currently then.
BUT
You could continue developing your web site not in folder, but in subdomain.
Something like this http://s****10.********.com/
Your shared web hosting service could provide you subdomain and you can transfer your web shop from current folder to such subdomain and test your issue again.
After all why do you want to use frontend product editing?
Ah, now I understand what you are saying. This website is not quite ready to go into production, so it is in a folder of one of my domains for testing purposes.
It sounds like this may be the cause of the problem?!! So sorry to have troubled you over this. I didn't imagine that setting up a test site in this way could cause problems.
It's a relief to know that when I move the site into production, I can turn on sef urls again!
As for why I want to use frontend product editing, it is essential for the owners/managers of the shop to update prices, stock levels, etc. I certainly do not want to give them back-end access to Joomla - it would overwhelm them, and it could be dangerous.
In future, I will create a subdomain for testing purposes - especially for VirtueMart. I feel very fortunate that you have understood all this and have supported me. Many thanks! :-*
Quote from: toddcartner on August 11, 2013, 18:19:30 PM
Missy W
I found an ACL Manager that works GREAT. You basically give backend access to your client for Virtuemart ONLY! It is a great tool.
http://www.aclmanager.net/
and, the support is second to none. AMAZING!
Give it a try. Saved me tons of time!
Todd
Hi Todd
Thanks for sharing this information. It's great to have a personal recommendation for a product. It looks like I don't need it at the moment, because Maxim has kindly solved the problem for me. But I will bookmark the extension for future reference in case I need it.
Do you know what caused your difficulty with editing and saving products from the front-end in the first place? (Just wondering if it was the same as my situation?) Anyway - glad to hear you got a good resolution to your problem.
Missy W
No. My issue was not the same as yours. I think what caused the issue was my client was not listed as a Super Admin in the back. Therefore, the permissions were not available for him to save the edits. However, I did not want him to have full backend access. Therefore, the ACL Manager did the trick.
You can check it out to see how I limited him here if you wish:
www.thetaylorcollection.com/administrator
U: missy
P: test
Todd
Quote from: toddcartner on August 12, 2013, 02:16:48 AM
Missy W
No. My issue was not the same as yours. I think what caused the issue was my client was not listed as a Super Admin in the back. Therefore, the permissions were not available for him to save the edits. However, I did not want him to have full backend access. Therefore, the ACL Manager did the trick.
You can check it out to see how I limited him here if you wish:
www.thetaylorcollection.com/administrator
U: missy
P: test
Todd
Hi Todd
Very kind of you to set up a user for me! However, I'm getting a server Authentication Required - looks like you've password protected the administrator folder? (A good idea). But I can't get in. PM me if you wish. Thanks!
Missy
You're welcome, Missy. It was nice trick with Authentication Required in your situation. Also thank you that you reported about issue with editing product from frontend.
Quote from: toddcartner on August 11, 2013, 18:19:30 PM
Missy W
I found an ACL Manager that works GREAT. You basically give backend access to your client for Virtuemart ONLY! It is a great tool.
http://www.aclmanager.net/
and, the support is second to none. AMAZING!
Give it a try. Saved me tons of time!
Todd
ACL is now already native in vm2.0.22 svn
But the real answer to the problem is that atm only super administrators are allowed to store products. In vm2.0.22a the ACL is not there and the system we used is quite simple and what you see there is just something we did not take care yet, because it does not happen for superadministrators and for any more rights for administrators we need the ACL, therefore the simpelst is to grant superuser rights.
Milbo
You are correct in that the simplest thing to do is grant superuser rights. However, I do not want my client to have the access to everything. And even though the ACL is built in, you will spend a ton of time setting it up. ACL Manager is simple and only takes a few minutes.
It was the best solution for me and sounds like an excellent solution for Missy.
Todd