miniBB version 2.0 FINAL is out!

Yes. Also, you can do this:

5) delete _install.php and _install_mysql.sql

even befor uploading the BB on the server, because you won't install it as a new board - you already have the DB.

And

10. Try if the board works :)))

Thank you for your input, Ivan. The job is done!
Moved my forum to a new server and made the upgrade from 2.0 RC2a to 2.0 Final.

I had to import the database through SSH because it was about 39 megabytes and phpMyAdmin cannot import files > 2 Mb. I also had to change the "ENGINE=MyISAM CHARSET=latin1 AUTO INCREMENT=..." lines in the dump file into "TYPE=MyISAM AUTO INCREMENT=..." in order to get the import done. Finally I had to remove some lines from the !UPDATE_DB.sql file because, apparently, they had already been executed (found this strange).

At first sight everything seems to be fine, except for 2 things:

1) When I want to edit messages that have been posted prior to the upgrade, I also get the html-codes in the message form, mostly <br>, <b>, <i> of course.

I don't have this problem with new messages I post (under 2.0 Final). When I take a look into the MySQL database, I see <br /> is placed in the new messages, instead of <br>, <b> becomes <strong>. <i> becomes <em>. So I assume I can correct the problem by changing all <br>, <b> and <i> tags into <br />, <strong> and <em> in my dump file?

2) The server that hosts my forum is based in the US. But all visitors to my forum live in Belgium and Holland in Europe. We are 9 hours ahead of the US. All time stamps under 2.0 RC2a are correctly showed under 2.0 Final. But now, after the upgrade, when I post new messages, the timezone for those new messages is, of course, US. I asked the webhosting provider if they could change the timezone, but they say it's not possible.

Of course, this is a major issue. So my question is if there's a possibility (modifying the forum code somewhere) that all new messages get the US time stamp + 9 hours ?

Pascal

You didn't need to remove any line from the DB update file :) If the request had already been executed somewhen, this won't be done again. Only an error will be shown and noting else.

1) is normal. It's because the new code implementation. At everyone is the same.

2) It's not an issue. The option for the timestamp and the time difference is in setup_options.php. Set it up there.

And, by the way, read the manual from time tio time in such cases.

Pascal
For converting old tags to new, look up for "Changes comparision: 2.0 RC5a - 2.0 RC6" in update history file, and in 4th point, there are some SQL commands to execute.

) It's not an issue. The option for the timestamp and the time difference is in setup_options.php. Set it up there.

It's not a solution, because the $timeDiff variable affects old and new messages. When I set $timeDiff at 32400 (9 hours), the time stamps from all the old messages (more than 36000 messages!) will change, and of course, that's not what I want.

So anyone who can make some code that can be added to the script?

Pascal

Paul might suggest something.

Pascal
PHP solution for such kind of task would be difficult. You need to fix dates in your old mySQL dump first. For example, notice largest topic ID, from what you want to update, and largest post ID. Then execute some kind of the following SQL:

update minibbtable_posts set post_time=FROM_UNIXTIME(unix_timestamp(post_time)+10800) where post_id<='max_post_id';

Substitute minibbtable_posts with your posts table name, +10800 with time difference to set in seconds (in this example, + 3 hours; 10800 seconds = 60 sec. * 60 min * 3 hours); max_post_id is your maximum post ID to count from.

The same type SQL must be executed also for topics table:

update minibbtable_topics set topic_time=FROM_UNIXTIME(unix_timestamp(topic_time)+10800), topic_last_post_time=FROM_UNIXTIME(unix_timestamp(topic_last_post_time)+10800) where topic_id<='max_topic_id';

I haven't tested this all out, but should work...

Hello Paul,

That's a fantastic (and easy) solution! It works very well.

Thanks!

For converting old tags to new, look up for "Changes comparision: 2.0 RC5a - 2.0 RC6" in update history file, and in 4th point, there are some SQL commands to execute.

Thanx. I see there are no sql commands listed for the old <b>, </b>, <i>, </i> html tags though. Can I execute the following commands to upgrade them?

update minibbtable_posts set post_text=REPLACE(post_text,'<b>','<strong>') where POSITION('<b>' IN post_text)>0;

update minibbtable_posts set post_text=REPLACE(post_text,'</b>','</strong>') where POSITION('</b>' IN post_text)>0;

update minibbtable_posts set post_text=REPLACE(post_text,'<i>','<em>') where POSITION('<i>' IN post_text)>0;

update minibbtable_posts set post_text=REPLACE(post_text,'</i>','</em>') where POSITION('</i>' IN post_text)>0;

Regards,
Pascal

Why to ask? Try and you'll see :-) Yes, it seems all commands are ok...

I'm not a sql wizard. That's why I want to hear the experts first :-)
The commands worked.

I discovered 2 things:

1) the {$loginName} tags in the Dutch e-mail templates do not work. The username is not shown in the e-mails. Didn't check the English ones, but I assume they have this problem too.

2) the $l_search[11]='Match whole words'; line in the language files is not necessary as it is not used anymore.

Pascal

So, you can fix the pack and send it back to us (ghappa [AT] gmail.com). We are not responsible for 3rd party packs.

I'll send it to you.

I've got 2 additional questions:

1) How to center the forum ?

2) The button in the 'new post' and 'new topic' forms doesn't light up when you click in one of the fields. How to solve this?

P.

1) This is done in CSS, classes table.forums, table.forumsmb, .tbTransparent, .tbTransparentmb etc. Compare old CSS to the new one, and you'll find the differences, which are responsible for align.

2) Sorry, I didn't get this one.