We're doing a custom skin for JForum, and right now the templates aren't working for the admin panel. Since we're more concerned with the user templates and those are working, we published the new templates and set up an alternate instance of JForum with the default skin on another box to talk to the same database so we could still perform admin duties while we finish the admin templates.
When we try to create new forums in the admin panel, they get cached somewhere and as a result don't show up on the user-viewable jforum version. We're trying to figure if the change is being write-cached on the admin box or if the jforum is read cached on the user-box and isn't reading the updated database table yet.
For performance reasons, jForum does a lot of caching of information in memory. Especially for pages like the overview page which requires a lot of queries to get all the needed information.
So, if you are running the admin server in a different web app context (or server), it is updating THAT cache information and not the information in your production cache. If you need to run this way, you'll need to restart the production web app for it to get updated info from the database.
A quick fix might be to just replace the templates in the admin subdirectory with the default on the production site and work on the new templates in the seconde "site"
You may also want to change the "Admin" link in the user pages to open a new browser window to make it look nicer. [originally posted on jforum.net by monroe]