Hello,
First of all, Merci bcp Vincent for this How to implement "Approved
Revisions"?<http://www.xwiki.org/xwiki/bin/view/FAQ/How+to+implement+%22Approved+Revisi…>
I was able to choose which revision to display by following the "how to",
now i need to add the object automatically to any page in my wiki or at
least any page in a given space
Thanks in advance :)
The XWiki development team is proud to announce the availability of
XWiki 6.1 Milestone 1.
This release introduces the ability to change the width of the panel
columns and comes with an improved Active Installs feature (with
evolution graph and many new filters). Developers can now use the LESS
preprocessor for skin style sheets. A couple of bug fixes (18) and
some small improvements (24) make this release worth trying.
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/ReleaseNotesXWiki61M1
Thanks
-The XWiki dev team
Hello devs,
I would like a repository for the Hierarchy Macro on
https://github.com/xwiki-contrib.
Hierarchy Macro use jQuery and jsTree (http://www.jstree.com) to display
dynamique tree view of wiki documents based on parent/child relationships
Thank you in advance.
Lyes Bandou
Needs: As you already know, the new skin, Flamingo, is based on Bootstrap (
http://getbootstrap.com/) which use a CSS Preprocessor to have more
flexibility. There is 2 majors competitors in this field: LESS (
http://lesscss.org/) and SASS (http://sass-lang.com/). Bootstrap is using
LESS but they also provide an official port for SASS.
We need to execute one of these preprocessors at the runtime, to recompile
the Bootstrap CSS according to the current Color Theme.
After a long thread [1] where we have compared the 2 preprocessors, and
after some discussions on IRC, **I am proposing you to choose LESS**.
Why:
* It is the original preprocessor used by Bootstrap, and so the majority of
Bootstrap Themes that we can find on the web provides LESS sources. If we
want to be able to use all these themes, using LESS is clearly an advantage.
* Caty, Denis and I have a bit of experience with it. Bluebird [2], Junco
[3] and the current Flamingo skins are built with LESS.
* The syntax is not too close to Velocity, meanwhile SASS is.
* The Java integration, using Rhino, works quite well. Although there is an
issue [4] for which I have written a patch. I hope the LESS community will
handle it.
* It looks a bit more popular than SASS.
Here is my +1 for using LESS.
For the record, this is what I am going to do:
* Implement a cache to only compile LESS files when needed, because the
computation is costly. The cache will be flushed only when the current
color theme is modified.
* Write new components and a script service to compile LESS files that are
present in the skin directory, partially parsed with Velocity. In the
future, we might want to integrate it directly in the Skin Action, but that
means we need to change oldcore.
Thanks,
Guillaume (Louis-Marie)
---
[1] The thread "[Proposal] Integrate LESS css in XWiki":
http://markmail.org/message/hw45txkv2vk5dnqw
[2] Bluebird Skin:
http://extensions.xwiki.org/xwiki/bin/view/Extension/Bluebird+Skin
[3] Junco Skin:
http://extensions.xwiki.org/xwiki/bin/view/Extension/Junco+Skin
[4] LESS issue: https://github.com/less/less.js/issues/2005
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 :)
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
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