hyperviperx99, I also missed some "hello world" info on these basics when I installed :o

First, MicroCart needs to be enabled in ACP / Plugins / Products, or all ACP parts for microCart will be hidden. You may need to refresh the ACP to see the microCart drop-down in the ACP left column.
THEN you should see user group rights at the bottom of:
- ACP - Usergoups - Usergroup Manager - Edit Usergroup / hit "Go" and look right at the bottom of the long page with options.

Small bug;

In ACP list of Products & Services, the item Name link and Edit drop-down point to different URLS:
Item Title: ..../admincp/microcart_admin.php?do=edit&id=1 (not working)
Edit: ..../admincp/microcart_admin.php?do=editproduct&id=1 (working)

I'm aware that this is bold, bad timing and opening a can of worms, but based on my own development and modding several shop systems and codes, my "dream version 2.0" of microCart would use the vB CMS pages, instead of a separate shop structure. Ie, shopping would be added as CMS page attributes:

- If this CMS page is a Shop Item [Y/N]
- then add to the CMS page; price, quantity, checkout buttons, item ID etc in the ACP and front end pages....

The big advantage would be that things like page navigation, editing, commenting, searches, page layout, categories sytem, images, thumbnails, gadgets etc in the front end and ACP page structure etc would be the normal vB CMS / forum, so no development would be needed for that.

Also important is that the shopping pages would blend in fully with the rest of the site.

The "Your Shopping Cart" code could be converted, possibly with very few changes, into a vB gadget, placed in a sidebar.

Order history and invoices could be found by the users, under their Profile page.

Many parts of the ACP / back end for microCart could probably remain unchanged....

I think that in the long term this would be a very efficient development path, as much of the front end development would be taken care of via the CMS and some of the back end development by the ACP so the microCart development could concentrate on the shop specifics only.

This is done at server level to your files either in your cpanel, plesk, ftp or ssh, CHMOD means to change the permissions , so you will be changing the file permissions from e.g 644 (or may show as 0644) to 777 (or 0777).

That cleans it up. Thanks.

There is a commercial version of this and thats about all i can say here visit my site for more info on this.

Thats good i thought i was going to have to go through all the templates and fix something lol.

I have also seen this error and will be fixing this very soon.

I like this idea and would have to look into this before making this step as that means there would be 3 versions of this cart system.

These would have to stay as some members dont use or want the CMPS system installed for there sites.
1 free version
1 commercial version

This would have to be a new system alltogether.
1 new CMPS version

The plugin gives me the error

Unable to find a class to validate: vB_TemplateParser_Curlycssfile on line 1083 in /*****/public_html/includes/class_template_parser.php
...............
Fatal error: Unable to find a class to validate: vB_TemplateParser_Curlycssfile on line 1083 in [path]/includes/class_template_parser.php in [path]/vb/vb.php on line 287
#0 vb_error_handler(256, Unable to find a class to validate: vB_TemplateParser_Curlycssfile on line 1083 in ....................

and a huge list af these errors

I can tell you this class (vB_TemplateParser_Curlycssfile) does not belong to this plugin so therefore you have a problem with something else not with the cart system.

cooiiieee :)

My version is 4.0.3 pl2
Maybe this is the problem