xwiki-devs January 2013

xwiki-devs@xwiki.org

27 participants
82 discussions

by Ecaterina Moraru (Valica)

Hi devs, I've been working in the 4.3 Roadmap for a new skin proposal. You can see it at http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Skin4x I recommend looking at the "Annotations Overview" gallery in order to see the different elements of the skin and some explanations. I've made also separate pages for different components of the skin. For example, you can see more information about how the menus work at http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Skin4xMenus For each component you can also see how the elements scale and see the responsive layout. For the record, the proposal is made by using Bootstrap ( http://twitter.github.com/bootstrap/). Thanks, Caty

11 years, 7 months

[xwiki-devs] Issue on l10n with history

by Ludovic Dubost

Working on l10n change to custom mapping showed up an issue with the l10n history. We have a huge history table with 2,3M lines (as well as an activity stream) and we use the history table for extracting contributor statistics. However looking at it more closely shows that the source of most data in the history table is useless. See here a grouping by dates showing that localisation of already close to 2M lines in 6 month in 2012. | 201201 | 318346 | | 201202 | 311403 | | 201203 | 728703 | | 201204 | 271657 | | 201205 | 296384 | | 201206 | 120463 | Here is an example of history for an entry mysql> select xwr_author,xwr_version1,xwr_version2,xwr_date,xwr_comment,cast(xwr_isdiff as unsigned), length(xwr_patch) from xwikircs where xwr_docid=596494851 ; +-----------------------+--------------+--------------+---------------------+-------------+------------------------------+-------------------+ | xwr_author | xwr_version1 | xwr_version2 | xwr_date | xwr_comment | cast(xwr_isdiff as unsigned) | length(xwr_patch) | +-----------------------+--------------+--------------+---------------------+-------------+------------------------------+-------------------+ | XWiki.XWikiTranslator | 1 | 1 | 2010-02-23 11:38:27 | | 1 | 163 | | XWiki.XWikiTranslator | 2 | 1 | 2010-02-23 11:40:26 | | 1 | 330 | | XWiki.rbuj | 3 | 1 | 2010-03-04 00:24:24 | | 1 | 189 | | XWiki.rbuj | 4 | 1 | 2010-03-04 01:02:52 | | 1 | 223 | | XWiki.rbuj | 5 | 1 | 2010-07-30 01:12:58 | | 0 | 5026 | | XWiki.XWikiTranslator | 6 | 1 | 2012-01-23 11:40:25 | | 1 | 115 | | XWiki.XWikiTranslator | 7 | 1 | 2012-01-23 11:58:25 | | 1 | 115 | | XWiki.XWikiTranslator | 8 | 1 | 2012-01-23 13:31:52 | | 1 | 234 | | XWiki.XWikiTranslator | 8 | 2 | 2012-01-23 15:36:02 | Prepared | 1 | 115 | | XWiki.XWikiTranslator | 8 | 3 | 2012-01-24 02:01:12 | Prepared | 0 | 5670 | | XWiki.XWikiTranslator | 8 | 4 | 2012-01-25 02:04:00 | Prepared | 1 | 115 | | XWiki.XWikiTranslator | 8 | 5 | 2012-01-26 02:02:29 | Prepared | 1 | 115 | | XWiki.XWikiTranslator | 8 | 6 | 2012-01-27 02:01:18 | Prepared | 1 | 115 | | XWiki.XWikiTranslator | 8 | 7 | 2012-02-04 02:01:08 | Prepared | 1 | 115 | | XWiki.XWikiTranslator | 8 | 8 | 2012-02-07 02:02:03 | Prepared | 0 | 5670 | | XWiki.XWikiTranslator | 8 | 9 | 2012-02-08 02:01:20 | Prepared | 1 | 115 | | XWiki.XWikiTranslator | 8 | 10 | 2012-02-14 02:01:07 | Prepared | 1 | 116 | | XWiki.XWikiTranslator | 8 | 11 | 2012-02-28 02:01:32 | Prepared | 1 | 116 | | XWiki.XWikiTranslator | 8 | 12 | 2012-03-03 02:01:20 | Prepared | 1 | 116 | | XWiki.XWikiTranslator | 8 | 13 | 2012-03-14 02:01:50 | Prepared | 0 | 5671 | | XWiki.XWikiTranslator | 8 | 14 | 2012-03-14 18:23:06 | Prepared | 1 | 116 | | XWiki.XWikiTranslator | 8 | 15 | 2012-03-14 18:32:38 | Prepared | 1 | 116 | | XWiki.XWikiTranslator | 8 | 16 | 2012-03-14 18:37:17 | Prepared | 1 | 116 | | XWiki.XWikiTranslator | 8 | 17 | 2012-03-24 02:01:34 | Prepared | 1 | 116 | | XWiki.XWikiTranslator | 8 | 18 | 2012-03-26 16:40:35 | Prepared | 0 | 5671 | | XWiki.XWikiTranslator | 8 | 19 | 2012-03-28 02:01:23 | Prepared | 1 | 116 | | XWiki.XWikiTranslator | 8 | 20 | 2012-03-29 02:01:45 | Prepared | 1 | 116 | | XWiki.XWikiTranslator | 8 | 21 | 2012-04-11 02:01:36 | Prepared | 1 | 116 | | XWiki.XWikiTranslator | 8 | 22 | 2012-04-19 15:20:10 | Prepared | 1 | 116 | | XWiki.XWikiTranslator | 8 | 24 | 2012-04-29 02:01:45 | Prepared | 1 | 116 | | XWiki.XWikiTranslator | 8 | 25 | 2012-05-04 18:55:30 | Prepared | 1 | 116 | | XWiki.XWikiTranslator | 8 | 26 | 2012-05-04 19:02:09 | Prepared | 1 | 116 | | XWiki.XWikiTranslator | 8 | 27 | 2012-05-10 02:04:36 | Prepared | 1 | 116 | | XWiki.XWikiTranslator | 8 | 28 | 2012-05-30 02:02:08 | Prepared | 0 | 5671 | | XWiki.XWikiTranslator | 8 | 29 | 2012-06-07 10:44:28 | Prepared | 0 | 5782 | +-----------------------+--------------+--------------+---------------------+-------------+------------------------------+-------------------+ http://l10n.xwiki.org/xwiki/bin/view/XE/XEXWikiCoreResources_2107067965_cor… Most entries are "no changes" and have been cause by the L10NUpdater which wrongefully saved the document with no changes. I believe this must have been fixed (by Thomas M.?) mid 2012. Now the 2M lines impact performance significantly and loads the DB for nothing (and in the activity stream as well). I suggest we clean up the history and activity stream. We have 2 possibilities: For xwikircs: 1/ Clean up only the bad data from XWikiTranslator when there are no changes: This is complicated as you need to verify if the change is actually a change and you cannot do that just with sql queries. It could be very long 2/ Clean up old data from pre-201206 from XWikiTranslator Simpler if it is safe to delete by date in the DB. After discussion with sergui this is a bit complicated because you need to make sure you don't delete the latest full version before the versions you keep. So you would have to do it by API which will take ages. 3/ Clean up up old data from pre-201206 from all users This is simpler as you can safely delete from the database everything older than a certain versions. Cleans-up even more but would loose contributor statistics unless we store 2012 contributor counts in an alternate table which would then be regularly updated In any case we should probably create this intermediary table for statistics as it would be much faster anyway. For activitystream: 1/ Clean up old data from XWikiTranslator 201206 or earlier 2/ Clean up old date from everybody 201206 or earlier What value do we see in the l10n history and actvity stream and which solutions do the other commiters suggest ? I would say it's interesting for contributor statistics (counting number of contribution by translators) but beyond that we can delete the data. So we would fix that by storing monthly statistics in a table and updating the latest 2 month through a scheduler job. This means that we can also delete history over 2 month. WDYT ? Ludovic -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

11 years, 7 months

[xwiki-devs] [ANN] XWiki 4.5 Milestone 1 released

by Vincent Massol

The XWiki development team is proud to announce the availability of XWiki 4.5 Milestone 1. This release is the last stabilization release for the 4.x cycle with improvements on Distribution Wizard, SOLR Search and App Within Minutes. 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/ReleaseNotesXWiki45M1 Thanks -The XWiki dev team

11 years, 7 months

[xwiki-devs] [VOTE] Release 4.5M1 on Monday + new dates

by Vincent Massol

Hi devs, We're very late for the 4.5 release. Here are the dates we planned initially (see http://www.xwiki.org/xwiki/bin/view/Roadmaps/WebHome): * 4.5M1: 14th of Jan 2013 * 4.5RC1: 21st of Jan 2013 * 4.5 Final: 4th of February 2013 Here are outstanding issues currently marked for 4.5M1: http://jira.xwiki.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=fixVer… Since we're late and since there are already interesting changes in 4.5M1 (see RN: http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki45M1), I'm proposing to have the following new dates: * 4.5M1: Monday 28th of Jan * 4.5RC1: Monday 4th of Feb * 4.5Final: Monday 11th of Feb WDYT? (that's one week of delay compared to original plan) Volunteers are also welcome to act as Release Manager for these releases. Barring that I'll do it but I'm getting a bit tired (I've done the last 4 releases). Thanks -Vincent

11 years, 7 months

[xwiki-devs] [VOTE] Reduce garbage in the log generated when a migration fails

by Denis Gervalle

Hi devs, I am currently working on XWIKI-8718 ( http://jira.xwiki.org/browse/XWIKI-8718) to improve the reporting of failed or missing migration directly in the error reported by the browser. To do so, I keep a cache of the exceptions generated by migrations, and reattach them to all access failure to a given database. This will really help the end user, since it is no more necessary to dig the logs to notice a duplicate key issue in a migration. However, during a simple initial request to XWiki, a lot of access is done to the database, and many of them are not fatal (especially in a farm with a valid main wiki), but reports warnings or errors to stdout. This produce between 5K (main wiki had failed) to 22K lines (a subwiki has failed). Most of them are caused while getting a value in preference of user, space or wiki. And since these are linked together, in a fallback manner, getting a user preferences cause three error reports and space two. Currently these errors are logged at WARN level. Since all these are not fatal, and provide correct fallbacks for the current situation, I would like to reduce that log level to DEBUG. Doing so will significantly simplify the logs (around 2K lines), and avoid really repetitive reports, since each access to a single value of the preferences are reported individually. Here is my +1 to reduce to DEBUG, the log level of: XWiki#getUserPreference(String prefname, XWikiContext context) XWiki#getSpacePreference(String preference, String space, String defaultValue, XWikiContext context) XWiki#getXWikiPreference(String prefname, String fallback_param, String default_value, XWikiContext context) WDYT ? -- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO

11 years, 7 months

[xwiki-devs] [PROPOSAL] So what do we do for our Maven projects names

by Thomas Mortagne

Hi devs, In order to automate the update of extensions imported from https://github.com/xwiki/ we need to have nothing to modify when an import is done. The last remaining thing is the name on which there is a debate is the name. Right now the name we have in our maven project looks like "XWiki Commons - Extension - Repository - Maven" so that's what we get when importing this project or when viewing it in EM UI. Some of us want to keep this idish name for Maven build but don't like it when displaying extension. I recently introduced a way to overwrite some extension related informations like the name based on properties. So here are the choices we have: 1) Do nothing which mean display "XWiki Commons - Extension - Repository - Maven" in EM UI and extensions.xwiki.org 2) Change our naming in Maven <name> property for it to be more a name than an id that would looks good in EM UI 3) Keep the same naming for Maven <name> and overwrite it everywhere using <xwiki.extension.name> property So, WDYT ? The one that makes the more sense to me is 2) so my +1 goes to this one. Frankly I don't care too much having the current id based display of the summary of built modules in Maven build and I personally won't have any issue to know what name correspond to what project (but that's because I know them well, I can understand new dev could be a bit more lost). Then: * +0 for 3) to +0 (I don't like too much having this special case everywhere in our Maven pom.xml) * -0 for 1) (I agree that it does not looks very nice as a display name). -- Thomas Mortagne

11 years, 7 months

[xwiki-devs] internationalization of DBTreeList

by Paul Libbrecht

Hello fellow XWikiers, Yesterday we released Curriki 1.13.1 and realized that one of our cluster nodes was actually speaking French for the subjects tree. This really felt like... a french-speaking-guy saved the wrong thing, I was under high suspicion! ;-). I dug the code for quite a while then found it: the subjects display simply uses doc.display(field). So it all happens internally. After a while, I realized that caching was quite intensive, which explains why it's working well. However, I also saw that this caching was actually implying that these tree-lists are monolingual, because treeview.vm uses item.value to express the labels. Is there a reason to not use i18n objects, in javascript or in velocity, there? thanks in advance Paul

11 years, 7 months

[xwiki-devs] Users and Groups not available after updating from 2.7* to 4.2

by echocoder

I migrated from Xwiki 2.7.33656 to version 4.2. In doing so, I seem to have lost my user and group objects. I exported the Xwiki from the previous version and just reimported into the new install of 4.2. The Admin console seems to hang when listing users or groups, I also cannot add either. Did the location of the user/group objects change in 4.2? Can anyone tell me why an export from 2.7* followed by an import in 4.2 would not transfer these objects correctly? -- View this message in context: http://xwiki.475771.n2.nabble.com/Users-and-Groups-not-available-after-upda… Sent from the XWiki- Dev mailing list archive at Nabble.com.

11 years, 7 months

[xwiki-devs] Issue with the document translation bundle created by AWM

by Marius Dumitru Florea

Hi devs, In order to implement http://jira.xwiki.org/browse/XWIKI-8584 I had to choose between using the document translation bundle on demand (only when needed) and using it automatically (in some scope). The problem with on demand is that if you have a live table you need a custom live table results page just to demand the translation bundle when live table results are fetched. So I decided to use wiki scope, but, as it turns out, you need special rights to register a document translation bundle on the entire wiki. A simple user creating an application with AWM won't have the application translation bundle registered. The reason I choose the 'wiki' scope is that there was no 'space' scope. Space (application) scope makes a lot of sense in my case and I'm wondering if it's hard to implement it. Note that I already make the application creator an admin of the application space, so requiring space administration rights for space scope is fine for me. WDYT I should do for 4.5: (1) use the document translation on demand and generate a custom live table results page or (2) push for Thomas to implement space scope if it's simple :) Thanks, Marius

11 years, 7 months

[xwiki-devs] [ANN] XWiki 4.4.1 released

by Vincent Massol

The XWiki development team is proud to announce the availability of XWiki 4.4.1 This is a bugfix release. 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/ReleaseNotesXWiki441 Thanks -The XWiki dev team

11 years, 7 months

← Newer
1
2
3
4
5
6
7
8
9
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs January 2013