xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

[xwiki-devs] [XWIKI-8160] Disappearing objects from user document

by Martino Dell'Ambrogio

Hello to everyone, My company has been using XWiki for a while and we have always been able to solve all problems by ourselves. This time, it's a bug so weird we need some help from you. Unfortunately, it is also quite urgent. Let's begin with a short description of the problem: - We use the latest XWiki development release, 4.2-milestone-2. - We use Basic Authentication. - We connect with a particular administrator to a particular subwiki (it does not happen with other admiministrators or in other subwikis). - We open XWikiPreferences once, all is fine. - We open XWikiPreferences once again, we get a login prompt. - Any subsequent call to any page gets us a login prompt. As you may know, with Basic Authentication, a login prompt is an impossible situation unless the user has been deactivated/removed or the server does not receive the logged-in username. But we dumped the JVM heap, and we found that the user object is still there and the server receives the logged-in username. After a lot of debugging, we discovered that the user document object used to retrieve the user object has no references to its objects. In other words, xObjects is an empty collection within the used instance of XWikiDocument. If you would like to help us just read the whole JIRA issue, it contains much more information. And thank you very much! http://jira.xwiki.org/browse/XWIKI-8160 -- Martino Dell'Ambrogio Security Auditor Web: http://www.tillo.ch/ Email: tillo(a)tillo.ch

12 years, 4 months

[xwiki-devs] Ignore whitespace at the start of the line when parsing Velocity templates

by Marius Dumitru Florea

Hi devs, The {{velocity}} macro has a nice filter that removes the whitespace from the start of each line. This allows us to format (indent) the Velocity code without generating whitespace garbage. Recently I had to move some Velocity macros from a wiki page to a Velocity template file and the absence of this filter turned out to be a pita. Even if my macros were generating HTML, consecutive whitespaces were collapsed into a single one which was still visible, breaking my layout a little. Some of my macros were generating Strings which now contained a lot of whitespace. I had to update my functional tests to trim the actual text taken from the UI whenever asserting something. WDYT about applying the same filter when parsing Velocity templates? Do you see any problems with ignoring the whitespace at the start of the line? Thanks, Marius

12 years, 4 months

[xwiki-devs] [VOTE] Add extension related information to XAR package.xml file

by Thomas Mortagne

Hi guys, I would like to modify a bit the Maven XAR plugin to add in the package.xml some extension related informations like the extension id and version at the very least. The idea is to be able to know what a XAR is exactly like we have the pom.xml packaged with the jar file for example. Among other things it will cover the following use cases: * when someone import a XAR with the standard UI, automatically register it in the extension index if it happen to be an extension (i.e. if we find extension informations in its package.xml) * wiki manager and workspaces can properly register actual extension when creating their default template from a XAR the first time (this is for example required to be able to upgrade a farm with EM where pretty much all the wiki as been created from this default template) In both cases the idea is to support as much current behaviours as we can and still be able to use the full power of Extension Manager. There should not be any backward compatibility issue here since it does not really change anything in the XAR structure. WDYT ? Here is my +1 Thanks, -- Thomas Mortagne

12 years, 4 months

[xwiki-devs] [UX][Proposal] Improvements on editing welcome block

by Ecaterina Moraru (Valica)

Hi, I have received numerous complains that simple users have problems in editing the content and title of the Welcome block ("Welcome to you wiki" gadget) from the homepage. There are multiple factors that influence the editing of that particular gadget and that make the job especially harder for beginners. One of these factors is that the gadget used to display the Welcome content is an "include" gadget. Without some custom actions for the gadget that would let the user navigate to the included page or without some auto-redirect mechanism, the simple users have difficulties in understanding where the welcome content is coming from and what actions they need to do in order to edit that content. Also the "include" macro has a lot of advanced properties that can be scary and confusing for users (context, reference, section, type, etc.). My proposal is to create a new "text" gadget. This gadget will be very-very simple and will contain just the gadget's title and the gadget's content. Its only purpose will be to let users add textual information inside a dashboard. http://incubator.myxwiki.org/xwiki/bin/view/Improvements/EditingWelcomeMess… Right now we have specialized gadgets for HTML content, velocity content, code in general, boxes, success messages, etc. but no way to put just a simple text inside the dashboard. Let me know what you think. Thanks, Caty

