CodeExtinguisher Release Candidate 11

[eluser]Majd Taby[/eluser]
tylderdurden, You can restrict certain controllers / methods using the access_levels.php file in the config/ directory. You can also restrict what information each user sees in the "Overview" page, by defining table_access_restrictions (alongside your rules..for example). You mentioned that you tried it...but by giving it an access level of 0, you're telling the system that any use whose level is 0 or above, has access to it. Increase the number, to restrict the group of users who have access to it.

As far as your image/plugin inquiry...yes, you define the upload directory as a param...and no, you can't get the upload path from another field..but that would be a specialized form of the File plugin. If you would like, you can write your own and (eventually) upload it to codeextinguisher.com

Finally, the delete confirmation message used to exist in prior builds, when each row in the table had a delete button, but I removed it, since how, you have to check the row, and _then_ click Delete Selected...which should stop you from deleting the wrong record (make sense)? What i'm trying to say is, by making the deletion of a record a 2-step process, i removed the chance of an accidental deletion...and the confirmation message seemed unecessary.


cre8tive, I'm working on docs (if you would like to help, PM me with your email), The permission system is already in place, I just have to make it more user-friendly, and CRUD based on models is on the roadmap

andjules, If the CRUD works off of models, you can define your own callbacks and special handling at the model level. Right now, if you wanted to modify CodeExtinguisher flow, you would have to create a controller...but that would be at the controller level, and isn't ideal/proper oop.

Oren, Both of those are very valid points, the search capability is first-draft (it was only added in RC11). The problems will be fixed in the next release.

Thanks for the kind words guys, it means a lot