Hi devs,
Seems I forgot a use case when introducing the new webjars URL format in http://jira.xwiki.org/browse/XWIKI-10881 and we need to add the wiki somewhere in the URL to serve some webjar resource located in a different subwiki (this is http://jira.xwiki.org/browse/XWIKI-12884).
I’m proposing this updated wrbjars URL format (updated from http://extensions.xwiki.org/xwiki/bin/view/Extension/WebJars+Integration#HU…):
http://<server>/<context path>/webjars/<path/to/resource>[?version=<version>&evaluate=true|false&wiki=<wiki name>]
Specifically I’ve added the optional wiki query string parameter. This means also updating the url() Script Service API to use that new parameter when the resource is not on the current wiki.
WDYT?
Thanks
-Vincent
I need a realtime collaboration editor for xwiki (it will be used as
collaboration tool for people who edit the same document at the same time).
I integrate xwiki with my app. I checked
http://realtime.webviewers.org/xwiki/bin/view/Demos/RTAdvancedWysiwyg it
works nice and I would like to implement it without demo mode but I don't
know how.
There is the following code:
{{velocity output=\"none\"}}
$xwiki.jsx.use(\"RTWysiwyg.WebHome\", {\"demoMode\":true})
I tried to change demoMode parameter, but I don't know how to persist data.
Could you give any useful link how to use the extension in real app?
Thanks in advance!
--
View this message in context: http://xwiki.475771.n2.nabble.com/How-to-run-RTWysiwyg-extension-not-in-dem…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
I tried to use rtwysiwyg extension and have problems with it. I would like to
have another option: to use rtwiki extension. The problem I have: rtwiki
works in demo mode (RTWiki/Demo), but I don't know how to use rtwiki
extension to edit other pages. What should I do to enable collaboration for
usual pages (not from RTWiki/Demo)?
--
View this message in context: http://xwiki.475771.n2.nabble.com/How-to-use-rtwiki-extension-not-in-demo-m…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi devs,
I was reading the comment from Marius on https://jira.xwiki.org/browse/XWIKI-13223 and indeed it seems that the “xwiki.usedefaultweb” config parameter has not been working for a very long time (Marius says at least before 2.7). Locally I’ve tested a 5.2.4 version and indeed it’s not working.
For Main.AllDocs the generated URL is:
http://localhost:8080/xwiki/bin/view/AllDocs
Maybe at some point we were counting the number of path segments after the action and if it was 1 and xwiki.usedefaultweb was set to true we would add “Main” as the space.
However that’s not the case in XWiki 5.2.4 and probably earlier.
In addition, with Nested Pages we’ve implemented the support of a single path element after the action. FTR, from BinEntityResourceReferenceResolverTest:
// Test when single space segment, to be Nested Document friendly.
// Normally the last segment is always the page name but we want to handle a special case when we
// have "/view/something" and we wish in this case to consider that "something" is the space. This
// is to handle Nested Documents, so that the user can have a top level Nested Document
// (something.WebHome) and access it from /view/something. If we didn't handle this special case
// the user would get Main.something and thus wouldn't be able to access something.WebHome. He'd
// need to use /view/something/ which is not natural in the Nested Document mode.
testCreateResource("http://localhost/bin/space", "view",
buildEntityReference("wiki", Arrays.asList("space"), null), fullSingleSpaceReference, EntityType.DOCUMENT);
I also don’t think it’s a big help for users to be able to omit the Main space since they need to keep the other spaces in the URL anyway.
So I’m proposing to officially drop support for this parameter and remove it from xwiki.cfg since it has not worked for ages.
WDYT? Have I missed something?
Thanks
-Vincent
Hi devs,
I’ve moved the IRC Bot app last week as a proof of concept and even though it was tedious and long, it worked fine.
FYI, I’m now going to perform the move of the FAQ app to contrib, as agreed.
Thanks
-Vincent