- xwiki-devs@xwiki.org - lists.xwiki.org

[xwiki-devs] What user agent ?
by Thomas Mortagne 24 Jan '12

24 Jan '12

Hi devs, I need to make Extension Manager provide a user agent when communicating with repositories to be a good http citizen but I'm not sure which user agent to set. Should it be: * an Extension Manager repository handler user agent * an Extension Manager user agent * an XWiki user agent * an XWiki platform user agent WDYT ? -- Thomas Mortagne

2 1

[xwiki-devs] creation date not correct
by Edo Beutler 23 Jan '12

23 Jan '12

Hi devs Today we stumbled across, what we think, is a bug. All (at least almost all) the creation dates are wrong. They are set to the first occurrence of getDocument() for a specific document and not on first save(). Usually the difference ist only small (minutes), but there are cases where the difference are several days. We suppose that calling getDocument('Test.NotExistingDoc') creates the document and puts it into the cache with a current timestamp in creation date. Let's say you work now for an hour before you save the document, then the creation date would be an hour old even though the document has just been created. We always expected the creation date to be the moment of the first save. Thus we think it's a bug. We came across the problem because we had someone complaining that a document he created on the 19th was listed under the ones from the 17th. This could even happen across users if e.g. there is a link to a not yet existing page. User A clicks on the link, realizes there is nothing on the page and leaves. Hours later user B goes to the page and adds content. Now the creation date of the page would be at an inexplicable time for user B since he never touched the document until hours after the shown creation date. We work on 2.7.2 at the moment, but judging by the source code we think it should be the same in the current version. To reproduce it create the following script: #set($newDoc = $xwiki.getDocument('Test.NotExistingDoc')) $newDoc.getCreationDate() If you reload several times you see, that the creation date does not change, even though the document has never been saved. Add a save to the script: $newDoc.save() Now you have a document where creation date and save date of the version 1.1 do not match. Should I create a JIRA issue for that? Maybe we could even send you a git pull request, but you would have to tell us where you want it to be fixed: 1. In save action. There the creator of the document gets set already. 2. In the store action. We think it would belong there, but are not sure if this would break something e.g. import or copy 3. Somewhere else Regards, Edo

2 2

[xwiki-devs] Dates for 3.4 final and 3.5 RC1/final
by Marius Dumitru Florea 23 Jan '12

23 Jan '12

Hi devs, The 3.4 final release has been delayed almost 3 weeks, for various reasons, so we need to adjust the planning for 3.5. I propose: 3.4Final: 23 January (this Monday, so in 3 days) 3.5RC1: 6 February (2 weeks) 3.5Final: 13 February (1 week) WDYT? I can be the release manager of 3.5 but we need a release manager for the beginning of the 4.x cycle. Thanks, Marius

6 7

[xwiki-devs] Upgraded from Xwiki 2.x to 3.1.1 now Admin panel looks strange is wiki or DB corrupt?
by Kaya Saman 22 Jan '12

22 Jan '12

Hi, I wonder if anyone can help me as I've tried to obtain help from the Xwiki Users list but didn't work? After an upgrade from my old version of Xwiki which was 2.x (I think I built it in 2010) to 3.1.1 I ended up seeing this as my admin panel: http://www.optiplex-networks.com/xwiki/bin/download/Main/WebHome/Screenshot… In comparison with my old Xwiki instance this doesn't look right. Additionally, figuring that I should upgrade to version 3.3 or 3.4rc-1 I ended up not being able to display anything and getting a 500 error in Tomcat. I am using Tomcat6 coupled with Postgresql as DB backend. I will post the logs of tomcat if requested but currently I am slightly more concerned with the ill looking admin panel. Also having two similar wiki sites running on 2 different instances of Tomcat, I am unable to use the WYSIYSG editor on this current wiki as it doesn't render, the little animation just keeps spinning forever but not actually doing anything. The other wiki's WYSIYSG editor is ok though after the upgrade?? Can anybody help? Regards, Kaya

2 4

[xwiki-devs] [Announcement] XWiki Enterprise 3.2.1 and XWiki Enterprise Manager 3.2.1 Released
by Sergiu Dumitriu 21 Jan '12

21 Jan '12

The XWiki development team is proud to announce the availability of XWiki Commons, XWiki Rendering, XWiki Platform, XWiki Enterprise and XWiki Enterprise Manager 3.2.1. This is the first and probably last bugfix release of the 3.2 series, with no new features, and a few bugfixes and minor improvements. One important change is the way relative references in an included document are resolved, reverting back to the pre-3.0 behavior. See http://jira.xwiki.org/browse/XWIKI-7382 for more details. Other areas with several bugfixes are support for Oracle databases, the rending engine, the WYSIWYG editor, and the Activity Stream. See the full release notes at http://www.xwiki.org/xwiki/bin/ReleaseNotes/ReleaseNotesXWikiEnterprise321 for more details. Note: The binaries for this release aren't listed on the Download page, but they can be obtained directly from our maven repository [1] or the OW2 forge download area [2]. [1] http://maven.xwiki.org/releases/org/xwiki/enterprise/ [2] http://forge.ow2.org/project/showfiles.php?group_id=170 -- Sergiu Dumitriu http://purl.org/net/sergiu/