12 years, 4 months

[xwiki-devs] [VOTE] Postpone the 4.2 Milestone 3 release by one week

by Marius Dumitru Florea

Hi devs, Me and Thomas are late on the work for making an XWiki farm upgradable through the Extension Manager in a few minutes and JV just committed two new modules, wiki components and UI extensions, in the platform and they need some time to be tested and stabilised. Thus I'm proposing to delay the 4.2M3 release by one week and reduce the 4.2RC1 by one week so that the final release date for 4.2 stays the same: * 4.2M3: 3 September * 4.2RC1: 10 September * 4.2 final: 17 September Here's my +1. Thanks, Marius

12 years, 4 months

[xwiki-devs] 4.2 Milestone 3 is planned for today

by Marius Dumitru Florea

Hi devs, Do you have unfinished work that needs to be included in this release? I know JV has to move the wiki components module from contrib to platform. Anything else? Also, are there any blocking issues? Otherwise, I'd like to start the maven release in the afternoon. I'll take care of the failing tests in the mean time. Thanks, Marius

12 years, 4 months

[xwiki-devs] [vote] Move wiki components module from contrib to platform

by Jean-Vincent Drean

Hi, I've been working on UI extensions lately and those extensions are implemented as components. To be able to have components both defined from java code and from wiki documents I've worked on the xwiki-platform-component-wiki module started by Jerome a while ago. The initial design is described here: http://dev.xwiki.org/xwiki/bin/view/Design/WikiComponents In addition the module allows other modules to easily synchronize java components with content coming from XObjects. To do so you need to implement WikiComponent [1] and WikiComponentBuilder [2]. Then a manager will automatically unregister/register your components whenever it's required: when the wiki starts, when a document is updated, deleted, etc. In order to commit the UI extension module I need xwiki-platform-component-wiki to be moved to platform. Here's my +1 [1] : https://github.com/xwiki-contrib/xwiki-platform-component-wiki/blob/master/… [2] : https://github.com/xwiki-contrib/xwiki-platform-component-wiki/blob/master/… -- Jean-Vincent Drean, XWiki.

12 years, 4 months

Re: [xwiki-devs] XEM xmlpc using a wiki farm

by Jones, Dan

Thank you Mr. Mortagne! Keep up the great work. I will go with the 2nd option and use the REST api. ________________________________ This communication (including all attachments) is intended solely for the use of the person(s) to whom it is addressed and should be treated as a confidential AAA communication. If you are not the intended recipient, any use, distribution, printing, or copying of this email is strictly prohibited. If you received this email in error, please immediately delete it from your system and notify the originator. Your cooperation is appreciated.

12 years, 4 months

Re: [xwiki-devs] [GSoC] Pencils down, submit your evaluations to Google, and your status to the XWiki Community

by Jonathan Solichin

