Dear XWiki experts,
I've been trying to undelete documents programmatically and I must say I failed thus far.
I need to do this so as to implement the undeletion of 450 documents.
Given the full name of the document, which currently shows when /view/-ed, that it has been deleted and offers me to restore or really delete, I am calling:
xwiki.getDeletedDocuments(fullName, "en");
however, thus far, the result of this call has been an array of size zero.
I would have expected to call the undelete method on the last of these DeletedDocuments.
Is this not the right way to act?
thanks in advance.
Paul
Hi devs/contributors/everyone,
This is an interesting article forwarded to me by Ludovic:
http://buytaert.net/a-method-for-giving-credit-to-organizations-that-contri…
I’ve been thinking a bit about it and the simplest solution I could think of (if we ever wanted to do something in this direction) would be:
* Add a new custom field in JIRA called “Sponsored By”. Since all our commits have associated JIRAs this should work fine to recognize everyone.
* Then we can easily query JIRA on a wiki page to provide visibility about companies and individuals sponsoring the development of XWiki.
* For example we could have a new page available in the Contribute menu of the top level horizontal menu called Sponsors which would:
- list all committers: link to the Hall of Fame page (http://dev.xwiki.org/xwiki/bin/view/Community/HallOfFame)
- list all Supporters: link to http://www.xwiki.org/xwiki/bin/view/Main/Supporters
- list all sponsors: query JIRA and list all sponsors including # of issues sponsored with ability to clean on each sponsor and go in JIRA itself to see the details
WDYT?
Would you be interested in this?
Thanks
-Vincent
Hi devs.
I am implementing the Color Theme Editor for Flamingo! And this is a
preview:
http://design.xwiki.org/xwiki/bin/download/Proposal/ColorThemeforFlamingo/f…
Since the current color theme application is strongly linked to Colibri,
and the new application will be strongly linked to Flamingo, I propose the
following:
1/ move xwiki-platform-colorthemes in xwiki-platform-colibri and state that
this application is only compatible with colibri-based skin.
2/ create the new application in xwiki-platform-flamingo
3/ the new color theme application will actually propose more than colors
(fonts, less code, etc...), so I propose to call it
xwiki-platform-flamingo-themes.
4/ in the administration, we have a page that propose which color theme we
want to use. Since the new application will not be compatible with the old
one, I propose to add an extension point (such as what we have to configure
search suggest sources) in order to propose the themes corresponding to the
selected skin (ie: xobjects of ColorThemes.ColorThemeClass for colibri and
skins based on colibri, and xobjects of FlamingoThemeCode.ThemeClass for
flamingo).
5/ modify SkinAction that currenlty executes velocity code on a skin file
if the mime type is CSS or JS, to also execute velocity on files suffixed
by .less.vm, because I need it for my application. To see what it looks
like, please look at
https://github.com/gdelhumeau/xwiki-platform/commit/49aca5733f4a820f3d1327c…
. The alternative is to create a new action which is too much IMO.
6/ when colibri will be deprecated on removed from XE, we will do the same
for the old color theme application.
WDYT?
Thanks,
Guillaume
Hello,
I have problem since one week.
I try to upgrade my xwiki 3.5 to 5.3.
The upgrade is ok, everything is fine but .. every attachment files doesn't
exists.
Though the attachment tables contains my files ..
I can add new files but the files on the database before the uprade are not
accessible.
How it's possible ?
On the logs : 0 error..
Thank you !
--
View this message in context: http://xwiki.475771.n2.nabble.com/Upgrade-database-tp7591061.html
Sent from the XWiki- Dev mailing list archive at Nabble.com.
The XWiki development team is proud to announce the availability of
XWiki 6.1 Milestone 2.
This milestone contains a new mail API and module to replace the old
mailsender plugin, Flamingo skin and Extension Manager improvements as
well as various performances improvements and bug fixes.
You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download
Make sure to review the release notes:
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki61M2
Thanks
-The XWiki dev team
Hi everyone,
On the 15th of December (i.e. in a month's time), it will be **10 years**
since the first commit on the XWiki open source project.
Ludovic did the first commit in CVS on Sourceforge:
"
15.12.2003 10:13:33, by ludovic
Initial revision
"
(Can be seen at
http://svnsearch.org/svnsearch/repos/XWIKI/search?from=20030101&to=20040101
)
10 years is starting to be some respectable milestone!
I invite everyone to join us in celebrating by adding your own story about
your interaction with the XWiki community or the XWiki software at
http://dev.xwiki.org/xwiki/bin/view/Drafts/TenYearsOfXWiki
<XWiki SAS hat>
Since I'm also the CTO of the XWiki SAS company, I'd like to officially
invite all the members of this great community to join us in celebrating
the 10 days of the XWiki project at the XWiki SAS office in Paris, France
on the 12th of December 2013.
Here's the invitation:
http://www.xwiki.com/lang/en/News/XWiki+10th+Anniversary
See you there!
</XWiki SAS hat>
Well done everyone!
-Vincent Massol
Hi devs,
Following this email thread http://markmail.org/message/batmj7h2oibckroy I’ve now progressed with Lyes and we would like to move our code to XWiki Platform.
More detail is available at http://design.xwiki.org/xwiki/bin/view/Proposal/MailModule
Here’s my +1
Note that it’s not fully finished but I’d like to start making it official in 6.1M2 and tune it from there. It’s already working and tested with some integration test for some use cases.
Thanks
-Vincent
Hello,
I'm working on semantic extension for XWiki[1][2] and currently on
performance tunning to be ready for scaling up. The problem with current
implementation is that it always modifies semantics DB on all page
views. E.g. when I do have a page with
{{semProp value="http://purl.org/dc/elements/1.1/title::The Hobbit"/}}
to define property 'title' to value 'The Hobbit', this macro basically
saves this knowledge to the DB everytime the page is viewed which is
obvious performance killer. Of course there is a possibility to optimize
this call to first check if the property is already defined and if not,
do nothing, but it's still not the best.
What I think I'd like to do is to kind of check if the pages is saved or
viewed and based on this semProp will do its job (during page save) or
will do nothing (during page view).
Now, my question is if something like that is possible since I've not
found any hints about it so far.
Thanks!
Karel
[1]: http://extensions.xwiki.org/xwiki/bin/view/Extension/Semantic+XWiki
[2]: https://github.com/kgardas/semxwiki
Folks,
I'm testing kind of scalability of XWiki by simple benchmark which
creates N pages in a loop (one page at a time, it's not parallel run!)
and then when this loop finishes, it again in another loop gets all the
pages from the server (again serially, one page at the time). For page
creation we're using REST API, for getting the pages we're using common
browseable URL (/xwiki/bin/view/...).
Now the problem is that if I try to attempt creation of 100k pages, then
I hit Java's out of memory errors and server is unresponsive from that
time. I've tested this on:
- xwiki-jetty-hsql-6.0.0
- xwiki-jetty-hsql-6.0.1
- xwiki-tomcat7-pgsql -- debian xwiki packages running on top of debian 7.5
Of course I know the way how to increase Java's memory space/heap space.
The problem is that this will not help here. Simply if I do so and then
create 100 millions of pages on one run I will still get to the same
issue just it'll take a lot longer.
I've googled a bit for memoryleaks issues on Java and found an
interesting recommendation to use parallel GC. So I've changed
start_xwiki.sh to include -XX:+UseParallelGC in XWIKI_OPTS
Anyway, the situation is still looking suspiciously. I've connected
JConsole to the xwiki java process and overall view looks:
https://app.box.com/s/udndu96pl2fvuz3igvor
this is whole run overview, but perhaps even more clear is it on last 2
hours view which is here:
https://app.box.com/s/deuix33fzejra4uur941
Sidenote this all is from debugging xwiki-jetty-hsql-6.0.1 distro.
Now, what worries me a lot is this bottom cap which is growing. You can
see that clearly in Heap Memory Usage from 15:15. In CPU usage you can
also see that around the same time the CPU consumption went up from ~15%
to ~45%
When I switch to Memory Tab in JConsole and click several times on
"Perform GC" button, the bottom cap is still there and I cannot get
lower in memory usage. With this going on I can also see server failing
after some time on OOM error.
Any help with this is highly appreciated here.
Thanks!
Karel