Open Source Document Management System | OpenKM

Hi,

I encounter an error when I do this:
Administration => User => Mail account => New filter => Browse folder:
==> The requested resource (/OpenKM/extension/DataBrowser) is not available.
Is it a bug ?

Indeed is not a feature

Which OpenKM version?

Version: 5.1.10-SNAPSHOT (build: 7539)

Hello,
It's any solution for this ? (I get same error)

Try upgrading to latest version at integration.openkm.com ( nightly build )

I do this 3,4 days ago but ok, I try

Hi - I now get a similar error when trying to do a repository import and click on the browse folder icons.

Version: 6.2.0 (build: 13077)

Thanks in advance for any help.

Jim

There was an error when importing OpenKM code to SurceForge and some file were missing. Please, try tonight nightbuild.

Yes, installing the latest nightly build cured my problem, repository import now works again
Many thanks,
Jim

How is the upgrade procedure?

After downloading the file Openkm.war from http://integration.openkm.com/6.2/, what must I do?. Simply replace the file /opt/tomcat-7.0.27/webapps/openkm.war with the new one?.

Thanks in advance

diego

If you just want to update your exisiting OpenKM 6.2 to the latest build, you should

1. stop tomcat
2. replace openkm.war
3. remove (or at least rename) OpenKM-folder in webapps
4. restart tomcat

Tomcat will then unpack openkm.war and recreate the OpenKM-folder. It might be necessary to change hibernate.hbm2ddl in openkm.cfg to "update" (instead of "none") as well.

Or are you upgrading from 5.x ?

macjaeger wrote:If you just want to update your exisiting OpenKM 6.2 to the latest build, you should

1. stop tomcat
2. replace openkm.war
3. remove (or at least rename) OpenKM-folder in webapps
4. restart tomcat

Tomcat will then unpack openkm.war and recreate the OpenKM-folder. It might be necessary to change hibernate.hbm2ddl in openkm.cfg to "update" (instead of "none") as well.

Or are you upgrading from 5.x ?

I want to upgrade from 6.2 to the latest 6.2 build! So I think that hibernate.hbm2ddl should be "none".

Thanks!

Normally is good idea set as update ( in this case I think we have not done any database change, but between version 6.2.0 to 6.2.1 in nigthly build can be done some database update, obviously we will release as 6.2.1 when we consider has arrived the moment )