PyroCMS v0.9.7.4 - an open-source modular general purpose CMS

[eluser]Yorick Peterse[/eluser]
[quote author="Phil Sturgeon" date="1256564504"][quote author="Doan Du" date="1256328952"]Just upgraded my system to PHP 5.3 and got an error message in libraries/Loader.php at line 414. It's easy to fix (use instantiate_class()). I think you should update the your Loader.php file like the one of CI 1.7.2.[/quote]

Sadly as we are using Matchbox we need to keep the Loader.php file. I can patch it for v0.9.7 with your suggestion which will get it working on 5.3. In v0.9.8 we will switch to using Modular Seperation which only extends the Loader instead of entirely replacing it, meaning it should stay closer to the core Loader as its improved by the EllisLab guys.

[quote author="dinhtrung" date="1256489613"]In Admin Control Panel, when I add new permission, I can choose Module, but only "All Controllers" and "All methods". This page need some jQuery or Ajax script to populate the Controllers and Methods whenever user change Modules. Maybe, store controllers in a variable, store methods as array (controllers_method), then use jQuery to filter them out.[/quote]

All of this information is stored in an XML file details.xml in the module. It is possible its broken, but I cannot test this right now. Could you take a look at application/models/modules_m.php and see whats going wrong?

[quote author="dinhtrung" date="1256489613"]Change the form into a table with all available modules and methods for easy select (like Drupal). Tick the checkbox with value="module_method_controllers", for example.

Store all rules permission in the permission_roles.permissions field, with json_encode($_POST['permissions']) or implode(";", $this->input->post('permission')) and store all those permission data in session. I think this will save a table, and alot of code (to view navigation admin panel, to check for permission...)

I really like the idea of using cache to store permission data (in your MX_Acl library) and DX_Auth regexp to check for permission (like /controllers/* can access all methods in controlles, and /controllers/add/ can only add... etc). Can we change pyroCMS to use the same?[/quote]

Um... Could I get some wireframes or screenshots of how this would work? Not sure I like the idea of removing a normalized DB structure and shoving it in a serialized field, feels like system devolution to me.

[quote author="dinhtrung" date="1256489613"]Is there something I could help?[/quote]

There are ALWAYS things to do. This permissions stuff could be easily improved if you are up for the job, but only when I have worked out how and if the features should be part of PyroCMS. Caching could definitly be handy. Translations would be good too.

[quote author="NateL" date="1256509723"]Any ideas on this installation error?

A PHP Error was encountered

Severity: Warning

Message: Missing argument 1 for installer_m::validate(), called in /home/topside2/public_html/pyrocms/installer/application/controllers/installer.php on line 165 and defined

Filename: models/installer_m.php

Line Number: 184[/quote]

This is something I have tried explaining to Yorick several times but it looks like he still hasn't made the change.

Code:

function validate($data)
{
// Get the database settings from the form
if(isset($data))
{

That DOES NOT work Yorick, it should be...

Code:

function validate($data = array())
{
// Get the database settings from the form
if(!empty($data))
{

The variable $data will either be set, or unset. If it is unset without a default value then PHP will fatal error, meaning the switch is pointless. It will never get to the else.

I am also assuming that $_POST should be passed to this model by application/controllers/installer.php on line 165? Could someone test this as I cannot code at work anymore.[/quote]

You never talked about that error but I'll fix it anyway