drigg 5.x-1.24
Download: drigg-5.x-1.24.tar.gz
Size: 109.02 KB
md5_file hash: db4881a521af9ef5a0ff23fde6db8f1b
First released: April 14, 2008 - 03:34
Last updated: April 14, 2008 - 03:35
View usage statistics for this release
This is a MAJOR release of Drigg. A _lot_ has changed. If you are upgrading (as you should), please read this carefully. This is in preparation of the Drupal 6 release.
Driggi s now split in several sub-modules. Some theme functions now have a different name (but the old ones will keep on working).
Here are the upgrade instructions:
* Switch to a non-drigg theme, at least for the administrator. This is important in case your theme has drigg calls without the checking if a module is defined with module_exists()
* Explode the module in a CLEAN directory, and replace the old one. Do NOT explode this on top of the old one
* The site's home page will stop functioning. Go to /admin/build/modules in your site. The home page will start working again. This is because we have actually changed the *location* of the drigg.module file.
* Then go to /admin. You will see the warning about the database being outdated
* Follow the database update procedure. This will actually enable the sub-modules, more than changing the DB
* This will automatically enable the core 9 modules Drigg is now made up of
* Check the home page with the original theme
* You will see several warning messages, about your theme using "old" functions. You will need to rename those functions in your theme
* Reconfigure your blocks! Sorry, this was unavoidable... You will need to reconfigure pretty much all of your blocks: placement, parameters, etc.
* Change drigg/drigg_theme/css/block.css with these differences:
http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/drigg/drigg...
Basically, the block divs are a little different now. Again, this is unavoidable since a separate module now generates the blocks... sorry! It's for a good cause though.
That's it! Please report here if you have any problems...
You may argue that we should have made this a Drigg 2.0 version... the thing is, the next step is to port everything to Drupal 6. This reorganisation is crucial. If we release this as Drigg 2, we would then have to maintain three trees (Drigg 1, Drigg 2 and the D6 version). Making this change is important before too many users start using Drigg (the number is increasing dramatically).
Enjoy!
