Sergiu Dumitriu wrote ..
>
> Try this:
>
> {{html clean="false"}}
> <fieldset>
> <input type="hidden" name="classname" value="XWiki.XWikiComments" />
> <textarea name="XWiki.XWikiComments_comment" rows="5" cols="80"></textarea>
> <input type="submit" name="action_objectadd" value="Send comment"/>
> </fieldset>
> {{/html}}
Fantastic. Thanks. I should have thought to look at the comments...
> The trick is the name of the submit button. action_objectadd instructs
> the server to ignore the action specified in the URL where the form was
> submitted, and instead to use the action that's specified after the
> "action_" part, in this case "objectadd". This special form parameter
> gets submitted only when clicking the "Send comment" button.
Out of interest where is that caught, I'd like to take a look at the
processing. If you're pretty busy don't worry - I'll probably
grep around in the files or code till I find it anyway!
Cheers,
Adam
Hi -
I see that XWiki Enterprise 3.0 Milestone 1 was just released a week ago.
I also found the roadmap at http://enterprise.xwiki.org/xwiki/bin/view/Main/Roadmap
I can't tell from the announcement however what the intended use is...
Is this something that is likely to blow up ("alpha" quality)?
At what point in the roadmap does it make
sense for a new install to try a 3.0.x release instead of 2.x release?
In addition to stability of the software, what about stability of any
APIs - are those frozen in M1?
If I adopt M1, will M2 automatically upgrade from M1, or are automatic
upgrades only assured for migration from a stable 2.x release?
When 3.0 final is out, will work on 2.7 basically stop?
Will the current release of XWord work with XE 3.0M1?
Regarding extensions, the listing at http://extensions.xwiki.org/xwiki/bin/view/Main/
says nothing about version compatibility. I'm guessing that because of the velocity upgrade,
trying any extension with heavy velocity usage would be a gamble with XE 3.0M1 ?
Or is there an automatic "smoke test" report somewhere of what extensions are
certain to not work?
Sorry for all the questions, but I seem to have hit xwiki at a cusp in its lifecycle
so I'm in a quandary about which version to start with.
-mda
I am trying to use getTOC, but unfortunately, my example always returns zero
...
{{velocity}}
#set($d=$xwiki.getDocument('Sandbox.WebHome'))
#set($tree=$d.getTOC(0,3,false))
$tree.size()
#foreach($key in $tree.entrySet())
* $key.value.text
#end
{{/velocity}}
Can somebody help me with syntax? What's I doing wrong?
Thanks beforehand!
Eugen Colesnicov
--
View this message in context: http://xwiki.475771.n2.nabble.com/Using-getTOC-function-tp5975427p5975427.h…
Sent from the XWiki- Users mailing list archive at Nabble.com.
I am trying to deploy xwiki on JBoss 5 using HSQL database. I have followed the Installation steps. When i start JBoss , it is unable to deploy xwiki.war . The other wars in the application are however deployed. The error message is given below.Please help.---------------08:12:19,078 INFO [TomcatDeployment] deploy, ctxPath=/, vfsUrl=ROOT.war08:12:19,397 INFO [TomcatDeployment] deploy, ctxPath=/docs, vfsUrl=docs.war08:12:19,508 WARN [config] Unable to process deployment descriptor for context '/docs'08:12:23,794 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console, vfsUrl=jmx-console.war08:12:24,313 INFO [TomcatDeployment] deploy, ctxPath=/logs, vfsUrl=logs.war08:12:24,619 WARN [config] Unable to process deployment descriptor for context '/logs'08:12:24,842 INFO [TomcatDeployment] deploy, ctxPath=/reports, vfsUrl=reports.war08:12:24,969 WARN [config] Unable to process deployment descriptor for context '/reports'08:12:25,311 INFO [TomcatDeployment] deploy, ctxPath=/updates, vfsUrl=updates.war08:12:25,402 WARN [config] Unable to process deployment descriptor for context '/updates'08:12:26,303 INFO [TomcatDeployment] deploy, ctxPath=/xwiki-enterprise-web-2.7, vfsUrl=xwiki-enterprise-web-2.7.war08:12:52,272 ERROR [Reflections] could not create Vfs.Dir from url. ignoring the exception and continuingorg.reflections.ReflectionsException: could not create Vfs.Dir from url, no matching UrlType was found [vfszip:/F:/gid_1/jboss/server/default/deploy/xwiki-enterprise-web-2.7.war/WEB-INF/lib/xbean-reflect-3.4.jar/META-INF/maven/]either use fromur-l(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.fromur-l(Vfs.java:104) at org.reflections.vfs.Vfs.fromur-l(Vfs.java:89) at org.reflections.Reflections.scan(Reflections.java:136) at org.reflections.Reflections.<init>(Reflections.java:91) at org.xwiki.extension.repository.internal.DefaultCoreExtensionRepository.loadExtensions(DefaultCoreExtensionRepository.java:84) at org.xwiki.extension.repository.internal.DefaultCoreExtensionRepository.initialize(DefaultCoreExtensionRepository.java:72) at org.xwiki.component.em-bed.em-beddableComponentManager.createInstance(em-beddableComponentManager.java:429) at org.xwiki.component.em-bed.em-beddableComponentManager.initialize(em-beddableComponentManager.java:361) at org.xwiki.component.em-bed.em-beddableComponentManager.lookup(em-beddableComponentManager.java:126) at org.xwiki.component.em-bed.em-beddableComponentManager.createInstance(em-beddableComponentManager.java:403) at org.xwiki.component.em-bed.em-beddableComponentManager.initialize(em-beddableComponentManager.java:361) at org.xwiki.component.em-bed.em-beddableComponentManager.lookupList(em-beddableComponentManager.java:143) at org.xwiki.component.internal.DefaultComponentManager.lookupList(DefaultComponentManager.java:105) at org.xwiki.observation.internal.DefaultObservationManager.initialize(DefaultObservationManager.java:133) at org.xwiki.component.em-bed.em-beddableComponentManager.createInstance(em-beddableComponentManager.java:429) at org.xwiki.component.em-bed.em-beddableComponentManager.initialize(em-beddableComponentManager.java:361) at org.xwiki.component.em-bed.em-beddableComponentManager.lookup(em-beddableComponentManager.java:116) at org.xwiki.container.servlet.XWikiServletContextListener.contextInitialized(XWikiServletContextListener.java:78) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3910) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4393) at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:367) at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:146) at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:460) at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) at org.jboss.web.deployers.WebModule.start(WebModule.java:96) 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:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) at $Proxy36.start(Unknown Source) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37) at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.system.ServiceController.doChange(ServiceController.java:688) at org.jboss.system.ServiceController.start(ServiceController.java:460) at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:146) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:104) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:45) at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) at org.jboss.Main.boot(Main.java:209) at org.jboss.Main$1.run(Main.java:547) at java.lang.Thread.run(Thread.java:595)08:12:52,277 ERROR [Reflections] could not create Vfs.Dir from url. ignoring the exception and continuingorg.reflections.ReflectionsException: could not create Vfs.Dir from url, no matching UrlType was found [vfszip:/F:/gid_1/jboss/server/default/deploy/xwiki-enterprise-web-2.7.war/WEB-INF/lib/xwiki-core-rendering-macro-groovy-2.7.jar/META-INF/maven/]either use fromur-l(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.fromur-l(Vfs.java:104) at org.reflections.vfs.Vfs.fromur-l(Vfs.java:89) at org.reflections.Reflections.scan(Reflections.java:136) at org.reflections.Reflections.<init>(Reflections.java:91) at org.xwiki.extension.repository.internal.DefaultCoreExtensionRepository.loadExtensions(DefaultCoreExtensionRepository.java:84) at org.xwiki.extension.repository.internal.DefaultCoreExtensionRepository.initialize(DefaultCoreExtensionRepository.java:72) at org.xwiki.component.em-bed.em-beddableComponentManager.createInstance(em-beddableComponentManager.java:429) at org.xwiki.component.em-bed.em-beddableComponentManager.initialize(em-beddableComponentManager.java:361) at org.xwiki.component.em-bed.em-beddableComponentManager.lookup(em-beddableComponentManager.java:126) at org.xwiki.component.em-bed.em-beddableComponentManager.createInstance(em-beddableComponentManager.java:403) at org.xwiki.component.em-bed.em-beddableComponentManager.initialize(em-beddableComponentManager.java:361) at org.xwiki.component.em-bed.em-beddableComponentManager.lookupList(em-beddableComponentManager.java:143) at org.xwiki.component.internal.DefaultComponentManager.lookupList(DefaultComponentManager.java:105) at org.xwiki.observation.internal.DefaultObservatio.............................................
Hi Guys,
I've been using xwiki for a while now, but have only "recently" started
using v2 syntax.
In v1 a trick I'd often use in apps was to have a nested <FORM> element to
allow me to add some pre-filled objects to a page. Something like this:
#set ($list = ["Problem", "Feature", "Question"])
<FORM>
<SELECT name="field1"> #foreach ($item in $list) <OPTION
value="$item">$item</OPTION> #end </SELECT>
<INPUT type="submit" name="add" value="add" />
</FORM>
Then you could just catch and use the selection:
#if ($request.getParameter("add"))
$doc.newObject("someclass").set("Field1", $request.getParameter("field1"))
$doc.save()
Obviously I've taken some shortcuts here.
This approach fails to work in inline mode for some reason. My form
definition seems to become subsumed by the overall form on the page now.
So is there some way for me to declare that I want my form outside of the
normal structure?
Or is there some smarter way of approaching this problem?
Thanks in advance.
Cheers,
Adam
Hi,
I was writing a piece of code so that PDF export prints associated meta data
of a page. Since I was in PDF macros code, I worked on a PDF export options
page.
By working on the PDF export options, I am using check boxes that allows
user to choose to export or not cover page, toc page, metadata page
attachments and comments. Issue I encountered is that when a check box is
not checked it is not set and I found no way to use check boxes with actual
code from pdfhtmlheader.vm page:
#if("$!request.pdfcover" != '0')
#set($displayPdfCover = 1)
#else
#set($displayPdfCover = 0)
#end
and the same for pdftoc
(I could have put <input value="0"/> instead but it makes more sense to have
<input value="1"/>)
Therefore I am proposing that we:
* update pdfhtmlheader.vm page so that cover and toc page are not exported
by default
* update existing pdf export button so that we keep the same behaviour
(pdfcover and pdftoc printed in PDF), meaning instead of
*page?format=pdf*it would be
*page?format=pdf&pdftoc=1&pdfcover=1*
Some UI will be needed afterward so that this page is exposed. (I am not
planning to work on this.)
The export options would be made in a template, but I put the code in this
page of the incubator so that it makes things clearer if needed:
http://incubator.myxwiki.org/xwiki/bin/view/PDFExport/ExportOptions
Thanks for your feedback on pdfhtmlheader.vm modification and on the feature
itself.
--
Thibaut
Hi everyone,
FOSDEM (http://www.fosdem.org/2011/) is around the corner (5-6 feb 2011) and some XWiki developers are going:
- Anca Luca
- Ludovic Dubost
- Jerome Velociter
- Oana Tabaranu
Anca will also give a talk on 6th February, from 14:40 to 14:55 PM, on annotations : "XWiki: Annotating documents, the eXtensible wiki way".
Summary:
"
Since version 2.3, XWiki integrates document annotations in its collaborative environment (http://extensions.xwiki.org/xwiki/bin/view/Extension/Annotations+Application). This talk will focus on the implementation of the annotation feature, with the challenges that an eXtensible wiki implies: handling user collaboration on documents and annotations, annotating dynamically generated content, flexible annotations structure to allow customization. As a default XWiki feature, it allows users to add notes on all types of content, plain unstructured documents or structured documents. It is also used in the Scribo project (http://www.scribo.ws) to manipulate automatic semantic annotations on wiki documents and collaboration around them. Since a demo is worth a thousand words, the presentation will center upon showing all these at work.
"
So if you intend to go to FOSDEM let us know here and it would be cool to meetup.
Some details here:
http://www.xwiki.com/xwiki/bin/view/Blog/XWiki%20Fosdem
Thanks
-Vincent
myxwiki.org username: zkai
I would like to use xwiki to create some documentation that I would like to
keep track off. Tech support, scripting, etc. In addition, am a CSC major
and being that xwiki is written in java I would like to test out the
"programmability" of the wiki,