Ulf Dittmer

The JForum2 software has been localized for a number of languages, but unfortunately some of those localizations are rather out of date - new features have been added, and for those only a few translations are available. Some languages are in good shape, but the others are in need of volunteers that can look through what's missing and help us out with translations. For more information, please head over to the JForum2 support forums. Thanks!

Since this thread is getting a bunch of extra attention, maybe I should say a bit about what JForum is. It's an open source Java web app for hosting public (or private) discussion forums. It works with the common SQL databases, and has a number of advanced features such as fine-grained permission and access control, thread bookmarks and thread and forum watching, powerful search, and numerous configurations for fine-tuning its behavior. In my opinion (biased, as I'm one of the committers to JForum) it's the best Java-based discussion software.

The JForum team has just released JForum 2.5.0, which has a number of new features (including mobile-friendly views of a number of pages) and numerous other improvements and bug fixes. A full list of what's changed can be found at https://sourceforge.net/p/jforum2/wiki2/NewFeatures250/, and the download is at https://sourceforge.net/projects/jforum2/files/. We welcome questions and suggestions at http://jforum.andowson.com/ (naturally hosted on JForum :-)

As a follow-up: the newly released JForum 2.5.0 has mobile-friendly views of a number of pages. Not exactly responsive, but better than nothing :-)

I have just checked in a fix for this, so it's available to anyone building JForum from source, and it will be part of the next regular release.

I think this topic can remain, if for no other reason than to remind people that the 2.1.9 version is not safe, and that they should switch to 2.4.1 at the least.

Please send me a "Purple Mooseage" (a.k.a. a private message) with the details and preferably your email - I'm one of the committers of JForum2.

Thanks for trying to debug the registration process, Tim. I'm not sure what's going on, maybe the captcha was acting up - did that get displayed for you, Mike?

Mike, I've sent you a message with contact information for the two principal developers (one of which would be me).

This looks similar to the already lengthy discussion at http://jforum.andowson.com/posts/list/141.page; maybe you can join in there?

JForum currently has no mobile (or responsive) version, and nothing to that effect is in the works (I'm a committer to the project, so I should know :-). If you want to start a discussion about this, head over to http://jforum.andowson.com/ where JForum2 is discussed and supported.

That should be sufficient. While you're at it, you should also expand the jforum_privmsgs.privmsgs_ip field (which stores the IP address for private messages). While that is not currently being filled in, it will be soon.

You can check out JForum2, one of the more popular open source Java-based forum web apps (disclaimer: I'm a committer, so obviously biased). You can see it in action at http://jforum.andowson.com/forums/list.page; that should give you some ideas what you might want or need.

The first thing to do is to switch to the latest JForum2 version, which you can find at https://sourceforge.net/projects/jforum2. Drop the war file into your servlet container, and proceed from there.

Hard to say, you may want to ask the question over at http://jforum.andowson.com/forums/list.page where JForum 2.x is supported.

Yes, after the initial run that extracts the war file. Or does your servlet container a) not unpack the war file, or b) does it do so every time the server is started?

Every time i restart my WildFly service and run my JForum, installation form is displayed and every time forum is created from scratch.

Only just saw this. The installation form is displayed even if you access an URL like http://localhost:8080/jforum2/? That sounds odd. You should actually remove the mapping of the InstallServlet after the initial install, so that nobody accidentally accesses it.