Migration from R20061204 to R20061206

• Upgrade the source. Run action=upgrade.

Migration from R20061004 to R20061204

• Upgrade the source. Run action=upgrade.

Migration from R20060114 to R20061004

• Upgrade the source. Run action=upgrade.

Migration from R20051004 to R20060114

• Upgrade the source. Run action=upgrade.

• Optionally

  • Set ALLOW_NONRATERS_TO_EDIT to false to forbid a user from editing a page until they have rated something. This is the main means of defending against PhpWiki spammers.
  • Set ENABLE_CAPTCHA to true if you have libgd installed and you wish to try to block spam robots with an image ("captcha"). Set SHOW_CAPTCHA_CODE_AS_ALT_TEXT if you don't have libgd, you are willing to live with the security hole of showing the code word as text, and you don't mind a broken image showing in Internet Explorer.

Migration from 20050626 to 20051004 (1.3.9.GL10)

• Install new code
• If you need to squeeze every ounce of speed out, add the following lines to index.php:

// Turn off possibly expensive assert-ing
if (!DEBUG) assert_options(ASSERT_ACTIVE, 0);

• Change PHPWIKI_VERSION to 1.3.9.GL10 in index.php
• Run action=upgrade (see below). The only real change is to change the "numbacklinks" column to "category_size" on the HomePage.

Migration from 20050512 to 20050626 (1.3.9.GL9)

