On Thu, Apr 23, 2015 at 1:49 PM, m...@ow2.org wrote:
> Le 21/04/2015 17:10, m...@ow2.org a écrit :
>> Why : the issue at
>> this point is there is no folder in the
>> PermDir/jobs/status/distribution/wiki/ which sounds logical
>> because we created the descriptor "by hand" throught a XAR import wh
I once had quite bad problems when having an apache in between
who internally decoded an URI and then encoded it back, but only "barely" ...
However it seems this is ruled out here, if the problem happens with tomcat,
too.
How do you reproduce the issue with tomcat directly?
a) if you directly
Thanks for the feedback.
Yes, there is an Nginx as frontend running, but I also can reproduce the
issue by calling the direct tomcat address.
I don't know what could be wrong because I'm no tomcat expert at all.
2015-04-23 13:10 GMT+02:00 Clemens Klein-Robbenhaar <
c.robbenh...@espresto.com>:
>
Hello,
I try to use this program to convert JSPWiki pages to xWiki page :
http://extensions.xwiki.org/xwiki/bin/view/Extension/JSPWiki+To+XWiki+Conversion
But I encounter many issues :
- I can't instantiate XWikiContext class, but the usage of
EmbeddableComponentManager before t
Do not get me wrong, I love Xwiki: what I mean it is always possible to make it
easyer (like distribution wizard by example). Wizard and advanced doc to goes
further is perfect. :-)
To answer at fisrt problem: a database dump (+ DW launched) will be enough to
reinit xwiki, no? I don't know if t
I installed tomcat8 as apache-tomcat-8.0.21, and java as jdk1.8.0_45
and cannot reproduce this either, at least not directly.
After I create a page with name `Page with "quotes"`,
I cannot trigger the problem in the browser, but of course I can do so manually
by feeding in a wrong URL:
i.e.:
Le 21/04/2015 17:10, m...@ow2.org a écrit :
> Why : the issue at
> this point is there is no folder in the
> PermDir/jobs/status/distribution/wiki/ which sounds logical
> because we created the descriptor "by hand" throught a XAR import which
> doesn't include the process of writing initial status.
What version of XWiki are you using? Have you installed
http://extensions.xwiki.org/xwiki/bin/view/Extension/Enable+Default+Action+for+Flamingo+Menu
or
http://extensions.xwiki.org/xwiki/bin/view/Extension/Hover+and+Default+Action+for+Flamingo+Menu
? Do you have a custom skin or a custom Color Them
This looks to me like a Tomcat issue. because Tomcat is known for
complaining about some characters in URLs, such as /, for security
reasons. I have no problem using " in the document name on Jetty.
Hope this helps,
Marius
On Wed, Apr 22, 2015 at 1:43 PM, D R wrote:
> Hi,
>
> it has nothing to d
Hi,
See below.
On 23 Apr 2015 at 11:57:02, Ecaterina Moraru (Valica)
(vali...@gmail.com(mailto:vali...@gmail.com)) wrote:
> Hi,
>
> First of all I'd like to thank Mahomed for the nice words he said about
> XWiki.
>
> I agree that we must try to make XWiki as simple as it can be for the
> en
Hi,
First of all I'd like to thank Mahomed for the nice words he said about
XWiki.
I agree that we must try to make XWiki as simple as it can be for the
end-users and, as Pascal said, one solution for this is to improve the
documentation.
The problem is that I'm not sure I completely understood
I'm sure we can debate this all day.
XWiki is very simple for end users to use. The actual purpose of the wiki (to
allow people to create/edit/view articles/pages) is simple and
straight-forward. I have everyone in our organisation using it successfully,
and trust me, some of the end users shou
12 matches
Mail list logo