A fix for this has just been checked in.

My guess is that it has something to do with the virtual Tomcat host. I just tried to install JForum as the ROOT web app (no virtual host), and I got correct URLs like "/install/install.page" rather than "//install/install.page" - which is indeed a different URL.

I'm not sure why Safari seems to mangle the URL.

The full URL for the install page would be http://localhost:8009/install/install.page?module=install&action=welcome (as you can see in the install.jsp file).

I can't think of what that might be - any JSP page should be able to access all classes in WEB-INF/lib and WEB-INF/classes.

When Tomcat starts up, are there any error messages in catalina.out or jforum.log?

That's odd. It sounds as if the jar file containing the actual forum classes is not present, or is damaged. Check that inside the WEB-INF/lib directory is a file called "jforum-2.5.jar", and that it is readable by executing "jar -tf jforum-2.5.jar" from the command line.

The basic steps are listed in https://sourceforge.net/p/jforum2/wiki2/UpgradingFrom241To250/. The basic outline is: !) stop the web app, 2) work through the steps on that page, 3) start the web app. If you have a specific question about a step, feel free to ask in more detail.

That is hard-coded in the JForumbaseServlet's init method class (variable defaultTemplatePath). But I doubt that changing the location of the templates directory has anything to do with this.

Anything in the log files, either JForum or server?

udittmer wrote:I'm fairly certain that the code makes assumptions about where it is.

Indeed it does. It is assumed to be in the "templates" directory that is in the root directory.

I don't think moving the templates directory is a good idea. I'm fairly certain that the code makes assumptions about where it is.

but it shows nothing

Anything in the log files, either JForum or server?

That could be the context.path entry I mentioned in config/jforum-custom.conf. The problem I see is that "context path" has a specific meaning for Java web apps (for the root web app it would be "/" which can't be changed), and I'm not sure that changing it in that config file would accomplish the right thing. No harm, on trying, I guess.

It means that if the directory does not exist, you should create it with write permissions for the user account that runs JForum.

I haven't tried this, but a few things come to mind:

In web.xml, CSRFGuard probably needs to map to /forum/*

You need to ensure that there are no *.ftl and *.page URLs elsewhere in the web app

There are a few entries in jforum-custom.conf that need to be adapted; at the least forum.link, homepage.link and context.path

An overview of what's new, changed and fixed can be found at https://sourceforge.net/p/jforum2/wiki2/NewFeatures250/

Strange, I had to do that, too. That wasn't necessary on my local development instance.

I got it, but I'm having problems getting JForum to use it. Even after setting Arabic as the board default language it isn't used by JForum, and doesn't show up in my profile settings. Not sure what's going on.

In general I would say it's better to encode the language files using the \uWXYZ notation you see in Russian file, amongst others. While some files use accented characters (Portuguese, for example), those tend to cause problems.