xwiki-devs January 2012

xwiki-devs@xwiki.org

28 participants
61 discussions

[xwiki-devs] Upgraded from Xwiki 2.x to 3.1.1 now Admin panel looks strange is wiki or DB corrupt?

by Kaya Saman

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

12 years, 11 months

[xwiki-devs] [Announcement] XWiki Enterprise 3.2.1 and XWiki Enterprise Manager 3.2.1 Released

by Sergiu Dumitriu

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/

12 years, 11 months

[xwiki-devs] [VOTE] Limit xwiki.authentication.group.allgroupimplicit to the group wiki

by Thomas Mortagne

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

12 years, 11 months

[xwiki-devs] About 3.2.1 release

by Guillaume Fenollar

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

12 years, 11 months

[xwiki-devs] [Announcement] XWiki Enterprise 3.3.1 and XWiki Enterprise Manager 3.3.1 Released

by Sergiu Dumitriu

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/

12 years, 11 months

[xwiki-devs] Time spent doing the release

by Marius Dumitru Florea

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!

12 years, 11 months

[xwiki-devs] username cookie a plan for the future?

by Paul Libbrecht

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

12 years, 11 months

[xwiki-devs] XWiki Enterprise and XWiki Enterprise Manager 3.4 Release Candidate 1 Released

by Marius Dumitru Florea

The XWiki development team is proud to announce the availability of XWiki Commons, XWiki Rendering, XWiki Platform, XWiki Enterprise and XWiki Enterprise Manager 3.4 Release Candidate 1. The first release candidate of the 3.4 version brings a few bug fixes and improvements over the previous version. The most notable addition is the possibility to easily import an extension from any repository into XWiki Repository. You can find the full list of issues fixed for this release at http://goo.gl/G9InJ . See the full release notes at http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWikiEnterpris… for more details. Thanks -The XWiki dev team

12 years, 11 months

[xwiki-devs] Wrongly deprecated xe.pagination.* translation properties?

by Vincent Massol

Hi Sergiu, I've seen you committed the following below. I'm now renaming properties since I' m moving the livetable to platform. You've marked 2 properties as "deprecated": +# Deprecated: xe.pagination.results=Results xe.pagination.results.of=out of However they're are still used in livetable.js. How come? Thanks -Vincent Author: sdumitriu Date: 2009-05-22 15:09:39 +0200 (Fri, 22 May 2009) New Revision: 20272 Modified: platform/core/trunk/xwiki-core/src/main/resources/ApplicationResources.properties Log: XWIKI-3880: Improve the pagination aspect Adding resources Modified: platform/core/trunk/xwiki-core/src/main/resources/ApplicationResources.properties =================================================================== --- platform/core/trunk/xwiki-core/src/main/resources/ApplicationResources.properties 2009-05-22 12:57:04 UTC (rev 20271) +++ platform/core/trunk/xwiki-core/src/main/resources/ApplicationResources.properties 2009-05-22 13:09:39 UTC (rev 20272) @@ -1675,11 +1675,19 @@ xe.space.index=Space Index xe.space.index.description=This page lists all your wiki's spaces +xe.pagination.page=Page +xe.pagination.page.title=Go to page {0} +xe.pagination.page.previous=« previous page +xe.pagination.page.prev.title=Previous Page +xe.pagination.page.next=next page » +xe.pagination.page.next.title=Next Page +xe.pagination.results.none=No results +xe.pagination.results.one=One result +xe.pagination.results.single=Result {0} of {1} +xe.pagination.results.many=Results {0} - {1} of {2} +# Deprecated: xe.pagination.results=Results xe.pagination.results.of=out of -xe.pagination.page=Page -xe.pagination.page.next.title=Next Page -xe.pagination.page.prev.title=Previous Page xe.livetable._actions.delete=delete xe.livetable._actions.rename=rename

12 years, 11 months

[xwiki-devs] [VOTE] Mark the xwiki/1.0 syntax as deprecated

by Sergiu Dumitriu

Hi devs, Since a long time ago, the xwiki/1.0 syntax has been deprecated in favor of the new rendering engine and the 2.x syntaxes, but this has never been declared deprecated formally. We should: * mark the syntax as deprecated in the UI (like 2.1 was marked experimental in the syntax choice dropdown) * deprecate classes and methods that deal only with the old syntax * push more for migrating all documents to the 2.1 syntax; the biggest troublemaker is the statistics application Here's my +1. We should also decide on a timeline for the complete removal of the 1.0 syntax. Is that something we want to do? Provided we manage to migrate all the official documents and some major contributed applications during the 4.x cycle, is XWiki 5.0 a good target? We should package the support for xwiki/1.0 as an optional extension installable using the extension manager, so that people can upgrade from older versions. Or we could package just a syntax migrator that can be used for an automatic conversion to a newer syntax, without actually providing rendering support for it. -- Sergiu Dumitriu http://purl.org/net/sergiu/

12 years, 11 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs January 2012