Hello fellow developers,
we have met a fairly hard bug on www.curriki.org which has almost delayed our release and required a last minute removal of our new discussions feature: the trigger of the sheet application has not been consistent. It has been inconsistent between servers (development, staging, production) and has been inconsistent between syntaxes.
For a while I thought that the lack of the class XWiki.ClassSheetBinding was guilty, but adding it did not change anything.
I then went through the XWiki core pages and added as much as possible that could have something related… then it started to work on pages in old syntax but failed with newly created pages (which are copies of a template page).
Where could I look to debug this?
There seems to be *something* applied, since the rendered page is empty and the content is ignored.
Thanks for hints.
Paul
PS: we're now running xwiki 3.5.1
Hi devs,
I’ve just committed support for http://jira.xwiki.org/browse/XRENDERING-278 (which allows copy pasting images in the WYSIWYG editor btw). However I’ve just realized (had forgotten) that my code will break image attachments to a subwiki named “data”:
image:data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAABHNCSVQICAgIfAhkiAAAAO9JREFUOE+lUrsNwjAUdCyWIBXjIEokVoCejgkyQ2gYAIkSsQUrUIUxwrund5bjX4OlyPG9u3v22Z2rjM1uWEtpkq//PC/fCs35UoHi/WGL8mTrErVsAJGJHU2KagGzHUi3I8iP+0s1nInXjBSPSfI/n2/vGTNFJZOVCRkYltdGl1FMRqmHYL0FFM6MjnFXaxCwNJMOZAbW6JyVkI1cbwcD3T5MGBjZLQxi8Lw9kp5iFFikUYwZr2dNQzQT7EavsDFOwl2ErNuIh5kgaX1E0bEyMTiZAcA0WAa26GSL7CUaHjJJz1wyqWLpe6gS/yn8AD9tcjFN7/ajAAAAAElFTkSuQmCC
Of course the solution for a user is to prefix with “attach:”, to show that it’s an image coming from an attachment:
image:attach:data:….
We discussed this previously:
* Original thread: http://markmail.org/thread/vw3derowozijqalr
* This lead to this first VOTE which was not conclusive: http://markmail.org/thread/vw3derowozijqalr
* Which lead to another VOTE which was also not conclusive: http://markmail.org/thread/t2wb2xq7534qsshg (note that this thread contains 2 proposals, the last one beeing a choice between A) and B)).
However we kind of agreed at the end that it would be acceptable to break backward compatibility (solution A in the last thread).
So the question here:
* Should I revert my change that I did for 5.4?
* Is it ok to break backward compatibility and thus add this in XWiki Syntax 2.1 as I did and document it on the release notes?
Note that I could also relatively easily implement a new rendering configuration option (e.g. rendering.ignoreResourceTypes=user,data) which would be optional and that would allow to ignore some resource types (IMO this is slightly overkill).
WDYT?
Thanks
-Vincent
Hi.
Since I have implemented a REST api for the creation of subwiki using the
new wiki API [1], we can remove wiki-manager from platform [2].
But there is a problem: the new implementation has the exact same interface
and the same path than the old one, so we can not have both the new api and
xwiki-platform-wiki-manager in the classpath anymore.
A solution is to release a new version of xwiki-platform-wiki-manager
without its own REST api.
I see 2 ways to acheive this:
1/ remove the REST api of wiki-manager and remove wiki-manager in 6.0
or
2/ remove wiki-manager in 5.4 and release a new wiki-manager without the
REST api in contrib.
What do you prefer?
Thanks
Louis-Marie
[1] : http://jira.xwiki.org/browse/XWIKI-9670
[2] : http://jira.xwiki.org/browse/XWIKI-9671
Hello,
I am having some issues with a new custom action that I did to solve a
platform issue.
My work was done a new branch created from the master branch of xwiki on
github. I added the new Action class and the form bean to the 'web' module
in the xwiki-platform-oldcore @com.xpn.xwiki.web and I mapped the new
action in struts-config.xml.
I've build the oldcore, followed by the build on the legacy-oldcore,
deployed the legacy-oldcore artifact to my local 5.4-SNAPSHOT instance and
deployed the struts-config.xml with the new modifications to the
WEB-INF/lib.
On accessing my action from the wiki, I get the following:
You are not allowed to view this document or perform this action.
Is there a mapping of the non-default actions and the rights that one must
have in order to run them?
Hi,
I just finished working on XWiki/WebSocket integration which allows
components which implement XWikiWebSocketHandler and they will be called
when a user creates a WebSocket connection to the wiki.
Now I'd like some permission and guidance on getting this published as an
extension, unfortunately I was a little bit too modular so I can't just
upload a .jar and I will have to publish this in maven.xwiki.org
What do people think about transferring this to xwiki-contrib and can anyone
give me some advice about publishing an extension through maven?
For reference, this is the code:
https://github.com/cjdelisle/xwiki-contrib-websocket
Thanks,
Caleb
Hi devs,
FYI I’m creating a new repository on xwiki-contrib’s github to host a demo project I’ll present in my FOSDEM talk about XWiki Rendering.
It show the following:
- exposing XWiki Rendering through a REST resource
- realtime rendering of what you type in your browser using AngularJS
Thanks
-Vincent
Hi guys,
A long time ago I sent a vote for naming configuration property
http://markmail.org/thread/xzz2gqmexkgargbz
And this is what has been mostly used in xwiki.properties…
However some developers have not followed the existing rules. For example:
# solr.embedded.home=/var/local/xwiki/solr
# solr.remote.url=http://localhost:8983/solr
# solr.indexer.batch.size=50
# solr.indexer.batch.maxLength=10000
# solr.indexer.queue.capacity=100000
This is a pity since it’s hard to change a property.
I have now taken the time to document it in our dev practices at
http://dev.xwiki.org/xwiki/bin/view/Community/DevelopmentPractices#HConfigu…
If some dev has an issue with this please raise it here.
If not, please make sure to follow it from now on.
Thanks
-Vincent
Hello developers,
I have made some tests today the 5.2.3-SNAPSHOT version, and I found out
some issues which I don't have on a 5.2.2 install.
On a 5.2.2 there is thew following behavior
- create test subwiki as "Open" and Admin as creator.
* No DW kick in, everything looks ok on the subwiki
5.2.3-SNAPSHOT
- create test subwiki as "Open" and Admin as creator.
* DW kicks in and asks me if this is an upgrade or not. It does not ask for
version.
* "Are you performing an upgrade? There are currently 291 documents in the
database which indicates this is not a new install. "
* Select: "No, this is a new install"
* Merge conflicts on pages: XWiki.XWikiAdminGroup, XWiki.XWikiAllGroup,
XWiki.XWikiPreferences, XWiki.DefaultSkin, XWiki.SearchSuggestConfig,
ColorThemes.WebPreferences, XWiki.WebPreferences
* Even that I created the subwiki as Admin, after finishing with the DW, I
have the Join button in the Wiki Information panel.
* I have an Admin user which is the member of the subwiki, but it seems to
be a local Admin. I created the wiki as the global Admin.
* Logging off and Logging back in on the subwiki with Admin, I am still
logged as the Global Admin, and still not listed as a member of the subwiki.
* On the homepage of the subwiki, I have the following text: "You are a
member of this wiki.
$services.localization.render('platform.workspace.currentUserCanLeave',
$leaveUrl)"
Just wanted to point these issues out before we release 5.2.3.
Regards,
Sorin B.
Hi devs,
We’re getting close to the end of the 5.x cycle with 5.4 and we need to find a new theme for 6.x.
At XWiki SAS we’ve had an internal meeting to brainstorm about what that theme could be and we’ve come up with the following idea:
Theme motto: “Slick and Slim”
Explanations:
* Performance improvements across the board: page load time, scalability, activity stream rewrite, memory usage rationalization
* Introduce the flavor mechanism (as already discussed here) with the idea of removing the maximum of extensions from the base and be able to build a minimal, lightweight wiki + create a few flavors (as already discussed here too).
* Slickiness achieved with things like new skin (see the proposal from Caty) + syntax highlighting + autocompletion + easier rights UI + etc…
In short we’ve realized that XWiki has grown along the years and it’s becoming a bit heavyweight in various aspects.
So the idea would be to focus on performances + ease of use to slim it down and ensure it’s kicking fast!
Of course, as usual, I’m sure there’ll be other things being worked on, but the idea would be to try our maximum to work within this theme.
WDYT?
Thanks
-Vincent
The XWiki development team is proud to announce the availability of
XWiki 5.4 Milestone 1.
This is an improvement and stability release for things started during
the 5.x cycle.
You can download it here:
http://www.xwiki.org/xwiki/bin/view/Main/Download (please allow a few
hours for the binaries to propagate to the download servers if the
download doesn't work yet)
Make sure to review the release notes:
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki54M1
Thanks
-The XWiki dev team
Hi devs,
Guillaume Delhumeau has been voted as a committer by the other committers and he’s accepted the role! :)
http://dev.xwiki.org/xwiki/bin/view/Community/Committership
Guillaume had been contributing daily to the XWiki project since last July (AFAIR), contributing recently to the Workspaces integration in XE.
Welcome aboard!
Thanks
-Vincent
Hi xwikiers,
The committers discussed and voted to include Clemens Robbenhaar in
the team which he agreed so a warm welcome to him !
He has been very active since he started working on XWiki, he already
spend a lot of time answering questions on the mailing list and on IRC
(more than me I think).
On the technical aspect everything I saw from him was good and very
clean and he is clearly no afraid to look at advanced stuff (he spent
a long time last month trying to help Kaisen and Denis on migration
stuff which I'm
sure was not that critically related to his own work).
Note that he is working on XWiki for EsPresto AG (don't forget to add
it to http://main.xwiki.org/xwiki/bin/view/Main/Support).
I'm sure he will be great addition to the team and it's always a nice bonus
to see non XWiki SAS members so active ;)
Welcome !
--
Thomas Mortagne
Hi devs,
In a recent pull request
(https://github.com/xwiki/xwiki-platform/pull/254), I have "fixed" a
bug reported by the accessibility validator by hiding a
link if javascript is not enabled on the browser. It didn't fix the fact
that the feature is unavailable without javascript, but at least the link
was not there.
I did it because I have the feeling that some committers think we don't
need support the navigation without javascript in 2014.
Now, it seems that we do not all agree about this.
That is why I think we should talk about this to decide what rule we should
put in place for the next years.
Thanks, in advance, for your opinions.
Louis-Marie
Due to performance reasons I had to improve Groovy script to
print results directly to the response object:
{{groovy}}
response.setContentType('application/xml');
response.setCharacterEncoding("UTF-8");
def out=response.getWriter();
try {
...
out.println('<?xml version="1.0" encoding="UTF-8"?>');
out.println('<certificates>');
...
But now problem is that after that I got additional XWiki HTML even
using ?outputSyntax=plain parameter.
I suspect, I need to end/close response somehow programmatically.
Any hints?
Thanks in advance
Hi devs,
Today is release day for 5.4M1.
I see that there are quite a few broken functional tests (GuillaumeD, it seems you’ve broken the build 2 weeks ago… could you please fix it ASAP?). Could everyone check the CI to see if there’s anything they can fix?
We also need a RM to start the release. Any volunteer? (If not, I’ll propose someone based on http://dev.xwiki.org/xwiki/bin/view/Community/ReleaseManagerRoster Good candidates: GuillaumeD, Denis, Sergiu and then Thomas, Vincent and last Marius who’s been doing quite a lot during the 5.x cycle).
Please don’t commit anything that may fail the build ATM since we need to release M1. Note that I’m worried since the next release is RC1 and not much has been done compared to the defined roadmap… Please make sure that you can still implement what you had planned to do. Let me know how you wish to proceed.
Thanks
-Vincent
http://ow.ly/sanLQ
Thanks for your hard work, for this nice product and even better community!
Warm regards,
Ricardo
--
Ricardo Rodríguez
Research Management and Promotion Technician
Technical Secretariat
Health Research Institute of Santiago de Compostela (IDIS)
http://www.idisantiago.es
Nota: A información contida nesta mensaxe e os seus posibles documentos adxuntos é privada e confidencial e está dirixida únicamente ó seu destinatario/a. Se vostede non é o/a destinatario/a orixinal desta mensaxe, por favor elimínea. A distribución ou copia desta mensaxe non está autorizada.
Nota: La información contenida en este mensaje y sus posibles documentos adjuntos es privada y confidencial y está dirigida únicamente a su destinatario/a. Si usted no es el/la destinatario/a original de este mensaje, por favor elimínelo. La distribución o copia de este mensaje no está autorizada.
See more languages: http://www.sergas.es/aviso_confidencialidad.htm
Hi guys,
I’ve rebuilt XE from sources and I’ve found that the DW is broken. I removed the data/ dir to get the DW from a HSQLDB/zip distribution and I’ve found 2 issues:
1) Tons of the following warnings:
2013-12-20 22:22:54,293 [http://localhost:8080/xwiki/bin/distribution/XWiki/Distribution] WARN o.x.v.i.DefaultVelocityEngine - Cannot retrieve method getcause from object of class java.lang.reflect.UndeclaredThrowableException due to security restrictions.
2013-12-20 22:22:54,294 [http://localhost:8080/xwiki/bin/distribution/XWiki/Distribution] WARN o.x.v.i.DefaultVelocityEngine - Cannot retrieve method getCause from object of class java.lang.reflect.UndeclaredThrowableException due to security restrictions.
2
2) The Admin user is not imported anymore.
Any idea?
Thanks
-Vincent
Hi devs,
I’ve added support for H2 locally as I wanted to test something on it. The question is whether we’re ok to add support for it in our source (creating subwikis, deleting subwikis)?
What I propose is:
* I add what I’ve done to the sources
* We don’t support it officially (ie similar to other DBs such as DB2)
WDYT?
Thanks
-Vincent
Hello XWiki gurus,
we've met an annoying bug in our xwiki 3.5.1: creating nested lists (numerated or bulleted) breaks the first sub-item because a (% %) appears in front of the list marker. (http://jira.xwiki.org/browse/CURRIKI-6409)
This is not there in xwiki.org today so I suppose it got fixed.
But crawling Jira did not illuminate me on when this got fixed.
Can someone give me a hint about it?
thanks in advance
paul
Hi everyone,
I’d like to wish you some very good Christmas holidays and a happy new year since I’m going on holidays tonight for 1 week.
Several committers are already on holidays and next week there’ll be very few of us active so it’ll be a quite week :)
We’re charging up our batteries for the new XWiki 6.x development cycle next year!
If you wish to help please fill the quick survey about what you’d like to see in XWiki 6.x:
bit.ly/1c6evZQ
Thanks a lot to all
Merry Christmas
-Vincent Massol