Roadmap for version beta 1.0 Expand all | Collapse all
74% of 8 tasks completed. 3 open tasks:
- FS#21 - Updated Payment System Expand Collapse
-
There needs to be a modular feature with the payment system. Needs to be more cubecart like with the payment system..
Have a folder called payments and sub folders under it.. the module will detect the sub folders and look for an image, if the image is not found it will use the name of the folder for that payment option to display in admin. The folder name will be the name of the payment option anyway.. Example subfolder \"Paypal\" will be the name \"Paypal\" displayed to the user as a payment option.
We also need to make another table called settings.. Here are the suggested fields.
table -> pumms_settings
field -> sett_id
field -> sett_type
field -> sett_enabled
field -> sett_data
The sett_data can be a serialized array we can even encrypt the serialized data but for not that\'s not necessary but we will be looking at that option.
If the field is enabled it will show a green box in admin beside the name of the payment system. Of cource if it\'s not active it will show a red box.
We can add standard and API options to the payment system.
Unlike cubecart we need the ability to add reaccuring billing and not just one time payments.
The payments table has to be also updated to include billing information. A good example is paypal that will give you that information when the sale has completed. We need to capture it.
- FS#27 - Super Admin, Normal admin and Moderators Expand Collapse
-
Currenly the PUMMS system can handle many admins but there needs to be a super admin so appointed admins can't high jack the membership script and disable the orgianl admin or the super admin.. There needs to be atleast one accout that is hijack proof..
Normally this is the first member when the script is setup but it does not mean that id 1 is the first member.. Especially if some edits were made.
Currently Moderators can change their profiles to admin this needs to be fixed. Moderators should not be able to change their trust levels or user type.
- FS#31 - Pesky module error notification on certain situations. Expand Collapse
-
If a module has been set, and then transfered to another site and that module was removed from the file directory there is no way to delete that setting for that module, and you keep getting an pecky error that the modulenam.panel.xxx is not correct.
It can be solved by logging into cpanel and deleting the module setting that's not being used anymore.
The script needs to delete the record from the database or ignore the error since it does not apply. Or atleast deactivate the record instead of deleting it..
Text Version