summaryrefslogtreecommitdiff
path: root/core/controllers/admin_dashboard.php
AgeCommit message (Collapse)Author
2009-05-27Restructure things so that the application is now just another module.Bharat Mediratta
Kohana makes this type of transition fairly straightforward in that all controllers/helpers/etc are still located in the cascading filesystem without any extra effort, except that I've temporarily added a hack to force modules/gallery into the module path. Rename what's left of "core" to be "application" so that it conforms more closely to the Kohana standard (basically, just application/config/config.php which is the minimal thing that you need in the application directory) There's still considerable work left to be done here.
2009-05-13Gee it's May already. Update copyright to 2009.Bharat Mediratta
2009-03-26Rename $block_id to $id to fix ticket #192Bharat Mediratta
2009-03-16Get rid of obsolete/undefined $block_adderBharat Mediratta
2009-01-18Drag and drop in the admin dashboard now saves the location.Bharat Mediratta
* Make block_adder a real block * Suppress the "close" link on block_adder * Move the drag/drop JS into the core code out of the admin theme
2009-01-18Refactor dashboard -> block_manager since it'll manage blocks siteBharat Mediratta
wide, not just in the dashboard.
2009-01-15Changing t() placeholder syntax from {{replace_me}} to %replace_me.Andy Staudacher
2009-01-12Refactor dashboard block handling out into a dashboard helper so thatBharat Mediratta
module installers don't have to know the grotty details of how it works.
2009-01-12Implement deleting dashboard blocks.Bharat Mediratta
* Refactor blocks so that they have a separate id vs css_id. This way we can have a unique identifier for each visual block. * Store blocks with a random id as their unique identifier * Add Admin_Dashboard::remove_block() and modify themes/admin_default/views/block.html.php to call it when you click the remove box.
2009-01-12Dashboard blocks are now data driven, and you can add new blocks toBharat Mediratta
both the sidebar and the center content area from a dropdown at the top of the dashboard sidebar.
2009-01-12Only the admin dashboard has a sidebar now.Bharat Mediratta
admin.html.php looks for $sidebar and renders the page appropriately if one exists. But only admin_dashboard has one currently.
2008-12-24Normalize our Admin controllers so that functions always print outBharat Mediratta
their results, as opposed to having them return their view back upstream. This is a little more code in every controller, but it's much less magical and more consistent. Look up the active_theme and active_admin_theme inside the view itself, no need to do that in the controllers. This makes view initialization easier in the controllers.
2008-12-22Normalize CSRF handling into the access helper. Probably not the bestBharat Mediratta
place for it, but it'll do for now. Do CSRF checking in the Admin controller so that we're safe across the board on the admin side.
2008-12-20Collapse Admin_Dashboard_Controller down into a single theme call, since nowBharat Mediratta
all dashboard blocks are stored in modules.
2008-12-19Create a new pattern for Site Admin controllers:Bharat Mediratta
1) They must all start with "admin_". This pattern is not directly routable. 2) Their urls must be /admin/xxx. 3) The Admin_Controller will take the xxx and look for Admin_Xxx_Controller and will delegate to that admin controller, after doing security checks. Moved the users and dashboard views into individual modules for now.