Status: offline
remy
Forum User
Full Member
Registered: 06/09/03
Posts: 162
I read in the developers manual:
However all phpblocks seem to end in lib-custom. I find this odd.
Starting with the original groupAccessCheck of Blaine, I put that phpblock into /blocks and added to lib-custom:
Ran into several errors with this block, corrected this, corrected that, and now it runs okay. My goal was to create a drop-in directory for phpblocks in stead of maintaining lib-custom. However, this idea is too simple to go with? Did I overlook some terrible security vulnerability? Is this mechanism okay to use? Am I safe?
Next move could be to adjust the Block admin to show a dropdown with available phpBlocks that can be configured.
If you have files that are located outside the webtree, like those located in the plugins/{plugin} directory, then put them in a directory called blocks/{block} at the same level as the plugins directory.
However all phpblocks seem to end in lib-custom. I find this odd.
Starting with the original groupAccessCheck of Blaine, I put that phpblock into /blocks and added to lib-custom:
/**
* My custom includer for all phpblocks in /blocks/
*/
foreach (glob($_CONF['path'] . 'blocks/phpblock_*.php'
as $phpBlock) {
include $phpBlock;
}
* My custom includer for all phpblocks in /blocks/
*/
foreach (glob($_CONF['path'] . 'blocks/phpblock_*.php'
as $phpBlock) { include $phpBlock;
}
Ran into several errors with this block, corrected this, corrected that, and now it runs okay. My goal was to create a drop-in directory for phpblocks in stead of maintaining lib-custom. However, this idea is too simple to go with? Did I overlook some terrible security vulnerability? Is this mechanism okay to use? Am I safe?
Next move could be to adjust the Block admin to show a dropdown with available phpBlocks that can be configured.
