28 Feb
2009
28 Feb
'09
11:15 a.m.
On Feb 27, 2009, at 11:18 PM, Sergiu Dumitriu wrote:
Vincent Massol wrote:
No it's not a bug. The problem is that to make it work we would need
to modify XWiki.include() so that it doesn't aggregate content of
included doc before rendering them in 1.0 syntax but instead that it
uses rendered content when doing the aggregation.
-Vincent
On Feb 27, 2009, at 6:24 PM, Vincent Massol
wrote:
Why does the include try to do this?
Hi,
On Feb 27, 2009, at 6:11 PM, hel-o wrote:
One problem is in our xwiki syntax 1.0 to 2.0 converter. What happens
is that when you convert a blog page into 2.0 syntax it calls
Blog.BlogPostSheet which is in xwiki 1.0 syntax so the new include
macro will automatically try to convert it to 2.0 syntax and there
seems to be some problem. Raised as comments in
http://jira.xwiki.org/jira/browse/XWIKI-3107 I try (if possible) to use only the new syntax in
this wiki. And in
its quite
stable for most parts. The new WYSIWYG is better, but it laks
functionality
the old one had.
Which features are you looking for that are lacking?
But back to my Blog problem:
http://semantic-web.hel.at/xwiki/bin/view/Blog/
flickrusertag Macro didn't work after update.
When i use the velocity code the result is an error
The image link and the {{velocity}} things show that no new
syntax is
used:wistle:
Using the Macro on a normal Page works
http://semantic-web.hel.at/xwiki/bin/view/Main/
So it seems no code can be used in the new Blog application
Yes there seems to be
some issues mixing the blog app written in 1.0
syntax with blog pages written in 2.0 syntax. I'll look into it to
understand the problem. The second problem is on the blog WebHome page
(which is syntax 1.0).
Since some blog pages are in syntax 2.0 their content are rendered in
syntax 2.0 but the syntax 1.0 page cannot display 2.0 content.... I'm
not sure yet how to solve this one...
Theoretically the blog displays the content in the document's
syntax, as
it calls $entryDoc.getRenderedContent($entryContent,
$entryDoc.syntaxId). Is there a bug here too?