Read all about it at the project site.

feine Sache, das! off topic: kann ich mich hier eigentlich auch dafür bedanken, dass es seit zwei wochen keinen referrer-spam mehr gibt, oder is das einfach so ge.com?

I installed 1.1 final, and I can't assign a gallery to a newly uploaded image (I get 'Please only use alphanumeric characters for the topic name.' error - but I use only characters) nor assigning a category later (I get An error occurred while processing your request: [object Object] error).

I tested 1.1pre2 before, and it worked there without problems.

Hallo, hab mir voll Begeisterung gleich die Installation runtergeladen.
Nach Einrichtung des Servers erscheint aber leider nur

Error in application 'antville':

Action not found

an Stelle der Aufforderung zur Anlage der Administration.
Worauf deutet das hin?
Wäre jemand bereit, meine Installation zu prüfen?
Ich tüftle schon seit Stunden ...

Hi,

I'm setting up antville for use with slovak language, where I need/prefer to use UTF-8 encoding.

The first problem was with MySQL database. I've changed content-type in all page.skins, so the browser submited valid UTF-8 strings. Then I was changing skins and submited few test-posts. Everything seemed to work well until I restarted Helma. After restart the text was as if the encoding was different. Then I figured out (thanks to some post I found on google), objects are cached in Helma, therefore it works well, but after restart they are fetched from MySQL, and that's the source of problem - they are stored with Latin1 encoding there. I was able to fix this problem with parameters "useUnicode=true&characterEncoding=UTF-8" in JDBC connection string.

Another problem I've came into is skin's encoding. For the main page I need to change some skins which are stored on the disk. I edit and save the file in UTF-8 encoding. Unfortunatelly Helma/Antville obviously does not read it with this format.

I use "charset=UTF-8" parameter in antclick-1.1/apps.properties, and I append "-Dfile.encoding=UTF-8" to JAVA_OPTIONS in startup script like this:

JAVA_OPTIONS="-server -Xmx128m -Djava.awt.headless=true -Dfile.encoding=UTF-8"



At the moment I have a problem with filebased skins, and I guess this will be a problem for messages.language file as well, but I didn't start changing that yet.

The installation runs on www.weblog.sk and you can see mangled text in "menu" (bottom right corner).

Any help appreciated.

regards,
Michal

PS: I checked the helma's sourcecode, and found framework.core.SkinFile.read() method, where the file is read onto a char[] array. I'm not sure if this is correct, could it be that the encoding is lost after this, and every byte of the file is a character on its own - and because of UTF-8 is multibyte encoding, it can't be used this way ???

    private void read() {
        try {
            FileReader reader = new FileReader(file);
            //char[] c = new char[(int) file.length()];
            //int length = reader.read(c);
            InputStream in = new FileInputStream(file);
            BufferedReader r = new BufferedReader(new InputStreamReader(in, "UTF-8"));
            char [] c = new char[(int)file.length()];
            System.err.println("Yupeee");
            int length = r.read(c);
            reader.close();
            skin = new Skin(c, length, app);
        } catch (IOException x) {
            app.logEvent("Error reading Skin " + file + ": " + x);
        }
        lastmod = file.lastModified();
    }

Gibt es irgendwo eine ultimative und ausführliche Update-Anleitung?
Habe hier eine ziemlich komplexe Installation W2K/IIS/mod_jk/MySQL (http://blog.escapenet.ch), die ich bereits einmal ohne Erfolg auf eine der PRE Versionen updaten wollte...