On this page

  1. What version of Managing News am I using?
  2. Manual upgrade
  3. Automatic upgrade with Aegir
  4. Special upgrade notes for particular versions
  5. See also

What version of Managing News am I using?

You can find out what version you are using by navigating to the base directory of your installation and opening the /profiles/managingnews/CHANGELOG.txt file. Here you will see a list of changes that have been made in each version. The version mentioned in the very first entry is the version that you're currently using. In the following example, you would be using version 1.0 beta 10

Managing News 1.0 beta 10, 2010-08-12
------------------------------------

Manual upgrade

  1. Read the notes under the special upgrade notes
  2. Log in as user 1 and put the site in offline mode.
  3. Back up your database.
  4. Unpack Managing News in a new directory (don't try to overwrite your existing site's files).
  5. Copy your existing Managing News site's settings.php and files directory into the corresponding places of your new site directory. Make sure you keep the permissions consistent.
  6. Move your old site directory out of the way and move your new site directory into your old site's place. You can alternatively use symbolic links or your web server configuration to do this switch. The purpose in the end is that when you point your browser to Managing News, it should be served from the new code base.
  7. Point your browser to your Managing News site's update.php and step through the interactive update process.
  8. RUN CRON ONCE. This is particular to Managing News and important for clearing all caches. You can run cron manually from admin/reports/status.

Automatic upgrade with Aegir

Managing News can be upgraded (migrated) with Aegir just like any other Drupalsite. No special measures need to be taken. Read more about Aegir here.

Special upgrade notes for particular versions

Upgrading from Beta 7

Due to a restructuring of the theme, wallpapers, logo images and custom color configurations will be lost during the upgrade. Prepare to reconfigure these settings after upgrading.

Any customizations to Views, Data tables, Feeds importers, Open Layers map configurations or similar that have been undertaken on the Managing News application before the upgrade may potentially conflict with the upgrade. Prepare to revert these changes to code and reconfigure them.

Managing News Beta 7 adds a new vocabulary for channel tagging. The site expects this vocabulary's ID to be 2, but this will not be the case for sites that have added their own vocabularies prior to upgrading. To correct this, you must upgrade your site and then alter your database so that the Channel tags vocabulary has the vid of 2.

See also

External resources