Yet another permission component was created this week but this time, it’s simplier and written in a text file. In one of our project, one of the follow-up requirement was to allow users of certain groups upgrade into a better status. The project was already in production and I was using ACL with Auth component to do my authentication. Unfortunately, this is one of ACLs weakness .
Changing a users group does not change the ARO parent (effectively making it useless/impossible to change groups). I tried fixing this home-brew style, but since there’s no setParent in 1.2’s db_acl, it’s far harder than it should be.
That was reported back in 2007 and there was still no solution found in the net. It is also not an option for me to go through the above suggestion in fixing the problem so the the other solution is to find another one or create one. I chose the latter.
Why create a new one?
The other solutions that I found still needs some configuration in the controllers. Since I already have a ton of files, I don’t want to go through all of them to add a line or two. I need ACLs way of doing it all in the background. Also, I am already using Auth component and I want to keep it.
Why did I choose a text file over a database?
My intention is to make the application faster since load time is really getting slower. Since the application isn’t that big, I only have less than 200 lines for the permissions, so a database is just overkill. Even if I use a database, I might cache it anyway so it saves me extra query.
The component
So Permission Component was created. Below is the instruction on how to install it.
Download this component and copy to your components folder. Create cake_dir/app/config/permissions.ini
The content for permissions.ini is as follows
[ ControllerName] actionName = group_id,group_id
[ PluginName.ControllerName] actionName = group_id,group_id
The ControllerName should be the controller name itself (in camel-case format).
The actionName is also the action name itself (in camel-case format).
The PluginName is the plugin name itself (in camel-case format).
The group_id is the one written in your Auth component. Your Auth component should have a group_id value because this is what our Permission component will look for. It could be a number or set of characters.
Example:
; Group ID 1 = Admin
; Group ID 2 = Member
[ Accounts] index =
add = 1
edit = 1 ,2
delete = 1 ,2
[ ShoppingCart.Orders] index =
report = 1
Assigning no group id in an actionName will simply ignore it.
Reminder
Use at your own risk. If you found a bug, please post them at the comment form.
blog tutorial in cakephp manual because it has a more complete introduction for the framework. Cakephp 1.2.0.7692 RC3 in demonstrating this little project because it is the latest release as of this writing. What to do and what do we need to begin?
To start off, we need a project. I opted a mini-library application which consists ofBooks
Read the rest of this entry »
Tags: applications , bake
In cakephp, adding relationships is easy. We just have to declare the hasOne, belongsTo, hasMany and the famous HABTM relationship to do all the dirty work of joining tables. But declaring them all at once could lead to a slow page.bindModel() and unbindModel() . We do not declare all associations in the Model class yet. This was a good solution. I was looking for this option in version 1.2 and I found the Containable Behavior. Studying containable was a little rough before but there are documents now that are really helpful.Read the rest of this entry »
Tags: containable , optimization
From now on, I’ll always use Model->create() before saving new data.Model->save() , you should also call Model->create() before saving if a previous call to Model->read() was made. Or better yet, always call Model->create() whenever you are about to save new data . There are cases the previous calls to save and read made are not that obvious, like in the beforeFilter() callbacks of the controller (or the parent::beforeFilter(), like in my case).
If you used the star rating plugin of jQuery in cakePHP, you might experienced that the hover effects are not working properly. This is because one of the class name used to identify the buttons uses the radio button name. This will be a problem in cakephp because we use brackets in names.
<input type = "radio" name = "data[Model][field]" class = "star" / >
jquery.rating.js :
// grouping:
var n = this .name ;
// grouping:
var real_name = this .name ;
var n = real_name.replace ( /[^A-Za-z0-9_\-]/g , '-' ) ; // remove unwanted characters
$.rating .groups [ n] .valueElem = $( '<input type="hidden" name="' + n + '" value=""' + ( settings.readOnly ? ' disabled="disabled"' : '' ) + '>' ) ;
$.rating .groups [ n] .valueElem = $( '<input type="hidden" name="' + real_name + '" value=""' + ( settings.readOnly ? ' disabled="disabled"' : '' ) + '>' ) ; reported this in the bugtracker and I hope it will be included in the next release.
Tags: bug fixes , jQuery , star rating
Hello again,$path , array $htmlAttributes , boolean $return = false); $title, string $url, array $htmlAttributes, string $confirmMessage = false, boolean $escapeTitle = true, boolean $return = false );PrometSource , previously known us Promet Solutions, new website is UP . We recently faced a transition in the company to better serve our clients.
) to present CakePHP Introduction for students of Centro Escolar University and University of the Philippines (Diliman). It was a very nice and fun experience to be working with Jeff, Chean, Ridvan, Paul, Francis, Jhayson, JrYap, Eric and the school representatives. Here are some pictures for the 2 events.