Following Blocks tutorial, Concrete5 expecting block to be in /concrete
Permalink
I'm following the basic Blocks tutorial found here:http://www.concrete5.org/documentation/how-tos/developers/understan...
I downloaded the test block package, and installed it in my installation's /blocks directory. I renamed the block to a custom name, and replaced all the class definitions with the correct name. (I took care to name the directory like this: `block_name` and use CamelCase inside the class declarations: `BlockName`)
However, when I try to navigate to the "Block types" page in the admin in order to activate the block, Concrete5 complains that
so it's looking for the controller.php file in /concrete/blocks while the actual block resides in /blocks.
Why is this?
I downloaded the test block package, and installed it in my installation's /blocks directory. I renamed the block to a custom name, and replaced all the class definitions with the correct name. (I took care to name the directory like this: `block_name` and use CamelCase inside the class declarations: `BlockName`)
However, when I try to navigate to the "Block types" page in the admin in order to activate the block, Concrete5 complains that
Warning: require_once(/www/htdocs/sites/sitename.com/htdocs/concrete/blocks/block_name/controller.php) [function.require-once]: failed to open stream: No such file or directory
so it's looking for the controller.php file in /concrete/blocks while the actual block resides in /blocks.
Why is this?
Is this by design?