xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

by Vincent Massol

Hi, The current header copyright says: "Copyright 2006-2007, XpertNet SARL, and individual contributors as indicated by the contributors.txt." 2 issues: - The sentence is not english - We don't have such a file I propose that we change it in favor of: "Copyright 2006-2007, XpertNet SARL, and individual contributors." Main Reason: - We don't specify where the contributors are listed which means we can decide to change that location. For example a list of contributors is on http://www.xwiki.org/xwiki/bin/view/Community/ HallOfFame#HContributors but it's far from being accurate. Tomorrow we may use another strategy or another location and we'd rather not change all headers. So better not specify where we define them. Another location is SVN. Here's my +1 to that. I also propose that we continue listing contributors on that HallOfFame page. Unfortunately I've been the only one adding names there. I need help. Thanks -Vincent

17 years, 3 months

Re: [xwiki-commits] r4049 - in xwiki-platform/xwiki-applications/trunk/panels: . src/main/resources/Panels

by Vincent Massol

Hi Catalin, That's cool. I think I had a jira issue in XE for fixing all orphaned links for 1.1M4. If you do more fixes of this kind maybe you could use that jira issue # in the commit (you may want to create other issues if your changes are not in the XE JIRA though. Thanks -Vincent On Jul 28, 2007, at 3:59 PM, Catalin Hritcu wrote: > Author: hritcu > Date: 2007-07-28 15:59:52 +0200 (Sat, 28 Jul 2007) > New Revision: 4049 > > Removed: > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/New Panel > Modified: > xwiki-platform/xwiki-applications/trunk/panels/ > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/AddClassProperty > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/AddObject > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/Backlinks > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/BlogCategories > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/ClassEditorWelcome > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/ClassSwitcher > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/CreatePanel > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/DocumentInformation > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/EditTranslations > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/GlobalRightsEditorWelcome > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/HomePageUpdate > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/IncludedDocuments > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/Members > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/MyRecentModifications > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/Navigation > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/NewPage > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/ObjectEditorWelcome > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/OrphanedPages > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/PanelClass > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/PanelLayoutUpdate > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/PanelSheet > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/PanelTemplate > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/PanelWizard > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/QuickLinks > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/Recently Created > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/Recently Modified > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/RecentlyVisited > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/RightsEditorWelcome > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/RightsHelp > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/RightsTips > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/Search > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/Shortcuts > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/SpaceDocs > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/Spaces > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/SyntaxHelp > xwiki-platform/xwiki-applications/trunk/panels/src/main/ > resources/Panels/Tags > Log: > Added svn:ignore for Eclipse project files > > XAPANELS-33: If it says Valid XHTML, then it MUST be valid XHTML. > All documents fixed > > Setting the parent for all panels.

17 years, 3 months

[Proposal] Solution for filtering out pages in the XE wiki

by Vincent Massol

Hi, We need a global solution for including/excluding pages in the XE wiki. The needs comes from the fact that we shouldn't show internal pages to casual xwiki users and we shouldn't show pages that they don't have the rights to view. At least the following places need to use this feature: * Navigation panel * All docs Treeview * All docs Index * WebSearch * WebSearchRss * WebRss * Orphaned pages + Panel I propose the following implementation: 1) Add a new API $xwiki.filterDocuments(List docNamesList, String persmissionToCheck). It would be used like this: for each ($item in $xwiki.filterDocuments($xwiki.searchDocuments ($sql), "view")) ... In the XE wiki: 2) Add a XWiki.PageFiltersClass class with 1 property: Includes. This property will contain pages to exclude, using HQL like format (one entry per line) 3) Add a XWiki.PageFiltersClassSheet to explain what this is about, explain how to add/remove entries, etc 4) Add a XWiki.PageFilters document that contains a XWiki.PageFiltersClass object and which has velocity code in its wiki content to compute the HQL clause corresponding to the exclusions specified in its object. 5) Modify the documents listed above to use XWiki.PageFilters as follows: #includeInContext("XWiki.PageFilters") #if (!$pageFiltersSqlClause) #set ($pageFiltersSqlClause = "") #end #set ($sql = ".... and $pageFiltersSqlClause ...") #set ($list = $xwiki.filterDocuments($xwiki.searchDocuments($sql , $nb , 0), "view")) ... WDYT? Thanks -Vincent

17 years, 3 months

using XAR pages to modify user details

by Radu Danciu

