summaryrefslogtreecommitdiff
path: root/modules/watermark/helpers/watermark_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-03-03Update the copyright to 2010. It's only 3 months into the year :-)Bharat Mediratta
2010-01-31Update the install version to 2 to match module.info.Bharat Mediratta
2009-08-27Remove 'ENGINE=InnoDB' specification from tables that we create. UseBharat Mediratta
the system's default table specification. Fixes ticket #597.
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-28Change the pattern to identify tables that need prefix substitution toTim Almdal
mirror the drupal pattern of using braces {}.
2009-02-27This implement table prefix for the watermark notification modules (Ticket #68)Tim Almdal
2009-01-14Make sure that helper functions are all static. Add newBharat Mediratta
File_Structure_Test to make sure we don't regress. According to the PHP docs, the "public" keyword is implied on static functions, so remove it. Also, require private static functions to start with an _. http://php.net/manual/en/language.oop5.visibility.php
2008-12-30Make some columns smaller so that multi-column keys don't exceed 1024Bharat Mediratta
bytes on some systems.
2008-12-26Added the concept of "permanent" messages that we show to admins. UseBharat Mediratta
this to show a "your thumbs/resizes are out of date" message whenever we change the graphics rules. Tweak watermark module to add graphics rules whenever we make a change, which triggers the graphics module to add the permanent message.
2008-12-26Added graphics::mark_all_dirty(). The watermark code now marks imagesBharat Mediratta
as dirty if the admin changes the watermark at all.
2008-12-25Add edit/delete links (they're just stubs now, but they open a dialog).Bharat Mediratta
Add active/position to Watermark_Model
2008-12-23Add very simple graphics toolkits.Bharat Mediratta
Track a set of rules in Graphics_Rule_Model which specify how we turn original images into thumbnails and resizes. There's one set of rules that applies to every image in the Gallery. Track the state of thumbs and resizes with a "dirty" bit. The new graphics helper manages the rules and can rebuild the thumbs and resizes for any images that are considered "dirty". Introduce the concept of an "album cover" which is an item that an album points to. We'll use that item as the source for the album's thumbnail/resize. Conflated with this change (sorry!) I also changed the Var table to use module_name instead of module_id. This may be marginally less efficient, but it's much easier to follow in the database.
2008-12-23Allow the site admin to upload watermark images. Can't do much with them yet.Bharat Mediratta
2008-12-15Start of the dialog to specify the watermark placement. For convience, ↵Tim Almdal
using the imagemagik nomicalture regarding watermark locations (east, west, center, etc.) You can drag the watermark around but it doesn't stay in place. Need to figure out how to resize the dialog box and all of the supporting javascript
2008-12-151) Move the deletion of the vars into module::delete helperTim Almdal
2) remove the watermark_add_form.html.php
2008-12-14The start of the watermark module. It doesn't save the watermark at this ↵Tim Almdal
point. This is more of trying out the approach where Forge is not used for forms. Basic html and the Validation library.