• Run action=upgrade by appending "?action=upgrade" to almost any URL and using the admin user and password. This will show several pages that are updated automatically, and several with the choice "edit conflicts - skipped Merge Edit, Restore Anyway".

  • You can ignore the 'mtime index not found' warnings. These are pages that did not have a modified time.
  • For almost every page, you can choose the "Restore Anyway" button, and it will overwrite what is in your wiki with what is in the "pgsrc" directory. (Choose that button by opening it into a new window, so you don't have to run action=upgrade over and over). This just creates a new version of the page, so you can still see the old version if you want.
  • If you want to see what is conflicting, you can choose "Merge Edit" (again I recommend into a new window) to see a page editor with the conflicts. Most of the time, they are not interesting and overwriting would be okay. On wikilens.org I found AddingPages and CreatePagePlugin had a few user comments I wanted to keep.
  • Run action=upgrade again to see if there are still pages that have not been updated. Update them all, either by merging or overwriting.

Migration from GalacticGopher to 20050512 (1.3.9.GL8)

• Remove the ManageBuddies, UpgradeInstructions, and TitleSearch pages. visit your HomePage?action=upgrade to load in the new versions of these pages.
• Add

/*
 * MIN_RATINGS_FOR_AVERAGE specifies how many ratings are needed before we are
 * willing to display an average rating for purposes of sorting and
 * recommending.
 */
if (!defined('MIN_RATINGS_FOR_AVERAGE')) define ('MIN_RATINGS_FOR_AVERAGE', 3);

• As of this release, you very much want to enable the MySQL query

cache, or things will slow down a lot, because it's asking for average ratings for a page like mad. See http://dev.mysql.com/doc/mysql/en/query-cache.html. Simplest is to add to the [mysqld] section of your my.cnf:

# Cache queries for speed
query_cache_size = 64M

and restart mysql.

Migration from StormZebra to GalacticGopher (1.3.9.GL7)

• To restrict themes to wikilens and csgsa themes, add the following to index.php (or equivalent)

/*
 * If PRESET_AVAILABLE_THEMES is defined, then these are the only themes offered.
 * Otherwise, everything in themes (other than "CVS") is shown.
 */
$PRESET_AVAILABLE_THEMES = array('wikilens', 'csgsa');

/*
 * BASE_THEME1 is 2nd in the overriding scheme.  That is, look for files in:
 *
 * 1. current theme
 * 2. BASE_THEME1 (if defined)
 * 3. 'default' theme
 */
define('BASE_THEME1', 'wikilens');

If you do not wish to offer the csgsa theme, you can take that out of PRESET_AVAILABLE_THEMES.

• To enable tell-a-friend-mini on register you must put:

if (!defined('TELL_FRIEND_ON_REGISTER')) define ('TELL_FRIEND_ON_REGISTER', true);

in index.php

• To restrict languages to English, add the following to index.php (or equivalent)

/*
 * If PRESET_AVAILABLE_LANGUAGES is defined, then these are the only
 * languages offered.  Otherwise, everything in locale (other than
 * "CVS") is shown.
 */
$PRESET_AVAILABLE_LANGUAGES = array('en');

if (!defined('FANCY_LOGGING')) define ('FANCY_LOGGING', true);

• Add the "logging" table. See schemas/mysql-initialize.sql for the CREATE TABLE statement.
• If course import is desired, obtain and add the course data table. See the grouplens/umn_course_catalog directory, or talk to TonyLam.

Migration from MoonBadger to StormZebra (1.3.9.GL6)

1. Go into index.php and set the new SEND_BUDDY_EMAIL to false with this line:

   • if(!defined('SEND_BUDDY_EMAIL')) define('SEND_BUDDY_EMAIL', false);

2. Go into index.php and define the new EMAIL_SERVER_NAME:

   • if (!defined('EMAIL_SERVER_NAME')) define('EMAIL_SERVER_NAME', <your web site here> );
3. You should now be able to visit your new Wiki, using the new index.php. Visit it. Delete the pages TextFormattingRules, LeftbarContent, CategoryConfig. Login as admin, visit each page, and use the remove button at the bottom of the page. The press the cute pink confirm button on the next page.
4. Visit the URL http://.../phpwiki/index.php/HomePage?action=upgrade. This will grab all the new pages and migrate users, buddies, etc.
5. Uncache all the pages: visit http://.../phpwiki/index.php/PhpWikiAdministration#Purge_Markup_Cache as admin and click the "Purge Cache" button.
6. Set SEND_BUDDY_EMAIL back to true if you want emails sent for buddy confirmations.

7. Log in as admin and delete the following pages if they exist:

   • ConvertPages2Users
   • ConvertRestaurants - use http://..../ConvertRestaurants?action=remove ... if you visit the page bad things will happen

Migration from WindWhale to MoonBadger (1.3.9.GL5)

The upgrade procedure

This procedure is for an existing pre-Moonbadger database. If you are starting out with Moonbadger, you should not need to upgrade.

• First upgrade to Windwhale (see the Windwhale section below)

Then perform the following actions. You should fill in your own database user, password, database name, wiki URL, and index.php file name (if you've changed it).

• Upgrade the database

% mysql -u user -ppassword -Ddatabase < phpwiki/schemas/mysql-moonbadger-upgrade.sql

http://.../phpwiki/index.php/HomePage?action=upgrade

• Change line 3 of migrate_categories.php to point to your index.php-like file. Run it:

http://.../phpwiki/migrate_categories.php

• Change line 3 of migrate_pagedata.php to point to your index.php-like file. Run it:

http://.../phpwiki/migrate_pagedata.php

• Follow instructions in ChefmozTutorial if you wish to be able to import restaurants.
• Visit the AmazonUpdate page at least every 90 days. Read AmazonImport for more information

</pre>

Migration from pre-Windwhale releases

What is Windwhale?

Windwhale is a release based on PhpWiki 1.3.9; we called it 1.3.9.GL4.

The upgrade procedure

• If you wish to protect yourself:

  • Back up the MySQL database
  • Back up the phpwiki tree
  • These two things combined can restore your old system
• Get Windwhale (CVS tag V1_3_9_GL4_0_2 if you have access)
• Change your configuration (index.php or whatever it has been named) to be as follows:

ALLOW_ANON_USER=true
ALLOW_ANON_EDIT=false
ALLOW_BOGO_LOGIN=false
USER_AUTH_ORDER = array("PersonalPage")
ALLOW_USER_PASSWORDS=true
USER_AUTH_POLICY=first-only
PASSWORD_LENGTH_MINIMUM=0
define('THEME', 'wikilens')
- Completely comment out $DBAuthParams (!)

• Log in as Wiki admin. After doing so, append to the end of the URL: "action=upgrade".

  • This will put new Wiki pages into your Wiki, although it will not change existing Wiki pages.

• Use the following MySQL query in a command-line tool to find the pagenames of raters in your system:

  • select distinct(pagename) from rating r, page p where r.raterpage=p.id;

  • you may prefer to execute this command with -e and pipe it into cat, so the fancy 'table' syntax that mysql generates on normal output is dropped. You can do that with a command like:

    • mysql -uuser -ppass -Ddatabase -e 'select distinct(pagename) from rating r, page p where r.raterpage=p.id;' | cat
• Visit the "ConvertPages2Users" page, and paste in all the raters in your system. Click the "Convert Pages to Users" button.

Whew! Now your existing users should be able to log in using the new style, as well as change their password to be non-zero length.