Issues after the update from 2.5.7 to 2.5.16

A number of issues have cropped up due to / during / after the update of the forums from 2.5.7 to 2.5.16 at the beginning of this week. This is a list of those issues as I have compiled them. It is a work in progress and I will update it when more information becomes available.

1 Username and email problems for some users. (fixed 2009-12-03)

Some users have a suffix appended to their username and their email address replaced with a random string (as a consequence email notifications don't work anymore). This problem is being worked on. Time to fix is unknown. Users experiencing this problem are requested to report so in this thread: My user handle and e-mail have been changed without my knowledge Please include your old username, which Adobe ID's you have and whether you used the same email address for those Adobe IDs.

2 Some user preferences are lost when logging in. (fixed 2009-12-03)

When you log in to the forums (either manually or automatially based on a "Remember me" cookie), some of your preferences are overwritten by their default values. The most noiceable prference is the settng to display your screen name (real name) that will get reset to displaying a username. This problem is being worked on. Time to fix is unknown.

3 The Rich Text Editor (RTE) is inserting linebreaks.

When typing a post the RTE will randomly insert linebreaks.

Workaround: remove the linebreaks manually.

4 Raw (FreeMarker?) code is inserted in some posts (through the RTE?).

In some posts code appears that was not entered by the user. The code looks something like below (but there may be much more then just this one line):

function(){return A.apply(null,[this].concat($A(arguments)))}

Workaround: edit the post and remove the code.

5 The logout button disappeared.

The logout button is no longer visible.

Workaround: How can I log out from the forums?

6 Search is down on one node. (fixed 2009-12-03)

Search is down on the SGAURWA41P cluster node. This does not show itself as an error, but instead as 0 search results.

Workaround: restart all browser windows and you may end up on another cluster node or use Google with a "site:forums.adobe.com" search modifier.

7 Users have 404 problems on first request.

This is not really a new problem, but it is something that was supposed to be fixed with the update. The problem is caused by the forums inserting a jsessionid parameter in the wrong place in the URL.

Workaround: reload the page where the incorrect link is located.

8 Image upload through camera button doesn't always work. (fixed 2009-11-30)

Some people have reported problems with uploading JPG and PNG images using the camera icon.

Workaround: attach the images instead.

Update 2009-11-28:

A probable cause for the error [The content type of this image is not allowed.] when uploading images through the camera button has been identified. Internet Explorer uploads images using a Content-Type header that differs from the IANA registered type for jpg and png images. As such, the recommended workaround for people wanting to upload images using the camera icon is to use a browser that is not Internet Explorer.