Hi devs,
I've changed 2 components in JIRA:
* I've created a new component named "Dependency Upgrades" for when we upgrade third party deps used by XWiki at runtime (don't use this category for third-party deps used only at development time like Selenium)
* I've renamed "Build, Infrastructure and Tests" to "Development Issues only" to remove the confusion. This is for issues that shouldn't make it in the release notes since they're internal issues only used for our development process and do not affect users running XWiki.
See http://dev.xwiki.org/xwiki/bin/view/Community/DevelopmentPractices#HRule:Do… for details
Let me know if there's any problem for you with this.
Thanks
-Vincent
In my "struggle" to adjust the size of the panels, I need to change the CSS
at multiple locations in order to change the width. I then thought "If the
width of a panel was a variable, and all other CSS where formulas which uses
that variable, I only have to change ONE parameter..."
So I did a quick search and found this site: LESS CSS <http://lesscss.org/>
Maybe this is something that is useful for XWiki?
--
View this message in context: http://xwiki.475771.n2.nabble.com/LESS-CSS-tp7587496.html
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi developers/contributors,
We have quite a lot of applications on http://extensions.xwiki.org
However several haven't been updated for a very long time even though XWiki has made progress.
I can think of 3 areas where help would be appreciated:
* Some apps have wiki pages in XWiki Syntax 1.0 version. Those need to be upgraded to XWiki Syntax 2.1.
* Some apps don't register themselves in the Applications Panel. To change that just need to create a new page with the proper XObject. You can copy the Blog.ApplicationsPanelEntry page to this app's space and edit it.
* Some apps don't automatically register translations and force the user to manually add documentation resource bundle in the Administration. There's now a better way which is to add an object of type XWiki.TranslationDocumentClass
Example of app that would need an update:
http://extensions.xwiki.org/xwiki/bin/view/Extension/Polls+Application
So who's willing to help? :)
Note that the best strategy is to ensure that the application has a git repo on https://github.com/organizations/xwiki-contrib (there should be a Source button on the app page on extensions.xwiki.org too). If not, then let me know by answering this email and I'll create it for you and give you access so that you can make changes there. FYI the full process is documented at http://contrib.xwiki.org and I can help you with that.
Thanks!
-Vincent
Hi devs,
We need to solve http://jira.xwiki.org/browse/XWIKI-9157
I'm proposing to simply move all ScriptService implementations out of the internal package and make that a rule.
These classes are used by introspection and as such as not used as components and thus they should not be in the internal package.
Here's my +1 and I'm proposing to handle the move.
I can't think of anything that would break except some users who would have had an import in a groovy script on some internal Script Service but that's ok IMO.
Thanks
-Vincent
We've succeeded in having a wiki devroom for FOSDEM 2014 (https://fosdem.org/2014/)! :)
This means we have a full track for wikis and we're now organizing a Call for Participation.
I hope to see a lot of proposals from the XWiki community.
If you know other wiki communities please forward them this email so that they can participate. The more communities the better so that we can cross-pollinate.
Thanks
-Vincent Massol
Begin forwarded message:
> From: Quim Gil <qgil(a)wikimedia.org>
> Subject: [wikis-devroom] Call for participation
> Date: October 7, 2013 9:24:39 PM GMT+02:00
> To: wikis-devroom(a)lists.fosdem.org
>
> Wikis devroom - FOSDEM, Brussels, 1 & 2 February 2014
>
> CALL FOR PARTICIPATION
>
> IN SHORT
>
> We accept proposals for wiki related submissions. The formats accepted are 25min sessions or 5min lighting sessions. All proposals must be submitted via https://penta.fosdem.org/submission/
>
> Deadline: 30 November 2013
>
> Questions? Feedback? Willing to help?
> https://lists.fosdem.org/listinfo/wikis-devroom
>
>
> BACKGROUND
>
> Wikis are essential tools for online collaboration, open knowledge and free software. They are everywhere: from the mainstream Wikipedia to a myriad of public, academic and corporate knowledge bases and personal sites. And most of them are open source software.
>
> Wikis became popular thanks to the edit button allowing users to create and modify text-based web pages easily. Over the years wikis have become more powerful, handling more content types, allowing better look & feel, championing localization and integrating (sometimes) with other tools. The development continues, with hundreds of professional and volunteer contributors specializing in this area.
>
> There are also challenges: the competition from (mainly proprietary and corporate) social media and online office tools, keeping up with UX expectations from users, editors and sysadmins, compatibility across different wiki engines and other publishing tools, collaboration between wiki projects...
>
>
> SCOPE
>
> Wikis devroom is a place to showcase and discuss
>
> * new features, especially exploring areas beyond plain text editing
>
> * compatibility and integration with other tools and services
>
> * lessons learned from deployments, surveys, research...
>
> * cross-project collaboration
>
> We want to focus on sessions for a technical audience including savvy editors. Basic introductions for end users and long tutorials are out of scope.
>
>
> FORMAT
>
> One day, one room. Most of the schedule will be filled with sessions of about 25 minutes that have gone through a call for participation.
>
> We will have a WikiWiki Hour of lightning presentations (5 minutes each).
>
> We will organize a panel session with representation of key wiki projects - the specific topic to be decided as we confirm the participants.
>
>
> ORGANIZATION
>
> Quim Gil (MediaWiki), Vincent Massol (XWiki) and Jean-Marc Libs (Tiki).
> _______________________________________________
> wikis-devroom mailing list
> wikis-devroom(a)lists.fosdem.org
> https://lists.fosdem.org/listinfo/wikis-devroom
Hi devs,
I'd like to add an archetype module in xwiki-enterprise so that users can easily extend XE to create their own distributions.
It'll generate a multimodule project with *-web, *-ui, *-data and *-distribution modules (and possibly installers in a second version).
I remember some users asking for this (e.g. Fabio) and I have the need myself now.
WDYT?
Thanks
-Vincent
Since Enterprise embeds Workspaces by default since 5.2-m2, I think it does
not make any sense to release XWiki Manager (XEM) anymore.
The build is currently broken (because of the XAR organization changes).
So I propose to remove XWiki Manager:
- stop releasing it
- move the github repo to xwiki-contrib/retired
- update manager.xwiki.org to explain the changes in XWiki 5.2.
- move the manager jira to the retired category
- remove the build in ci.xwiki.org
Here is my non-binding +1.
LM
The XWiki development team is proud to announce the availability of XWiki 5.2.
This release comes with multiwiki support enabled by default: users
are able to create new wikis without the need to install additional
extensions. This is possible because the Workspace Application has
been integrated in XWiki Enterprise. We stopped the support for XWiki
Enterprise Manager as a consequence. Apart from this, the new release
brings a Solr-based live search (to replace the one based on Lucene)
and the ability to track active XWiki installs. The Distribution
Wizard has a new step to upgrade all wikis. Developers will be
interested by the new Wiki Stream framework which can already be used
to export large wikis in XAR format. A lot of bug fixes (135) and many
improvements (50) complete this release and make it 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/ReleaseNotesXWiki52
Thanks
-The XWiki dev team
Hello, i tried to implement the component example
http://extensions.xwiki.org/xwiki/bin/view/Extension/WikiComponent+Module
which is also available from
https://github.com/jvdrean/xwiki-proverb-example
When i put the compiled jar at WEB-INF/lib i get after starting the server
org.xwiki.query.QueryException: Exception while execute query. Query
statement = [ select doc.space , doc.name from XWikiDocument as doc ,
BaseObject as proverb
where ( proverb.proverb <> '' ) and doc.fullName=proverb.name and
proverb.className='XWiki.Proverb' ]
...
"Caused by: com.xpn.xwiki.XWikiException: Error number 0 in 3: Exception
while hibernate execute
Wrapped Exception: could not resolve property: proverb of:
com.xpn.xwiki.objects.BaseObject [ select doc.space , doc.name from
com.xpn.xwiki.doc.XWikiDocument a
s doc , com.xpn.xwiki.objects.BaseObject as proverb where ( proverb.proverb
<> '' ) and doc.fullName=proverb.name and proverb.className='XWiki.Proverb'
]
I use XWIKI v5.1 with embedded HsqlDB on Windows7. I dont get whats wrong
and really appreciate some hints.
My goal is to all new classes to a document or new properties to a page, but
even get this example. Has anyone an idea what i did wrong?
Regards,
Matthias
--
View this message in context: http://xwiki.475771.n2.nabble.com/Componente-Example-Proverb-Not-working-tp…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hello fellow developers,
what is the best practice to decide on a skin in the session and not carry it along with the URLs?
We are building a mobile UI and it should have more limited functionalities so that the same pages should eb visited by the same users with different skins depending if the device is a mobile or not.
thanks for hints.
Paul
Hi devs,
For the past weeks I've been working on a skin based on Bootstrap[1]. You
can read more about it and test the new Junco Skin at
http://extensions.xwiki.org/xwiki/bin/view/Extension/Junco+Skin
This proposal is about using the Junco Skin (Blueberry
Theme<http://extensions.xwiki.org/xwiki/bin/view/Extension/Junco+Skin#HTheme:Blue…>)
for xwiki.org.
I prepared some responsive screenshots for the xwiki.org Homepage and an
Extension page.
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/XWikiOrgJuncoHomep…
This is my +1
Please report any issues on https://github.com/evalica/bootswatch/issues
__Advantages__
- a change is always welcomed, shows the users there is activity on the
website;
- the skin is responsive;
- by using Bootstrap we have the whole framework's power to use (grids,
components, etc.);
- we have the chance to test a bit the skin in production and see the
possible bugs, in order to later integrate;
- IMO the skin looks nice :)
__Disadvantages__
- the only disadvantage is that there will be bugs and they will take some
time to be detected and fixed;
__Platform integration problems__
1. currently the new skin uses the HTML5 doctype. This is needed if we were
to use some Bootstrap JS components (carousel, menus, etc.) - which we
currently don't on xwiki.org, so I could use the old doctype (but lose some
of the testing purpose). Because of the HTML5 doctype, the HTML validation
fails. See http://jira.xwiki.org/browse/XWIKI-7552
2. Junco Skin currently doesn't have support for changing the ColorThemes
on the fly. I would need the help of a developer to fix this problem. Is
not so much a problem for xwiki.org (I could fix them by duplicating some
code in the xwiki.org skin), but it is a problem for the integration.
3. Being build on Bootstrap, it needs LESS to compile the files into CSS.
Again I would need a developer to see how we could integrate the building
of the themes in platform. Right now this is done locally, partially manual
by using Grunt.
Tell me what you think and take some time to test the skin,
Caty
[1] http://getbootstrap.com/
Hi devs !
In 5.2, we have introduced Workspace Application in XE. Now, we should go
further and merge Wiki Application with Workspaces.
= New idea =
* Add a "hidden" field to the Wiki. For example, I would like to be able to
create wiki:
** which can not be seen by others
** which does not appear in searches
** e.g: workspacetemplate, or on a farm if I don't want people to know that
I host a company AND its competitor
= Options =
* In your wiki, do you want to have the "Home" menu?
* In your wiki, do you want to create your own users?
= XARs and template =
* The home menu is enabled only if the user want it (trivial)
* The registration button should redirect to the home wiki depending on the
configuration (trivial)
* Disable XWiki.AdminRegistrationSheet, XWiki.AdminUsersSheet from the
Administration (depending on the configuration)
* Create a new UI, partially based on the current WorkspaceManager and
WikiManager spaces.
= API =
* Create a new API: xwiki-platform-wiki.
* The old modules (xwiki-platform-wiki-manager and
xwiki-platform-workspace) go into legacy, and we mark them as deprecated.
* The new API will use the new modules of Vincent:
https://github.com/xwiki/xwiki-platform/compare/feature-resource-and-wiki-m…
= Proposal for the API =
* xwiki-platform-wiki
** xwiki-platform-wiki-descriptor
*** xwiki-platform-wiki-descriptor-api
**** WikiDescriptor.java
***** ID
***** Alias
***** Hidden
***** Description?
***** Ability to add custom data (where all will be stored)
**** WikiDescriptorManager.java
***** getAll()
***** set()
***** remove()
***** getByWikiAlias()
***** getByWikiId()
** xwiki-platform-wiki-manager (but this name conflicts with the previous
module that we put into legacy...)
*** WikiManager.java
**** createWiki() (create an empty wiki)
**** deleteWiki()
**** copyWiki()
** xwiki-platform-wiki-template
*** WikiTemplateManager.java
**** setWikiAsTemplate()
**** unsetWikiAsTemplate()
**** getWikiTemplates()
**** isWikiTemplate()
** xwiki-platfrom-wiki-user (handle or not the local users)
*** WikiUsersManager.java
**** canWikiHasLocalUsers()
**** setCanWikiHasLocalUsers()
**** getWikiOwner()
**** setWikiOwner()
**** getMembershipType() (join/invite only/ask to join)
**** setMembershipType()
**** getWikiUsers() (list of the local users + those who are
'members' of the wiki)
** xwiki-platform-wiki-script (for script services)
*** Wiki.java (only an helper)
**** getDescriptor()
**** getId()
**** getAlias()
**** addAlias()
**** removeAlias()
**** getReference()
**** IsTemplate()
**** setIsTemplate()
**** getOwner()
**** setOwner()
**** canHasLocalUsers()
**** setCanHasLocalUsers()
**** getMembershipType()
**** setMembershipType()
**** getUsers()
**** isHidden()
**** setHidden()
**** getDescription()
**** setDescription()
*** WikiManagerScript.java ("$services.wikimanager" but the name
conflicts with the previous module...)
**** getAllWikis()
**** getHomeWiki()
**** getWikiByAlias()
**** getWikiById()
**** getWikiTemplates()
**** createWiki()
**** deleteWiki()
**** copyWiki()
**** isWikiExists()
**** isWikiNameAvailable()
**** joinWiki()?
**** askToJoinWiki()?
** xwiki-platform-wiki-ui (pages for both the home AND the (sub)wikis)
*** ...
+ write tests
+ need a migration path
+ in the future:
* Create a new wiki from a flavor:
** instead of creating a wiki from a template, you give an extension ID
If you like this proposal, I will try to implement it as close it is
possible, but I may change some elements to minimize dependencies. I will
tell you.
WDYT?
Thanks,
Louis-Marie
Hi devs,
As you may have seen I've started working again on xwiki-platform-url module (http://jira.xwiki.org/browse/XWIKI-3951) and I now need to add wiki alias support for it. Right now wiki alias support is in oldcore and the url module must not depend on oldcore so I need to extract wiki alias support to a new module. I'm proposing to create a xwiki-platform-wiki module which should contain in the future all modules related to multi wiki handling for stuff not in the model (stuff in the model will go in xwiki-platform-model).
Right now I'm proposing to have:
xwiki-platform-wiki
|_ xwiki-platform-wiki-descriptor
where xwiki-platform-wiki-descriptor will implement description of wikis as xobjects in wiki pages (XWikiServerClass), i.e. what is currently in oldcore's XWiki#findServer.
In the future the idea will be to rewrite xwiki-platform-wiki-manager and to move it to xwiki-platform-wiki/xwiki-platform-wiki-manager for example (or with another name).
WDYT?
Barring negative feedback I'll try to start working on this in the coming week.
Thanks
-Vincent
Hello,
I'm trying to save a document from inside a job [1] execution, as follows
roughly:
xwiki.getXWiki(context).saveDocument(doc, comment, context);
Nothing really special ... It used to work (out of a job), but now it
throws NPE:
<trace>com.xpn.xwiki.XWiki.stripSegmentFromPath(XWiki.java:4725)</trace>
<trace>com.xpn.xwiki.XWiki.getRequestWikiName(XWiki.java:566)</trace>
<trace>com.xpn.xwiki.XWiki.getXWiki(XWiki.java:492)</trace>
<trace>org.xwiki.contrib.mailarchive.internal.persistence.XWikiPersistence.saveAsUser(XWikiPersistence.java:678)</trace>
Checking source code, it happens there (sorry, I roughly decompiled it):
/* 560 */ if ("1".equals(Param("xwiki.virtual.usepath", "1"))) {
/* 561 */ String uri = request.getRequestURI();
/* 562 */ if (LOGGER.isDebugEnabled()) {
/* 563 */ LOGGER.debug("Request uri is: " + uri);
/* */ }
/* */
/* 566 */ uri = stripSegmentFromPath(uri, request.getContextPath());
>From the logs in DEBUG, I see:
"Request uri is: null"
... which is kind of logical I believe, as I'm in a Thread triggered by
another thread, and not directly in an http request.
I'm not sure of what I should do from here ... And if my analysis is
correct, or if something else is wrong. Maybe I should do something with
ExecutionContext ...
Thanks,
BR,
Jeremie
[1] http://extensions.xwiki.org/xwiki/bin/view/Extension/Job+Module
Hi devs,
5.2 final was planned [1] for today but since the RC1 has been delayed
till Friday 27 September (to be announced today) I propose to postpone
the final release for 3 days, till 2nd October so that we can test it.
Let me know if you don't agree.
Thanks,
Marius
The XWiki development team is proud to announce the availability of
XWiki 5.2 Release Candidate 1.
This is mostly a stabilization release leading to XWiki 5.2 final and
it brings a new "Home" top level menu (available when there is more
than one wiki) and a new Distribution Wizard step to upgrade all
wikis. The WikiStream framework has been improved and now can be used
to export large wikis in XAR format. Besides this the new release
includes 49 bug fixes and 16 small improvements.
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/ReleaseNotesXWiki52RC1
Thanks
-The XWiki dev team
Hello,
I'm doing some manual tests of my app, and use EM to install it first, with
an extension repository targeting my m2 local repository, my app being in
version 0.3-SNAPSHOT.
When I fix something, I reinstall a new 0.3-SNAPSHOT of the app in my maven
repository, and update the app in my xwiki instance.
One thing that would be very nice, would be to be able to force the update
of an already installed extension, even if it's in same version (ie,
0.3-SNAPSHOT), or even better to allow this update if a more recent
-SNAPSHOT artifact exists (in the artifact, or in one of its dependencies).
Currently, it's not possible as EM sees it as installed and proposes
nothing else than "uninstall" action. So, to update my app, I have to stop
my server, patch each new .jar file directly in xwiki data dir under
/extension/repository/blablabla, then restart the server. Uninstalling
before does not help as the artifacts are kept in this location anyway (and
not rechecked as long as expected version is found). Also, I don't want to
uninstall, as usually I edit UI parts directly in xwiki, so I'd eventually
prefer a merge as managed by EM.
That feature would save my day as developer/tester :)
WDYT ?
(maybe it's my process that is poor)
BR,
Jeremie
hey developers,
I am trying this feature in my application.
The feature is like I am coming to Xwiki's page from a different Java Application, and now when I click on the various alerts(units) in my application, I want an informative page on that alert/unit in Xwiki.
So, all it has to do is check whether a page with the same name as alert already exist or not.
If it exists, then directly go to the page.( which I am successful in doing)
And if it doesn't exist then take the required parameters from my java application and fill it in my xwiki page( which is also I am successful in doing)
Now when I get those variables in the page, I want to store them in the object. So, they could be viewed later on.
Thank you in advance.
Hello,
Seems I have some new issue with the xwiki-platform-tool-packager-plugin ...
I migrated to XWiki 5.1 (and then 5.2-milestone-2) and in both cases I get
the following when building:
[INFO] Copying HSQLDB JDBC Driver JAR ...
[INFO] Copying Skins ...
Downloading:
http://nexus.xwiki.org/nexus/content/groups/public/org/xwiki/platform/xwiki…
Downloaded:
http://nexus.xwiki.org/nexus/content/groups/public/org/xwiki/platform/xwiki…
B at 0.0 KB/s
ec)
[INFO] Extracting SmartClient ...
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 1:57.850s
[INFO] Finished at: Fri Sep 27 18:27:54 CEST 2013
[INFO] Final Memory: 33M/247M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.xwiki.platform:xwiki-platform-tool-packager-plugin:5.2-milestone-2:package
(default) on project xwiki-contrib-mailarchive-test-tests: Execution d
efault of goal
org.xwiki.platform:xwiki-platform-tool-packager-plugin:5.2-milestone-2:package
failed: For artifact {com.smartgwt:smartgwt:null:jar}: The version cannot
be empty. ->
[Help 1]
Should I specify this smartgwt artifact in my pom ?
BR,
Jeremie
Hey developers,
I want to redirect from A page to B, in editing mode and also some variables in url. But it gives me an error if I try to redirect it to a page in editing mode from the WebHome page of my Xwiki. Please suggest.
Thank you
Prachi Maheshwari
Hi everyone,
Tomorrow is BFD 37.
We're currently at 3158 bugs created over 1400 days vs 3167 closed, so we're good for 1400 days:
http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=10352
I'm proposing to increase to 1500 days which gives us:
* 3485 created vs 3394 closed, i.e. 91 bugs to catch up with
This seems reasonable to reach before the end of the 5.x cycle (we could probably go even a bit higher later on once we reach it).
WDYT?
Here's the BFD#37 dashboard to follow the progress during the day:
http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=11697
Let's crush bugs!
Thanks
-Vincent
Issue :
* Since XWiki.Admin is packaged in xwiki-platform-administration-ui, it
comes with xwiki-enterprise-ui-wiki (which is the subwiki default UI).
* XWiki.Admin is a member of XWiki.XWikiAdminGroup and XWiki.XWikiAllGroup,
which are also bundled in xwiki-platform-administration-ui.
* WorkspaceManager.Install removes XWiki.Admin from workspacetemplate, in
order to not have local admin in new workspaces.
* When we upgrade subwikis, DW does not install XWiki.Admin (DW is aware
that the user has been intentionally removed), but the merge of
XWiki.XWikIAllGroup does no work well : it add XWiki.Admin to the group.
* That leads us to: http://jira.xwiki.org/browse/XWIKI-9501 (The local
admin does not exist, but she is a member of XWiki.XWikiAllGroup).
+ I think the WorkspaceManager.Install trick is not clean.
My proposal is to *move XWiki.Admin to XE mainwiki*.
But it breaks the *functional tests* that needs to *log-in as *an admin. It
can be solved by using the *superadmin*!
+ When DW does the first install, it should use superadmin too, so all
default macros come with the rights of superadmin.
Here is my +1.
Thanks,
Louis-Marie
Hi,
I'm making an application that make an AJAX request frequently from page to
page in xwiki.
About 1 per 10s
The request look like this:
$.ajax({
type: "GET",
crossDomain: true,
url: "/xwiki/bin/get/Lib/LibPage?outputSyntax=plain",
dataType: 'text',
data: data2send,
success: function(result) {...},
error: function(xhr, status, error) {
console.log(error)
console.log(status)
console.log(xhr)
}
});
And respone is simple as a text or something like a JSON Map, List.
I took a look at jconsole and here it is
<http://xwiki.475771.n2.nabble.com/file/n7587262/9-26-2013_1-51-09_PM.jpg>
Please help! I don't understand how xwiki works on this.
Thank in advanced.
--
View this message in context: http://xwiki.475771.n2.nabble.com/Frrequently-AJAX-request-caused-PernGen-E…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hey Everyone,
I have been using Xwiki since a month now and I am pretty familiar with it. But I want to manually code now in any of the languages(groovy||velocity||java) to create a new entry in the application with the same form outlet and some default values. Can someone suggest how to go about this??
Thanks.