i've updated the need_for_speed-branch. it should be fully functional now and (hopefully significantly) faster compared to the main-branch of antville (quite a bunch of code was either removed or streamlined). please give it a try and tell me how it performs on your systems (and of course: please report any new - or newly introduced - bugs).

i think we're really close to the mysterious FC now ;-)

This is more or less a design and cross-site-scripting issue: The login page should be a standalone page and not modifyable within the skins of a blog. Everybody with proper knowledge in DHTML, Javascript is able to logout a user and maybe forcing a subscriber to relogin on the modified blog. Redirect the username and password to another server and redirect it back to antville. If the login-page (template, snippet) is not changeable, it would be no problem at all within the login-skin. It is still possible within all skins to login, logout, and redirect, but it should not be possible within the login-skin.

In this case antville needs to step back to a central sign-on that is trustworthy.

Solution: skins/edit?proto=membermgr&name=login should be not modifyable within a blogs skin.

My point of view is, the login-procedure should be somewhat trusted and not changeable/accessable within a users skin.

Suggested workaround: never ever login on another blog. If you don't have a blog, thats mmhhh say: bad luck - or a lesson in trust - you can use mine. (o;

It happened to me twice today that clicking one of the recently-modified-items in my weblog produced a strange outcome. I still get "my" url in the address-field, but a completely different page (see screenshot at left). When I reloaded the page, everything was alright again.

When I go to a topic thru the topics page and select a topic, then at the bottom click "...next page" I get the error:

URL /ajtcs/topics/Computers+and+Internet was not found on this server!

This is because the spaces %20 as they should be are replaced by + signs in the target URL.

I think this is so for all antville logs so please look at it.

Isn't any body else having problems with this ?

GreetZ , Peter Lunk ajtcs.antville.org

I configured IE5/Mac OS X to display JavaScript Errors. When I edit a skin in the skin editor the browser reports an error at the line: <script type="text/javascript" src="xxx.antville.org"></script> I suppose it's because the script at xxx.antville.org/javascript contain the html script tag. Can you confirm this?

Have you axed the Wiki thingy? <* ... *> doesn't work anymore.

I'm not sure what the "enable archive" option is good for but I noticed that topics don't work when the archive is disabled, i.e. when you click on a topic you will be redirected to the frontpage. An result is that you can't create stories that are online in topics only.

I propose to ditch this function entirely because I don't see the point in disabling the archive and it only causes confusion to newbies. What do you think?