This is a simple step-by-step guide for people who want to update their antclick 1.0 pre1 installation to a recent version.

1. Get a fresh version from antclick from CVS or from the download page.
2. Install the fresh antclick version side by side to your old installation (i.e. do not overwrite the old version) and make sure both are not running.
3. Copy the following directories from your old installation to the new one:
   1. db/antville/*
   2. data/*
Do not work on the original files, and make sure you have backup copies!
4. Next, you need to update your antclick data to a new database format. You do this by invoking the following command from command line in your new antclick installation:

   java -cp lib/ext/mckoidb.jar com.mckoi.tools.DataFileConvertTool -path data

   Note that you may have to include the full path to your java runtime such as C:\programme\j2sdk1.4.1\bin\java . You should get the following output:

   Version 1.1 found. Converting database to version 1.2 schema... Guessing administrator is: admin Setting grant options for administrator. Converting: APP.AV_ACCESSLOG Converting: APP.AV_CHOICE Converting: APP.AV_FILE Converting: APP.AV_IMAGE Converting: APP.AV_MEMBERSHIP Converting: APP.AV_POLL Converting: APP.AV_SKIN Converting: APP.AV_SYSLOG Converting: APP.AV_TEXT Converting: APP.AV_USER Converting: APP.AV_VOTE Converting: APP.AV_SITE -- Convert Successful --

5. Finally, you need to add some columns to the database tables which have been added to antville since antclick 1.0 pre1. To do this, we launch the Mckoi Query tool:

   java -cp lib/ext/mckoidb.jar com.mckoi.tools.JDBCQueryTool -url jdbc:mckoi:local://./db.conf -u admin -p entwil

   A window similar to this should pop up. Enter the following line and hit "Run Query".

   alter table AV_USER add column USER_EMAIL_ISPUBLIC tinyint(1) null

   If you don't get any error message and the result grid says "0", you should be fine.

6. Exit the Mckoi Query tool and start antclick via hop.sh or hop.bat, depending on whether you are on Linux/Unix/OS X or Windows. Your new antclick should be functional. However, if you customized some of the skins it is very likely that you have some additional work to do here. The new skin diff feature should help you catch up with the changes in the default skins.

While I have performed the steps in this guide several times myself, it is possible, even probable, that I missed something. If you meet any problems with your updated antclick, please let me know by adding a comment to right here.

I just saw such a cool Featureino over at Textism; check this: The PHP script (which could easily be re-implemented in Helma-ish ECMA) checks if the referrer is Google (one could extend this to other search engines), and if appropriate extracts the query string from the referrer URL, so it knows what the user is looking for at your site. Nothing groovy so far, that's what your vanilla eXTReMe tracker does, but now comes the clever bit: It marks up all occurences of the search terms in the response so they'll be highlighted with a little help from Mr. Stylesheet!

Antville needs this (or maybe it should be implemented at Helma level?)! Okay, maybe not now, with all the effort being put into getting a fine 1.0. But at some point, we've got to catch up with the competition. Maybe I'll even have a shot at it myself once I've got some spare time again.

More ideas: If there are a lot of search engine queries in the backlinks, you have a long list of links that start like "www.google.com..." and are cut off from there anyway. See the frist comment for an example of how silly this looks. We could replace the texts of those links with just the actual search terms and display this list of queries in a block instead above each other (to make it less bloated). Then we'd have the individual keywords extracted anyway and could use those for highlighting, if an apropriate option is turned on.

Has anybody tried to run antville on win xp? I did so today & hop.bat exited with the message "there is already a server running on port 80" - which i could not verify up till now. Any ideas / experiences?

i finished the need_for_speed branch in cvs and merged it with the main branch of antville. Here's a brief summary of what i did:

• cleaned up code and optimized performance
• logging (both access-logging and incrementing the read-counter of a story) is now done asynchronously. from now on it can take a minute for new referrers to be stored in database, same with read-counter of stories (but they should be correct now)
• it's now possible to display an existing weblog on the main frontpage of an antville-installation instead of the more or less static default frontpage. this is done by simply entering the alias of the weblog system configuration.
• added a new default story-skin called "embed" which will be used by the < story >-macro unless a different skin was chosed using the option "useskin" (see here).
• Implemented a "rescue"-mechanism to prevent stories/comments from being lost because the creator/modifier was logged out (timed out) or lost the session because of a changed ip-address: users will be redirected to the login-form as usual, but before the contents of the story/comment are saved in the session-object. After a successful login the story/comment will be created automagically.
• added a permalink for comments in their default-skins.

This version is currently only available in CVS (it's not installed here on antville.org!) Please give it a try and report any bugs or strange misbehaviour. If no serious bugs are appearing i would like to propose this version as v1.0 FC, with the final release coming within the next two weeks.

I figured out that using <% story id="..." %> you can easily make editable boxes in your template for linklists, desktop wallpapers, current readings etc. Here is little explanation in German. It only works because I'm using the story.display skin in a way it is not intended. A nicer solution would be an additional skin, say story.include.

It's just a new skin and tiny modifications in the skin manager (additional field) and the <% story %> macro (new default value for the skin). If you agree I can make the changes.

I am looking for someone who's running Antville on their own server and accepts logs to be created.

GreetZ, Peter Lunk

If you want something simple that runs out-of-the-box^TM, you can get a quite up-to-date snapshot of helma in a .jar, and the latest weekly antclick build.

If you're a developer and want a fresh copy of the full monty, you can download Antville and Helma from the CVS. Yes, there's a story explaining how to use the CVS. Or if you're on Windows and want to do it the clicky-clicky way, learn how Downloading Antville with WinCVS works.

Keywords: download Antville CVS snapshot newest current. It always took me too long to find the appropriate URLs for downloading up-to-date Helma and Antville versions. Consequently, I created this story with the search keywords above, so next time I forget the link and search for "download Antville from CVS", I will find something.