Hello Jerome, Vincent, friends Good idea. The extension page is here: http://extensions.xwiki.org/xwiki/bin/view/Extension/xorange wdyt? Thanks again, Jonathan Solichin > On Tue, Aug 21, 2012 at 11:43 AM, Jonathan Solichin <jssolichin(a)gmail.com>wrote: > >> Hello Sergiu, friends, >> >> First of all, thank you once again for this wonderful opportunity to work >> with the xwiki team. It has been a learning experience that will no doubt >> change my future in programming and open source. Like Sasinda said, all the >> support and help throughout the project have been enormous. I think all of >> us GSOC students will agree that it was one of the most interesting and >> useful summer we ever had. >> >> Thank you for the reminders to submit the code and evaluation. >> >> The XWiki team made a great impression, and in my opinion, a very good >> face for the open source community. I hope to be able to contribute more >> and continue support/development on the skin as it comes up. Like Sasinda I >> will definitely try to come back in my free time >> >> Status: >> The overall design and implementation goals of the skin is, in my >> opinion, achieved (note: as planned we did not use foundation as the base >> of our skin as the GSOC proposal stated). The skin works on a plethora of >> browsers (tested in ie7-9, opera, ffx, chrome, and safari. devices: g2x, >> nokia 710, nexus7, bb curve) and responds to size changes. Due to the >> limitation of some browser, there will be slight deviations, but none >> should impact the function of the skins. >> >> There are some minor differences than those of the design plan. For >> example the apps are not skinned as they were designed in the design plans. >> After working on the skin, I did not think that was priority since there >> are so many apps, that it wouldn't be the most fruitful use of the gsoc >> time to skin one. I'll try to work on these in my free time. The idea to >> create a 2nd configuration page for the skin was scraped since it was >> deemed to not be efficient. >> >> In general, the skin is usable and "complete". I think to truly complete >> the skin, we would need users to try and use the skins since I did not have >> the time, and I think XWiki is too expansive for me to test every use case >> scenario anyway. Future explorations would be how to make the skin >> functions more efficient. >> >> Thank you once again for the opportunity, do let me know of anything you >> would like me to do. Thanks Asiri for dropping by and dropping us the hint >> ahaha. >> Thank you for all those involved in making GSOC happen, from Caty, >> Eduard, Sergiu, Vincent, Thomas and anyone who I missed. Finally, last but >> not least, Thank you especially to Jerome, for mentoring me through out >> this time. >> >> Best, >> Jonathan Solichin >> > >

12 years, 4 months

Re: [xwiki-devs] [GSoC] Pencils down, submit your evaluations to Google, and your status to the XWiki Community

by Jonathan Solichin

Hello Sergiu, friends, First of all, thank you once again for this wonderful opportunity to work with the xwiki team. It has been a learning experience that will no doubt change my future in programming and open source. Like Sasinda said, all the support and help throughout the project have been enormous. I think all of us GSOC students will agree that it was one of the most interesting and useful summer we ever had. Thank you for the reminders to submit the code and evaluation. The XWiki team made a great impression, and in my opinion, a very good face for the open source community. I hope to be able to contribute more and continue support/development on the skin as it comes up. Like Sasinda I will definitely try to come back in my free time Status: The overall design and implementation goals of the skin is, in my opinion, achieved (note: as planned we did not use foundation as the base of our skin as the GSOC proposal stated). The skin works on a plethora of browsers (tested in ie7-9, opera, ffx, chrome, and safari. devices: g2x, nokia 710, nexus7, bb curve) and responds to size changes. Due to the limitation of some browser, there will be slight deviations, but none should impact the function of the skins. There are some minor differences than those of the design plan. For example the apps are not skinned as they were designed in the design plans. After working on the skin, I did not think that was priority since there are so many apps, that it wouldn't be the most fruitful use of the gsoc time to skin one. I'll try to work on these in my free time. The idea to create a 2nd configuration page for the skin was scraped since it was deemed to not be efficient. In general, the skin is usable and "complete". I think to truly complete the skin, we would need users to try and use the skins since I did not have the time, and I think XWiki is too expansive for me to test every use case scenario anyway. Future explorations would be how to make the skin functions more efficient. Thank you once again for the opportunity, do let me know of anything you would like me to do. Thanks Asiri for dropping by and dropping us the hint ahaha. Thank you for all those involved in making GSOC happen, from Caty, Eduard, Sergiu, Vincent, Thomas and anyone who I missed. Finally, last but not least, Thank you especially to Jerome, for mentoring me through out this time. Best, Jonathan Solichin

12 years, 4 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs