BackendPro 0.5
Author: Adam
21
Mar
After a long cold winter BackendPro 0.5 is here. This release is mainly about bug fixes and a few new little features. So if you havn’t tried BackendPro yet, give it a whirl. If you are currently using it, upgrade if possible to get the new features and bug fixes. A list of the things changed and added is below:
Additions
- Added a section into the user guide to talk about the file system and matchbox, See Enhancement #10
- JS Code Output – The Page class now has the feature to store JS code and then output it into a view (very much like the PHP to JS variable converter), See Enhancement #84
- i18n Support – The status class language strings are now contained within a language file, See Enhancement #75
- CI Profiler Intergration – The CI profiler is now intergrated into the admin control panel. When turned on in the system settings rather than some of the output being hidden it is now clearly visible, See Enhancement #41
- Login Selection – It is now possible to select how a user can login, either with their email, username or either.
Modifications
- The page->icon() method now accepts a title paramter for the displayed image.
- Moved some of the dashboard files into their own module to tidy the file system up a bit. Also have created a new class to store to Statistics Widget creation code it.
- Improved the is_user() method so if $config['sess_use_database'] is FALSE then extra user checks are performed. For this to work the value returned by validateLogin() has changed, See Enhancement #80
- Removed PHP short tags from files, See Task #42
- Added some extra language strings for the dropdown options inside application/controllers/admin/settings.php, See Enhancement #73
- Updated the Page Module so it uses the functions in the CodeIgniter HTML helper, See Enhancement #36
- Changed the MY_Controller so the charset header and metatag value is taken from the CI config file, See Enhancement #74
- Altered the default dashboard statistics panel so it now also shows the current CodeIgniter version.
- Changed the way the install process is done. Now you can specify your CI folder structure, See Enhancement #53
Bug Fixes
- The dashboard widget system now restores moved widgets, See Bug #64
- The BackendPro tree menu in the admin panel now saves its open/closes status rather than it being lost between different pages, See Bugs #15 and #145
- Redirection upon login is now fixed, See Bug #100
- Spelling errors throughout the code, See Bugs #71, #76, #77
- Corrected the user guide section on the Page class. Originally it listed output_trail() as a method this is now output_breadcrumb, See Bug #69
- Modified the path to the user guide from inside the BackendPro control panel (footer), See Bug #68
7 Responses for "BackendPro 0.5"
[...] systems we use. I was surprised to find out that BackendPro was yesterday released in a new version: BackendPro 0.5 (THANK YOU very much Adam Price for this good [...]
I’d like to customize just about everything in this application… when reading the license you’ve supplied I get conflicting information with regard to modifications / changes. Could you set this in stone for me and let me know if BackendPro is unmodifiable?
The licence should allow you to modify it as much as you want. If not I will maybe have to re-consider the licence.
Hi great work!
Couldnt you write a tutorial on how develop on BackendPro?
I may do that if I have time but it is not a big priority I am afraid. BeP is designed mainly for my own personal use but I have released it to the community for if people do want to use it.
Hi Adam,
Thank you for your great contribution. With reference to backendro 0.5, I was trying to create a access permission for a user but am not been able to get into what exactly I was looking for. I will explain my problem with this example.
o Site (Deny)
o Control Panel (Allow)
o System (Deny)
o sellers (Allow)
o Access Control (Deny)
o Actions
o Resources
o Groups
o Permissions
o Members (Deny)
o Settings (Deny)
o Utilities (Deny)
I am able to allow the permission to sellers but the user cannot login to control panel. When i gave the permission to control panel. The user was able to access every ACO.
Could you please give me a hints to implement the above example in backendpro.
I would be grateful to you for your kind support and suggestion.
Thank you once again for the great contribution
I think the first problem is you have said, Deny to site. This should always be allow, for a logged in user.
I definitely know there are some issues with the permission system, but to fix these would require a full re-write.
Leave a reply