UBB.threads 6.1 has been released to the Member Area
What's new for 6.1? <img border="0" title="" alt="[Confused]" src="images/icons/confused.gif" />
An important security fix that affects all versions of UBB.threads. If, for some reason, you cannot update to version 6.1 please
read this post for patch information.
The ability to back up your UBB.threads database from the admin panel (read the notes below).
The ability for users to opt out of mass emails sent by the admins.
Mass emails can now be sent in HTML or text instead of just text.
Admins can use a custom database prefix so that they can run more than one board per database. This is for new installs only. Existing installs cannot be changed.
Admins can use a custom cookie prefix. Again this is so that more than one board can be run per domain. You can change this prefix at any time but if you do change the prefix your users will all be logged out and must log back in again.
Admins can add more (or remove) graemlins via the admin panel.
Admins can add more (or remove) message icons via the admin panel.
Attachments now use a download script rather than direct linking to the attached file. There is also a counter to show how many times an attachment has been downloaded.
Added a new time format option (HH:MM DD/MM/YYYY).
Made all subject text boxes the same size, as there were different sizes in different scripts.
Made a change so the temporary password field is always cleared out on successful login.
Added an image next to the subject of posts that are sticky. Thanks to Lisa_P for the image.
Rick has posted a more in-depth change log
here.We have an updated and improved version of the UBB.classic to UBB.threads import script available in the Member Area. The previous import script will not work for UBB.threads 6.1. For more information on the importer script please
read this thread.MySQL backup notes:
The user that PHP runs as must have access to the mysql and mysqldump binaries on the server or the process will fail.
Be sure to read the file size displayed after the backup. If the file size is 0 bytes the backup did not work. If the file size is far smaller than your database it may not have completed.
If you are using MySQL 4.x the database user must have LOCK TABLES permissions. This is a new permission as of MySQL 4.0. Default for this permission is 'N'.
If you are using MySQL 4.x updated from a 3.23.x version and do not have this permission in your mysql.users table you've forgotten to run the update script.
Read this for more.Honor The Victims
