[Arrow768]

General Information

The Store WebPanel is a easier way to administrate your Store installation.
It allows you to

• Add/Edit Items
• Add/Edit Categories
• Edit Users
• Import/Export new Modules

Bugs Documentation and Downloads
Please Report all and any Bugs on GitHub
Please use GitHub to make feature requests for the WebPanel, because it allows me to keep track about all what needs to be done for the next version


You can find a Documentation in the GitHub


Requirements
The requirements are listed in the requirements section of the installation tutorial in the github wiki


Credits
alongub for his awesome Store Plugin
Bor3d Gaming for their Design

[Yoshi69]

I've followed all the steps in the installation of the webpanel, but each attempt i make to access it tells me either SSL connection error or error 500. I've made the .htpasswd file with the login and an an ecrypted password and put in the .htpasswd folder, as well as made a .htaccess file and put where it belongs. I'm pretty sure I did everything correctly but for the life of me I can't get working. Lol. I feel as if the error is in the in the AuthUserFile part of that file:

www.[site].clanservers.com/home/[login]/.htpasswds/.htpasswd

If this isn't the correct way it's supposed to be put could u please inform me of what i did wrong. Sorry I'm not that literate with myphpadmin or anything mysql related. So this is all a blank to me, but I'm very intersted in learning. Any useful help would be greatly appreciated. If you need any other information feel free to ask, and I shall provide.

[Arrow768]

I recommend you try to install CI without a .htaccess and a .htpasswd first.
Once it is working without a .htaccess, you can try to create a access restriction.

If you want to get into web development, you should take a look at xampp.
Xampp is a Apache WebServer with MySQL and PHP, that allows you to test Websites, ... on your Local PC (no need for a WebServer)

[Drixevel]

Any updates on this work for PHP 5.3? I'm waiting for the script to be a bit more bug-free before I release it for my admins to use.

Cheers,
- Keith(Jack)

[Arrow768]

There might be a working version this evening (when testing is successful)

[Arrow768]

I have just commited a version that should work on PHP 5.3

Can you please confirm that it works on 5.3, or tell me what is not working


Please vote for the issues you would like to have finished first (in the Issue Tracker)

[vodka00]

@Yoshi69.

I've tried the 0.2 version and now a basic .htaccess file works just fine.

[Arrow768]

Originally Posted by vodka00 I've tried the 0.2 version and now a basic .htaccess file works just fine.

We are still on Verson 0.1 ,the commit on git was just a first step to Version 0.2 (that is planned to be released this evening

[Drixevel]

Originally Posted by Arrow768 I have just commited a version that should work on PHP 5.3 Can you please confirm that it works on 5.3, or tell me what is not working Please vote for the issues you would like to have finished first (in the Issue Tracker)

I'll try it now. For some odd reason, .htaccess and the password file don't work and just gives me an error. Not entirely sure why it's doing that anyways.

[Arrow768]

Version 0.2 is out (as promised)
You can get it by downloading the latest tagged Version on GitHub


Release Notes - Store-Webpanel - Version 0.2

Bug

• [STWPAN-6] - No input file specified.
• [STWPAN-8] - Exporting has no validation

Improvement

• [STWPAN-9] - Add table sorter jQuery plugin
• [STWPAN-10] - PHP 5.3 Compatibility
• [STWPAN-15] - In Items List, add '# of times bought'

There is a huge increase in the time it takes to generate the item list on the manage page (Because of STWPAN-15)
This is caused because I need i+1 queries to generate the item table for i items. (501 queries for 500 items)
If someone can suggest a better method of getting the times a item has been bought it would be great.

Some comments about the inbuilt Bug Reporter
I have integrated a Bug Reporter into the Frontend of the Store Webpanel.
This is a service for you, so you do not have to log into Jira everytime you want to Report a Bug.
It will remain there, as long as it is not used to send spam.
When I discover, that it is used to spam the Bugtracker, it is going to be disabled.