The way webpage indexes work has changed. They are better integrated into the work flow of editing messages with the Relative Url field set.

Prior to the change webpage indexes were created on the fly. If you added a message and set the Relative Url field to /my/webpage/ then your website would build the /my/ webpage on the fly. The default presentation of the webpage index was to sort the list by the message topic in ascending order and use an (X)HTML unordered list.

To control elements of the webpage index such as title, sort by, and etc. you needed to make a trip to your TWH Admin and add an entry to the Webpage Index database.

Now when you edit a message and set the Relative Url field your website will add messages to your discussion with default entries for any missing webpage indexes. If you added a message and set the Relative Url field to /my/webpage/ then your website would add a message with the Topic field set to my, the Content field would be set to the template tag {% webpage_index %}, and the Relative Url field set to /my/. The default sort by behavior is as before.

To control the presentation of the index the webpage_index accepts two optional parameters sort_by and template_name.

For more information see How To Change A Webpage Index.

Access to discussion feeds is now controlled by the Can read messages option. When unchecked only logged in users can read discussion feeds.

The configuration for your discussion has changed.

The Can view comment/message links option has been moved into a new Anonymous User section on the change form. A new Can read messages option has been added to this section. The default is unchecked. When unchecked only logged in users can read discussion messages and listings of messages.

This is a change from the previous behavior which allowed anonymous users to read message listings but not messages. Because of this mixed access I was unable to cleanly preserve the previous behavior for your website. I opted for the more secure route of setting the new Can read messages option for your website to unchecked. If you want anonymous users of your website to be able to read messages and message listings then check the Can read messages option.

• Click on the TWH Admin link on your website.
• Click on the Database Admin link.
• Click on the Configuration link just after the M_Discussion link.
• Click on the Default link.
• Find the Anonymous User section of the change configuration form.
• Click the Can read messages? checkbox so that it has a check mark.
• Click the Save button.

The steps for entering a relative url for a message have changed. The relative url is now entered in the Add/Edit Message forms.

I needed to change the character set for a MySQL database with which I'm working. It was created with latin1 and I needed it to be in utf-8. Here are some relevant links.

• http://codex.wordpress.org/Converting_Database_Character_Sets
• http://www.mysqlperformanceblog.com/2009/03/17/converting-character-sets/

My need was pretty simple, convert the database without to much concern for the data itself. So my main challenge was how to loop over the tables in my database and alter the tables. I decided to use the mysql command line. Here is what I came up with...

USE databasename;

DELIMITER //

DROP PROCEDURE IF EXISTS test//

CREATE PROCEDURE test()

    BEGIN

      DECLARE done INT DEFAULT 0;
      DECLARE a CHAR(64);
      DECLARE cur1 CURSOR FOR SHOW TABLES;
      DECLARE CONTINUE HANDLER FOR NOT FOUND SET done = 1;

      OPEN cur1;

      LOOP

        FETCH cur1 INTO a;

        IF NOT done THEN

          SET @s = CONCAT('ALTER TABLE ',a,' CONVERT TO CHARACTER SET utf8');

          PREPARE stmt FROM @s;

          EXECUTE stmt;

          DEALLOCATE PREPARE stmt;

        END IF;

      END LOOP;

      CLOSE cur1;

    END//

DELIMITER ;