1 0

[xwiki-devs] [VOTE] Limit xwiki.authentication.group.allgroupimplicit to the group wiki
by Thomas Mortagne 21 Jan '12

21 Jan '12

Hi devs, Right now if you enable xwiki.authentication.group.allgroupimplicit any user from any wiki will be part of any XWiki.XWikiAllgroup group from any wiki. I think this is wrong, for me xwiki.authentication.group.allgroupimplicit is supposed to have the same behavior as if it was disabled except that it allows to avoid loading a potentially huge group just to check if the user is in it. So I propose to also compare the user and group wiki and not just check that the group has space "XWiki" and name "XWikiAllGroup". WDYT ? -- Thomas Mortagne

4 3

[xwiki-devs] About 3.2.1 release
by Guillaume Fenollar 21 Jan '12

21 Jan '12

Hi devs, I'm still waiting for xwiki 3.2.1 to be released, we have to use this version for some projects. Any news on that? Thanks, -- Guillaume Fenollar XWiki SysAdmin Tel : +33 (0)1.83.62.65.97

6 8

[xwiki-devs] [Announcement] XWiki Enterprise 3.3.1 and XWiki Enterprise Manager 3.3.1 Released
by Sergiu Dumitriu 21 Jan '12

21 Jan '12

The XWiki development team is proud to announce the availability of XWiki Commons, XWiki Rendering, XWiki Platform, XWiki Enterprise and XWiki Enterprise Manager 3.3.1. This is the first and probably last bugfix release of the 3.3 series, with no new features, and a few bugfixes and minor improvements. One important change is the way relative references in an included document are resolved, reverting back to the pre-3.0 behavior. See http://jira.xwiki.org/browse/XWIKI-7382 for more details. Other areas with several bugfixes are the workspaces functionality, the Debian installer, the extension manager, cache management, and App Within Minutes. See the full release notes at http://www.xwiki.org/xwiki/bin/ReleaseNotes/ReleaseNotesXWikiEnterprise331 for more details. -- Sergiu Dumitriu http://purl.org/net/sergiu/

1 0

[xwiki-devs] Time spent doing the release
by Marius Dumitru Florea 21 Jan '12

21 Jan '12

Hi devs, Vincent asked me to write down the time I spend doing the release so that we can see what part of the release process needs to be improved. Here's the result: (1) Stabilize the build, making sure all tests pass on CI: up to 4 days (2) Update translations: ~15min (lots of unsignificant changes that have to be reviewed and ignored) (3) Set up the release agent: ~10min (4) Release on Jira, checking opened issues for partial commits, moving or splitting issues: ~30min (it really depends on how many issues have the "Fix Version/s" set to the released version and are not yet closed) (5) Write the release notes: from 2h to a full day (the relatively easy part is scanning closed Jira issues for new features, upgrades, important bugfixes, migration or backward compatibility problems; then you have to push developers to document the new features and the migration problems that they have introduced -- this takes longer) (6) Maven release: ~2h (if everything goes smoothly, otherwise you maybe have to spend an additional 1h to fix cyclic dependencies or bad dependency versions) (7) Collect Clirr report and clean up the release agent: ~10min (8) Paper work (announcements/news): ~1h 30min As you can see the most time consuming is: * stabilizing the build -> committers should check the CI after they commit * writing the release notes -> committers should document their work on XWiki.org before the release day Thanks, Marius P.S.: Kudos to Sergiu and Caleb for the (semi-)automated release script!

3 2

[xwiki-devs] username cookie a plan for the future?
by Paul Libbrecht 20 Jan '12

20 Jan '12

Hello developers, since quite long I see that XWiki has the practice of a cookie that says the username (and password) encrypted. The way to encrypt the username seems a "simple" cipher that would be fairly easy to share, provided the key is shared of course. I am considering to use this for the purpose of recognizing the authenticity of a request to another web-application. I am thinking a simple servlet-filter would be able to do most of the authentication services, provided the user is logged in into xwiki (and the cookie-path makes /blabla also receive the cooke). But there are two questions: - is this encryption recognizable as signed? (i.e. can someone without the key generate an encrypted username?) - is this practice expected to last? If yes to both, it would be interesting to share a servlet filter (or even Apache module) that would do this recognition and indicate the recognized user-principals. Maybe that was done already? thanks in advance Paul

2 1