xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

[xwiki-devs] [History] Add links to every revision

by walid yaich

Good morning, I read the user guide and a part of developer's guide and i really really really like the philosophy and architecture of XWIKI, thanks for all XWIKI Teams and contributors for this great work :) Actually, i need some help, Now, In the page history, we have one link "delete" related to every revision I need to add for every revision next to "delete" two links, "approve" and "unapprove" like this in mediaWiki [image: Images intégrées 1] Questions : 1)how can i find the right XCLASS and/XOBJECT to modify, 2)how can i know the code behind the link "delete", is it velocity ? Thanks in advance, Have a nice day :)

10 years, 8 months

[xwiki-devs] myxwiki.org status

by Ludovic Dubost

Hi, myxwiki.org seem to crash quite a lot recently and we have also detected that it's using a lot of CPU (compared to many other services that XWiki SAS is running). I've taken a memory dump of myxwiki.org to give it a look. I see in the memory analysis 400Mb in the velocimacro structures. This could be normal as there are some caches of macros for each wiki (and there are a lot of wikis), however this is a lot and should be looked at. I've put the page http://www.myxwiki.org/xwiki/bin/view/Admin/CheckVelocityManager to check if we see any macros being cached that should not be (like the bug we had on USH). In any case, in multiwiki we have an issue with cache of velocity macros which can grow pretty big without any cleaning up when the wiki is not accessed. I've also closed registration on the main wiki (there seem to be spam users) and will run some scripts with check for open wikis and for pages with big RCS (spam suspects). We should in any case reduce the load of myxwiki (private cloud analysis shows a big CPU usage) and for this some cleaning up of unused wiki sounds like a plan. We should contact all users and closed unused wikis (I bet there are a lot). Ludovic -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

10 years, 8 months

[xwiki-devs] [contrib] Move realtime-backend and realtime-wiki to xwiki-contrib

by Caleb James DeLisle

Hi, I'd like to shove these two projects over into xwiki-contrib github group. One is for the backend which supports realtime-wysiwyg and realtime-wiki and the other is the realtime-wiki (text editor). https://github.com/cjdelisle/xwiki-contrib-rtbackend https://github.com/cjdelisle/xwiki-contrib-rtwiki Thanks, Caleb

10 years, 8 months

[xwiki-devs] [IDEA] Start supporting IE10 and IE11

by Andreea Popescu

Hello all, I’m writing this e-mail because I want to propose supporting Internet Explorer 10 and Internet Explorer 11 on 6.x cycle. First of all, it’s known that Internet Explorer 8 and Internet Explorer 9 are still widely used by users, but many of them are currently choosing to update to IE10 and IE11. According to netmarketshare.com (Browsers -> Desktop Share by Version) from a total of 100%, IE10 is used by 6.85% users and IE11 by 16.61% users. It’s true that IE10 is not as popular as the older versions (IE8 - 20.85% and IE9 - 8.89%), but its usage percentage is still significant. Second of all, both versions (IE10 and IE11) have some problems rendering our content sometimes, and you will see that below: IE10 known problems (unfixed) reported on JIRA: 1. XWIKI-10269: Table edit: pressing enter inserts new line in a different table cell 2. XWIKI-10299: The last annotation for a word isn’t displayed on IE10 3. XWIKI-10300: If a text has multiple annotations after removing one of them the text looks like isn’t annotated on IE10 4. XWIKI-10192: The "Username" and "Password" input fields don't have the same size IE11 known problems (unfixed) reported on JIRA: 1. XWIKI-9933: When you press "Alt+C" in IE11 (cancel edition) in edit wiki mode, the wiki session is canceled, but it also appears the "View favourites, feeds and history" option 2. XWIKI-9787: Jump to a page using CTRL+G doesn’t work 3. XWIKI-10192: The "Username" and "Password" input fields don't have the same size Last but not least, since December - January I’ve been testing IE10 and IE11 (smoke tests or full tests) and their biggest problems were with WYSIWYG (you can see that on: XWIKI-9698, XWIKI-10282 and XWIKI-10283). So, what do you think? Andreea

10 years, 8 months

[xwiki-devs] [Proposal] Display the extension ID on e.x.o

by Denis Gervalle

Hi devs, I know this have been removed and considered too technical, but I am sure this is a bad idea because: - we display it in EM, so is it less technical there ? - this is the only way to be sure you talk about the same extension, and there are couple of extension with very similar names - it allows finding the right extension for sure (using advance search), which could avoid ambiguities while working remotely with an end user Ok, it should not be the title of the document, but it should be there somewhere to be copy pasted. Here is my +1 to put it back. -- Denis Gervalle SOFTEC sa - CEO

10 years, 8 months

[xwiki-devs] [CONTRIB] New contrib project for realtime-wysiwyg

by Caleb James DeLisle

Hi, I'm working on the realtime wysiwyg extension and it's working fairly well but it's still a bit rough around the edges, some issues I'm aware of and others I am not so I would like to #1 move it to xwiki-contrib git repository and #2 have a bugtracker project to keep track of issues for this project. I'm thinking RTWYSIWYG as a project name on the xwiki.org bugtracker, does this make sense? Thanks, Caleb

10 years, 8 months

[xwiki-devs] About Bootstrap and Color Themes

by Guillaume "Louis-Marie" Delhumeau

Yesterday, I was talking to some of you on IRC, and I realized that we do not have the same expectations about our Bootstrap usage. So I would like to write a brief summary of my thoughts. Benefits of using Bootstrap ====== * Good-looking and practicals components to re-use. * A responsive CSS grid * Supported by a great community * Newcomers on XWiki will find a tool they might already know. That's already some good reasons to use it! What it cannot do for us ===== * Out-of-the box usage of a compiled Bootstrap CSS with different colors. Why? * The images URL needs to be rewritten (/xwiki/bin/resources/etc...) * A compiled Bootstrap CSS does not allow us to use the mix-ins (ie 'functions') that we can use with the Bootstrap sources. So it's less powerful. * There will always be a need to write some 'fixs' to not break the existing XWiki applications. Moreover, the kits that we can find on the internet, in my opinion, do not only change the parameters of Bootstrap. But they should also add their own CSS classes with an example of use in a HTML template. It will never auto-magically fit with XWiki. What I have in mind ===== Write a color theme editor, inspired by what there is for Bootstrap, that allows us to set values for bootstrap variables we decide to expose (there are more than 300, so I guess we should make a choice). We can take inspiration from http://stylebootstrap.info/ (but it should be less technical IMO). Plus add a textarea that lets the user enter some LESS code. So they could set other bootstrap variables and create their own CSS classes. So integrating a theme kit bought on the web would be possible without too much effort as soon as the LESS files are provided within the kit. Example: integrating a theme from Bootswatch ( http://bootswatch.com/ ) ==== Let say we want to integrate http://bootswatch.com/slate/ into XWiki, using the Flamingo skin. Steps: 1 - Create a new Color Theme for Flamingo 2 - In http://bootswatch.com/slate/ , download variables.less and bootswatch.less 3 - Paste the content of these 2 files in the textarea at the bottom of the Color Theme Editor. 4 - If some problem occurs, add some fixes in the textarea. Results: http://tof.canardpc.com/view/73dd64b9-2023-4839-8dcc-47880d823591.jpg Not perfect, so we need some fixes (about the glyphicons). After removing from the textarea the following line: @icon-font-path: "../fonts/"; We get: http://tof.canardpc.com/view/cd25fc9f-921f-4582-b2c7-05680dd6d284.jpg Looks quite simple, maybe not enough for a basic user, but still good for web integrators. WDYT? Thanks Guillaume

10 years, 8 months

[xwiki-devs] Separate GET/POST submits to filter spam for anonymous comments

by Valdis Vītoliņš

Another idea which couldn't bother normal users for anonymous XWiki comments would be separation between GET/POST submits, because spammers mostly use GET instead of POST. I couldn't find how added comment request is handled on server side though. I suspect, it is not handled with velocity scripts. Can you provide some directions? Thanks! Valdis

10 years, 8 months

[xwiki-devs] [contrib] proposal to move xwiki-tools into contrib repo.

by Caleb James DeLisle

Hi, xwiki-tools is a set of command line tools and a node.js library for building and parsing parts of xwiki .xar files. It is unique in that it contains a fairly complete model of XWiki documents, objects, and classes which is not based on the original model in oldcore. It is capable of compiling a filesystem representation of an xwiki extension such as: https://github.com/xwiki-contrib/realtime-wysiwyg into either a Maven compatible directory structure or a .xar file (which can optionally be auto-posted up to the rest interface of a running wiki). Until now I have never considered moving it into xwiki-contrib because it was always "the ducttape I needed to make the real project I was doing approachable" but even if it does not enjoy API stability guarantees, it is useful even if only as a tool for facilitating better thought about the XWiki model so I would like to move it into xwiki-contrib repository and setup a bugtracker for it. Unfortunately the name xwiki-tools which is quite descriptive in the npm repository is not so helpful in xwiki-contrib so I would be willing to rename it to node-xwikimodel (in npm it would be xwikimodel) and using a jira project name NODEXWIKIMODEL. WDYT? The project: https://www.npmjs.org/package/xwiki-tools https://github.com/cjdelisle/xwiki-tools

10 years, 8 months

[xwiki-devs] adding a javascript library(PramukhIME) to a XWiki page.

by ananthakrishna

Hi all, I want to add a javascript library called PramukhIME( http://www.vishalon.net/PramukhIME/JavaScriptLibrary.aspx) into an XWiki page. The objective is to edit Kannada language text(which is already in the page) in a XWiki page.Also,as I wan't to edit multiple pages,it will be better if the library is added only once(together for all pages). As I am new to XWiki, I don't know the basics of XWiki programming and can't even find relevant documents. Can someone please help me out.. -- Thanks and Regards, Ananthakrishna

10 years, 8 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