xwiki-users January 2012

xwiki-users@xwiki.org

48 participants
125 discussions

Re: [xwiki-users] dafault DB name change

by Haru Mamburu

Yes, I did. :-( XEM 3.4 javax.servlet.ServletException: com.xpn.xwiki.XWikiException: Error number 3 in 0: Could not initialize main XWiki context Wrapped Exception: Error number 3202 in 3: Exception while reading document [name = [XWikiPreferences], type = [DOCUMENT], parent = [name = [XWiki], type = [SPACE], parent = [name = [xwiki], type = [WIKI], parent = [null]]]] Wrapped Exception: Error number 3301 in 3: Exception while switching to database xwiki Wrapped Exception: Access denied for user 'test'@'localhost' to database 'xwiki' And actually there is no DB xwiki in Mysql. Xwiki is completely right. The rest settings in xwiki.cfg are intact. Kind regards Dmitry PS. Sorry for the private mailing > > 30 января 2012, 20:46 от Thomas Mortagne <thomas.mortagne(a)xwiki.com>: > > On Mon, Jan 30, 2012 at 5:06 PM, Haru Mamburu <haru_mamburu(a)mail.ru> wrote: > > > Hi, All! > > > > > > Does anyone know, is it possible to change default DB name xwiki to smth else? > > > > > > I changed in config.cfg, > > > > > > xwiki.db=test > > > > > > in hibernate.cfg.xml > > > > > > <property name="connection.url">jdbc:mysql://localhost/test</property> > > > > > > After XWiki reload it tries to access xwiki db still. :-( > > > > > > What is correct way to do it? > > > > Well that's supposed to be the correct way actually. You sure you > > uncommented xwiki.db ? > > > > > > > > Thanks in advance, > > > > > > Dmitry > > > _______________________________________________ > > > users mailing list > > > users(a)xwiki.org > > > http://lists.xwiki.org/mailman/listinfo/users > > > > -- > > Thomas Mortagne > >

13 years, 2 months

[xwiki-users] dafault DB name change

by Haru Mamburu

Hi, All! Does anyone know, is it possible to change default DB name xwiki to smth else? I changed in config.cfg, xwiki.db=test in hibernate.cfg.xml <property name="connection.url">jdbc:mysql://localhost/test</property> After XWiki reload it tries to access xwiki db still. :-( What is correct way to do it? Thanks in advance, Dmitry

13 years, 2 months

[xwiki-users] What is happening with xcontext object through process of creating a new page?

by Ozren Lasić

Hi, In order to customize WYSIWYSG editor only on some pages I have made following changes in wysiwyg_storeConfig macro: #macro(wysiwyg_storeConfig $parameters $editedDocument $fieldId $full) ... #if($xcontext.contains('wysiwyg_overriding_parameters')) #set($ok = $parameters.putAll($xcontext.putAll('wysiwyg_overriding_parameters'))) #end ... #end Part of sheet for these pages looks like this: #set($overriding_parameters = $util.hashMap) #set($ok = $overriding_parameters.put('plugins', ...)) #set($ok = $overriding_parameters.put('menu', ...)) #set($ok = $overriding_parameters.put('toolbar', ...)) #set($ok = $xcontext.put('wysiwyg_overriding_parameters', $overriding_parameters)) This is good enough for editors on previously created pages. Editors look (in inline mode) just the way I want. But, on new pages editors always use default configuration. To test these unexpected result I added following two lines in the sheet: #set($ok = $xcontext.put('foo', 'bar')) $xcontext.get('foo') On new pages $xcontext.get('foo') is displayed, and on existing ones it is bar. (Version 3.1) Thanks, Ozren

13 years, 2 months

Re: [xwiki-users] Workspace manager free default pages set

by Haru Mamburu

Thanks a lot for clarification. It makes sence now from explained point of view, but I still can't get WHY as global user on NON-workspace wiki I should see Workspace Manager menus? Anyhow I can't use Workspace Manager INSIDE virtual Wiki. It makes sence if you would extend Workspace manager and make it completely independent on each and every virtual wiki. So, the main reason why: it's just useles inside virtual wiki (for now) For me, e.g., ideal workflow looks like: Case 1. XEM -> virtual wiki isolated, no Workspace Manager on board Case 2. XEM -> virtual wiki isolated, WITH Workspace Manager on board. Each virtual wiki in this case will be able to produce it's own workspaces isolated from each other (like independent projects on the same server). Only Local Users can take part in workspace management. Case 3. XEM -> virtual wiki isolated + Workspace manager on board. Same as Case 2, but Local Users can log once in any virtual/workspace wiki they allowed AND via this login have access to each and every wiki they registered/invited. For current purposes I would prefer Case 1 behaviour. Soon I'd like to use Case 2 then 3 scenario, but for now - no way :-( Hope it would be useful for futher development. Kind Regards, Dmitry 27 января 2012, 16:48 от Eduard Moraru <enygma2002(a)gmail.com>: Oh, I see now. The way it works now when visiting a normal subwiki (not a workspace) is that: 1) If you are a global user (user of the main wiki), the menus will be displayed to you (and you will be thus exposed to the global context of which you are part of). 2) If you are a local user (user of a subwiki that is part of a wiki *farm*), you don`t see the menus any more and are isolated inside the wiki (and not exposed to the global context). So, as a conclusion, the menus appear to you based on your user type and not on the type of wiki you are currently viewing. Does that make sense now? Does this fit your usecase? If not, can you please elaborate on the reason why you would like global users not to be able to see the global context when viewing a regular subwiki? Thanks, Eduard On Fri, Jan 27, 2012 at 1:32 PM, Haru Mamburu <haru_mamburu(a)mail.ru> wrote: Thank you Eduard, Sorry, probably I wasn't clear in my questions... - I want to use WORKSPACE Manager on MAIN Wiki and manage them as designed. - BUT, the same time I want to use WIKI Manager to have completely independent from main wiki and other workspaces virtual wikis. So, I set up XEM, installed Workspace manager to play around AND with Wiki Manager created virtual Wiki. Now I completely stuck how to get rid of all Workspace Manager links in wiki farm (!) (not workspaces). I would prefer to keep running Workspace Manager on main Wiki AND Wiki farm simultaneously, if possible. Is there any simple solution? The only thing I suppose should work is to take *.vm files from XE and attach them to the skin file. Looks wierd and unpredictable for me :-( Kind Regards, Dmitry 27 января 2012, 14:26 от Eduard Moraru <enygma2002(a)gmail.com>: Hi Dmitry, Starting with 3.3, XEM has moved the main usecase for subwikis from farm to workspaces. This means that, additionally to the WikiManager application [1], now XEM also contains the Workspace Application [2]. The encouraged way of for creating a wiki farm right now (if that is really what you need) is to get XE, install WikiManager [1] and create your farm. If you *insist* on using XEM for creating a wiki farm, all you have to do is delete the WorkspaceManager space, thus removing the Workspaces application and disabling the extra menus that were getting in your way. Additionally, you should also remove the xwiki-platform-workspace-api-<version>.jar file from the /webapps/xwiki/WEB-INF/lib/ folder, since you don`t want to use it anymore and you have removed the UI. However, if your plan is to have global users that work on different subwikis (like an intranet with departments mapped to subwikis or a place where you work on projects mapped to subwikis, etc.), you might reconsider using Workspaces. In any case, I hope this solves your problem. Thanks, Eduard ----------------- References: [1] http://extensions.xwiki.org/xwiki/bin/view/Extension/Wiki+Manager+Applicati… [2] http://extensions.xwiki.org/xwiki/bin/view/Extension/Workspace+Application On Fri, Jan 27, 2012 at 11:57 AM, Haru Mamburu <haru_mamburu(a)mail.ru> wrote: Ooops, wrong solution. The problem is still active: is there a right way to get rid of Workspace Manager's links in virtual wikis in 3.4? 27 января 2012, 13:46 от Haru Mamburu <haru_mamburu(a)mail.ru>: > Hi All, > > By accident I found a soluion. For me it looks a bit wierd. > > If you set in xwiki.cfg xwiki.virtual.usepath to 0, then all menus become Workspace Manager links free. > > For now, if I want to use usepath and don't want to use Workspace Manager, there is no an "one click solution" :-( > > Is it a bug or it's a feature? Should I report it? > > Kind regards, > > Dmitry > > 27 января 2012, 01:34 от Haru Mamburu <haru_mamburu(a)mail.ru>: > > Hi. all! > > > > XEM 3.4. Main Wiki works fine. > > > > I want to set up virtual wiki without Workspace Manager application inside and it's links in menu, because as far as I inderstood it is useless in virtual wikis. > > > > What is right way to get rid of Workspace Manager and it's links in top menu in virtual wiki? > > > > Kind regards, > > > > Dmitry _______________________________________________ users mailing list users(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/users _______________________________________________ users mailing list users(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/users

13 years, 2 months

[xwiki-users] Issues upgrading to 3.4 from 3.1

by Chris Meyer

Hi All, I am trying to upgrade our existing xwiki implementation of version 3.1 to 3.4 and I am running into an error when attempting to start up the server. Environment: 1. OS: Redhat Linux 2. Container: Jboss 5.1 3. DB: Hypersonic At this point, I am just tying to get it to launch with the out-of-the-box configurations (no customization). Below is the stack dump I am receiving: 2012-01-27 10:45:52,759 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/xwiki 2012-01-27 10:45:53,146 ERROR [STDERR] (main) SLF4J: Class path contains multiple SLF4J bindings. 2012-01-27 10:45:53,146 ERROR [STDERR] (main) SLF4J: Found binding in [vfszip:/apps/jboss/ jboss-5.1.0.GA/server/default/deploy/xwiki.war/WEB-INF/lib/logback-classic-1.0.0.jar/org/slf4j/impl/StaticLoggerBinder.class ] 2012-01-27 10:45:53,146 ERROR [STDERR] (main) SLF4J: Found binding in [vfszip:/apps/jboss/ jboss-5.1.0.GA/common/lib/slf4j-jboss-logging.jar/org/slf4j/impl/StaticLoggerBinder.class ] 2012-01-27 10:45:53,146 ERROR [STDERR] (main) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. 2012-01-27 10:45:57,830 INFO [STDOUT] (main) 2012-01-27 10:45:57,811 [main] ERROR o.r.Reflections - could not create Vfs.Dir from url. ignoring the exception and continuing org.reflections.ReflectionsException: could not create Vfs.Dir from url, no matching UrlType was found [vfszip:/apps/jboss/ jboss-5.1.0.GA/server/default/deploy/xwiki.war/WEB-INF/lib/xwiki-platform-extension-api-3.4.jar/ ] either use fromURL(final URL url, final List<UrlType> urlTypes) or use the static setDefaultURLTypes(final List<UrlType> urlTypes) or addDefaultURLTypes(UrlType urlType) with your specialized UrlType. at org.reflections.vfs.Vfs.fromURL(Vfs.java:105) ~[reflections-0.9.6.jar!/:na] at org.reflections.vfs.Vfs.fromURL(Vfs.java:90) ~[reflections-0.9.6.jar!/:na] at org.reflections.Reflections.scan(Reflections.java:211) [reflections-0.9.6.jar!/:na] at org.reflections.Reflections.<init>(Reflections.java:103) [reflections-0.9.6.jar!/:na] at org.xwiki.extension.internal.DefaultExtensionLicenseManager.initialize(DefaultExtensionLicenseManager.java:84) [xwiki-platform-extension-api-3.4.jar!/:na] at org.xwiki.component.embed.InitializableLifecycleHandler.handle(InitializableLifecycleHandler.java:39) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.createInstance(EmbeddableComponentManager.java:295) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:358) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:324) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.lookup(EmbeddableComponentManager.java:147) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.createInstance(EmbeddableComponentManager.java:281) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:358) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:324) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.lookup(EmbeddableComponentManager.java:147) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.createInstance(EmbeddableComponentManager.java:281) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:358) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:324) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.lookup(EmbeddableComponentManager.java:147) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.createInstance(EmbeddableComponentManager.java:281) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:358) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:324) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.lookup(EmbeddableComponentManager.java:147) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.createInstance(EmbeddableComponentManager.java:281) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:358) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:324) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.lookup(EmbeddableComponentManager.java:147) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.createInstance(EmbeddableComponentManager.java:281) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:358) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.lookupMap(EmbeddableComponentManager.java:171) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.lookupList(EmbeddableComponentManager.java:155) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.internal.DefaultComponentManager.lookupList(DefaultComponentManager.java:84) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.observation.internal.DefaultObservationManager.initialize(DefaultObservationManager.java:142) [xwiki-commons-observation-local-3.4.jar!/:na] at org.xwiki.component.embed.InitializableLifecycleHandler.handle(InitializableLifecycleHandler.java:39) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.createInstance(EmbeddableComponentManager.java:295) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:358) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:324) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.component.embed.EmbeddableComponentManager.lookup(EmbeddableComponentManager.java:141) [xwiki-commons-component-default-3.4.jar!/:na] at org.xwiki.container.servlet.XWikiServletContextListener.contextInitialized(XWikiServletContextListener.java:73) [xwiki-platform-container-servlet-3.4.jar!/:na] at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3910) [jbossweb.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.apache.catalina.core.StandardContext.start(StandardContext.java:4393) [jbossweb.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:310) [jboss-web-service.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:142) [jboss-web-service.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461) [jboss.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) [jboss.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.web.deployers.WebModule.start(WebModule.java:97) [jboss.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.6.0_16] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) ~[na:1.6.0_16] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) ~[na:1.6.0_16] at java.lang.reflect.Method.invoke(Method.java:597) ~[na:1.6.0_16] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) [jboss-mbeans.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) [jboss-mbeans.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) [jboss-mbeans.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) [jboss-mbeans.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) [jboss-jmx.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) [jboss-system-jmx.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at $Proxy38.start(Unknown Source) [na:na] at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42) [jboss-system-jmx.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37) [jboss-system-jmx.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.0.6.GA] at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.0.6.GA] at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.0.6.GA] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) [jboss-dependency.jar:2.0.6.GA] at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286) [jboss-system-jmx.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) [jboss-dependency.jar:2.0.6.GA] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) [jboss-dependency.jar:2.0.6.GA] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) [jboss-dependency.jar:2.0.6.GA] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) [jboss-dependency.jar:2.0.6.GA] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) [jboss-dependency.jar:2.0.6.GA] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) [jboss-dependency.jar:2.0.6.GA] at org.jboss.system.ServiceController.doChange(ServiceController.java:688) [jboss-system-jmx.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.system.ServiceController.start(ServiceController.java:460) [jboss-system-jmx.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:163) [jboss-system-jmx.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:99) [jboss-system-jmx.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46) [jboss-system-jmx.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62) [jboss-deployers-spi.jar!/:2.0.7.GA] at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) [jboss-deployers-spi.jar!/:2.0.7.GA] at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) [jboss-deployers-impl.jar!/:2.0.7.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) [jboss-deployers-impl.jar!/:2.0.7.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) [jboss-deployers-impl.jar!/:2.0.7.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178) [jboss-deployers-impl.jar!/:2.0.7.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) [jboss-deployers-impl.jar!/:2.0.7.GA] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) [jboss-dependency.jar:2.0.6.GA] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) [jboss-dependency.jar:2.0.6.GA] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) [jboss-dependency.jar:2.0.6.GA] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) [jboss-dependency.jar:2.0.6.GA] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) [jboss-dependency.jar:2.0.6.GA] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) [jboss-dependency.jar:2.0.6.GA] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) [jboss-dependency.jar:2.0.6.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) [jboss-deployers-impl.jar!/:2.0.7.GA] at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702) [jboss-deployers-impl.jar!/:2.0.7.GA] at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) [jboss-system.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70) [jboss-system.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53) [jboss-system.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361) [jboss-system.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) [jboss-dependency.jar:2.0.6.GA] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) [jboss-dependency.jar:2.0.6.GA] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) [jboss-dependency.jar:2.0.6.GA] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) [jboss-dependency.jar:2.0.6.GA] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) [jboss-dependency.jar:2.0.6.GA] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) [jboss-dependency.jar:2.0.6.GA] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) [jboss-dependency.jar:2.0.6.GA] at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306) [jboss-system.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271) [jboss-system.jar!/:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461) [jboss-bootstrap.jar:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.Main.boot(Main.java:221) [run.jar:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at org.jboss.Main$1.run(Main.java:556) [run.jar:5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] at java.lang.Thread.run(Thread.java:619) [na:1.6.0_16]

13 years, 2 months

Re: [xwiki-users] Workspace manager free default pages set

by Haru Mamburu

Thank you Eduard, Sorry, probably I wasn't clear in my questions... - I want to use WORKSPACE Manager on MAIN Wiki and manage them as designed. - BUT, the same time I want to use WIKI Manager to have completely independent from main wiki and other workspaces virtual wikis. So, I set up XEM, installed Workspace manager to play around AND with Wiki Manager created virtual Wiki. Now I completely stuck how to get rid of all Workspace Manager links in wiki farm (!) (not workspaces). I would prefer to keep running Workspace Manager on main Wiki AND Wiki farm simultaneously, if possible. Is there any simple solution? The only thing I suppose should work is to take *.vm files from XE and attach them to the skin file. Looks wierd and unpredictable for me :-( Kind Regards, Dmitry 27 января 2012, 14:26 от Eduard Moraru <enygma2002(a)gmail.com>: Hi Dmitry, Starting with 3.3, XEM has moved the main usecase for subwikis from farm to workspaces. This means that, additionally to the WikiManager application [1], now XEM also contains the Workspace Application [2]. The encouraged way of for creating a wiki farm right now (if that is really what you need) is to get XE, install WikiManager [1] and create your farm. If you *insist* on using XEM for creating a wiki farm, all you have to do is delete the WorkspaceManager space, thus removing the Workspaces application and disabling the extra menus that were getting in your way. Additionally, you should also remove the xwiki-platform-workspace-api-<version>.jar file from the /webapps/xwiki/WEB-INF/lib/ folder, since you don`t want to use it anymore and you have removed the UI. However, if your plan is to have global users that work on different subwikis (like an intranet with departments mapped to subwikis or a place where you work on projects mapped to subwikis, etc.), you might reconsider using Workspaces. In any case, I hope this solves your problem. Thanks, Eduard ----------------- References: [1] http://extensions.xwiki.org/xwiki/bin/view/Extension/Wiki+Manager+Applicati… [2] http://extensions.xwiki.org/xwiki/bin/view/Extension/Workspace+Application On Fri, Jan 27, 2012 at 11:57 AM, Haru Mamburu <haru_mamburu(a)mail.ru> wrote: Ooops, wrong solution. The problem is still active: is there a right way to get rid of Workspace Manager's links in virtual wikis in 3.4? 27 января 2012, 13:46 от Haru Mamburu <haru_mamburu(a)mail.ru>: > Hi All, > > By accident I found a soluion. For me it looks a bit wierd. > > If you set in xwiki.cfg xwiki.virtual.usepath to 0, then all menus become Workspace Manager links free. > > For now, if I want to use usepath and don't want to use Workspace Manager, there is no an "one click solution" :-( > > Is it a bug or it's a feature? Should I report it? > > Kind regards, > > Dmitry > > 27 января 2012, 01:34 от Haru Mamburu <haru_mamburu(a)mail.ru>: > > Hi. all! > > > > XEM 3.4. Main Wiki works fine. > > > > I want to set up virtual wiki without Workspace Manager application inside and it's links in menu, because as far as I inderstood it is useless in virtual wikis. > > > > What is right way to get rid of Workspace Manager and it's links in top menu in virtual wiki? > > > > Kind regards, > > > > Dmitry _______________________________________________ users mailing list users(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/users

13 years, 2 months

Re: [xwiki-users] Workspace manager free default pages set

by Haru Mamburu

Ooops, wrong solution. The problem is still active: is there a right way to get rid of Workspace Manager's links in virtual wikis in 3.4? 27 января 2012, 13:46 от Haru Mamburu <haru_mamburu(a)mail.ru>: > Hi All, > > By accident I found a soluion. For me it looks a bit wierd. > > If you set in xwiki.cfg xwiki.virtual.usepath to 0, then all menus become Workspace Manager links free. > > For now, if I want to use usepath and don't want to use Workspace Manager, there is no an "one click solution" :-( > > Is it a bug or it's a feature? Should I report it? > > Kind regards, > > Dmitry > > 27 января 2012, 01:34 от Haru Mamburu <haru_mamburu(a)mail.ru>: > > Hi. all! > > > > XEM 3.4. Main Wiki works fine. > > > > I want to set up virtual wiki without Workspace Manager application inside and it's links in menu, because as far as I inderstood it is useless in virtual wikis. > > > > What is right way to get rid of Workspace Manager and it's links in top menu in virtual wiki? > > > > Kind regards, > > > > Dmitry

13 years, 2 months

Re: [xwiki-users] Workspace manager free default pages set

by Haru Mamburu

Hi All, By accident I found a soluion. For me it looks a bit wierd. If you set in xwiki.cfg xwiki.virtual.usepath to 0, then all menus become Workspace Manager links free. For now, if I want to use usepath and don't want to use Workspace Manager, there is no an "one click solution" :-( Is it a bug or it's a feature? Should I report it? Kind regards, Dmitry 27 января 2012, 01:34 от Haru Mamburu <haru_mamburu(a)mail.ru>: > Hi. all! > > XEM 3.4. Main Wiki works fine. > > I want to set up virtual wiki without Workspace Manager application inside and it's links in menu, because as far as I inderstood it is useless in virtual wikis. > > What is right way to get rid of Workspace Manager and it's links in top menu in virtual wiki? > > Kind regards, > > Dmitry

13 years, 2 months

[xwiki-users] Workspace manager free default pages set

by Haru Mamburu

Hi. all! XEM 3.4. Main Wiki works fine. I want to set up virtual wiki without Workspace Manager application inside and it's links in menu, because as far as I inderstood it is useless in virtual wikis. What is right way to get rid of Workspace Manager and it's links in top menu in virtual wiki? Kind regards, Dmitry

13 years, 2 months

[xwiki-users] Call for test Extension Manager

by Thomas Mortagne

Hi xwikiers, I just add clustering support which was the last big peace of framework that was blocking a first fully functional version of Extension Manager. I will now dedicate my time to write tests and fix bugs and small improvements I find and try to fix some UI bugs too if Sergiu does not have time. I also have some improvement work in XWiki Repository and finally make extension.xwiki.org fully based on standard XWiki Repository and not have custom version anymore. During the 3.5 and 4.0 timeframe it would be nice to get as much tests and reports as possible on what is not working or still blocker in term or usability so that we get a nice and strong first version we can advertise in 4.0. There is obviously lots of possible improvements some of which you can find on http://dev.xwiki.org/xwiki/bin/view/Design/ExtensionManager (and I need to add more things in there) but I would like to limit to a fully working minimum for 4.0 and then do a priority survey on the many new features and improvements ideas. Here are the grey areas I know about and on which I'm going to concentrate on writing tests: * automatic xar merging is a quick implementation not excessively tested. Also the string properties content merging is not able to merge modification done on the same line which is not nice when things like the title is customized in the wiki and also changed in the new version of the xar. Right now in doubt the merge always take the new version when there is a conflict so that nothing is lost since it's easy to get back the previous version from the history. Also I'm not going to have time to work on a real manual conflict resolution UI for this timeframe, not alone at least. * clustering is a bit young ;) Also it expect all members to have the exact same constraints, if for any reason an extension is installed to a member and fail on another it could create quite a mess if that's an important extension. * it's not very hard to add versions and dependencies in XWiki Repository but it require using object editor which is not very nice for all profiles of users (now it's generally done by the developer of the extension so not a basic user either). Will try to work on that if I have some time left. Thanks, -- Thomas Mortagne

13 years, 2 months

← Newer
1
2
3
4
5
6
7
...
13
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-users January 2012