summaryrefslogtreecommitdiff
path: root/modules/image_block/helpers/image_block_installer.php
AgeCommit message (Collapse)Author
2013-01-31Drop the requirement to have the install() function set the moduleBharat Mediratta
version. It's redundant. Fixes #1985.
2013-01-21Update copyright to 2013. Fixes #1953.Bharat Mediratta
2012-02-27Update copyright to 2012. #1822Bharat Mediratta
2011-01-21Update copyright to 2011.Bharat Mediratta
2010-12-02Ok, do a real fix for #1499 by creating version 3 of the image_blockBharat Mediratta
module and creating the image_count variable if it wasn't already set.
2010-12-02Duh, set the image_block.image_count variable in the installer! ThisBharat Mediratta
issue was introduced in cdf0f7f765a5bd5e0d5619d345bdc6aba069c555 which was a follow-on for 3c523bcac6e902973c5891c02842254eaecd33a4 which fixes #1499.
2010-11-29In 3c523bcac6e902973c5891c02842254eaecd33a4 (fix for #1499) I left outBharat Mediratta
the install() function which should set the image_block module to version 2. Fix that here.
2010-11-21Create a module setting for the number of random images to show in theBharat Mediratta
sidebar. Fixes #1499.
2009-11-18Remove the image_block_installer class as it does nothing, except erroneous ↵Tim Almdal
set the version number to 2.
2009-11-09Since the activate_sidebar_blocks mentod is called from the module::install, ↵Tim Almdal
we don't need to add the block in the image_block_installer::install method as well> Fixes ticket 874.
2009-09-29Refactor sidebar_blocks into a separate function and then call ↵Tim Almdal
block_manager::get_html(site.sidebar). Convert image_block to use block management instead of theme::sidebar_blocks
2009-09-05Change the module installer so that you don't need to provide your ownBharat Mediratta
install() function if all you're going to do is to set the version of the module from module.info into the database. This means that for some simple modules, you don't need an install.php file at all.
2009-06-23Refactor the install/upgrade code to be more flexible.Bharat Mediratta
Add xxx_installer::upgrade($version) method so that upgrade stanzas are separate from install stanzas. In the old code, to do an upgrade meant that you had to re-evolve everything from the initial install because we'd step through each version's changes. But what we really want is for the initial install to start off in the perfect initial state, and the upgrades to do the work behind the scenes. So now the install() function gets things set up properly the first time, and the upgrade() function does any work to catch you up to the latest code. See gallery_installer.php for a good example.
2009-05-26Restructure the module lifecycle.Bharat Mediratta
Install: <module>_installer::install() is called, any necessary tables are created. Activate: <module>_installer::activate() is called. Module controllers are routable, helpers are accessible, etc. The module is in use. Deactivate: <module>_installer::deactivate() is called. Module code is not accessible or routable. Module is *not* in use, but its tables are still around. Uninstall: <module>_installer::uninstall() is called. Module is completely removed from the database. Admin > Modules will install and activate modules, but will only deactivate (will NOT uninstall modules).
2009-05-13Gee it's May already. Update copyright to 2009.Bharat Mediratta
2009-02-27Remove unneeded code.Bharat Mediratta
2009-02-26Update to image_block based on bharat's feedbackTim Almdal
1) move the rand_key column into core 2) don't do a max rand, just try to a get a random number less than the current random number if that doesn't successd look the other way
2009-02-26Implement a random image block for the side bar. Ticket #13Tim Almdal