BackendPro 0.3.1 Released
Author: Adam
22
Jun
Well I must first apologise to everyone for taking so long to get this next release out, but the last 2 months have been so busy with University finals, but they are all behind me now so as promised a new release. The majority of this release is a few new features which I was planning to incorporate in BeP for a long time. Examples of these are a dashboard for the control panel, conditional CSS files (for IE), features to use CSSTidy to optimise CSS code and many more.
Additions
- Added a dashboard to the control panel front page.
- Added cancel buttons to forms.
- Added new CSS styles to create buttons.Added icon() to Page library.
- Added a generate password feature to the member administration area
- Added CSS caching using CSS Tidy in the Page library.
- Added output_variables() to Page library.
- Added conditional CSS files in the Page library.
- Added meta tag creation into the Page library.
Modifications
- Added a value option to <button> elements so the form can submit.
- Updated some of the documentation so its simpler to navigate around.
- Updated getUsers() in User_model.php to also fetch user profile columns.
- Changed the version control system from including a date to release candidate, purely to be shorter.
- Updated Nested_sets_model.php to remove the public attribute from the constructor
So head over to the BackendPro Development home and download it. Please as usual if you find any problems raise a ticket or post on the forum thread. As always if you want the latest updates keep an eye on the SVN repository.
5 Responses for "BackendPro 0.3.1 Released"
Suggestion: Replace all the short tags with long tags.
In the acl_groups controller delete function there is a line $this->khacl->aro->delete($group) that should delete the group.
My question is whether this line will also delete groups that are locked?
When I use firebug to add checkboxes to the Member and Administrator groups and check the boxes and click the delete button, the groups were deleted.
A check should be done in the delete function to verify that a selected group is not inclusive of the “Member” and “Administrator” groups, so no matter what a person does they would not be able to cripple the application.
@Adrian: Currently the locked group feature only works by stopping the user clicking the checkboxes.
The code that the KhACL library uses dosn’t know about by group locking and I will not be changing the library just for that. I will add it to my tickets and have a look at it.
Adam, If you are available, I would like to discuss hiring you to make customizations to BP. I couldn’t find your contact information so I’m leaving this comment. Please e-mail me. Thank you
Leave a reply