1 Jul
2008
1 Jul
'08
4:05 p.m.
Hi James,
This is probably because of our "flaky" WYSIWYG editor. In the version
you have it's escaping the special characters as xml entities thus
making the URL fail... This is a known bug and we're working hard on a
brand new WYSIWYG editor based on GWT that will not have all the
deficiencies of the current editor. Right now all I can suggest is to
not use the WYSIWYG editor and use the wiki editor one as much as
possible. I know it's a good answer but we're a bit stuck, whenever we
make changes to the current editor it breaks it in other places; it's
really too hard to maintain (hence our decisions to rewrite it - a
first version should be out in September).
Sorry about that.
Thanks
-Vincent
On Jul 1, 2008, at 3:57 PM, James Weir wrote:
That seems to work now.
interesting though, when I add an http URL the first time it works
fine;
however if I re-edit the page then the httpURL gets interpreted by the
Wiki and corrupts the link, for example
if I add this:
#video('http://www.dailymotion.com/video/x5yyb9_sarkozy-en-off-sur-france-3_news')
save the page and then later I re-edit the page the http link is
saved as:
#video('http://www.dailymotion.com/video/
x5yyb9_sarkozy-en-off-sur-france-3_news')
and an error is thrown:
Error number 4001 in 4: Error while parsing velocity page
Tutorials.SAFTutorialBuild
Wrapped Exception: Failed to evaluate content with id SAFTutorial
Build <http://demo.usharesoft.com:8080/xwiki/bin/view/Tutorials/SAFTutorialBuild
com.xpn.xwiki.XWikiException: Error number
4001 in 4: Error while
parsing velocity page Tutorials.SAFTutorialBuild
Wrapped Exception: Failed to evaluate content with id SAFTutorial
Build <http://demo.usharesoft.com:8080/xwiki/bin/view/Tutorials/SAFTutorialBuild
at
com
.xpn
.xwiki
.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:231)
at
com
.xpn
.xwiki
.render.XWikiVelocityRenderer.render(XWikiVelocityRenderer.java:93)
at
com
.xpn
.xwiki
.render
.DefaultXWikiRenderingEngine
.renderText(DefaultXWikiRenderingEngine.java:252)
at
com
.xpn
.xwiki
.render
.DefaultXWikiRenderingEngine
.renderText(DefaultXWikiRenderingEngine.java:176)
at
com
.xpn
.xwiki
.render
.DefaultXWikiRenderingEngine
.renderText(DefaultXWikiRenderingEngine.java:145)
at
com
.xpn
.xwiki
.render
.DefaultXWikiRenderingEngine
.renderDocument(DefaultXWikiRenderingEngine.java:134)
at
com
.xpn.xwiki.doc.XWikiDocument.getRenderedContent(XWikiDocument.java:
423)
at com.xpn.xwiki.api.Document.getRenderedContent(Document.java:371)
at sun.reflect.GeneratedMethodAccessor328.invoke(Unknown Source)
at
sun
.reflect
.DelegatingMethodAccessorImpl
.invoke(DelegatingMethodAccessorImpl.java:25)
... partial exception, the rest has been removed
at java.lang.reflect.Method.invoke(Method.java:597)
I know there is a notion of {pre} that stops xwiki interpeting parts
of
the page to stop this, however I was suprised that xwiki did this in a
macro. How can I stop this happening ?
I have a more generic question; if you wish to use a widget in html as
part of the wiki, what is the best way to go about this ? Do you have
to create your own Macro ? or is there a way to tell xWkki to parse a
block as html ?
Thanks
James
Vincent Massol wrote:
> Hi James,
>
> The person who wrote the installation tutorial was wrong. The way it
> was described doesn't work.
> I've updated the instructions.
> See http://code.xwiki.org/xwiki/bin/view/Macros/VideoMacroDownloads
>
> Thanks
> -Vincent
>
> On Jul 1, 2008, at 12:05 PM, James Weir wrote:
>
>
>> Hi,
>>
>> I have been trying to use the video macro [1] without much success.
>>
>> I followed the instructions to upload and import the xar file into
>> my
>> xwiki. The import was successful.
>>
>> I then add the macro into the Velocity macros:
>> Administration:
>> Preferences->Advanced->Velocity Macro Pages I added:
>> Marcos.Video,
>>
>> I was then hoping to embed a video into my xwiki. Unfortunately
>> all I
>> see is the text of the macro rather than the video, For example:
>>
>> #video('http://www.youtube.com/v/NEV2TnDUA-E&hl=en');
>>
>> Any ideas on why this is not working ?
>> Thanks
>> James