Mat Whitney

With that routes file, admin/developer and admin/settings should give a 404 error or redirect to your role's default context. admin/content should display the view in `/application/views/admin/content/index.php` and admin/reports should display...

> The module builder provided views for all the contexts under > `/application/modules/admin/views/` and I added several under > /datamart as I was building out that module. Module Builder shouldn't...

You definitely don't want an 'admin' module at this point. If you were to create one, anything in it would override the files I'm discussing below. You also should not...

Has your admin theme been modified in some way? If /admin/datamart loads, the others should load. The only reason I can think of for it to stop on that file...

I'm running out of ideas on this one. Is `$config['template.admin_theme']` set to `'admin'`? (Normally this is set in `/application/config/application.php`, but it is possible to override the setting elsewhere.) Do any...

Even though this is an old issue, I wanted to add a note that, although permissions can be longer (255 characters), the description of the permission can only be 100...

As far as I can tell, this fix only works properly with the MarkdownExtra driver. The MarkdownExtended driver will not display any errors, but will also not display the tables....

Sorry, I missed this earlier, but in your quoted `Template::block()` call, the first two arguments are reversed, which is why you get the error message about being unable to load...

Did you set a route for the context in `/application/config/routes.php`? For example, in the existing contexts section: ``` php // Contexts Route::prefix(SITE_AREA, function(){ Route::context('content', array('home' => SITE_AREA .'/content/index')); Route::context('reports', array('home'...

Currently, module builder has no ability to edit the routes. We should probably add some documentation regarding that, but I thought we added a note to the page when building...