Complement of upgrading from beta2

jetl

I upgrade it today, since I follow the official document, it went wrong. The server response a 500 error.

So I install Flarum completely. And I found some issues.

Database table was changed mostly

The guideline said

UPDATE `migrations` SET `extension` = CONCAT('flarum-', extension) WHERE `extension` IS NOT NULL;
UPDATE `config` SET `key` = CONCAT('flarum-', `key`) WHERE `key` LIKE '%.%';

It's not enough, many database table have changed as you can see.

I'm not going to list the change of all table, I want to say is, there are some little error that hardly be found.

Such as

Most of the tables was changed you can find it by yourself
The config table was rename to setting
Some properties in setting table were different to the config table
The most hidden problem is the notifications_read_time and notification_read_time key in table users

Besides, since you sync your old database with the new one, your site will works 🙂

Toby

Beta 3 contains an update script which does all of the hard work for you! It's run during step 7 of the update process:

Visit yourforum.com/admin and enter your database password to perform the update.

The two queries provided explicitly in the instructions are of a special nature – they are not related to core database changes, but rather the fact that extension names now have a vendor prefix (flarum-). That's why we included them in the instructions separately.

Sounds like you got it sorted, but for anyone else reading – you don't need to make any manual database changes, apart from those two queries. If you run into a problem with the update script, your best bet is to troubleshoot it 🙂

jetl

A ha, the first time I follow the guideline, my server return a 500 error too, maybe something I got missed

I'll test it again !