Could anybody point me towards some documentation about how to write/use xar files? Thanks, Radu

17 years, 3 months

[Proposal] Document history storage

by Sergiu Dumitriu

Hi, Sometime ago, there was a discussion regarding how should the document history be stored in a better way. Right now, the complete history is stored as one field in the xwikidoc table. From my PoV, this has some major disadvantages: - loading an older version requires parsing all the history -> memory inefficiency - as the documents grow older, loading a document will take a lot of time -> time inefficiency - queries on archives cannot return just one version, but they match the whole document (somewhere in the history, there was a version containing "search term") The blocking issue with storing old version in a different table was, at that time, the fact that a document archive should contain all information needed for completely restoring the document, like content, metadata, objects. I don't think that is actually an issue. We are archiving document versions, but we're joining all versions in one large string. Why don't we archive the complete version, but one version per row? So, the archive table should look like: - document name - version number - language (for translations) - content - archived metadata (one field, or the same fields as in xwikidoc) - archived objects (one field) - attachment names and versions It is not like storing the version as a normal document is, with separate objects and properties, but at least it provides a better storage and retrieval mechanism, and it separates a bit the parts of a wikidocument - content, metadata, objects. WDYT? -- http://purl.org/net/sergiu

17 years, 3 months

Re: [xwiki-commits] Build XWiki Enterprise::Default #8 failing

by Sergiu Dumitriu

Why are there links to localhost? teamcity(a)xwiki.org wrote: > Build XWiki Enterprise::Default #8 failing > Agent: Default agent > Build results: http://localhost:8111/viewLog.html?buildId=30&buildTypeId=bt7 > > Changes included (1 change) > ==================================================== > Change 4048 by sdumitriu (2 files): > XE-30: If it says Valid XHTML, then it MUST be valid XHTML. > Fixed some documents. > > > see more information about changed files: http://localhost:8111/viewLog.html?tab=buildChangesDiv&buildId=30&buildType… > > > ============================================================================ > Configure email notifications: http://localhost:8111/profile.html?init=1#notifications > > >

17 years, 3 months

TeamCity is back

by Vincent Massol

ok, after fighting for 2 days, TeamCity is back working fine. http://teamcity.xwiki.org We had a disk full problem dues to the large size of our maven repos so I cleaned them all and then discovered the build on TC wasn't working anymore. This was due to several errors in the build which were hidden by the fact that the local repo on the TC machine had the artifacts there. To be more precise, in order to do a release with maven we cannot have any SNAPSHOT deps in our POM so we had to "release" some external dependencies we're using in SNAPSHOT version. One of these was the maven selenium plugin and I've discovered that faking a release of an external maven plugin isn't as simple as it appears... But I now know how to do that. Thanks -Vincent

17 years, 3 months

About Copyright Statements...

by tharindu jayasuriya

Hi Vincent, We are going to add copyright statements to Xeclipse source, I think we can get them from xwiki sources, please let us know if you have any concerns... Btw, is it Xeclipse or XEclipse ? :) Thanks. - Tharindu & Asiri

17 years, 3 months

Re: Build XWiki Platform Web::Maven2 #217 failed

by Vincent Massol

All those errors were caused by some disk space issue that has been fixed now. -Vincent On Jul 24, 2007, at 2:18 PM, teamcity(a)xwiki.org wrote: > Build XWiki Platform Web::Maven2 #217 failed > Agent: Default agent > Build results: http://teamcity.xwiki.org/viewLog.html? > buildId=1395&buildTypeId=bt7 > > Changes included (1 change) > ==================================================== > Change 4019 by vmassol (1 file): > XWIKI-1519: The version shouldn't come from xwiki.cfg file > > see more information about changed files: http://teamcity.xwiki.org/ > viewLog.html?tab=buildChangesDiv&buildId=1395&buildTypeId=bt7 > > > ====================================================================== > ====== > Configure email notifications: http://teamcity.xwiki.org/ > profile.html?init=1#notifications

17 years, 3 months

Change of SVN externals for trunks-users

by Vincent Massol

Hi, I'm about to modify the SVN externals definition for trunks-users so that they point to our own XWiki readonly SVN repo instead of pointing to the OW repo as there are issues with it. If you have checked out trunks-users, then do a svn update once I've made the change. Hopefully that'll just work. If not, you might need to do a new checkout. Sorry for that Thanks -Vincent

17 years, 3 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs