xwiki-users

xwiki-users@xwiki.org

10408 discussions

[xwiki-users] How to track user activity?

by Ezequiel Scott

Hello, Since XWiki support user accounts, enabling visitors to create an account and sign in to the site, Can you tell me if It's possible with a little bit of effort track the activity of logged users? This can include recording activities such as what pages were visited as well as what actions were performed. May be it is possible implementing a plugin with Velocity or extracting the data from database. Have any idea how to do it? Thanks!! -- *Ezequiel Scott** * ezequielscott(a)gmail.com

12 years, 3 months

[xwiki-users] [ANN] XWiki Enterprise and XWiki Enterprise Manager 4.2 Release Candidate 1 released

by Eduard Moraru

The XWiki development team is proud to announce the availability of XWiki Enterprise 4.2 Release Candidate 1. This is the first and hopefully final release candidate of the 4.2 release cycle. Being a release candidate, this release contains bugfixes and polishing, most of them focused on the new distribution wizard. 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/ReleaseNotesXWikiEnterpris… Thanks -The XWiki dev team

12 years, 3 months

[xwiki-users] User rights?

by Matt Lamoureux

Can someone please confirm that I understand user rights properly? I have a wiki in which I have loaded all of our custom pages into a space called "1". We use LDAP, so every user is automatically added to the XWikiAllGroup. We have a small team that wants to utilize secured pages, so I created a group called GroupA. I then went through and added team members to GroupA (without removing them from XWikiAllGroup). At the wiki level, I have granted both groups "view" access, but blocked everything else. At the "1" space level, I have granted both groups "edit" and "delete" rights Now, in that space, there are some pages that we only want GroupA to see. I thought it was simple - I could just go into each page, block XWikiAllGroup from view/edit/delete, and grant view/edit/delete access to GroupA. Apparently that is not true - the fact that they are still in XWikiAllGroup prevents them from viewing those pages, since that group is blocked? I expected the fact that they are part of GroupA and GroupA is authorized, they would be authorized. If that is true, what is the solution to this? What is the simplest way to secure a page from everyone except the members of GroupA? If I remove GroupA members from XWikiAllGroup, that seems to cause other issues with skins and such. Any suggestions? Thanks! - Matt L.

12 years, 4 months

[xwiki-users] Default value for 'static list' class property

by Ryszard Łach

Hi. Is it possible to assign default value for class property of 'static list' ? TIA, R.

12 years, 4 months

[xwiki-users] Collapsable sections on a wiki-page

by Hamster

Is it possible to create collapsable sections on a wiki-page? (collapsable just like the panels you can add to your wiki). I think it would be realy cool to have this feature. People can just collapse sections and "browse" quicker to the information they seek on a large wiki-page. WDYT? -- View this message in context: http://xwiki.475771.n2.nabble.com/Collapsable-sections-on-a-wiki-page-tp758… Sent from the XWiki- Users mailing list archive at Nabble.com.

12 years, 4 months

[xwiki-users] Components best practices

by Jeremie BOUSQUET

Hi, I wonder if they are some specific recommendations, in addition to what's described in [1] and [2] ? My particular use-case, is to know if there is such a rule as to create one maven module for one xwiki component, or if several components can be grouped in the same maven module. Detailed description: for the xwiki-contrib-mailarchive-api, I started from a monolithic class (@Component), then I started splitting it up in several classes. While each of these sub-groups could be considered components (highly related to the mail archive use-case, ie not particularly re-usable), for now their life-cycle is managed by the main Component (ie if one of them needs a query manager, it is not injected by xwiki framework, but provided to it by the main Component). Would it be recommended to move to a whole component architecture, and make all these sub-components Components managed by xwiki framework ? Are there any limitations (perfs...) to do it that way ? I'm pretty sure it's obvious to xwiki devs, but I prefer to ask. Br, Jeremie [1] http://platform.xwiki.org/xwiki/bin/view/DevGuide/WritingComponents [2] http://extensions.xwiki.org/xwiki/bin/view/Extension/Component+Module

12 years, 4 months

[xwiki-users] Horizontal Menu like xwiki.org in Farm

by niko dangl

Hi everyone, i just created my own farm and try to build a template wiki which i can use for upcoming wikis. now i got some problems with the configuration. after searching for a menu bar like on xwiki.org i found the extension which is what i was looking for. http://extensions.xwiki.org/xwiki/bin/download/Extension/Navigation+Menu+Wi… if i go to the main wiki i can use this menu and it works..but on my subwiki it wont work.. hopefully someone is more experienced in running a farm and culd help me out. i dont really know where to start now because i checked the rights and i think its fine. thanks so far and regards Niko

