29 Jul
2009
29 Jul
'09
11:29 p.m.
I am close to have the entire Blog Application upgraded to 2.0 Syntax (now I upgraded the
Panels). That brings me back to the create an export of the application which is a pain in
the next using the full export but does not work using the Import / Export Application.
Looking into the I/E App I saw that it is using XWiki.searchDocuments(String sql) but that
will not return any HIDDEN documents. The PackageAPI (used by the full export) is not
providing a list and it seems it would break its indention to do so.
So first I was wondering if there is a way to obtain a list of documents including the
hidden ones?
I not then I was wondering if we should export XWiki or should create another Plugin that
delivers all documents?
Finally I am thinking that we might should extend the full export (XWiki Administration)
allowing a user to create custom exports more or less like the I/E application?
Cheers - Andy
30 Jul
30 Jul
11:04 a.m.
Hi Andreas
On Wed, Jul 29, 2009 at 11:29 PM, Andreas Schaefer <schaefera(a)me.com> wrote:
I am close to have the entire Blog Application
upgraded to 2.0 Syntax (now
I upgraded the Panels).
Many thanks for that. Hopefully we'll be able to review your patch and make
it part of XE 2.0.
That brings me back to the create an export of the
application which is a
pain in the next using the full export but does not work using the Import /
Export Application.
Looking into the I/E App I saw that it is using
XWiki.searchDocuments(String sql) but that will not return any HIDDEN
documents. The PackageAPI (used by the full export) is not providing a list
and it seems it would break its indention to do so.
So first I was wondering if there is a way to obtain a list of documents
including the hidden ones?
I remember a discussion about this topic from some time ago (the issue with
hidden documents being that the implementation was at too deep a level,
meaning that standard queries can't find them anymore). I'm not sure what
the solution was (it might involve writing a query using a protected API),
Sergiu, JV or Vincent are more knowledgeable on this topic.
I not then I was wondering if we should export XWiki or should create
another Plugin that delivers all documents?
Finally I am thinking that we might should extend the full export (XWiki
Administration) allowing a user to create custom exports more or less like
the I/E application?
Improving the overall export experience (export big wikis without hassle,
select which pages to export) is definitely part of our roadmap. There are 2
parts to this, the application manager and improving the way files use
memory during upload / download operations. Their inclusion in the XE 2.1
roadmap will be discussed at the beginning of September.
Cheers - Andy
Thanks for all your work,
Guillaume
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Guillaume Lerouge
Product Manager - XWiki
Skype: wikibc
Twitter: glerouge
http://guillaumelerouge.com/
5624
days inactive
5625
days old
1 comments
2 participants
participants (2)
-
Andreas Schaefer -
Guillaume Lerouge