In addition the following: I registered a new property group (variation on sample consulting group). This works, the wizard with uploading a single file uses it. Even the "add property group" icon works, at least when accessing files in okm:root. In My Documents, it is still grey, even with files with the property group attached. When I copy a file from My Documents to okm:root, the icon works again.
Looks like something with user rights?
Because information matters
Inactive my "Add property group"
- OpenKM has many interesting features, but requires some configuration process to show its full potential.
Forum rules: Please, before asking something see the documentation wiki or use the search feature of the forum. And remember we don't have a crystal ball or mental readers, so if you post about an issue tell us which OpenKM are you using and also the browser and operating system version. For more info read How to Report Bugs Effectively.
In version 5.x metadata ( propery groups ) are only allowed in taxonomy, at version 6.0 we added in any panel, that really was a feature that we've have think to be changed to allow in any place ( except in trash view )
I think it will be alright to ask a similar question here.
As log as the Administrator (ROLE_ADMIN) wants to add a property group, it goes well. But "add property group" is inactive for the users (ROLE_USER), though they use a similar profile as administrator (Default Profile + Wizard) and the all the security rights are granted.
Should I check or set anything else?
PS: I want to let the users to add the defined property groups to the files and also be able to force them (which is evidently not completely possible) to add metadata, keyword, etc. (according to the wizard) to the files they upload.
Thanks in advanced for your help and suggestions
EDIT: OpenKM Trial v6.2.4 (build: 13753)
UPDATE: add property group will be active for users , IFF the file is selected with the check box (highlighting with right click will not suffice for users, but works for admins). However after setting the metadata this error message is shown : Error when communication with server (AddGroup). I have noticed that the same error message is generated, when a user tries to upload a file (but the file will be uploaded!).
As log as the Administrator (ROLE_ADMIN) wants to add a property group, it goes well. But "add property group" is inactive for the users (ROLE_USER), though they use a similar profile as administrator (Default Profile + Wizard) and the all the security rights are granted.
Should I check or set anything else?
PS: I want to let the users to add the defined property groups to the files and also be able to force them (which is evidently not completely possible) to add metadata, keyword, etc. (according to the wizard) to the files they upload.
Thanks in advanced for your help and suggestions
EDIT: OpenKM Trial v6.2.4 (build: 13753)
UPDATE: add property group will be active for users , IFF the file is selected with the check box (highlighting with right click will not suffice for users, but works for admins). However after setting the metadata this error message is shown : Error when communication with server (AddGroup). I have noticed that the same error message is generated, when a user tries to upload a file (but the file will be uploaded!).
sorry I know it is annoying to post relentlessly and the error may be irrelevant to this post, but since I am on the subject I though the error from the server.log might be helpful.
This appears in log file, when I add a property to a file as a user (not administrator)
This appears in log file, when I add a property to a file as a user (not administrator)
Code: Select all
2013-01-15 16:47:24,658 [http-bio-0.0.0.0-8080-exec-16] ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/OpenKM] - Exception while dispatching incoming RPC call
com.google.gwt.user.server.rpc.UnexpectedException: Service method 'public abstract void com.openkm.frontend.client.service.OKMMassiveService.addGroup(java.util.List,java.lang.String)' threw an unexpected exception: com.openkm.frontend.client.c:
/okm:root/jever/Docs/100602_Lösungskatalog_web_d.velop.pdf
51c82a1b-3ebe-4737-92e3-82ca6a2437d7 : 1a374a83-d65b-4277-907f-a320a13263a2
at com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:385)
at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:588)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:208)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:248)
at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:311)
at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:116)
at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:83)
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:323)
at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113)
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:323)
at org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:101)
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:323)
at org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113)
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:323)
at org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54)
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:323)
at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45)
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:323)
at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:182)
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:323)
at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87)
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:323)
at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:173)
at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346)
at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:999)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:565)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:309)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: com.openkm.frontend.client.c:
/okm:root/jever/Docs/100602_Lösungskatalog_web_d.velop.pdf
51c82a1b-3ebe-4737-92e3-82ca6a2437d7 : 1a374a83-d65b-4277-907f-a320a13263a2
at com.openkm.servlet.frontend.MassiveServlet.addGroup(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:569)
... 44 moremahyar better if you add the question in other post because this is related to massive add group feature in trial version, and this is other kind of problem that is not related with initial post.
Add somes creenshot with user with ROLE_ADMIN and other with ROLE_USER.
Take only as a note actual openkm version is 6.2.8 and between 6.2.4 to 6.2.8 we have corrected some bugs ( yes I know, should be good idea release a new trial version but needs a lot of work and we have decided stay 2-4 months with a trial before release new version, when the cycle will be finished will release a newer version). To test this feature you could try our demo.openkm.com which has latest version ( try to reproduce there ).
Add somes creenshot with user with ROLE_ADMIN and other with ROLE_USER.
Take only as a note actual openkm version is 6.2.8 and between 6.2.4 to 6.2.8 we have corrected some bugs ( yes I know, should be good idea release a new trial version but needs a lot of work and we have decided stay 2-4 months with a trial before release new version, when the cycle will be finished will release a newer version). To test this feature you could try our demo.openkm.com which has latest version ( try to reproduce there ).
thanks, this was actually all I needed to know. I will not try to test all the functions and features in my installation anymore, but will check these things with online demo.
OpenKM 5.1 maintenance period has ended. We only support some special customer installations. I recommend to upgrade to OpenKM 6.2