12 years, 4 months

[xwiki-users] XWiki's WYSIWYG editor -- tinyMCE and GWT-based

by ray ye

Hi All, Two WYSIWYG editors were included in XWiki -- tinyMCE and GWT-based. I understand that 1. tinyMCE was used at the very beginning, and later GWT-based was used to replace tinyMEC because tinyMCE was buggy, and its performance was not good (at the time) 2. the version for tinyMCE included in XWiki 4.1.4 is 2.0.6.1 released on 2006-05-04 ( I checked the code ), and the latest version is 3.5.7 release on 2012-09-20. My questions are: 1. have any one revisit later release of tinyMCE, since lots have changed over the 6 years? 2. for the GWT-based WYSIWYG solution, is it developed by XWiki? and is there a way that i can get WYSIWYG related codes only, and integrate it into one of our internal project? Thank you very much! Ray

12 years, 4 months

Re: [xwiki-users] [Brainstorming] XWiki 5.x cycle

by Dmitry Bakbardin

Hi, Andreas, See below, Tue, 18 Sep 2012 15:36:15 +0200 от Thomas Mortagne <thomas.mortagne(a)xwiki.com>: >On Tue, Sep 18, 2012 at 2:20 PM, Vincent Massol <vincent(a)massol.net> wrote: > > Hi Dmitry, > > > > Thanks for your inputs! See below. > > > > On Sep 18, 2012, at 2:10 PM, Dmitry Bakbardin <haru_mamburu(a)mail.ru> wrote: > > > >> Hi, Vincent, > >> > >> My 10 coins to the suggested topic :-) > >> > >> 1. New Access Rights management system. There are a lot of weak points already known. Probably, it's time to review this. > > > > Have you been able to play with it already? Would be great to provide feedback and details. I'm sure Denis would love some feedback. > > Andreas too ;) > > Do you actually know there is a new right management system ? It's not > clear in your question if you talk about introducing a new right > management system or using more the new one.I mean situations like http://jira.xwiki.org/browse/XWIKI-2184 and http://jira.xwiki.org/browse/XWIKI-6987 Probably I missed something in the roadmap and release notes, but I didn't see it fixed. And these reports were not the only "bugs" found as far as I remember mailing lists conversations. All of them required brand new system and Vincent said, that these changes are planned after comprehensive discussion and voting in futher releases. So, I mean BRAND NEW system that acts as expected, e.g. user with edit rights is in the "god mode" as to the page. I expect edit rights means edit page, but not access rights change. Access rights looks more admin function. And so on. IMHO it worth discussion. > > > > >> 2. Second level XWiki virtualization http://jira.xwiki.org/browse/XEM-207 > >> > >> 3. Add WYSIWYG's editor logic while adding the link Space -> Page -> Anchor on the page http://jira.xwiki.org/browse/XWIKI-4084 > >> > >> and the same in XEM Environment: Workspace/Virtual Wiki -> Space -> Page -> Anchor > >> http://jira.xwiki.org/browse/XWIKI-7483 > >> > >> 4. WebDAV access to deleted attachments http://jira.xwiki.org/browse/XWIKI-6989 > > > > So you're using XWiki WebDAV feature ATM? > > > >> 5. Rebuild Translation System and add possibility to translate not only page content, but objects' content (and field names) also. > > > > Just on this point, we're planning to work on this in XE 4.3 in the coming month. > > Except for the object content translation part which has more to do > with the model and is not going to change very soon. Note that fields > names are already translatable, for this you can use the id <class > full name>_<field name> like in "Blog.BlogClass_title" for the title > field name of a blog object. >Looks disaster for me :-) Let's overview simple usecase: - I buld FAQ (or something like it) in English with Application within minutes - I want to make it multilingual. Looks like I'm stuck by default: "not going to change very soon" :-( - I see the only "human-friendly" option to modify default scripting, produce templates for each language, then build pages like <PageName>_<Language> and load required page depending on requested language. I didn't make it like this yet, but if it is "not going to change very soon", I'd consider this way as an option to make application running in multilanguage environment. I understand, that this is not the best solution, but as far as I understand XWiki - it should work. > > > >> 6. Evolve filestorage system from "experimental" to all-kind-production-ready and make it more or less comprehensive: > >> - for example, add possibility of XWiki clustering and automatic attachments synchronization while FS is on. > >> - to configure path to store attachments for each XWiki/virtual wiki/workspace/space separetly. > >> - fix current bugs (like http://jira.xwiki.org/browse/XWIKI-6917) and probably add some other fatures :-) > > > > Yeah I also think we need Caleb to work a bit on this so that we could call it production-ready ;) > > > >> 7. Smooth upgrade system (to make it look more like linux upgrades): upgrade AND KEEP all XWiki customization with minimal manual config files comparison and reediting of customized pages inside XWiki. > > > > Yep, we're working on this one (XAR upgrades). You should see some first version with XE 4.2 when it's released next week. Next step is to tackle WAR and config file upgrades indeed. > > Note that for the server side (WAR and configuration) you have the > Debian package (see >http://platform.xwiki.org/xwiki/bin/view/AdminGuide/InstallationViaAPT) > that can help a lot since apt/dpkg is taking care of configuration > file comparison/merging. But that's only for Debian based system of > course. > > For the XAR part as Vincent said we are working on it and you get a > first version of an install/upgrade Wyzard for it in the coming 4.2.Thanks a lot. I was going to set up new server soon. Migration to Debian looks fine for me in this case. :-) Looking forward to 4.2. It would be "admin-rescue" release :-)))) > > > > >> 8. Add Space -> Subspace -> Page logic to XWiki hierarchy to build "trees" instead of "horizontal" set of spaces. > >> > >> 9. Extend TOC macro to logic: ...wiki1:Space1.Page1, wiki2:Space2.Page2... to include TOCs of separate pages inside current TOC. > >> > >> 10. XWiki Native support for mobile users (Skins, ColorThemes for all kind of mobile users bundled with XE/XEM) > > > > Ludovic has a pull request for improving mobile skin support for XE 4.3 but probably not to the extent you're interesting in at the moment. > > > > Thanks, keep the ideas coming. No promise that they'll be implemented but the more people who want the same thing the more weight it has. And developers are reading this! > > -Vincent > > > >> Hope it helps :-) > >> > >> Kind Regards, > >> > >> Dmitry > >> > >> > >> Tue, 18 Sep 2012 08:58:04 +0200 от Vincent Massol <vincent(a)massol.net>: > >>> > >>> > >>> > >> > >> > >>> > >> > >> > >> > >>> Dear XWiki lovers ;), > >>> > >>> > >> We're getting close to the end of the 4.x cycle which is about to be finished with XWiki 4.5 around end of January and we need to start brainstorming about the 5.x cycle (1 year duration from Feb 2013 to Jan 2014). > >>> > >>> > >> * 3.x was about "Building Apps and Distributing them" (priority 1) and "Polishing" > >>> > >> * 4.x was about "Ease of use" (priority 1) and "Quality" > >>> > >>> > >> So what would you like to see in the coming year? > >>> > >>> > >> You can suggest both general themes and specific items. > >>> > >>> > >> Thanks > >>> > >> -Vincent > >>> > >>> > >> > >> > >> > >> > >> Kind regards, > >> > >> Dmitry > >> WebDAV access to deleted attachments > > > > _______________________________________________ > > users mailing list > > users(a)xwiki.org > > http://lists.xwiki.org/mailman/listinfo/users > > > > -- > Thomas Mortagne > Thank you for good news and excellent work. Kind regards, Dmitry

12 years, 4 months

[xwiki-users] Multipage PDF Export and child/parent dependency

by Ryszard Łach

Hi. I'm trying to use http://extensions.xwiki.org/xwiki/bin/view/Extension/Multipage+Export+Appli… . It works almost fine, but I cannot find out how to create document structure exactly as I need. I've created three pages in Sandbox (T1, T2 and T3) with the following content (xwiki source): T1: = T1-1 = T2: = T1-2 = T3: = T1-3 = (T1 stands for "Title1" heading). Each one of them has 'Sandbox.WebHome' as their parent. When I create Multipage export (html or pdf), then in resulting document heading levels are being changed. This is HTML output: <h1 id="HT1-1"><span>T1-1</span></h1><h4 id="child_1543277317"><span>T2</span></h4><h5 id="HT1-2"><span>T1-2</span></h5><h4 id="child_1543277318"><span>T3</span></h4><h5 id="HT1-3"><span>T1-3</span></h5> Is there any way to keep the original heading levels intact? TIA, R.

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-users