Didactylos --

I did some checking on a couple of points that you made.

First of all, the "Last Post" feature: I too am a bit annoyed that it delivers you to the last page and not to the last post, but it appears that the heading of the column does not agree with the icon below it. If you hover your cursor over the icon, it does not say "Last Post" but instead it indicates "Last Page". I am not sure that being delivered to the last post would be the best solution. In very active threads such as you might find in the Teams Forum, it is very likely that there have been several postings made since your last visit to a thread. In other forums such as this one, most threads to not run into multiple pages (especially if you have set your profile to view 50 posts at a time) and it isn't that difficult to navigate to the bottom of the page. I will, however report the discrepancy between the column heading and the actual action taken to the techs.

Next: I believe that the navigation bar errors you point to when you are delivered to the last page were corrected quite some time ago. I know that I had reported the problem last April. I am not sure but I think the fix went in sometime last fall. I verified that I now see the correct page highlighted and that there is a "previous" selection listed.

I am afraid that I do not understand exactly what you are describing in the issue of attribute parsing. Perhaps you could give an example so that I could better understand the issue.

In getting the image to display when I quoted your post, I had to remove an "enter" or "return" between the specified image and the trailing {/img]. Using { instead of {, I will try coding the following myself:

"An example speaks a thousand words:
{img]http://gahood.org/user.png{/img]"

An example speaks a thousand words:

Seems I need the words as well :-(

mvnForum is replacing the linebreak with <br> and inserting that into the image attribute. Correct attribute handling requires that the linebreak be removed. Also, < and > are illegal characters in an attribute.

Quite simply, mvnForum is applying its filters in the wrong order, causing whitespace in tags to be significant. Not a big deal (like the previous/next thing), but a pedant like myself finds it annoying.

I know what's happening. I did my best to explain it, but it looks like I failed. Anyway, a little glitch like that can be ignored easily enough. Thanks for taking the time to look at it.

But to fix the last page functionality, please will you consider upgrading the forum software to RC4, where it is (mostly) fixed?

And another oddity I noticed.... several times, now, the forum has logged me out actually while I was browsing and posting. Most login systems use a rolling window for timing out a session. Yours, however, is tied somehow to the site login. And that's where it gets really weird, because while the forum shows me as logged out, the WCG bar at the top shows me as logged in. Is this a known issue?