You can now do bulk mark message as deleted and not deleted operations in the Message administration for your websites.
Say you have a product section with lots of related webpages on your website and that you are no longer going to carry that product. Using a bulk operation you can mark the whole product section as deleted with just a few clicks.
Four checkbox preferences have been added to your user account profile that give you control over most website pending disablement status report emails. These reports are sent when your websites are pending disablement after no payment has been received for your user account. The preferences are...
Email two week website status report - pending disablement.
Email one week website status report - pending disablement.
Email three day website status report - pending disablement.
Email one day website status report - pending disablement.
By default the preferences are checked. I encourage you to keep them checked as email, although pretty reliable, is not a perfect system. Emails can and do get lost and misplaced and you should only be receiving these emails when your websites are about to go offline.
You can now control what HTML markup elements (tags) are allowed to be entered into your discussion messages.
There is a list of builtin markup elements that can be toggled between allowed and not allowed. The list of builtin elements is from XHTML Modularization 1.1 - Second Edition.
You can also add your own custom elements.
See How To Edit Allowed HTML Elements.
When a non-allowed element is entered it is escaped. The escaping happens after the markup language for your message is rendered.
The social bookmarking is now working on your websites tag webpages.
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.
I've added the weblog entry permalink to discussion messages that have been marked as weblog entries.
This will save you a trip to the weblog entry itself to grab the permalink for use in other places.
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.
Your websites now have social bookmarking. Users of your website can share content they find of interest. This feature is enabled for weblog entries, webpages, and discussion messages.