Re: [xwiki-users] Error saving Notifications Preferences

2017-05-18 Thread Guillaume Delhumeau
[[Note: The XWiki project is switching away from this mailing list and moving 
to a forum: https://discourse.xwiki.org. This list will be made readonly in a 
few days. Please post on the forum from now on. Thanks.]]

-
The nginx proxy should not cause any harm, otherwise nothing should be
working.

Your user is called "admin" with every character in lower case?

2017-05-16 12:38 GMT+02:00 Marcio Barreto <marcio.barr...@first-global.com>:

> [[Note: The XWiki project is switching away from this mailing list and
> moving to a forum: https://discourse.xwiki.org. This list will be made
> readonly in a few days. Please post on the forum from now on. Thanks.]]
>
> -
> I realized that I didn't mention that I'm using nginx in front of tomcat
> (nginx port 80 -> tc port 8080).
> Do you think it could be related to this issue?
>
> Is there any logs I could check for adicional errors?
>
> thanks
>
>
>
> --
> View this message in context: http://xwiki.475771.n2.nabble.
> com/Error-saving-Notifications-Preferences-tp7603801p7603903.html
> Sent from the XWiki- Users mailing list archive at Nabble.com.
>



-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project


Re: [xwiki-users] [xwiki-devs] [ANN] New XWiki forum: https://forum.xwiki.org

2017-05-17 Thread Guillaume Delhumeau
[[Note: The XWiki project is switching away from this mailing list and moving 
to a forum: https://discourse.xwiki.org. This list will be made readonly in a 
few days. Please post on the forum from now on. Thanks.]]

-
Just my feedback: I like it :)

2017-05-16 19:59 GMT+02:00 Vincent Massol <vinc...@massol.net>:

> Before anyone mentions it, it’s down ATM; I tried to install a discourse
> plugin and apparently I’m missing some steps since I couldn’t restart it.
> I’m waiting for an infra admin to help me out… :) Sorry about that!
>
> -Vincent
>
> > On 15 May 2017, at 17:32, Vincent Massol <vinc...@massol.net> wrote:
> >
> > And we now have this alias too which is more neutral and probably better
> to use:
> >
> > https://forum.xwiki.org
> >
> > Thanks
> > -Vincent
> >
> >> On 15 May 2017, at 17:09, Vincent Massol <vinc...@massol.net> wrote:
> >>
> >> Hi XWiki users,
> >>
> >> In order to make it simpler and more modern for users to participate to
> XWiki discussions, we’ve set up a new forum based on Discourse:
> >>
> >> https://discourse.xwiki.org
> >>
> >> Please start using it instead of the XWiki User Mailing list. This
> mailing list will become read only in a few days so please start moving to
> the forum ASAP.
> >>
> >> Note that you can subscribe to receive all forum posts as email
> notifications if you wish (it’s configurable in your user profile). Also
> note that for the moment it’s not possible to reply to the mails (we’re
> still trying to configure this).
> >>
> >> We hope that you’ll appreciate this move :)
> >>
> >> Thanks
> >> -Vincent
> >>
> >> PS: For the moment the XWiki Devs mailing list remains. It’s possible
> that it could be moved to a forum too in the future but nothing is decided
> and we’re migrating the users list first.
> >>
> >
>
>


-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project


Re: [xwiki-users] Error saving Notifications Preferences

2017-05-16 Thread Guillaume Delhumeau
[[Note: The XWiki project is switching away from this mailing list and moving 
to a forum: https://discourse.xwiki.org. This list will be made readonly in a 
few days. Please post on the forum from now on. Thanks.]]

-
Yes it is the information I needed. The request sent is correct. I don't
understand why you get this 500 error.

2017-05-16 10:29 GMT+02:00 Marcio Barreto <marcio.barr...@first-global.com>:

> We're switching away from this mailing list and moving to a forum:
> https://discourse.xwiki.org. This list will be made readonly in a few
> days. Please post on the forum from now on. Thanks.
> Hi,
>
> Thnak you for your time, is this info you need?
>
>
> Request
> URL:http://wiki.XXX.com/xwiki/rest/wikis/xwiki/spaces/XWiki/
> pages/admin/objects?media=json
> Request Method:POST
> Status Code:500
> Remote Address:XXX.XXX.XX.XXX:80
> Referrer Policy:no-referrer-when-downgrade
>
> Query String Parameters
> media:json
>
> Form Data
> className:XWiki.Notifications.Code.NotificationPreferenceClass
> property#eventType:create
> property#notificationEnabled:1
>
> So I'm getting a 500 error:
> 
> jquery.js:9203 POST
> http://wiki.XXX.com/xwiki/rest/wikis/xwiki/spaces/XWiki/
> pages/admin/objects?media=json
> 500 ()
> send@   jquery.js:9203
> ajax@   jquery.js:8684
> n.(anonymous function)  @   jquery.js:8835
> (anonymous) @   XWikiUserNotificationsSheet?
> language=pt_PT=1.1:1
> dispatch@   jquery.js:4737
> r.handle@   jquery.js:4549
> trigger @   jquery.js:7819
> b   @   eventsBridge.js:1
> (anonymous) @   jquery.js:7903
> each@   jquery.js:365
> each@   jquery.js:137
> trigger @   jquery.js:7902
> $element.on.change.bootstrapSwitch  @   bootstrap-switch.min.js:22
> dispatch@   jquery.js:4737
> r.handle@   jquery.js:4549
> trigger @   jquery.js:7819
> b   @   eventsBridge.js:1
> (anonymous) @   jquery.js:7903
> each@   jquery.js:365
> each@   jquery.js:137
> trigger @   jquery.js:7902
> t.state @   bootstrap-switch.min.js:22
> $label.on.mouseup.bootstrapSwitch touchend.bootstrapSwitch  @
> bootstrap-switch.min.js:22
> dispatch@   jquery.js:4737
> r.handle@   jquery.js:4549
>
>
> thanks,
> Marcio
>
>
>
>
> --
> View this message in context: http://xwiki.475771.n2.nabble.
> com/Error-saving-Notifications-Preferences-tp7603801p7603894.html
> Sent from the XWiki- Users mailing list archive at Nabble.com.
>



-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project


Re: [xwiki-users] Error saving Notifications Preferences

2017-05-16 Thread Guillaume Delhumeau
Hello.

Could you try again with the console of your web browser open? What
interests me is the "network" panel. When you toggle a button, you should
see an XHR request to /xwiki/rest/{something}. You could look at this
request, and its parameters?

Thanks,

Guillaume

2017-05-09 12:24 GMT+02:00 Marcio Barreto <marcio.barr...@first-global.com>:

> Hi,
>
> I have just installed xwiki 9.3 and I am having problems with the
> notification settings. I've used tomcat9, mysql14 on centos 6.9.
>
> On the user profile, Notifications Preferences option I cant change the
> notification settings. Every time i toggle the option I get an error:
> "Failed to save your settings"
>
> and get this error on the server:
> mai 09, 2017 11:19:02 AM org.restlet.engine.application.StatusFilter
> doHandle
> WARNING: Exception or error caught in status service
> java.lang.IllegalStateException: The Web form cannot be parsed as no fresh
> content is available. If this entity has been already read once, caching of
> the entity is required
> at org.restlet.engine.util.FormUtils.parse(FormUtils.java:272)
> at org.restlet.data.Form.(Form.java:88)
> at
> org.xwiki.rest.internal.representations.objects.
> FormUrlEncodedObjectReader.readFrom(FormUrlEncodedObjectReader.java:82)
> at
> org.xwiki.rest.internal.representations.objects.
> FormUrlEncodedObjectReader.readFrom(FormUrlEncodedObjectReader.java:52)
> at
> org.restlet.ext.jaxrs.internal.wrappers.provider.
> SingletonProvider.readFrom(SingletonProvider.java:304)
> at
> org.restlet.ext.jaxrs.internal.wrappers.params.EntityGetter.getValue(
> EntityGetter.java:109)
> at
> org.restlet.ext.jaxrs.internal.wrappers.params.ParameterList.get(
> ParameterList.java:1090)
> at
> org.restlet.ext.jaxrs.internal.wrappers.AbstractMethodWrapper.
> internalInvoke(AbstractMethodWrapper.java:169)
> at
> org.restlet.ext.jaxrs.internal.wrappers.ResourceMethod.invoke(
> ResourceMethod.java:291)
> at
> org.restlet.ext.jaxrs.JaxRsRestlet.invokeMethod(JaxRsRestlet.java:1043)
> at org.restlet.ext.jaxrs.JaxRsRestlet.handle(
> JaxRsRestlet.java:792)
> at org.restlet.routing.Filter.doHandle(Filter.java:159)
> at org.restlet.routing.Filter.handle(Filter.java:206)
> at org.restlet.routing.Router.doHandle(Router.java:500)
> at org.restlet.routing.Router.handle(Router.java:740)
> at org.restlet.routing.Filter.doHandle(Filter.java:159)
> at org.restlet.routing.Filter.handle(Filter.java:206)
> at org.restlet.routing.Filter.doHandle(Filter.java:159)
> at org.restlet.routing.Filter.handle(Filter.java:206)
> at org.restlet.routing.Filter.doHandle(Filter.java:159)
> at org.restlet.routing.Filter.handle(Filter.java:206)
> at org.restlet.routing.Filter.doHandle(Filter.java:159)
> at org.restlet.routing.Filter.handle(Filter.java:206)
> at org.restlet.routing.Filter.doHandle(Filter.java:159)
> at
> org.restlet.engine.application.StatusFilter.doHandle(StatusFilter.java:
> 154)
> at org.restlet.routing.Filter.handle(Filter.java:206)
> at org.restlet.routing.Filter.doHandle(Filter.java:159)
> at org.restlet.routing.Filter.handle(Filter.java:206)
> at org.restlet.engine.ChainHelper.handle(ChainHelper.java:114)
> at
> org.restlet.engine.application.ApplicationHelper.
> handle(ApplicationHelper.java:75)
> at org.restlet.Application.handle(Application.java:391)
> at org.restlet.routing.Filter.doHandle(Filter.java:159)
> at org.restlet.routing.Filter.handle(Filter.java:206)
> at org.restlet.routing.Router.doHandle(Router.java:500)
> at org.restlet.routing.Router.handle(Router.java:740)
> at org.restlet.routing.Filter.doHandle(Filter.java:159)
> at org.restlet.routing.Filter.handle(Filter.java:206)
> at org.restlet.routing.Router.doHandle(Router.java:500)
> at org.restlet.routing.Router.handle(Router.java:740)
> at org.restlet.routing.Filter.doHandle(Filter.java:159)
> at org.restlet.routing.Filter.handle(Filter.java:206)
> at org.restlet.engine.ChainHelper.handle(ChainHelper.java:114)
> at org.restlet.Component.handle(Component.java:391)
> at org.restlet.Server.handle(Server.java:491)
> at org.restlet.engine.ServerHelper.handle(ServerHelper.java:74)
> at
> org.restlet.engine.http.HttpServerHelper.handle(HttpServerHelper.java:153)
> at
> org.restlet.ext.servlet.ServerServlet.service(ServerServlet.java:1031)
> at

Re: [xwiki-users] [ANN] XWiki 9.3.1 released

2017-04-26 Thread Guillaume Delhumeau
Thanks for this release.

2017-04-26 15:15 GMT+02:00 Thomas Mortagne <thomas.morta...@xwiki.com>:

> The XWiki development team is proud to announce the availability of XWiki
> 9.3.1.
> This version fix a bug that makes impossible to migrate subwikis and a
> regression related to escaping in requests LIKE values.
>
> 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/Data/XWiki/9.3.1
>
> Thanks for your support
> -The XWiki dev team
>



-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project


[xwiki-users] [ANN] XWiki 9.2 released

2017-03-28 Thread Guillaume Delhumeau
The XWiki development team is proud to announce the availability of XWiki
9.2.

This release introduces the Notification menu to follow wiki activity more
easily. The Administration has been re-organized with a collapsible menu.
The Menu Application becomes responsive with burger menus. For the advanced
users, the CKEditor integration adds support for dedicated Insert Macro
tool bar buttons and the Extension Manager adds support for conflict
resolution configuration when installing an extension. As usual, the
release also brings many bug fixes and other 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/Data/XWiki/9.2

Thanks for your support
-The XWiki dev team


Re: [xwiki-users] [xwiki-devs] [ANN] XWiki 9.1.1 released

2017-03-01 Thread Guillaume Delhumeau
We can be proud to have released it that fast :)

2017-03-01 19:20 GMT+01:00 Vincent Massol <vinc...@massol.net>:

>
> > On 1 Mar 2017, at 18:47, Thomas Mortagne <thomas.morta...@xwiki.com>
> wrote:
> >
> > The XWiki development team is proud to announce the availability of
> XWiki 9.1.1.
>
> Well, we’re not that proud actually :)
>
> Thanks to Thomas for having released quickly a new version that fixes the
> regression introduced in 9.1.
>
> Thanks
> -Vincent
>
> > This version fix a bug that makes the Distribution Wizard always
> automated.
> >
> > 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/Data/XWiki/9.1.1
> >
> > Thanks for your support
> > -The XWiki dev team
>
>


-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project


Re: [xwiki-users] [ANN] XWiki 9.0 Release Candidate 1 released

2017-01-26 Thread Guillaume Delhumeau
And thanks to Thomas Mortagne who performed a big part of the release
process.

2017-01-26 11:11 GMT+01:00 Guillaume Delhumeau <
guillaume.delhum...@xwiki.com>:

> The XWiki development team is proud to announce the availability of XWiki
> 9.0 Release Candidate 1.
> This version opens the new 9.x cycle. It contains all improvements
> introduced in versions 8.4.1 to 8.4.4, and brings admin and developer
> features mostly. Among other things, XWiki deals better with big
> attachments now.
>
> 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/Data/XWiki/9.0RC1/
>
> Thanks for your support
> -The XWiki dev team
>



-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project


[xwiki-users] [ANN] XWiki 9.0 Release Candidate 1 released

2017-01-26 Thread Guillaume Delhumeau
The XWiki development team is proud to announce the availability of XWiki
9.0 Release Candidate 1.
This version opens the new 9.x cycle. It contains all improvements
introduced in versions 8.4.1 to 8.4.4, and brings admin and developer
features mostly. Among other things, XWiki deals better with big
attachments now.

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/Data/XWiki/9.0RC1/

Thanks for your support
-The XWiki dev team


Re: [xwiki-users] Editing font using LESS Code

2017-01-12 Thread Guillaume Delhumeau
Your browser does not always download the CSS of XWiki, since it is almost
everytime the same. It saves performances and bandwidth. However, when you
make a change, the browser does not see it and does not download the
updated CSS. So by clearing your browser's cache, it has not other choice
than downloading the updated CSS file when it tries to display your XWiki
page.

Clear your cache could be done easily with firefox, by doing CTRL+SHIFT+R
to refresh your page.

2017-01-10 4:29 GMT+01:00 hamiazuhk26 <khu.gamba...@gmail.com>:

> Yes, done and its work.Thanks.
>
> What is the relation with this cache? How often this thing happen?
>
>
>
> --
> View this message in context: http://xwiki.475771.n2.nabble.
> com/Editing-font-using-LESS-Code-tp7602322p7602348.html
> Sent from the XWiki- Users mailing list archive at Nabble.com.
>



-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project


Re: [xwiki-users] Editing font using LESS Code

2017-01-09 Thread Guillaume Delhumeau
Hi.

Have you tried to clear your browser's cache before refreshing the page?

Thanks,

2017-01-09 4:20 GMT+01:00 hamiazuhk26 <khu.gamba...@gmail.com>:

> Hi, I have changed the font using LESS-CODE. I want to know maybe this
> LESS-Code is under renovation or what because, I have change the font
> (small
> the font for heading 2), Under this preview, when i select the doc, the
> font
> is changed. But in main xwiki, i mean main page. no changes for this font
> for heading 2.
>
>
> I have try and error so many times, cut and paste again the code but still
> the same(the font is not changed). You can see the picture below:
>
> <http://xwiki.475771.n2.nabble.com/file/n7602322/heading2.png>  As you see
> here, the font for heading 2 which is 1.1 System Developing is changed.
>
> <http://xwiki.475771.n2.nabble.com/file/n7602322/mainPage-heading2_is_not_
> change.png>
> (the font for heading 2 is not change)
>
>
>
> --
> View this message in context: http://xwiki.475771.n2.nabble.
> com/Editing-font-using-LESS-Code-tp7602322.html
> Sent from the XWiki- Users mailing list archive at Nabble.com.
>



-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project


Re: [xwiki-users] [myxwiki] new wiki request

2016-12-01 Thread Guillaume Delhumeau
Hello

I've created your wiki: http://mwoyorlando.myxwiki.org/

Envoy!

2016-11-30 4:29 GMT+01:00 Gomez, Luis (North & Central Florida) <
luis.go...@lls.org>:

> I am looking to use xwiki as a communication tool for my volunteer
> leadership team for a campaign for the Leukemia and Lymphoma Society. I am
> the LLS Man and Woman of the Year Campaign Manager.
>
>
> Owner name: Luis Gomez
>
> Wiki name: mwoyorlando
>
>
>
> Thank you,
>
>
>
> Luis Gomez
>
> Man & Woman of the Year Campaign Manager, Orlando
>
> Leukemia and Lymphoma Society
>
> 407-965-6575
>
> NOTICE: This message, including all attachments transmitted with it, is
> for the use of the addressee only. It may contain proprietary, confidential
> and/or legally privileged information. No confidentiality or privilege is
> waived or lost by any mistransmission. If you are not the intended
> recipient, you must not, directly or indirectly, use, disclose, distribute,
> print or copy any part of this message. If you believe you have received
> this message in error, please delete it and all copies of it from your
> system and notify the sender immediately by reply email. Thank you.
>



-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project


Re: [xwiki-users] New installation - top menu bar missing?

2016-12-01 Thread Guillaume Delhumeau
2016-12-01 16:38 GMT+01:00 Vincent Massol <vinc...@massol.net>:

>
> > On 01 Dec 2016, at 16:35, Patrick M. Hausen <p...@hausen.com> wrote:
> >
> > Hi Guillaume,
> >
> >> Am 01.12.2016 um 15:42 schrieb Guillaume Delhumeau <
> guillaume.delhum...@xwiki.com>:
> >>
> >> Hello Patrick.
> >>
> >> I think you should read
> >> http://platform.xwiki.org/xwiki/bin/view/Features/ContentOrganization/
> that
> >> will explain you everything.
> >
> > Thanks.
> >
> >> Short story: we don't have space anymore but only pages that can have
> >> children.
> >>
> >> Hope you will appreciate.
> >
> > Your help - yes, of course. The demise of spaces - no, sorry.
> > Spaces were a key feature why I picked Xwiki. We need
> > different $SOMETHINGS for different working groups that
> > should not be visible at all to users who are not members of
> > that partciular group, yet easily navigatable for users with
> > the necessary privileges. Very much like Confluence spaces.
> >
> > I'll read the docs and decide if we keep exploring XWiki and
> > which feature (subwiki or nested pages) to use …
>
> You get what you want with XWiki :)
>
> You can have pages under other pages and you can set permissions on pages
> that affect all children too.
>

Exactly. You can see each individual page as a space actually :)


>
> Thanks
> -Vincent
>
>
> >
> > Thanks again
> > Patrick
>
>


-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project


Re: [xwiki-users] New installation - top menu bar missing?

2016-12-01 Thread Guillaume Delhumeau
Hello Patrick.

I think you should read
http://platform.xwiki.org/xwiki/bin/view/Features/ContentOrganization/ that
will explain you everything.

Short story: we don't have space anymore but only pages that can have
children.

Hope you will appreciate.

Guillaume

2016-11-30 13:37 GMT+01:00 Patrick M. Hausen <p...@hausen.com>:

> Hi, all,
>
> > Am 29.11.2016 um 21:36 schrieb Patrick M. Hausen <p...@hausen.com>:
> > [...]
> >
> > http://platform.xwiki.org/xwiki/bin/view/Features/Spaces#HSpacecreation
> >
> > Unfortunately my XWiki doesn't have that menu bar with the "Home | Main
> | WebHome | Add"
> > at all! What am I missing here?
> > Completely dumbfounded - the docs say "click Add -> Space" ...
>
> No one? The menu bar is clearly visible here:
> http://platform.xwiki.org/xwiki/bin/view/Features/Spaces#HSpacecreation
>
> Yet, it is missing in my Wiki which looks like this:
> http://i.imgur.com/ctG5kM3.jpg
>
> Thanks
> Patrick




-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project


[xwiki-users] [ANN] Release of Nested Pages Migrator Application 0.7

2016-11-30 Thread Guillaume Delhumeau
Hello,

A new version of the Nested Pages Migrator Application is available. See
http://extensions.xwiki.org/xwiki/bin/view/Extension/Nested+Pages+Migrator+Application#Hv0.7
You can install or upgrade with the Extension Manager.

This version brings a new tool that help you to check if the migration is
needed.

Thanks,
-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project


[xwiki-users] [ANN] Release of Limits Application 1.2.1.

2016-11-24 Thread Guillaume Delhumeau
Hello

A new version of the Limits Application is available. See
http://extensions.xwiki.org/xwiki/bin/view/Extension/Limits+Application/#Hv1.2.1
You can install with the Extension Manager.

This version fixes an important bug which prevents the user to install the
application via the Extension Manager.

However, I would remind you that using the Extension Manager to install
this particular application is not the recommend way, since any user having
the administration right will be able to uninstall it. And thus remove the
limitations you wanted to enforce.

Have a good day,

-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


[xwiki-users] [ANN] Release of Nested Pages Migrator Application 0.6

2016-11-23 Thread Guillaume Delhumeau
Hello

A new version of the Nested Pages Migrator Application is available. See
http://extensions.xwiki.org/xwiki/bin/view/Extension/Nested+Pages+Migrator+Application#Hv0.6
You can install or upgrade with the Extension Manager.

The application is still in beta but some progress have been made. Anca and
Alex have fixed a couple of bugs and I have improved the UI. Complex
settings are now hidden by default and it's now clear that the plan is
actually a tree that you can expand.

I hope it will help you to perform the migration, if you have not already
done it.

Thanks,

-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Re-organize the Drawer's entries

2016-11-14 Thread Guillaume Delhumeau
OK so now it's a bit more than only re-organizing the drawer's entries.
Your proposition is also about removing some elements, and renaming some of
them. We are more closer to your original issue (
http://jira.xwiki.org/browse/XE-1582).

It's a big change that we usually don't do at the end of a development
cycle.

Concerning its content, and more precisely the renaming of the items, I
would love to read the opinion of committers. For example, I agree it looks
more natural to see "All users" than "User Index" or "All other wikis"
instead of "Wiki Index" in a subwiki, but it breaks the famous consistency
principle we tend to have.

I also like "Settings" instead of "Administration", but we could even go
deeper and say "Settings of the wiki" to not confuse with "User Settings".

You also propose a "Recent Changes" item, which could lead to the Activity
Stream. Should I open a new discussion about this?

For now, I could change the order of the elements, and introduce 2
categories: "items concerning the current wiki", and "items concerning the
main wiki". It's already a breakage from the UI Extension API point of view.

Thanks,

2016-11-03 10:01 GMT+01:00 Guillaume Delhumeau <
guillaume.delhum...@xwiki.com>:

> Yes Miroslav, we have received your message. Thanks you :)
>
> 2016-11-02 23:13 GMT+01:00 Miroslav Galajda <miroslav.gala...@gmail.com>:
>
>> Hi, I've sent an email with preference for P5, last week. Have you
>> received
>> it?
>>
>> P5 seems to me clean and logical to work with.
>>
>> Thanks
>> Mirec
>>
>> On 2 November 2016 at 11:23, Guillaume Delhumeau <
>> guillaume.delhum...@xwiki.com> wrote:
>>
>> > Hello.
>> >
>> > Thanks for your comments. Any other?
>> >
>> > Guillaume
>> >
>> > 2016-10-26 17:03 GMT+02:00 Jan-Paul Kleijn <em...@biggee.nl>:
>> >
>> > > P5 is also my favorite because it draws more attention to the content.
>> > > It's the more grown-up version.
>> > >
>> > >
>> > > Op 26-10-2016 om 10:28 schreef Guillaume Delhumeau:
>> > >
>> > > No opinion?
>> > >>
>> > >> 2016-10-24 18:09 GMT+02:00 Guillaume Delhumeau <
>> > >> guillaume.delhum...@xwiki.com>:
>> > >>
>> > >> Hello dear developers and XWiki users.
>> > >>>
>> > >>> I would you to take a look at the issue
>> http://jira.xwiki.org/browse/
>> > >>> XWIKI-13070.
>> > >>>
>> > >>> The problem is that the current order (that I have implemented
>> based on
>> > >>> my
>> > >>> intuition) seems to not be clear for our users. The main point is
>> that
>> > >>> the
>> > >>> menu mixes up global items (Home wiki, Wiki Index) and local ones
>> > >>> (Administer Wiki, Page Index, Delete wiki, etc...).
>> > >>>
>> > >>> Caty and Oliver have made some proposals that you could find in the
>> > >>> issue.
>> > >>>
>> > >>> They are called P1, P2, P3, P4 and P5.
>> > >>>
>> > >>> I propose you to express your preferences so we can implement it
>> based
>> > on
>> > >>> a consensus.
>> > >>>
>> > >>> Here are mine:
>> > >>>
>> > >>> P1: There is a logical order and separation between item. However,
>> it
>> > >>> seems the more used actions (Wiki Index, Page Index) are less
>> visible
>> > >>> than
>> > >>> some other (Delete Wiki, Create Wiki...)
>> > >>>
>> > >>> P2: The order and the separation are logic. The "delete wiki"
>> action is
>> > >>> still very visible but all other items are good.
>> > >>>
>> > >>> P3: Same than P2. Except that having "Wiki Index" along with "User,
>> > Page
>> > >>> and Application Index" mixes up local and global items.
>> > >>>
>> > >>> P4: Why not, but maybe the 3 first actions should be placed after
>> the
>> > >>> other ones, since they would be less used. Same remark about the
>> mixing
>> > >>> of
>> > >>> local and global items.
>> > >>>
>> > >>> P5: A clear distinction between local a

[xwiki-users] [ANN] XWiki 8.4 released

2016-11-10 Thread Guillaume Delhumeau
The XWiki development team is proud to announce the availability of XWiki
8.4.

This version brings a lot of usability improvements. The WYSIWYG editor (
*CKEditor*) has been upgraded and proposes a better dialog for the creation
of links. It is also possible to configure it from the administration.

Application Within Minutes does not enforce anymore the location where the
application's entries must be created, but proposes to the creator the
places *where* and *from where* these entries should be. We have also get
rid of the Data page where the entries where created before.

The default values of the user preferences are now better exposed to the
users. The order of the applications in the application panel can now be
changed by the administrator. And the users now have the ability to filter
the page types when they create a page.

As usual plenty of less noticeable improvements are proposed, and 45 bugs
have been fixed since XWiki 8.3.
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/Data/XWiki/8.4/

Thanks for your support
-The XWiki dev team
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] hiding breadcrumbs

2016-11-07 Thread Guillaume Delhumeau
Hi Olivier.

Actually, you cannot, except by modifying some template inside your skin.

Guillaume

2016-11-05 19:47 GMT+01:00 oseres <ose...@xwiki.com>:

> Hi, how do I remove breadcrumbs with Flamingo?
> Thanks
>
>
>
> --
> View this message in context: http://xwiki.475771.n2.nabble.
> com/hiding-breadcrumbs-tp5514619p7601764.html
> Sent from the XWiki- Users mailing list archive at Nabble.com.
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>



-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Re-organize the Drawer's entries

2016-11-03 Thread Guillaume Delhumeau
Yes Miroslav, we have received your message. Thanks you :)

2016-11-02 23:13 GMT+01:00 Miroslav Galajda <miroslav.gala...@gmail.com>:

> Hi, I've sent an email with preference for P5, last week. Have you received
> it?
>
> P5 seems to me clean and logical to work with.
>
> Thanks
> Mirec
>
> On 2 November 2016 at 11:23, Guillaume Delhumeau <
> guillaume.delhum...@xwiki.com> wrote:
>
> > Hello.
> >
> > Thanks for your comments. Any other?
> >
> > Guillaume
> >
> > 2016-10-26 17:03 GMT+02:00 Jan-Paul Kleijn <em...@biggee.nl>:
> >
> > > P5 is also my favorite because it draws more attention to the content.
> > > It's the more grown-up version.
> > >
> > >
> > > Op 26-10-2016 om 10:28 schreef Guillaume Delhumeau:
> > >
> > > No opinion?
> > >>
> > >> 2016-10-24 18:09 GMT+02:00 Guillaume Delhumeau <
> > >> guillaume.delhum...@xwiki.com>:
> > >>
> > >> Hello dear developers and XWiki users.
> > >>>
> > >>> I would you to take a look at the issue
> http://jira.xwiki.org/browse/
> > >>> XWIKI-13070.
> > >>>
> > >>> The problem is that the current order (that I have implemented based
> on
> > >>> my
> > >>> intuition) seems to not be clear for our users. The main point is
> that
> > >>> the
> > >>> menu mixes up global items (Home wiki, Wiki Index) and local ones
> > >>> (Administer Wiki, Page Index, Delete wiki, etc...).
> > >>>
> > >>> Caty and Oliver have made some proposals that you could find in the
> > >>> issue.
> > >>>
> > >>> They are called P1, P2, P3, P4 and P5.
> > >>>
> > >>> I propose you to express your preferences so we can implement it
> based
> > on
> > >>> a consensus.
> > >>>
> > >>> Here are mine:
> > >>>
> > >>> P1: There is a logical order and separation between item. However, it
> > >>> seems the more used actions (Wiki Index, Page Index) are less visible
> > >>> than
> > >>> some other (Delete Wiki, Create Wiki...)
> > >>>
> > >>> P2: The order and the separation are logic. The "delete wiki" action
> is
> > >>> still very visible but all other items are good.
> > >>>
> > >>> P3: Same than P2. Except that having "Wiki Index" along with "User,
> > Page
> > >>> and Application Index" mixes up local and global items.
> > >>>
> > >>> P4: Why not, but maybe the 3 first actions should be placed after the
> > >>> other ones, since they would be less used. Same remark about the
> mixing
> > >>> of
> > >>> local and global items.
> > >>>
> > >>> P5: A clear distinction between local and global scope. More used
> items
> > >>> are located first. This is my favorite one.
> > >>>
> > >>>
> > >>> So +1 for P5, +0 for the other options so far.
> > >>>
> > >>> Now, what about you?
> > >>>
> > >>> Thanks,
> > >>> Guillaume
> > >>>
> > >>> PS: I send this message to both devs and users mailing lists,
> because I
> > >>> think users are directly concerned by this topic.
> > >>>
> > >>> --
> > >>> Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
> > >>> Research & Development Engineer at XWiki SAS
> > >>> Committer on the XWiki.org project
> > >>>
> > >>>
> > >>
> > >>
> > > ___
> > > users mailing list
> > > users@xwiki.org
> > > http://lists.xwiki.org/mailman/listinfo/users
> > >
> >
> >
> >
> > --
> > Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
> > Research & Development Engineer at XWiki SAS
> > Committer on the XWiki.org project
> > ___
> > users mailing list
> > users@xwiki.org
> > http://lists.xwiki.org/mailman/listinfo/users
> >
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>



-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Re-organize the Drawer's entries

2016-11-02 Thread Guillaume Delhumeau
Hello.

Thanks for your comments. Any other?

Guillaume

2016-10-26 17:03 GMT+02:00 Jan-Paul Kleijn <em...@biggee.nl>:

> P5 is also my favorite because it draws more attention to the content.
> It's the more grown-up version.
>
>
> Op 26-10-2016 om 10:28 schreef Guillaume Delhumeau:
>
> No opinion?
>>
>> 2016-10-24 18:09 GMT+02:00 Guillaume Delhumeau <
>> guillaume.delhum...@xwiki.com>:
>>
>> Hello dear developers and XWiki users.
>>>
>>> I would you to take a look at the issue http://jira.xwiki.org/browse/
>>> XWIKI-13070.
>>>
>>> The problem is that the current order (that I have implemented based on
>>> my
>>> intuition) seems to not be clear for our users. The main point is that
>>> the
>>> menu mixes up global items (Home wiki, Wiki Index) and local ones
>>> (Administer Wiki, Page Index, Delete wiki, etc...).
>>>
>>> Caty and Oliver have made some proposals that you could find in the
>>> issue.
>>>
>>> They are called P1, P2, P3, P4 and P5.
>>>
>>> I propose you to express your preferences so we can implement it based on
>>> a consensus.
>>>
>>> Here are mine:
>>>
>>> P1: There is a logical order and separation between item. However, it
>>> seems the more used actions (Wiki Index, Page Index) are less visible
>>> than
>>> some other (Delete Wiki, Create Wiki...)
>>>
>>> P2: The order and the separation are logic. The "delete wiki" action is
>>> still very visible but all other items are good.
>>>
>>> P3: Same than P2. Except that having "Wiki Index" along with "User, Page
>>> and Application Index" mixes up local and global items.
>>>
>>> P4: Why not, but maybe the 3 first actions should be placed after the
>>> other ones, since they would be less used. Same remark about the mixing
>>> of
>>> local and global items.
>>>
>>> P5: A clear distinction between local and global scope. More used items
>>> are located first. This is my favorite one.
>>>
>>>
>>> So +1 for P5, +0 for the other options so far.
>>>
>>> Now, what about you?
>>>
>>> Thanks,
>>> Guillaume
>>>
>>> PS: I send this message to both devs and users mailing lists, because I
>>> think users are directly concerned by this topic.
>>>
>>> --
>>> Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
>>> Research & Development Engineer at XWiki SAS
>>> Committer on the XWiki.org project
>>>
>>>
>>
>>
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>



-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Re-organize the Drawer's entries

2016-10-26 Thread Guillaume Delhumeau
No opinion?

2016-10-24 18:09 GMT+02:00 Guillaume Delhumeau <
guillaume.delhum...@xwiki.com>:

> Hello dear developers and XWiki users.
>
> I would you to take a look at the issue http://jira.xwiki.org/browse/
> XWIKI-13070.
>
> The problem is that the current order (that I have implemented based on my
> intuition) seems to not be clear for our users. The main point is that the
> menu mixes up global items (Home wiki, Wiki Index) and local ones
> (Administer Wiki, Page Index, Delete wiki, etc...).
>
> Caty and Oliver have made some proposals that you could find in the issue.
>
> They are called P1, P2, P3, P4 and P5.
>
> I propose you to express your preferences so we can implement it based on
> a consensus.
>
> Here are mine:
>
> P1: There is a logical order and separation between item. However, it
> seems the more used actions (Wiki Index, Page Index) are less visible than
> some other (Delete Wiki, Create Wiki...)
>
> P2: The order and the separation are logic. The "delete wiki" action is
> still very visible but all other items are good.
>
> P3: Same than P2. Except that having "Wiki Index" along with "User, Page
> and Application Index" mixes up local and global items.
>
> P4: Why not, but maybe the 3 first actions should be placed after the
> other ones, since they would be less used. Same remark about the mixing of
> local and global items.
>
> P5: A clear distinction between local and global scope. More used items
> are located first. This is my favorite one.
>
>
> So +1 for P5, +0 for the other options so far.
>
> Now, what about you?
>
> Thanks,
> Guillaume
>
> PS: I send this message to both devs and users mailing lists, because I
> think users are directly concerned by this topic.
>
> --
> Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
> Research & Development Engineer at XWiki SAS
> Committer on the XWiki.org project
>



-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


[xwiki-users] Re-organize the Drawer's entries

2016-10-24 Thread Guillaume Delhumeau
Hello dear developers and XWiki users.

I would you to take a look at the issue
http://jira.xwiki.org/browse/XWIKI-13070.

The problem is that the current order (that I have implemented based on my
intuition) seems to not be clear for our users. The main point is that the
menu mixes up global items (Home wiki, Wiki Index) and local ones
(Administer Wiki, Page Index, Delete wiki, etc...).

Caty and Oliver have made some proposals that you could find in the issue.

They are called P1, P2, P3, P4 and P5.

I propose you to express your preferences so we can implement it based on a
consensus.

Here are mine:

P1: There is a logical order and separation between item. However, it seems
the more used actions (Wiki Index, Page Index) are less visible than some
other (Delete Wiki, Create Wiki...)

P2: The order and the separation are logic. The "delete wiki" action is
still very visible but all other items are good.

P3: Same than P2. Except that having "Wiki Index" along with "User, Page
and Application Index" mixes up local and global items.

P4: Why not, but maybe the 3 first actions should be placed after the other
ones, since they would be less used. Same remark about the mixing of local
and global items.

P5: A clear distinction between local and global scope. More used items are
located first. This is my favorite one.


So +1 for P5, +0 for the other options so far.

Now, what about you?

Thanks,
Guillaume

PS: I send this message to both devs and users mailing lists, because I
think users are directly concerned by this topic.

-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] XWiki 8 migration JSX Extension velocity parse

2016-10-13 Thread Guillaume Delhumeau
Of course, this will not fix the real bug, and it won't work with your
stylesheet extension.

2016-10-13 13:20 GMT+02:00 Guillaume Delhumeau <
guillaume.delhum...@xwiki.com>:

> You are probably experiencing a bug.
>
> However, I will propose you a solution that we consider as a Best Practice.
>
> var url = new XWiki.Document(XWiki.Model.resolve('cdlsDashboard.statsGlobal',
> XWiki.EntityType.DOCUMENT)).getURL('view', 'xpage=plain=
> plain')
>
> I hope it helps,
>
> Guillaume
>
> 2016-10-13 12:15 GMT+02:00 Gerritjan Koekkoek <gerrit...@cdlsworld.org>:
>
>> Yes : parse was/is set to true
>>
>> Verstuurd vanaf mijn iPhone
>>
>> > Op 13 okt. 2016 om 12:13 heeft Guillaume Delhumeau <
>> guillaume.delhum...@xwiki.com> het volgende geschreven:
>> >
>> > Hello.
>> >
>> > On your JavaScript Skin Extension object, have you set "Parse content"
>> to
>> > "yes"?
>> >
>> > 2016-10-12 13:59 GMT+02:00 Gerritjan Koekkoek <gerrit...@cdlsworld.org
>> >:
>> >
>> >> Hi,
>> >>
>> >>
>> >> We have this javascript function
>> >>
>> >>  function getStats(event) {
>> >>
>> >>var url = "$xwiki.getURL('cdlsDashboard.statsGlobal',
>> >> 'view')?xpage=plain=plain";
>> >>
>> >>request(url, setStats, event);
>> >>
>> >>  }
>> >>
>> >> Since migration to version 8 the browser console shows a strange get
>> >> function and resulting error:
>> >> cdlsworld.devxwiki.com/xwiki/bin/view/cdlsDashboard/$xwiki.
>> >> getURL('cdlsDashboard.statsGlobal',%20'view')
>> >>
>> >> It looks like the velocity is not based before creating a javascript?
>> >> I've had similar in a stylesheet extension
>> >>
>> >> Is something changed in version XWiki 8 (we came from 6.4.x)?
>> >>
>> >>
>> >> Gerritjan Koekkoek
>> >> Vader van Rai Koekkoek (cdls) en voorzitter vereniging CdLS
>> >> Visit our website<http://www.cdlsworld.org>
>> >> Facebook<https://www.facebook.com/gerritjan.koekkoek>
>> >> email<gerrit...@cdlsworld.org>
>> >>
>> >>
>> >>
>> >> ___
>> >> users mailing list
>> >> users@xwiki.org
>> >> http://lists.xwiki.org/mailman/listinfo/users
>> >>
>> >
>> >
>> >
>> > --
>> > Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
>> > Research & Development Engineer at XWiki SAS
>> > Committer on the XWiki.org project
>> > ___
>> > users mailing list
>> > users@xwiki.org
>> > http://lists.xwiki.org/mailman/listinfo/users
>> ___
>> users mailing list
>> users@xwiki.org
>> http://lists.xwiki.org/mailman/listinfo/users
>>
>
>
>
> --
> Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
> Research & Development Engineer at XWiki SAS
> Committer on the XWiki.org project
>



-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] XWiki 8 migration JSX Extension velocity parse

2016-10-13 Thread Guillaume Delhumeau
You are probably experiencing a bug.

However, I will propose you a solution that we consider as a Best Practice.

var url = new
XWiki.Document(XWiki.Model.resolve('cdlsDashboard.statsGlobal',
XWiki.EntityType.DOCUMENT)).getURL('view', 'xpage=plain=plain')

I hope it helps,

Guillaume

2016-10-13 12:15 GMT+02:00 Gerritjan Koekkoek <gerrit...@cdlsworld.org>:

> Yes : parse was/is set to true
>
> Verstuurd vanaf mijn iPhone
>
> > Op 13 okt. 2016 om 12:13 heeft Guillaume Delhumeau <
> guillaume.delhum...@xwiki.com> het volgende geschreven:
> >
> > Hello.
> >
> > On your JavaScript Skin Extension object, have you set "Parse content" to
> > "yes"?
> >
> > 2016-10-12 13:59 GMT+02:00 Gerritjan Koekkoek <gerrit...@cdlsworld.org>:
> >
> >> Hi,
> >>
> >>
> >> We have this javascript function
> >>
> >>  function getStats(event) {
> >>
> >>var url = "$xwiki.getURL('cdlsDashboard.statsGlobal',
> >> 'view')?xpage=plain=plain";
> >>
> >>request(url, setStats, event);
> >>
> >>  }
> >>
> >> Since migration to version 8 the browser console shows a strange get
> >> function and resulting error:
> >> cdlsworld.devxwiki.com/xwiki/bin/view/cdlsDashboard/$xwiki.
> >> getURL('cdlsDashboard.statsGlobal',%20'view')
> >>
> >> It looks like the velocity is not based before creating a javascript?
> >> I've had similar in a stylesheet extension
> >>
> >> Is something changed in version XWiki 8 (we came from 6.4.x)?
> >>
> >>
> >> Gerritjan Koekkoek
> >> Vader van Rai Koekkoek (cdls) en voorzitter vereniging CdLS
> >> Visit our website<http://www.cdlsworld.org>
> >> Facebook<https://www.facebook.com/gerritjan.koekkoek>
> >> email<gerrit...@cdlsworld.org>
> >>
> >>
> >>
> >> ___
> >> users mailing list
> >> users@xwiki.org
> >> http://lists.xwiki.org/mailman/listinfo/users
> >>
> >
> >
> >
> > --
> > Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
> > Research & Development Engineer at XWiki SAS
> > Committer on the XWiki.org project
> > ___
> > users mailing list
> > users@xwiki.org
> > http://lists.xwiki.org/mailman/listinfo/users
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>



-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] XWiki 8 migration JSX Extension velocity parse

2016-10-13 Thread Guillaume Delhumeau
Hello.

On your JavaScript Skin Extension object, have you set "Parse content" to
"yes"?

2016-10-12 13:59 GMT+02:00 Gerritjan Koekkoek <gerrit...@cdlsworld.org>:

> Hi,
>
>
> We have this javascript function
>
>   function getStats(event) {
>
> var url = "$xwiki.getURL('cdlsDashboard.statsGlobal',
> 'view')?xpage=plain=plain";
>
> request(url, setStats, event);
>
>   }
>
> Since migration to version 8 the browser console shows a strange get
> function and resulting error:
> cdlsworld.devxwiki.com/xwiki/bin/view/cdlsDashboard/$xwiki.
> getURL('cdlsDashboard.statsGlobal',%20'view')
>
> It looks like the velocity is not based before creating a javascript?
> I've had similar in a stylesheet extension
>
> Is something changed in version XWiki 8 (we came from 6.4.x)?
>
>
> Gerritjan Koekkoek
> Vader van Rai Koekkoek (cdls) en voorzitter vereniging CdLS
> Visit our website<http://www.cdlsworld.org>
> Facebook<https://www.facebook.com/gerritjan.koekkoek>
> email<gerrit...@cdlsworld.org>
>
>
>
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>



-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] XWQL datatype question

2016-09-28 Thread Guillaume Delhumeau
More over, it also depends on the field "Relational Storage".

See, for example:
https://www.xwiki.org/xwiki/bin/view/FAQ/HowToCreateAOneToManyRelationshipInXWiki

2016-09-28 17:31 GMT+02:00 Guillaume Delhumeau <
guillaume.delhum...@xwiki.com>:

> For list of Users, it's the fullname of the document holding the user,
> example: XWiki:gdelhumeau.
>
> For a database list, it depends on what you have put in the class. You
> haven't given enough information about the "research" field. Could you
> describe it a bit more?
>
> 2016-09-28 16:23 GMT+02:00 Gerritjan Koekkoek <gerrit...@cdlsworld.org>:
>
>> Thanks, code checked, made some improvements.
>>
>> But the query should recognize that both class attributes are of type
>> DBLIST.
>>
>>
>> the question is how I should specify the where clause:
>>
>>
>> so
>>
>> where dblist_property1 = :bindvalue1 and dblist_property2 = :bindvalue2
>>
>>
>> What should we put in our two bindvalue's ?
>>
>>  a string: 'text'
>>
>>  a array: ['text']
>>
>>  a object {text}
>>
>>
>> Gerritjan Koekkoek
>> Vader van Rai Koekkoek (cdls) en voorzitter vereniging CdLS
>> Visit our website<http://www.cdlsworld.org>
>> Facebook<https://www.facebook.com/gerritjan.koekkoek>
>> email<gerrit...@cdlsworld.org>
>>
>>
>>
>> 
>> From: users <users-boun...@xwiki.org> on behalf of Guillaume Delhumeau <
>> guillaume.delhum...@xwiki.com>
>> Sent: 28 September 2016 12:12:16
>> To: XWiki Users
>> Subject: Re: [xwiki-users] XWQL datatype question
>>
>> Hi.
>>
>> Note that this line:
>> #set( $qParticipations = "from doc.object('$participationClassName') as
>> participation where doc.fullName <> 'waihonapediaResearchParticipa
>> tionTemplate'
>> and participation.research = :thisresearch" and participation.family =
>> :thisUser)
>>
>> is invalid (you closed the " too soon). But I guess it's not your problem.
>>
>> Also, I really doubt that you have a page called
>> 'waihonapediaResearchParticipationTemplate' (it's supposed to be a
>> fullname).
>>
>> There is also invalid simple quotes (') in doc.object.
>>
>>
>> So the correct query should be:
>> #set( $qParticipations = "from doc.object(WaihonaCode.
>> waihonapediaResearchParticipationClass) as participation where
>> doc.fullName
>> <> 'WaihonaCode.waihonapediaResearchParticipationTemplate' and
>> participation.research = :thisresearch and participation.family =
>> :thisUser")
>>
>> I hope it helps,
>>
>> 2016-09-27 14:03 GMT+02:00 Gerritjan Koekkoek <gerrit...@cdlsworld.org>:
>>
>> > Hi,
>> >
>> >
>> > I have this class:
>> >
>> > #set( $participationClassName = "WaihonaCode.
>> > waihonapediaResearchParticipationClass" )
>> >
>> >
>> > Class properties
>> >
>> > researchparticipation.family (family: List of Users)
>> >
>> > researchparticipation.research (research: Database List)
>> >
>> > researchparticipation.participate (participate: Boolean)
>> >
>> > researchparticipation.datasend (datasend: Boolean)
>> >
>> >
>> >
>> > I have this XWQL:
>> >
>> >
>> > #set( $qParticipations = "from doc.object('$participationClassName') as
>> > participation where doc.fullName <> 'waihonapediaResearchParticipa
>> tionTemplate'
>> > and participation.research = :thisresearch" and participation.family =
>> > :thisUser)
>> >
>> >
>> > I'm getting velocity error:
>> >
>> > Caused by: org.hibernate.QueryException: could not resolve property:
>> > research of: com.xpn.xwiki.objects.BaseObject [ select doc.fullName
>> from
>> > com.xpn.xwiki.doc.XWikiDocument as doc , com.xpn.xwiki.objects.BaseObje
>> ct
>> > as participation where
>> >
>> >
>> > When doing similar on a class where class properties are of type string
>> I
>> > have no Issues?
>> >
>> > What should I do with these properties: List of Users (always only 1)
>> and
>> > Database List (always only 1)?
>> >
>> >
>> > Gerritjan Koekkoek
>> > Vader van Rai Koekkoek (cdls) en voorzitter vereniging CdLS
>> > Visit our 

Re: [xwiki-users] XWQL datatype question

2016-09-28 Thread Guillaume Delhumeau
For list of Users, it's the fullname of the document holding the user,
example: XWiki:gdelhumeau.

For a database list, it depends on what you have put in the class. You
haven't given enough information about the "research" field. Could you
describe it a bit more?

2016-09-28 16:23 GMT+02:00 Gerritjan Koekkoek <gerrit...@cdlsworld.org>:

> Thanks, code checked, made some improvements.
>
> But the query should recognize that both class attributes are of type
> DBLIST.
>
>
> the question is how I should specify the where clause:
>
>
> so
>
> where dblist_property1 = :bindvalue1 and dblist_property2 = :bindvalue2
>
>
> What should we put in our two bindvalue's ?
>
>  a string: 'text'
>
>  a array: ['text']
>
>  a object {text}
>
>
> Gerritjan Koekkoek
> Vader van Rai Koekkoek (cdls) en voorzitter vereniging CdLS
> Visit our website<http://www.cdlsworld.org>
> Facebook<https://www.facebook.com/gerritjan.koekkoek>
> email<gerrit...@cdlsworld.org>
>
>
>
> 
> From: users <users-boun...@xwiki.org> on behalf of Guillaume Delhumeau <
> guillaume.delhum...@xwiki.com>
> Sent: 28 September 2016 12:12:16
> To: XWiki Users
> Subject: Re: [xwiki-users] XWQL datatype question
>
> Hi.
>
> Note that this line:
> #set( $qParticipations = "from doc.object('$participationClassName') as
> participation where doc.fullName <> 'waihonapediaResearchParticipat
> ionTemplate'
> and participation.research = :thisresearch" and participation.family =
> :thisUser)
>
> is invalid (you closed the " too soon). But I guess it's not your problem.
>
> Also, I really doubt that you have a page called
> 'waihonapediaResearchParticipationTemplate' (it's supposed to be a
> fullname).
>
> There is also invalid simple quotes (') in doc.object.
>
>
> So the correct query should be:
> #set( $qParticipations = "from doc.object(WaihonaCode.
> waihonapediaResearchParticipationClass) as participation where
> doc.fullName
> <> 'WaihonaCode.waihonapediaResearchParticipationTemplate' and
> participation.research = :thisresearch and participation.family =
> :thisUser")
>
> I hope it helps,
>
> 2016-09-27 14:03 GMT+02:00 Gerritjan Koekkoek <gerrit...@cdlsworld.org>:
>
> > Hi,
> >
> >
> > I have this class:
> >
> > #set( $participationClassName = "WaihonaCode.
> > waihonapediaResearchParticipationClass" )
> >
> >
> > Class properties
> >
> > researchparticipation.family (family: List of Users)
> >
> > researchparticipation.research (research: Database List)
> >
> > researchparticipation.participate (participate: Boolean)
> >
> > researchparticipation.datasend (datasend: Boolean)
> >
> >
> >
> > I have this XWQL:
> >
> >
> > #set( $qParticipations = "from doc.object('$participationClassName') as
> > participation where doc.fullName <> 'waihonapediaResearchParticipat
> ionTemplate'
> > and participation.research = :thisresearch" and participation.family =
> > :thisUser)
> >
> >
> > I'm getting velocity error:
> >
> > Caused by: org.hibernate.QueryException: could not resolve property:
> > research of: com.xpn.xwiki.objects.BaseObject [ select doc.fullName from
> > com.xpn.xwiki.doc.XWikiDocument as doc , com.xpn.xwiki.objects.
> BaseObject
> > as participation where
> >
> >
> > When doing similar on a class where class properties are of type string I
> > have no Issues?
> >
> > What should I do with these properties: List of Users (always only 1) and
> > Database List (always only 1)?
> >
> >
> > Gerritjan Koekkoek
> > Vader van Rai Koekkoek (cdls) en voorzitter vereniging CdLS
> > Visit our website<http://www.cdlsworld.org>
> > Facebook<https://www.facebook.com/gerritjan.koekkoek>
> > email<gerrit...@cdlsworld.org>
> >
> >
> >
> > ___
> > users mailing list
> > users@xwiki.org
> > http://lists.xwiki.org/mailman/listinfo/users
> >
>
>
>
> --
> Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
> Research & Development Engineer at XWiki SAS
> Committer on the XWiki.org project
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>



-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Skins - Fix Nav Menus when scrooling page content

2016-09-28 Thread Guillaume Delhumeau
Hello.

For the top menu, I think you should look at:
http://getbootstrap.com/components/#navbar-fixed-top

Example: https://jsfiddle.net/5hspvk08/

For the panels, however, it's more complex.

I hope it helps,



2016-09-27 17:09 GMT+02:00 Ramon Gomes Brandao <
ramon.bran...@planejamento.gov.br>:

> Hi XWiki Team,
>
> I'm trying to design a new skin based on flaming to attend our company's
> use cases (with XE 8.x) and we were required to fix the top menu divs (for
> instance, the menuview div and the headerglobal div), as well as, if
> possible, side panels, while scrooling the page content. The side panels
> div shoud also be scroolabe, when the elements overflow the viewport.
>
> I could not achieve any success overriding some flamingo's CSS and trying
> to fix elements with position CSS statement. How is the best way to achieve
> that using a new skin approach? I won't also forget to be responsible for
> small screens, so fixing side panels and top menu is not a good idea. How
> is the best way to deal with this?
>
> Best Regards,
>
>
> RAMON BRANDÃO
>
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>



-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] XWQL datatype question

2016-09-28 Thread Guillaume Delhumeau
Hi.

Note that this line:
#set( $qParticipations = "from doc.object('$participationClassName') as
participation where doc.fullName <> 'waihonapediaResearchParticipationTemplate'
and participation.research = :thisresearch" and participation.family =
:thisUser)

is invalid (you closed the " too soon). But I guess it's not your problem.

Also, I really doubt that you have a page called
'waihonapediaResearchParticipationTemplate' (it's supposed to be a
fullname).

There is also invalid simple quotes (') in doc.object.


So the correct query should be:
#set( $qParticipations = "from doc.object(WaihonaCode.
waihonapediaResearchParticipationClass) as participation where doc.fullName
<> 'WaihonaCode.waihonapediaResearchParticipationTemplate' and
participation.research = :thisresearch and participation.family =
:thisUser")

I hope it helps,

2016-09-27 14:03 GMT+02:00 Gerritjan Koekkoek <gerrit...@cdlsworld.org>:

> Hi,
>
>
> I have this class:
>
> #set( $participationClassName = "WaihonaCode.
> waihonapediaResearchParticipationClass" )
>
>
> Class properties
>
> researchparticipation.family (family: List of Users)
>
> researchparticipation.research (research: Database List)
>
> researchparticipation.participate (participate: Boolean)
>
> researchparticipation.datasend (datasend: Boolean)
>
>
>
> I have this XWQL:
>
>
> #set( $qParticipations = "from doc.object('$participationClassName') as
> participation where doc.fullName <> 
> 'waihonapediaResearchParticipationTemplate'
> and participation.research = :thisresearch" and participation.family =
> :thisUser)
>
>
> I'm getting velocity error:
>
> Caused by: org.hibernate.QueryException: could not resolve property:
> research of: com.xpn.xwiki.objects.BaseObject [ select doc.fullName from
> com.xpn.xwiki.doc.XWikiDocument as doc , com.xpn.xwiki.objects.BaseObject
> as participation where
>
>
> When doing similar on a class where class properties are of type string I
> have no Issues?
>
> What should I do with these properties: List of Users (always only 1) and
> Database List (always only 1)?
>
>
> Gerritjan Koekkoek
> Vader van Rai Koekkoek (cdls) en voorzitter vereniging CdLS
> Visit our website<http://www.cdlsworld.org>
> Facebook<https://www.facebook.com/gerritjan.koekkoek>
> email<gerrit...@cdlsworld.org>
>
>
>
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>



-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


[xwiki-users] [ANN] Release of Limits Application 1.2.

2016-09-19 Thread Guillaume Delhumeau
Hi users and devs,

The Limits Application has been improved again. It seems I have taken the
manta "release early, release often" very seriously :).

The 1.2 version has been released and brings the ability to handle custom
limits.

See: http://extensions.xwiki.org/xwiki/bin/view/Extension/Limits+Application

Thanks,

-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


[xwiki-users] [ANN] Limits Application 1.1 has been released

2016-09-15 Thread Guillaume Delhumeau
Hello.

Yesterday, I announced you the availability of a new extension: the Limits
Application.

Since, Thomas Mortagne suggested me an idea to make it better. The UI of
the application is now contained in the JAR, so it cannot be removed by
mistake by an user who manipulates wiki pages. Moreover, the UI is now
visible on every subwikis, without the need to install something on each of
them.

Also, developers will be happy because they can overwrite the default UI
like any skin template!

To download it or see more informations, see:
http://extensions.xwiki.org/xwiki/bin/view/Extension/Limits+Application/#Hv1.1

Thanks,

-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


[xwiki-users] [ANN] A new extension released on Contrib: Limits Application

2016-09-14 Thread Guillaume Delhumeau
Hello.

I just have released the first version of a new application in contrib, the
Limits Application.

This extension prevents the creation of too many users or wikis in an
instance. It can also limits the number of members of any global group you
want.

The reason behind the creation of this application is the need, for XWiki
hosters, to add some restrictions on their instances to save their
resources. For example, a virtual machine handling a lot of users needs
more memory: it's fair that the client pay more to push back these limits.

See:
http://extensions.xwiki.org/xwiki/bin/view/Extension/Limits+Application/

Thanks,

-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


[xwiki-users] [myxwiki] How to return to the first installed version of my xwiki space ?

2016-09-12 Thread Guillaume Delhumeau
Hi.

I transfer your message to the proper mailing list.


-- Forwarded message --
From: paulebou...@gmail.com <paulebou...@gmail.com>
Date: 2016-09-09 17:49 GMT+02:00
Subject: How to return to the first installed version of my xwiki space ?
To: guillaume.delhum...@xwiki.com



Hi,

How can i come back to the original configuration of my xwiki space ?

... Seem i have deleted the administration module !!! and, i can't use my
xwiki space anymore ...

It's very problematic because,i have plan to use it all this year to
animate the local discussion groups for citizens of Bagnolet ...

Can you please re-initialize my space ?

Thanks for your help.

Paule Bouton
paulebou...@gmail.com





--
[image: Avast logo] <https://www.avast.com/antivirus>

This email has been checked for viruses by Avast antivirus software.
www.avast.com <https://www.avast.com/antivirus>




-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] [xwiki-devs] [ANN] Tour Application 1.0.3 Released

2016-08-29 Thread Guillaume Delhumeau
Hi Mario.

Indeed, since 8.2, the Tour Application is already bundled with XWiki
Enterprise, which means that the webjar of the dependency (bootstrap-tour)
is considered as a "core extension" which also means that it can only be
upgraded along with the whole XWiki Enterprise.

It's an issue that we know and we are currently looking for solutions:
http://markmail.org/message/mbut2lhatyeu6wzv

Thanks,

2016-08-26 9:34 GMT+02:00 Mario <mario.hofstaet...@automationx.com>:

> I'm unable to update the Tour Application from 1.0.2 to 1.0.4:
>
>
>
> I'm running xwiki 8.2.1 (standalone sandbox on Windows).
>
> If i click on dependency [org.webjars:bootstrap-tour-0.11.0] it Displays
> "Version 0.10.2-1 is pre installed", but no option to update?
>
> Thank you
> Mario
>
>
>
> --
> View this message in context: http://xwiki.475771.n2.nabble.
> com/ANN-Tour-Application-1-0-3-Released-tp7600865p7600889.html
> Sent from the XWiki- Users mailing list archive at Nabble.com.
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>



-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] [xwiki-devs] [ANN] Tour Application 1.0.3 Released

2016-08-25 Thread Guillaume Delhumeau
I've just release Tour Application 1.0.4 which fixes an important bug.

See:
http://extensions.xwiki.org/xwiki/bin/view/Extension/Tour+Application#Hv1.0.4

Thanks.

2016-08-25 12:29 GMT+02:00 Alexandru Cotiuga <alexandru.coti...@xwiki.com>:

> In fact I don't know how I ended up with the broken link in the browser by
> clicking your. At a second try it worked. Sorry for the noise.
>
> On Thu, Aug 25, 2016 at 1:27 PM, Alexandru Cotiuga <
> alexandru.coti...@xwiki.com> wrote:
>
> > Hi,
> > The link you gave is wrong (contains an extra '_'). See
> > http://extensions.xwiki.org/xwiki/bin/view/Extension/Tour+
> > Application#Hv1.0.3.
> >
> >
> >
> > On Thu, Aug 25, 2016 at 12:29 PM, Guillaume Delhumeau <
> > guillaume.delhum...@xwiki.com> wrote:
> >
> >> Hello all,
> >>
> >> Yesterday, I have released a new bugfix version of the Tour Application.
> >>
> >> One of the interesting fix is the fact that the elements that were badly
> >> highlighted should be better displayed now.
> >>
> >> See http://extensions.xwiki.org/xwiki/bin/view/Extension/Tour+
> Application
> >> #Hv1.0.3
> >> <http://extensions.xwiki.org/xwiki/bin/view/Extension/Tour+
> Application#Hv1.0.3>
> >> .
> >>
> >> You can install or upgrade with the Extension Manager.
> >>
> >> Thanks,
> >>
> >> --
> >> Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
> >> Research & Development Engineer at XWiki SAS
> >> Committer on the XWiki.org project
> >> ___
> >> devs mailing list
> >> d...@xwiki.org
> >> http://lists.xwiki.org/mailman/listinfo/devs
> >>
> >
> >
> ___
> devs mailing list
> d...@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>



-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


[xwiki-users] [ANN] Tour Application 1.0.3 Released

2016-08-25 Thread Guillaume Delhumeau
Hello all,

Yesterday, I have released a new bugfix version of the Tour Application.

One of the interesting fix is the fact that the elements that were badly
highlighted should be better displayed now.

See http://extensions.xwiki.org/xwiki/bin/view/Extension/Tour+Application
#Hv1.0.3.

You can install or upgrade with the Extension Manager.

Thanks,

-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


[xwiki-users] [ANN] XWiki 8.3 Milestone 1 released

2016-08-24 Thread Guillaume Delhumeau
The XWiki development team is proud to announce the availability of XWiki
8.3 Milestone 1.
This release brings mostly usability 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/ReleaseNotesXWiki83M1

Thanks for your support
-The XWiki dev team
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Custom Mapping.

2016-06-06 Thread Guillaume Delhumeau
Hello.

It would be better with a stack trace so we can see what happens.

Have you executed the groovy script, as explained there:
http://platform.xwiki.org/xwiki/bin/view/DevGuide/CustomMapping

Thanks,
Guillaume

2016-06-02 21:49 GMT+02:00 dullfig <da...@grmcompany.com>:

> Ok, first off, I tried, I really did
>
> I'm trying to map an object called Data.Code.Employee.Class to its own
> table. Here's what I have done so far:
>
> In \xwiki\WEB-INF\ i have a file called EmployeeClass.hbm.xml that has the
> following content
>
>
>
> 
>-//Hibernate/Hibernate Mapping DTD//EN
>   http://www.hibernate.org/dtd/hibernate-mapping-3.0.dtd;>
>
> 
> 
> 
> 
> 
> 
>  length="255"/>
>  length="255"/>
>  length="255"/>
> 
>  column="xws_supervisor"/>
> 
> 
> 
>  length="255"/>
>  length="255"/>
>  length="255"/>
>  length="255"/>
> 
>  length="255"/>
>  length="255"/>
> 
> 
>
>
> Then in the hibernate.cfg.xml file I added a mapping resource to the MySQL
> section like this:
>
>
> jdbc:mysql://localhost/xwiki
> xwiki
> xwiki
>  name="connection.driver_class">com.mysql.jdbc.Driver
>  name="dialect">org.hibernate.dialect.MySQL5InnoDBDialect
> true
> 20
> 
> 
> 
> 
> 
> 
>
> I also enabled custom mapping by setting
> xwiki.store.hibernate.custommapping=1 in xwiki.cfg
>
> I created the xwikiemployeeclass table in MySQL manually and it made no
> difference.
>
> So here is what happens: if  I add the mapping resource to the hibernate
> file, xwiki freezes at about 50% loading. If I remove that line everything
> is fine. I'm fresh out of ideas.
>
> HELP!!
>
> Dan
>
> PS.: none of those other xml files mentioned in the MySQL section seem to
> be
> anywhere. Can't find them. Where are they? (like the instance.hbm.xml file
> for example)
>
>
>
> --
> View this message in context:
> http://xwiki.475771.n2.nabble.com/Custom-Mapping-tp7599790.html
> Sent from the XWiki- Users mailing list archive at Nabble.com.
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>



-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] [ANN] Release of Nested Pages Migrator Application 0.5

2016-05-25 Thread Guillaume Delhumeau
The link is bad. The good one is:
http://extensions.xwiki.org/xwiki/bin/view/Extension/Nested+Pages+Migrator+Application#Hv0.5

2016-05-25 13:13 GMT+02:00 Guillaume Delhumeau <
guillaume.delhum...@xwiki.com>:

> Hello
>
> A new version of the Nested Pages Migrator Application extension is
> available. See
>
> http://extensions.xwiki.org/xwiki/bin/view/Extension/Nested+Pages+Migrator+Application#Hv0.5
> <http://extensions.xwiki.org/xwiki/bin/view/Extension/Tour+Application#Hv1.0>
> You can install or upgrade with the Extension Manager.
>
> The application is still a beta version that you should use carefully.
> XWiki crashes might occur during the migration. But this version brings the
> ability to detect bad documents created because of these crashes so you are
> able to finish the migration by restarting XWiki (several times if needed).
> It is still not a friendly process, but at least it is possible and I know
> it will help some peoples.
>
> It also brings an icon in the applications panel :)
>
> Enjoy!
>
> --
> Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
> Research & Development Engineer at XWiki SAS
> Committer on the XWiki.org project
>



-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


[xwiki-users] [ANN] Release of Nested Pages Migrator Application 0.5

2016-05-25 Thread Guillaume Delhumeau
Hello

A new version of the Nested Pages Migrator Application extension is
available. See
http://extensions.xwiki.org/xwiki/bin/view/Extension/Nested+Pages+Migrator+Application#Hv0.5
<http://extensions.xwiki.org/xwiki/bin/view/Extension/Tour+Application#Hv1.0>
You can install or upgrade with the Extension Manager.

The application is still a beta version that you should use carefully.
XWiki crashes might occur during the migration. But this version brings the
ability to detect bad documents created because of these crashes so you are
able to finish the migration by restarting XWiki (several times if needed).
It is still not a friendly process, but at least it is possible and I know
it will help some peoples.

It also brings an icon in the applications panel :)

Enjoy!

-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Rights inheritance doubt in v7.4

2016-04-27 Thread Guillaume Lerouge
Hi Iago,

indeed, the documentation is slightly wrong on this. Rights applied
downstream take precedence over rights applied upstream, so you also need
to give GroupA edit rights on the page.

One exception to this is the admin right, which keeps applying downstream
in all circumstances.

Guillaume

On Wed, Apr 27, 2016 at 2:27 PM, Iago Lluque <iago.llu...@alineasol.com>
wrote:

> Hi all,
>
> I have doubts about how permissions are inherited in XWiki v7.4. Does this
> statement from your documentation still apply for this version?
> /"*Note on permission inheritance*//
> //When a permission is explicitly set for a given group or user at a
> certain scope (page, space or wiki) then other groups and users must also
> have the right explicitly set as well, at this scope or a scope upstream.//
> //For example, when you decide to explicitly allow the view right for
> "GroupA" on a given space, users that are not members of "GroupA" must have
> the view right explicitly set either on the given space or on the whole
> wiki to be able to view the space as well."/
>
> I expose my problem:
> GroupA with edit rights at Wiki level.
> GroupB with view rights at Wiki level.
> I grant GroupB edit permissions on a certain page => GroupA is no longer
> able to edit this page (neither its children) until I specifically grant
> them edit rights (again, as at Wiki level they have them). This contradicts
> previous statement.
>
> Could you please clarify? Thanks in advance!
>
> --
> ASOL Email Un cordial saludo,
> Iago Lluque
> /
> *Alínea Software Solutions S.L.*
> Travesía del Comercio 3, 2º 36002 Pontevedra España
> Tel: +34 986 845 699
> Email: i...@alineasol.com <mailto:i...@alineasol.com>
> Web: http://www.alineasol.com
> /
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Mindtouch to Xwiki

2016-04-27 Thread Guillaume Lerouge
Hi Daniel,

I hope you're doing well. I was wondering whether you had had success with
your Mindtouch to XWiki migration?

Best,

Guillaume

On Wed, Mar 23, 2016 at 6:42 PM, Dan T <daniel.t...@gmail.com> wrote:

> Hello,
>
> Thank you for your answer. Sorry to be late with this reply. This project
> was on hold until last week.
>
> We have now one xwiki ready on a production server (RHEL7) and we are
> ready to begin with it.
>
> I tried a lot of way to import data into xwiki from mindtouch but without
> success. The only way I see right now is with manually with html pages.
>
> I can create a new page and insert the content in html format. Converted
> or not in xwiki syntax, we can work with that. All the links in the pages
> are working (and have to be corrected in the future to point to xwiki
> instead of the old one)
>
> We have to review all the pages and recreate or move the content
> progressively. A new structure will be applied and some of the pages will
> be useless.
>
> The goal, right now, is to have all pages (660) available directly in
> xwiki. That + the search tool will be enough.
>
> Then you need to have some code that does the looping over the 600 pages
> you got.
>
> This is a part I’m interested in. A way to not have to click, copy and
> paste with all the html pages.
>
> My knowledge is limited but I have some people around me to help me
> achieve things i can’t do by myself.
>
> Thanks
>
> Daniel
>
> Le 9 décembre 2015 à 23:46:38, vinc...@massol.net (vinc...@massol.net) a
> écrit:
>
> Hi Daniel,
>
> Let me start by saying that ideally XWiki should offer some tool to help
> convert HTML content into wiki pages. That would be awesome and it’s doable
> but we don’t have this yet.
>
> However XWiki internally supports parsing HTML.
>
> First thing you can try is to enable HTML 4.01 syntax in your XWiki
> instance. Then create a new page, select HTML 4.01 as the page syntax and
> copy paste the HTML you got. Save. Then edit again and switch to XWiki
> Syntax 2.1 for example. This should convert the HTML to wiki markup.
>
> Now you’ll get some issues with this. Links are probably going to be off
> for example.
>
> So what you really need is to create an HTML importer to transform the
> HTML you got into an Annotated HTML format that XWiki supports. The
> Annotated HTML format is an internal format used by XWiki when you edit a
> page using the WYSIWYG editor and it’s a lossless format, meaning you can
> convert it to XWiki Syntax without loosing any meaning/data.
>
> This requires some knowledge of that format and some massaging of your
> HTML to transform it into this format.
>
> Then you need to have some code that does the looping over the 600 pages
> you got.
>
> This is quite technical. You’d need first to tell us your level of
> technical knowledge so that we could try to help you.
>
> Another option (the simplest for sure, especially if you’re not that
> technical or don’t have the time to delve deeply into the technical
> details) would be to contact one of the companies offering professional
> support for XWiki and asking them if they’d be interested in making a quote
> for doing this job for you. There are some listed at
> http://www.xwiki.org/xwiki/bin/view/Main/Support#HProfessionalSupport
>
> Hope it helps,
> -Vincent
>
>
> On 9 Dec 2015 at 12:01:15, Daniel Tibô (daniel.t...@gmail.com(mailto:
> daniel.t...@gmail.com)) wrote:
>
> > Hello,
> >
> > In our department, the actuel wiki is based on Mindtouch/dekiwiki and we
> > want to go to for a global wiki for the company with Xwiki.
> >
> > To do that, we need to transfer our data from the actual wiki and I
> > managed to extract all the pages in HTML format (600+ files).
> >
> > I have found in the mailing list history a reply from Vincent in August
> > 2013 to a similar request :
> >
> > --
> >
> > Hi Jason,
> >
> > I don't know of any existing Mindtouch converter to XWiki. However there
> > are several handmade converter tools on http://extensions.xwiki.org that
> > could serve as examples.
> >
> > What is the markup syntax used by Mindtouch? I have the feeling they
> > only provide HTML which would be fine since XWiki's Rendering can
> > convert HTML into wiki markup for example (or keep it as HTML too).
> >
> > So converting a page would be:
> > * Read the export format from Mindtouch (what is it? XML?)
> > * Use the XWiki API to create a wiki page, convert the HTML content to
> > wiki markup (easy to do), add attachments
> >
> > Also note that Thomas Mortagne (one of the XWiki committer) i

[xwiki-users] [ANN] XWiki 8.1 Milestone 2 released

2016-04-27 Thread Guillaume Delhumeau
The XWiki development team is proud to announce the availability of XWiki
8.1 Milestone 2.

This milestone release brings a new parameter to the Document Macro, the
synchronization of the avatars coming from LDAP and the support of feeds
delivered over HTTPS in the RSS Macro.

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/ReleaseNotesXWiki81M2

The following people have contributed code to this release (sorted
alphabetically):

- Alexandru Cotiuga
- Clemens Robbenhaar
- Eduard Moraru
- Guillaume Delhumeau
- Lukas Raska
- Manuel Smeria
- Marius Dumitru Florea
- Thomas Mortagne
- Vincent Massol
- Yuri Konotopov

Thanks for your support
-The XWiki dev team
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Help spread the word about XWiki - add your review!

2016-03-02 Thread Guillaume Lerouge
Hi again,

I haven't seen many reactions on this... I've been told that the G2Crowd
feedback form was too long to fill, so I also created a page for XWiki on
Capterra, where the review form is much shorter/easier to fill:

*http://www.capterra.com/collaboration-software/reviews/149030/XWiki/XWiki/new
<http://www.capterra.com/collaboration-software/reviews/149030/XWiki/XWiki/new>*

Every review counts if we are to make XWiki the best-known wiki software in
the world :-)

Thanks in advance, for your help,

Guillaume

On Mon, Feb 22, 2016 at 11:36 AM, Guillaume Lerouge <guilla...@xwiki.com>
wrote:

> Hi users,
>
> I'm trying new ways to spread the word about XWiki. One approach that
> seems to be popular right now are review websites such as Getapp and
> G2Crowd. For instance Drupal has a page on G2Crowd
> <https://www.g2crowd.com/products/drupal/reviews>, so I thought it could
> be interesting to try it out too.
>
> In order to see whether this could work well for XWiki, I have created a
> page on G2Crowd: *https://www.g2crowd.com/products/xwiki/reviews
> <https://www.g2crowd.com/products/xwiki/reviews>*
>
> It would be very cool if you could spend a bit of time to add a review of
> your experience with XWiki there!
>
> Thanks and happy XWikiing,
>
> Guillaume
>
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Feature Request: Allow copy & paste of images into WYSIWYG editor

2016-03-01 Thread Guillaume Lerouge
Hi Stuart,

On Tue, Mar 1, 2016 at 11:58 AM, Stuart Stephen <
stuart.step...@tracegroup.com> wrote:

> Hi,
>
> Sorry, I've not been getting the replies to these messages. I've
> re-subscribed to the list, so hopefully that is now resolved :)
>
> I tried copy and pasting images on the http://playground.xwiki.org site,
> but didn't have any luck. I was copying these images directly from MS Word,
> but I also did try copying from a web browser (in this instance Chrome).
> Does that mean the demo site is not using the CKEditor and the out of the
> box editor doesn't support the copy and paste?
>

The demo site does not have the CKEditor extension installed.

The new version of the CKEditor extension does support this use case (at
least in Firefox) at the moment.

Guillaume

Thanks,
> Stuart
>
> From: Stuart Stephen
> Sent: 23 February 2016 10:47
> To: 'users@xwiki.org'
> Subject: Feature Request: Allow copy & paste of images into WYSIWYG editor
>
> Hi all,
>
> In various web applications these days it is now possible to copy and
> paste images into web pages which makes the process of adding an image to a
> document online so much easier as you do not need to save it off somewhere,
> then upload it. Copy and paste makes the process so much more efficient.
>
> See the upload feature on http://imgur.com/ for example, where they also
> support drag and drop.
>
> Thanks,
> Stuart
> Disclaimer: The contents of this E-mail plus any attachment is intended
> for the use of the addressee only and is confidential, proprietary and may
> be privileged. It will not be binding upon Trace Group or any group company
> (Trace). Opinions, conclusions, contractual obligations and other
> information in this message in so far as they relate to the official
> business of Trace must be specifically confirmed in writing by Trace. If
> you are not the intended recipient you must not copy this message or
> attachment, use or disclose the contents to any other person, but are
> requested to telephone or E-mail the sender and delete the message and any
> attachment from your system. Trace takes all reasonable precautions to
> ensure that no virus or defect is transmitted via this e mail, however
> Trace accepts no responsibility for any virus or defect that might arise
> from opening this E-mail or attachments.
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Feature Request: Allow copy & paste of images into WYSIWYG editor

2016-02-23 Thread Guillaume Lerouge
Hi Edy,

On Tue, Feb 23, 2016 at 2:38 PM, Eduard Moraru <enygma2...@gmail.com> wrote:

> On Tue, Feb 23, 2016 at 1:22 PM, vinc...@massol.net <vinc...@massol.net>
> wrote:
>
> >
> >
> > On 23 Feb 2016 at 12:06:43, Guillaume Lerouge (guilla...@xwiki.com
> (mailto:
> > guilla...@xwiki.com)) wrote:
> >
> > > Hi Stuart,
> > >
> > > thanks for your feedback. This is indeed a frequent request. In the
> > current
> > > WYSIWYG editor, it partially works (your image has to be available
> from a
> > > public server).
> > >
> > > However, we added full support for this feature in the last version of
> > the
> > > CKEditor extension:
> > >
> >
> http://extensions.xwiki.org/xwiki/bin/view/Extension/CKEditor+Integration
> > > => if you drag & drop an image in CKEditor, it is automatically
> attached
> > to
> > > the wiki page.
> > >
> > > Please also note that drag & drop of images currently work if you go to
> > the
> > > "attachments" tab of any page (while in view mode) and drop your image
> > > there.
> >
> > hmm are you sure? I’m not aware of this feature. I just tested it and it
> > didn’t work for me on 8.0M2.
> >
>
> Tried it and it seems to work only if you drop the file exactly over the
> file upload field ("Browse" button or "No files selected" label, i.e. field
> with id "xwikiuploadfile"). This definitely needs to be improved.
>
> Personally, I would prefer we go full page Drag & Drop support, i.e. if a
> file is dropped in the XWiki browser tab, a popup asks the user if he wants
> to attach the dropped files to the current XWiki document. Something like
> GitHub is doing when you can drop a file anywhere in the tab of an XWiki
> repository (and a commit form will show up for you to fill details).
>

I agree that this would be nice too. However, it doesn't mean you don't
need it in edition mode. Having to switch back and forth between view and
edit because you forgot to upload a file would be tedious. It's needed in
both places.

Thanks,

Guillaume

Thanks,
> Eduard
>
> >
> > Thanks
> > -Vincent
> >
> > >
> > > Thanks,
> > >
> > > Guillaume
> > >
> > > On Tue, Feb 23, 2016 at 11:57 AM, Eduard Moraru
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > Found this issue http://jira.xwiki.org/browse/XWIKI-10026
> > > >
> > > > However, as far as I have tested it, it works. Taking a screenshot,
> > copying
> > > > it to the clicpboard and pasting in wysiwyg produces an
> [[image:data:]]
> > > > type image.
> > > >
> > > > Then, right clicking on an image on a website, selecting "Copy Image"
> > > > (Firefox) then going to wysiwyg and pasting produces an
> > [[image:http...]]
> > > > type image.
> > > >
> > > > So copy/paste is one thing, which seems to work pretty well, while
> > > > Drag is another and that would be a nice to have feature.
> > > >
> > > > Thanks,
> > > > Eduard
> > > >
> > > > On Tue, Feb 23, 2016 at 12:50 PM, vinc...@massol.net
> > > > wrote:
> > > >
> > > > > Hi Stuart,
> > > > >
> > > > > I agree that’s would be a very nice feature addition: ability to
> > drag and
> > > > > drop images as attachments directly on wiki pages (without having
> to
> > go
> > > > > through edit).
> > > > >
> > > > > Strangely I couldn’t find a jira issue for this. Would be awesome
> if
> > you
> > > > > could create one at http://jira.xwiki.org
> > > > >
> > > > > Thanks for the idea
> > > > > -Vincent
> > > > > On 23 Feb 2016 at 11:47:12, Stuart Stephen (
> > > > stuart.step...@tracegroup.com)
> > > > > wrote:
> > > > >
> > > > > Hi all,
> > > > >
> > > > > In various web applications these days it is now possible to copy
> and
> > > > > paste images into web pages which makes the process of adding an
> > image
> > > > to a
> > > > > document online so much easier as you do not need to save it off
> > > > somewhere,
> > > > > then upload it. Copy and paste makes the process so much more
> > efficient.
> > > > >
> > > > > See the upload feature on http://imgur.com/ for example, where
> they
> > also
> > > > > support drag and drop.
> > > > >
> > > > > Thanks,
> > > > > Stuart
> >
> > ___
> > users mailing list
> > users@xwiki.org
> > http://lists.xwiki.org/mailman/listinfo/users
> >
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Feature Request: Allow copy & paste of images into WYSIWYG editor

2016-02-23 Thread Guillaume Lerouge
Hi Vincent,

On Tue, Feb 23, 2016 at 12:22 PM, vinc...@massol.net <vinc...@massol.net>
wrote:

>
>
> On 23 Feb 2016 at 12:06:43, Guillaume Lerouge (guilla...@xwiki.com(mailto:
> guilla...@xwiki.com)) wrote:
>
> > Hi Stuart,
> >
> > thanks for your feedback. This is indeed a frequent request. In the
> current
> > WYSIWYG editor, it partially works (your image has to be available from a
> > public server).
> >
> > However, we added full support for this feature in the last version of
> the
> > CKEditor extension:
> >
> http://extensions.xwiki.org/xwiki/bin/view/Extension/CKEditor+Integration
> > => if you drag & drop an image in CKEditor, it is automatically attached
> to
> > the wiki page.
> >
> > Please also note that drag & drop of images currently work if you go to
> the
> > "attachments" tab of any page (while in view mode) and drop your image
> > there.
>
> hmm are you sure? I’m not aware of this feature. I just tested it and it
> didn’t work for me on 8.0M2.
>

Yes, it works if you drag & drop the file in the CKeditor edition window. I
just tried again and I got a "file successfully uploaded" confirmation
message and the file shows up in attachment. It also works with copy/paste,
I also get the confirmation message.

Are you sure you have version 1.2 of the CKEditor extension installed?

Thanks,

Guillaume

Thanks
> -Vincent
>
> >
> > Thanks,
> >
> > Guillaume
> >
> > On Tue, Feb 23, 2016 at 11:57 AM, Eduard Moraru
> > wrote:
> >
> > > Hi,
> > >
> > > Found this issue http://jira.xwiki.org/browse/XWIKI-10026
> > >
> > > However, as far as I have tested it, it works. Taking a screenshot,
> copying
> > > it to the clicpboard and pasting in wysiwyg produces an [[image:data:]]
> > > type image.
> > >
> > > Then, right clicking on an image on a website, selecting "Copy Image"
> > > (Firefox) then going to wysiwyg and pasting produces an
> [[image:http...]]
> > > type image.
> > >
> > > So copy/paste is one thing, which seems to work pretty well, while
> > > Drag is another and that would be a nice to have feature.
> > >
> > > Thanks,
> > > Eduard
> > >
> > > On Tue, Feb 23, 2016 at 12:50 PM, vinc...@massol.net
> > > wrote:
> > >
> > > > Hi Stuart,
> > > >
> > > > I agree that’s would be a very nice feature addition: ability to
> drag and
> > > > drop images as attachments directly on wiki pages (without having to
> go
> > > > through edit).
> > > >
> > > > Strangely I couldn’t find a jira issue for this. Would be awesome if
> you
> > > > could create one at http://jira.xwiki.org
> > > >
> > > > Thanks for the idea
> > > > -Vincent
> > > > On 23 Feb 2016 at 11:47:12, Stuart Stephen (
> > > stuart.step...@tracegroup.com)
> > > > wrote:
> > > >
> > > > Hi all,
> > > >
> > > > In various web applications these days it is now possible to copy and
> > > > paste images into web pages which makes the process of adding an
> image
> > > to a
> > > > document online so much easier as you do not need to save it off
> > > somewhere,
> > > > then upload it. Copy and paste makes the process so much more
> efficient.
> > > >
> > > > See the upload feature on http://imgur.com/ for example, where they
> also
> > > > support drag and drop.
> > > >
> > > > Thanks,
> > > > Stuart
>
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Feature Request: Allow copy & paste of images into WYSIWYG editor

2016-02-23 Thread Guillaume Lerouge
Hi Stuart,

thanks for your feedback. This is indeed a frequent request. In the current
WYSIWYG editor, it partially works (your image has to be available from a
public server).

However, we added full support for this feature in the last version of the
CKEditor extension:
http://extensions.xwiki.org/xwiki/bin/view/Extension/CKEditor+Integration
=> if you drag & drop an image in CKEditor, it is automatically attached to
the wiki page.

Please also note that drag & drop of images currently work if you go to the
"attachments" tab of any page (while in view mode) and drop your image
there.

Thanks,

Guillaume

On Tue, Feb 23, 2016 at 11:57 AM, Eduard Moraru <enygma2...@gmail.com>
wrote:

> Hi,
>
> Found this issue http://jira.xwiki.org/browse/XWIKI-10026
>
> However, as far as I have tested it, it works. Taking a screenshot, copying
> it to the clicpboard and pasting in wysiwyg produces an [[image:data:]]
> type image.
>
> Then, right clicking on an image on a website, selecting "Copy Image"
> (Firefox) then going to wysiwyg and pasting produces an [[image:http...]]
> type image.
>
> So copy/paste is one thing, which seems to work pretty well, while
> Drag is another and that would be a nice to have feature.
>
> Thanks,
> Eduard
>
> On Tue, Feb 23, 2016 at 12:50 PM, vinc...@massol.net <vinc...@massol.net>
> wrote:
>
> > Hi Stuart,
> >
> > I agree that’s would be a very nice feature addition: ability to drag and
> > drop images as attachments directly on wiki pages (without having to go
> > through edit).
> >
> > Strangely I couldn’t find a jira issue for this. Would be awesome if you
> > could create one at http://jira.xwiki.org
> >
> > Thanks for the idea
> > -Vincent
> > On 23 Feb 2016 at 11:47:12, Stuart Stephen (
> stuart.step...@tracegroup.com)
> > wrote:
> >
> > Hi all,
> >
> > In various web applications these days it is now possible to copy and
> > paste images into web pages which makes the process of adding an image
> to a
> > document online so much easier as you do not need to save it off
> somewhere,
> > then upload it. Copy and paste makes the process so much more efficient.
> >
> > See the upload feature on http://imgur.com/ for example, where they also
> > support drag and drop.
> >
> > Thanks,
> > Stuart
> > ___
> > users mailing list
> > users@xwiki.org
> > http://lists.xwiki.org/mailman/listinfo/users
> >
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] A tool to convert terminal pages to Nested Pages

2016-02-22 Thread Guillaume Delhumeau
Hello.

The version 0.3 has been released today.

The preferences and the rights of pages are now handled. So if you move a
page under an other one, causing different preferences or rights are
applied on that page, the tool will create preferences/rights on this page
to preserve the old settings.

You can test it there:
http://extensions.xwiki.org/xwiki/bin/view/Extension/Nested+Pages+Migrator+Application

Feedback are welcome.

Next objective: apply the plan on the wiki!

Thanks,

Guillaume

2016-02-09 19:47 GMT+01:00 Guillaume Delhumeau <
guillaume.delhum...@xwiki.com>:

> Hello.
>
> Charlie, you might have experienced http://jira.xwiki.org/browse/NPMIG-11.
> The good news is that I've fixed it.
>
> Now, I am happy to announce that I have released the version 0.2.1 of the
> application. It brings some new features:
> - the plan computation is done asynchronously
> - the ability to set manually the parent of a document has been implemented
> - 2 converted pages cannot have the same target (no collision).
> - more cases are handled.
>
> More informations there:
> http://extensions.xwiki.org/xwiki/bin/view/Extension/Nested+Pages+Migrator+Application#Hv0.2.1
>
> Thanks,
>
> Guillaume
>
> 2016-02-02 15:27 GMT+01:00 Guillaume Delhumeau <
> guillaume.delhum...@xwiki.com>:
>
>> Hi Charlie, and thanks for your feedback.
>>
>> I was considering using a job and displaying a progress bar during the
>> computation of the plan. Your example shows that we need it :)
>>
>> 2016-02-01 22:09 GMT+01:00 Charlie Mann <charlie.m...@aed.pro>:
>>
>>> I tried this extension out on our test server where we are simulating
>>> upgrading from 7.1.2 to 7.4.  It looks like it will be a very helpful
>>> tool
>>> in converting to the new nested pages scheme.  One thing I did notice is
>>> that one of our wikis that had a lot of nested pages under a space would
>>> never show the migration plan.  It was as though it was frozen.
>>>
>>> Charlie
>>>
>>> -Original Message-
>>> From: users [mailto:users-boun...@xwiki.org] On Behalf Of Guillaume
>>> Delhumeau
>>> Sent: Tuesday, January 26, 2016 2:43 AM
>>> To: XWiki Users <users@xwiki.org>
>>> Subject: Re: [xwiki-users] A tool to convert terminal pages to Nested
>>> Pages
>>>
>>> No opinion ?
>>>
>>> Thanks,
>>>
>>> 2016-01-20 9:53 GMT+01:00 Guillaume "Louis-Marie" Delhumeau <
>>> gdelhum...@xwiki.com>:
>>>
>>> > Hello, users of XWiki!
>>> >
>>> > I just have released the first version (alpha) of a new application to
>>> > help you convert your existing (terminal) pages to nested pages after
>>> > an upgrade to a recent wiki (7.4.x is the targeted version).
>>> >
>>> > This tool is available and can be installed directly with Extension
>>> > Manager. All informations are there:
>>> >
>>> > http://extensions.xwiki.org/xwiki/bin/view/Extension/Nested+Pages+Migr
>>> > ator+Application
>>> >
>>> > The application *does not currently apply the migration*. It only
>>> > computes a plan which say what actions should be done. The purpose,
>>> > right now, is only to test the tool without affecting any wiki.
>>> >
>>> > There is an option to simply convert your pages to nested pages
>>> > (Space.Page => Space.Page.WebHome) so they can have children (which
>>> > they cannot while being terminal). But, by default, the migrator tries
>>> > to preserve the existing hierarchy of pages (based on the "parent"
>>> > field of each page) by moving the pages under their parent page. So if
>>> > you have SpaceA.PageA with SpaceB.PageB as parent, the proposed
>>> > migration will be SpaceA.PageA => SpaceB.PageB.PageA.WebHome.
>>> >
>>> > In the future, the plan will also contain actions for preserving the
>>> > configured preferences (right now, if a page is moved, all the
>>> > preferences from its previous space are not applied to it anymore), and
>>> rights.
>>> >
>>> > This version is a first step in order to have a very complete tool. A
>>> > design document have been written with more informations (
>>> > http://design.xwiki.org/xwiki/bin/view/Proposal/UpgradeToNestedPages).
>>> >
>>> > I would love to see some of you testing this application, the user
>>> > interface, and judging the proposed plans. Don't hesi

[xwiki-users] Help spread the word about XWiki - add your review!

2016-02-22 Thread Guillaume Lerouge
Hi users,

I'm trying new ways to spread the word about XWiki. One approach that seems
to be popular right now are review websites such as Getapp and G2Crowd. For
instance Drupal has a page on G2Crowd
<https://www.g2crowd.com/products/drupal/reviews>, so I thought it could be
interesting to try it out too.

In order to see whether this could work well for XWiki, I have created a
page on G2Crowd: *https://www.g2crowd.com/products/xwiki/reviews
<https://www.g2crowd.com/products/xwiki/reviews>*

It would be very cool if you could spend a bit of time to add a review of
your experience with XWiki there!

Thanks and happy XWikiing,

Guillaume
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] A tool to convert terminal pages to Nested Pages

2016-02-09 Thread Guillaume Delhumeau
Hello.

Charlie, you might have experienced http://jira.xwiki.org/browse/NPMIG-11.
The good news is that I've fixed it.

Now, I am happy to announce that I have released the version 0.2.1 of the
application. It brings some new features:
- the plan computation is done asynchronously
- the ability to set manually the parent of a document has been implemented
- 2 converted pages cannot have the same target (no collision).
- more cases are handled.

More informations there:
http://extensions.xwiki.org/xwiki/bin/view/Extension/Nested+Pages+Migrator+Application#Hv0.2.1

Thanks,

Guillaume

2016-02-02 15:27 GMT+01:00 Guillaume Delhumeau <
guillaume.delhum...@xwiki.com>:

> Hi Charlie, and thanks for your feedback.
>
> I was considering using a job and displaying a progress bar during the
> computation of the plan. Your example shows that we need it :)
>
> 2016-02-01 22:09 GMT+01:00 Charlie Mann <charlie.m...@aed.pro>:
>
>> I tried this extension out on our test server where we are simulating
>> upgrading from 7.1.2 to 7.4.  It looks like it will be a very helpful tool
>> in converting to the new nested pages scheme.  One thing I did notice is
>> that one of our wikis that had a lot of nested pages under a space would
>> never show the migration plan.  It was as though it was frozen.
>>
>> Charlie
>>
>> -Original Message-
>> From: users [mailto:users-boun...@xwiki.org] On Behalf Of Guillaume
>> Delhumeau
>> Sent: Tuesday, January 26, 2016 2:43 AM
>> To: XWiki Users <users@xwiki.org>
>> Subject: Re: [xwiki-users] A tool to convert terminal pages to Nested
>> Pages
>>
>> No opinion ?
>>
>> Thanks,
>>
>> 2016-01-20 9:53 GMT+01:00 Guillaume "Louis-Marie" Delhumeau <
>> gdelhum...@xwiki.com>:
>>
>> > Hello, users of XWiki!
>> >
>> > I just have released the first version (alpha) of a new application to
>> > help you convert your existing (terminal) pages to nested pages after
>> > an upgrade to a recent wiki (7.4.x is the targeted version).
>> >
>> > This tool is available and can be installed directly with Extension
>> > Manager. All informations are there:
>> >
>> > http://extensions.xwiki.org/xwiki/bin/view/Extension/Nested+Pages+Migr
>> > ator+Application
>> >
>> > The application *does not currently apply the migration*. It only
>> > computes a plan which say what actions should be done. The purpose,
>> > right now, is only to test the tool without affecting any wiki.
>> >
>> > There is an option to simply convert your pages to nested pages
>> > (Space.Page => Space.Page.WebHome) so they can have children (which
>> > they cannot while being terminal). But, by default, the migrator tries
>> > to preserve the existing hierarchy of pages (based on the "parent"
>> > field of each page) by moving the pages under their parent page. So if
>> > you have SpaceA.PageA with SpaceB.PageB as parent, the proposed
>> > migration will be SpaceA.PageA => SpaceB.PageB.PageA.WebHome.
>> >
>> > In the future, the plan will also contain actions for preserving the
>> > configured preferences (right now, if a page is moved, all the
>> > preferences from its previous space are not applied to it anymore), and
>> rights.
>> >
>> > This version is a first step in order to have a very complete tool. A
>> > design document have been written with more informations (
>> > http://design.xwiki.org/xwiki/bin/view/Proposal/UpgradeToNestedPages).
>> >
>> > I would love to see some of you testing this application, the user
>> > interface, and judging the proposed plans. Don't hesitate to give your
>> > feedbacks. Please tell me if you have other ideas that I have not
>> > listed in the design document, like features that I have not think
>> about.
>> >
>> > Thanks a lot,
>> > --
>> > Guillaume Delhumeau (gdelhum...@xwiki.com) Research & Development
>> > Engineer at XWiki SAS Committer on the XWiki.org project
>> >
>>
>>
>>
>> --
>> Guillaume Delhumeau (gdelhum...@xwiki.com)
>> Research & Development Engineer at XWiki SAS
>> Committer on the XWiki.org project
>> ___
>> users mailing list
>> users@xwiki.org
>> http://lists.xwiki.org/mailman/listinfo/users
>>
>> ___
>> users mailing list
>> users@xwiki.org
>> http://lists.xwiki.org/mailman/listinfo/users
>>
>
>
>
> --
> Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
> Research & Development Engineer at XWiki SAS
> Committer on the XWiki.org project
>



-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] A tool to convert terminal pages to Nested Pages

2016-02-02 Thread Guillaume Delhumeau
Hi Charlie, and thanks for your feedback.

I was considering using a job and displaying a progress bar during the
computation of the plan. Your example shows that we need it :)

2016-02-01 22:09 GMT+01:00 Charlie Mann <charlie.m...@aed.pro>:

> I tried this extension out on our test server where we are simulating
> upgrading from 7.1.2 to 7.4.  It looks like it will be a very helpful tool
> in converting to the new nested pages scheme.  One thing I did notice is
> that one of our wikis that had a lot of nested pages under a space would
> never show the migration plan.  It was as though it was frozen.
>
> Charlie
>
> -Original Message-
> From: users [mailto:users-boun...@xwiki.org] On Behalf Of Guillaume
> Delhumeau
> Sent: Tuesday, January 26, 2016 2:43 AM
> To: XWiki Users <users@xwiki.org>
> Subject: Re: [xwiki-users] A tool to convert terminal pages to Nested Pages
>
> No opinion ?
>
> Thanks,
>
> 2016-01-20 9:53 GMT+01:00 Guillaume "Louis-Marie" Delhumeau <
> gdelhum...@xwiki.com>:
>
> > Hello, users of XWiki!
> >
> > I just have released the first version (alpha) of a new application to
> > help you convert your existing (terminal) pages to nested pages after
> > an upgrade to a recent wiki (7.4.x is the targeted version).
> >
> > This tool is available and can be installed directly with Extension
> > Manager. All informations are there:
> >
> > http://extensions.xwiki.org/xwiki/bin/view/Extension/Nested+Pages+Migr
> > ator+Application
> >
> > The application *does not currently apply the migration*. It only
> > computes a plan which say what actions should be done. The purpose,
> > right now, is only to test the tool without affecting any wiki.
> >
> > There is an option to simply convert your pages to nested pages
> > (Space.Page => Space.Page.WebHome) so they can have children (which
> > they cannot while being terminal). But, by default, the migrator tries
> > to preserve the existing hierarchy of pages (based on the "parent"
> > field of each page) by moving the pages under their parent page. So if
> > you have SpaceA.PageA with SpaceB.PageB as parent, the proposed
> > migration will be SpaceA.PageA => SpaceB.PageB.PageA.WebHome.
> >
> > In the future, the plan will also contain actions for preserving the
> > configured preferences (right now, if a page is moved, all the
> > preferences from its previous space are not applied to it anymore), and
> rights.
> >
> > This version is a first step in order to have a very complete tool. A
> > design document have been written with more informations (
> > http://design.xwiki.org/xwiki/bin/view/Proposal/UpgradeToNestedPages).
> >
> > I would love to see some of you testing this application, the user
> > interface, and judging the proposed plans. Don't hesitate to give your
> > feedbacks. Please tell me if you have other ideas that I have not
> > listed in the design document, like features that I have not think about.
> >
> > Thanks a lot,
> > --
> > Guillaume Delhumeau (gdelhum...@xwiki.com) Research & Development
> > Engineer at XWiki SAS Committer on the XWiki.org project
> >
>
>
>
> --
> Guillaume Delhumeau (gdelhum...@xwiki.com)
> Research & Development Engineer at XWiki SAS
> Committer on the XWiki.org project
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>



-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] A tool to convert terminal pages to Nested Pages

2016-01-26 Thread Guillaume Delhumeau
No opinion ?

Thanks,

2016-01-20 9:53 GMT+01:00 Guillaume "Louis-Marie" Delhumeau <
gdelhum...@xwiki.com>:

> Hello, users of XWiki!
>
> I just have released the first version (alpha) of a new application to
> help you convert your existing (terminal) pages to nested pages after an
> upgrade to a recent wiki (7.4.x is the targeted version).
>
> This tool is available and can be installed directly with Extension
> Manager. All informations are there:
>
> http://extensions.xwiki.org/xwiki/bin/view/Extension/Nested+Pages+Migrator+Application
>
> The application *does not currently apply the migration*. It only
> computes a plan which say what actions should be done. The purpose, right
> now, is only to test the tool without affecting any wiki.
>
> There is an option to simply convert your pages to nested pages
> (Space.Page => Space.Page.WebHome) so they can have children (which they
> cannot while being terminal). But, by default, the migrator tries to
> preserve the existing hierarchy of pages (based on the "parent" field of
> each page) by moving the pages under their parent page. So if you have
> SpaceA.PageA with SpaceB.PageB as parent, the proposed migration will be
> SpaceA.PageA => SpaceB.PageB.PageA.WebHome.
>
> In the future, the plan will also contain actions for preserving the
> configured preferences (right now, if a page is moved, all the preferences
> from its previous space are not applied to it anymore), and rights.
>
> This version is a first step in order to have a very complete tool. A
> design document have been written with more informations (
> http://design.xwiki.org/xwiki/bin/view/Proposal/UpgradeToNestedPages).
>
> I would love to see some of you testing this application, the user
> interface, and judging the proposed plans. Don't hesitate to give your
> feedbacks. Please tell me if you have other ideas that I have not listed in
> the design document, like features that I have not think about.
>
> Thanks a lot,
> --
> Guillaume Delhumeau (gdelhum...@xwiki.com)
> Research & Development Engineer at XWiki SAS
> Committer on the XWiki.org project
>



-- 
Guillaume Delhumeau (gdelhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] How to display strucured Data

2016-01-21 Thread Guillaume Delhumeau
Example:
https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwiki-platform-wiki/xwiki-platform-wiki-default/src/main/java/org/xwiki/wiki/internal/descriptor/builder/DefaultWikiDescriptorBuilder.java#L254-254

2016-01-21 14:47 GMT+01:00 Guillaume Delhumeau <gdelhum...@xwiki.com>:

> When you save a document with the Java API, you need to set a content
> author to the document. Otherwise, the change is saved with "Unknow User",
> which has not the right to write scripts.
>
> 2016-01-21 12:59 GMT+01:00 Giordano Ninonà <giordano.nin...@gmail.com>:
>
>> P.S. I am working on Java, thus in each page I see that the last
>> modification was performed by "Unknown user".
>>
>> 2016-01-21 12:58 GMT+01:00 Giordano Ninonà <giordano.nin...@gmail.com>:
>>
>> > Hi users,
>> >
>> > Searching and reading plenty of material, I have understood some of the
>> > XClass and Sheet behaviour, but I have still some problems because,
>> even if
>> > I have created an XClass and a related Sheet (binded adding an
>> > "XWiki.ClassSheetBinding" object to the XClass document) and after have
>> > inserted in the sheet the velocity script:
>> >
>> > {{velocity}}\n
>> >#set($class = $doc.getObject('MySpace.myXClass').xWikiClass)
>> >#foreach($prop in $class.properties)
>> > === $prop.prettyName ===
>> > :$doc.display($prop.getName())\n";
>> > #end
>> > {{/velocity}}\n";
>> >
>> > When I update my pages in each pages I get this Velocity error:
>> > "
>> >
>> > org.xwiki.rendering.macro.MacroExecutionException: The execution of the
>> [velocity] script macro is not allowed. Check the rights of its last author
>> or the parameters if it's rendered from another script.
>> >   at
>> org.xwiki.rendering.macro.script.AbstractScriptMacro.execute(AbstractScriptMacro.java:178)
>> >   at
>> org.xwiki.rendering.macro.script.AbstractScriptMacro.execute(AbstractScriptMacro.java:58)
>> >   at
>> org.xwiki.rendering.internal.transformation.macro.MacroTransformation.transform(MacroTransformation.java:269)
>> >   at
>> org.xwiki.rendering.internal.transformation.DefaultRenderingContext.transformInContext(DefaultRenderingContext.java:183)
>> >   at
>> org.xwiki.rendering.internal.transformation.DefaultTransformationManager.performTransformations(DefaultTransformationManager.java:95)
>> >   at
>> org.xwiki.display.internal.DocumentContentDisplayer.display(DocumentContentDisplayer.java:253)
>> >   at
>> org.xwiki.display.internal.DocumentContentDisplayer.display(DocumentContentDisplayer.java:126)
>> >   at
>> org.xwiki.display.internal.DocumentContentDisplayer.display(DocumentContentDisplayer.java:56)
>> >   at
>> org.xwiki.display.internal.DefaultDocumentDisplayer.display(DefaultDocumentDisplayer.java:96)
>> >   at
>> org.xwiki.display.internal.DefaultDocumentDisplayer.display(DefaultDocumentDisplayer.java:39)
>> >   at
>> org.xwiki.sheet.internal.SheetDocumentDisplayer.display(SheetDocumentDisplayer.java:229)
>> >   at
>> org.xwiki.sheet.internal.SheetDocumentDisplayer.applySheet(SheetDocumentDisplayer.java:209)
>> >   at
>> org.xwiki.sheet.internal.SheetDocumentDisplayer.maybeDisplayWithSheet(SheetDocumentDisplayer.java:164)
>> >   at
>> org.xwiki.sheet.internal.SheetDocumentDisplayer.display(SheetDocumentDisplayer.java:102)
>> >   at
>> org.xwiki.sheet.internal.SheetDocumentDisplayer.display(SheetDocumentDisplayer.java:50)
>> >   at
>> org.xwiki.display.internal.ConfiguredDocumentDisplayer.display(ConfiguredDocumentDisplayer.java:68)
>> >   at
>> org.xwiki.display.internal.ConfiguredDocumentDisplayer.display(ConfiguredDocumentDisplayer.java:42)
>> >   at
>> com.xpn.xwiki.doc.XWikiDocument.getRenderedContent(XWikiDocument.java:1164)
>> >   at
>> com.xpn.xwiki.doc.XWikiDocument.getRenderedContent(XWikiDocument.java:1127)
>> >   at
>> com.xpn.xwiki.doc.XWikiDocument.getRenderedContent(XWikiDocument.java:1179)
>> >   at
>> com.xpn.xwiki.api.Document.getRenderedContent(Document.java:692)
>> >   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> >   at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> >   at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> >   at ja

Re: [xwiki-users] How to display strucured Data

2016-01-21 Thread Guillaume Delhumeau
achedChain.doFilter(ServletHandler.java:1652)
> >   at
> org.xwiki.container.servlet.filters.internal.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:208)
> >   at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
> >   at
> org.xwiki.container.servlet.filters.internal.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:111)
> >   at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
> >   at
> org.xwiki.resource.servlet.RoutingFilter.doFilter(RoutingFilter.java:137)
> >   at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
> >   at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
> >   at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> >   at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
> >   at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
> >   at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
> >   at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
> >   at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
> >   at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
> >   at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> >   at
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)
> >   at
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110)
> >   at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> >   at org.eclipse.jetty.server.Server.handle(Server.java:499)
> >   at
> org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310)
> >   at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
> >   at
> org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
> >   at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
> >   at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
> >   at java.lang.Thread.run(Thread.java:745)"
> >
> > Thanks,
> > Giordano.
> >
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>



-- 
Guillaume Delhumeau (gdelhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


[xwiki-users] A tool to convert terminal pages to Nested Pages

2016-01-20 Thread Guillaume "Louis-Marie" Delhumeau
Hello, users of XWiki!

I just have released the first version (alpha) of a new application to help
you convert your existing (terminal) pages to nested pages after an upgrade
to a recent wiki (7.4.x is the targeted version).

This tool is available and can be installed directly with Extension
Manager. All informations are there:
http://extensions.xwiki.org/xwiki/bin/view/Extension/Nested+Pages+Migrator+Application

The application *does not currently apply the migration*. It only computes
a plan which say what actions should be done. The purpose, right now, is
only to test the tool without affecting any wiki.

There is an option to simply convert your pages to nested pages (Space.Page
=> Space.Page.WebHome) so they can have children (which they cannot while
being terminal). But, by default, the migrator tries to preserve the
existing hierarchy of pages (based on the "parent" field of each page) by
moving the pages under their parent page. So if you have SpaceA.PageA with
SpaceB.PageB as parent, the proposed migration will be SpaceA.PageA =>
SpaceB.PageB.PageA.WebHome.

In the future, the plan will also contain actions for preserving the
configured preferences (right now, if a page is moved, all the preferences
from its previous space are not applied to it anymore), and rights.

This version is a first step in order to have a very complete tool. A
design document have been written with more informations (
http://design.xwiki.org/xwiki/bin/view/Proposal/UpgradeToNestedPages).

I would love to see some of you testing this application, the user
interface, and judging the proposed plans. Don't hesitate to give your
feedbacks. Please tell me if you have other ideas that I have not listed in
the design document, like features that I have not think about.

Thanks a lot,
-- 
Guillaume Delhumeau (gdelhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Dropdown menù with child pages

2016-01-14 Thread Guillaume "Louis-Marie" Delhumeau
Hello.

You need to look at:
* the query module:
http://extensions.xwiki.org/xwiki/bin/view/Extension/Query+Module
* the bootstrap's documentation about dropdowns:
http://getbootstrap.com/javascript/#dropdowns
* the HTML macro:
http://extensions.xwiki.org/xwiki/bin/view/Extension/HTML+Macro
* the children viewer to look at the used query:
https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwiki-platform-web/src/main/webapp/templates/children.vm#L70-70


2016-01-14 10:40 GMT+01:00 Giordano Ninonà <giordano.nin...@gmail.com>:

> Hi users,
>
> Today I am wondering about how to create, inside a wiki page, a drop down
> menù containing all the child pages of another space.
>
> Any idea?
> Giordano.
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>



-- 
Guillaume Delhumeau (gdelhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] How retrieve terminal pages

2016-01-12 Thread Guillaume "Louis-Marie" Delhumeau
Hi Giordano.

Is it possible for you to modify your method to have a list of spaces
instead of the space name? Or better: having a DocumentReference as input?

If not, it means that you need to parse your "wikiSpace" input, get the
list of spaces from it, and then create a clean DocumentReference.

You should use a SpaceReferenceResolver to get a clean space reference.

Example:

@Inject
@Named("current")
private SpaceReferenceResolver spaceReferenceResolver;

public void myMethod(String wikiName, String wikiSpace, String wikiPage) {
  // resolve the spaces:
  SpaceReference spaceRef = spaceReferenceResolver.resolve(wikiSpace, new
WikiReference(wikiName));
  // Create a clean DocumentReference:
  DocumentReference docRef = new DocumentReference(wikiPage, spaceRef);
  // Work with the docRef
  XWikiDocument doc = xwiki.getDocument(docRef, xcontext);
  // ...
}

Similar code in Groovy:

{{groovy}}
def spaceReferenceResolver =
services.component.getInstance(org.xwiki.model.reference.SpaceReferenceResolver.TYPE_STRING,
"current");
def spaceRef = spaceReferenceResolver.resolve("AB.CD\\.E.F", new
org.xwiki.model.reference.WikiReference('hello'));
def docRef = new org.xwiki.model.reference.DocumentReference('page',
spaceRef);
{{/groovy}}

I hope it helps,
Guillaume


2016-01-12 16:27 GMT+01:00 Giordano Ninonà <giordano.nin...@gmail.com>:

> Hi users,
>
> I have a problem with my Java component. I have a hjava method wich take as
> input 3 strings: wikiName, wikiSpace and the wiki page to retrieve the doc,
> thus the content and perform modification.
>
> Ok, when I try to delete a terminal page inside a nested page, there is no
> problem, the component retrieve the page's document and can delete it, it
> works!
>
> But when I want to delete a terminal page that is inside a nested page
> which is inside another nested page it stops working. The point is that I
> can't retrieve the terminal page's document, probably because of the
> wikiSpace variable.
> I have tried "NestedPage1.NestedPage2" but it is not woking at all, it is
> keep creating and successively deleting new documents(thus pages).
>
> Thank you,
> Giordano.
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>



-- 
Guillaume Delhumeau (gdelhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] How retrieve terminal pages

2016-01-12 Thread Guillaume "Louis-Marie" Delhumeau
I think you only need xwiki-platform-model as a dependency of your module.

You should paste your code on http://pastebin.com/ to enable us to
understand what is going wrong.

2016-01-12 17:43 GMT+01:00 Giordano Ninonà <giordano.nin...@gmail.com>:

> I got the same behaavior also with the modifications suggested by
> Guillaume.
>
> Any other ideas?
>
> Giordano.
>
> 2016-01-12 17:16 GMT+01:00 Giordano Ninonà <giordano.nin...@gmail.com>:
>
> > Hi Guillaume,
> >
> > Thank you a lot, that really helps! The only thing is which library I
> > should import :
> >
> >1. org.xwiki.model.reference
> >2. org.wiki.rendering.wikimodel
> >
> > Moreover, there is a place to find how this "reference-game" works? I
> mean
> > that I've found Entity References, Document References, SpaceReferecens,
> > Wiki References but I don't understand how this works.
> >
> >
> > Thank you,
> >
> > Giordano
> >
> > 2016-01-12 17:05 GMT+01:00 Guillaume "Louis-Marie" Delhumeau <
> > gdelhum...@xwiki.com>:
> >
> >> Hi Giordano.
> >>
> >> Is it possible for you to modify your method to have a list of spaces
> >> instead of the space name? Or better: having a DocumentReference as
> input?
> >>
> >> If not, it means that you need to parse your "wikiSpace" input, get the
> >> list of spaces from it, and then create a clean DocumentReference.
> >>
> >> You should use a SpaceReferenceResolver to get a clean space reference.
> >>
> >> Example:
> >>
> >> @Inject
> >> @Named("current")
> >> private SpaceReferenceResolver spaceReferenceResolver;
> >>
> >> public void myMethod(String wikiName, String wikiSpace, String
> wikiPage) {
> >>   // resolve the spaces:
> >>   SpaceReference spaceRef = spaceReferenceResolver.resolve(wikiSpace,
> new
> >> WikiReference(wikiName));
> >>   // Create a clean DocumentReference:
> >>   DocumentReference docRef = new DocumentReference(wikiPage, spaceRef);
> >>   // Work with the docRef
> >>   XWikiDocument doc = xwiki.getDocument(docRef, xcontext);
> >>   // ...
> >> }
> >>
> >> Similar code in Groovy:
> >>
> >> {{groovy}}
> >> def spaceReferenceResolver =
> >>
> >>
> services.component.getInstance(org.xwiki.model.reference.SpaceReferenceResolver.TYPE_STRING,
> >> "current");
> >> def spaceRef = spaceReferenceResolver.resolve("AB.CD\\.E.F", new
> >> org.xwiki.model.reference.WikiReference('hello'));
> >> def docRef = new org.xwiki.model.reference.DocumentReference('page',
> >> spaceRef);
> >> {{/groovy}}
> >>
> >> I hope it helps,
> >> Guillaume
> >>
> >>
> >> 2016-01-12 16:27 GMT+01:00 Giordano Ninonà <giordano.nin...@gmail.com>:
> >>
> >> > Hi users,
> >> >
> >> > I have a problem with my Java component. I have a hjava method wich
> >> take as
> >> > input 3 strings: wikiName, wikiSpace and the wiki page to retrieve the
> >> doc,
> >> > thus the content and perform modification.
> >> >
> >> > Ok, when I try to delete a terminal page inside a nested page, there
> is
> >> no
> >> > problem, the component retrieve the page's document and can delete it,
> >> it
> >> > works!
> >> >
> >> > But when I want to delete a terminal page that is inside a nested page
> >> > which is inside another nested page it stops working. The point is
> that
> >> I
> >> > can't retrieve the terminal page's document, probably because of the
> >> > wikiSpace variable.
> >> > I have tried "NestedPage1.NestedPage2" but it is not woking at all, it
> >> is
> >> > keep creating and successively deleting new documents(thus pages).
> >> >
> >> > Thank you,
> >> > Giordano.
> >> > ___
> >> > users mailing list
> >> > users@xwiki.org
> >> > http://lists.xwiki.org/mailman/listinfo/users
> >> >
> >>
> >>
> >>
> >> --
> >> Guillaume Delhumeau (gdelhum...@xwiki.com)
> >> Research & Development Engineer at XWiki SAS
> >> Committer on the XWiki.org project
> >> ___
> >> users mailing list
> >> users@xwiki.org
> >> http://lists.xwiki.org/mailman/listinfo/users
> >>
> >
> >
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>



-- 
Guillaume Delhumeau (gdelhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] How retrieve terminal pages

2016-01-12 Thread Guillaume "Louis-Marie" Delhumeau
BTW the documentation is there:
http://extensions.xwiki.org/xwiki/bin/view/Extension/Model+Module

2016-01-12 17:54 GMT+01:00 Guillaume "Louis-Marie" Delhumeau <
gdelhum...@xwiki.com>:

> I think you only need xwiki-platform-model as a dependency of your module.
>
> You should paste your code on http://pastebin.com/ to enable us to
> understand what is going wrong.
>
> 2016-01-12 17:43 GMT+01:00 Giordano Ninonà <giordano.nin...@gmail.com>:
>
>> I got the same behaavior also with the modifications suggested by
>> Guillaume.
>>
>> Any other ideas?
>>
>> Giordano.
>>
>> 2016-01-12 17:16 GMT+01:00 Giordano Ninonà <giordano.nin...@gmail.com>:
>>
>> > Hi Guillaume,
>> >
>> > Thank you a lot, that really helps! The only thing is which library I
>> > should import :
>> >
>> >1. org.xwiki.model.reference
>> >2. org.wiki.rendering.wikimodel
>> >
>> > Moreover, there is a place to find how this "reference-game" works? I
>> mean
>> > that I've found Entity References, Document References, SpaceReferecens,
>> > Wiki References but I don't understand how this works.
>> >
>> >
>> > Thank you,
>> >
>> > Giordano
>> >
>> > 2016-01-12 17:05 GMT+01:00 Guillaume "Louis-Marie" Delhumeau <
>> > gdelhum...@xwiki.com>:
>> >
>> >> Hi Giordano.
>> >>
>> >> Is it possible for you to modify your method to have a list of spaces
>> >> instead of the space name? Or better: having a DocumentReference as
>> input?
>> >>
>> >> If not, it means that you need to parse your "wikiSpace" input, get the
>> >> list of spaces from it, and then create a clean DocumentReference.
>> >>
>> >> You should use a SpaceReferenceResolver to get a clean space reference.
>> >>
>> >> Example:
>> >>
>> >> @Inject
>> >> @Named("current")
>> >> private SpaceReferenceResolver spaceReferenceResolver;
>> >>
>> >> public void myMethod(String wikiName, String wikiSpace, String
>> wikiPage) {
>> >>   // resolve the spaces:
>> >>   SpaceReference spaceRef = spaceReferenceResolver.resolve(wikiSpace,
>> new
>> >> WikiReference(wikiName));
>> >>   // Create a clean DocumentReference:
>> >>   DocumentReference docRef = new DocumentReference(wikiPage, spaceRef);
>> >>   // Work with the docRef
>> >>   XWikiDocument doc = xwiki.getDocument(docRef, xcontext);
>> >>   // ...
>> >> }
>> >>
>> >> Similar code in Groovy:
>> >>
>> >> {{groovy}}
>> >> def spaceReferenceResolver =
>> >>
>> >>
>> services.component.getInstance(org.xwiki.model.reference.SpaceReferenceResolver.TYPE_STRING,
>> >> "current");
>> >> def spaceRef = spaceReferenceResolver.resolve("AB.CD\\.E.F", new
>> >> org.xwiki.model.reference.WikiReference('hello'));
>> >> def docRef = new org.xwiki.model.reference.DocumentReference('page',
>> >> spaceRef);
>> >> {{/groovy}}
>> >>
>> >> I hope it helps,
>> >> Guillaume
>> >>
>> >>
>> >> 2016-01-12 16:27 GMT+01:00 Giordano Ninonà <giordano.nin...@gmail.com
>> >:
>> >>
>> >> > Hi users,
>> >> >
>> >> > I have a problem with my Java component. I have a hjava method wich
>> >> take as
>> >> > input 3 strings: wikiName, wikiSpace and the wiki page to retrieve
>> the
>> >> doc,
>> >> > thus the content and perform modification.
>> >> >
>> >> > Ok, when I try to delete a terminal page inside a nested page, there
>> is
>> >> no
>> >> > problem, the component retrieve the page's document and can delete
>> it,
>> >> it
>> >> > works!
>> >> >
>> >> > But when I want to delete a terminal page that is inside a nested
>> page
>> >> > which is inside another nested page it stops working. The point is
>> that
>> >> I
>> >> > can't retrieve the terminal page's document, probably because of the
>> >> > wikiSpace variable.
>> >> > I have tried "NestedPage1.NestedPage2" but it is not woking at all,
>> it
>> >> is
>> >> > keep creating and successively deleting new documents(thus pages).
>> >> >
>> >> > Thank you,
>> >> > Giordano.
>> >> > ___
>> >> > users mailing list
>> >> > users@xwiki.org
>> >> > http://lists.xwiki.org/mailman/listinfo/users
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Guillaume Delhumeau (gdelhum...@xwiki.com)
>> >> Research & Development Engineer at XWiki SAS
>> >> Committer on the XWiki.org project
>> >> ___
>> >> users mailing list
>> >> users@xwiki.org
>> >> http://lists.xwiki.org/mailman/listinfo/users
>> >>
>> >
>> >
>> ___
>> users mailing list
>> users@xwiki.org
>> http://lists.xwiki.org/mailman/listinfo/users
>>
>
>
>
> --
> Guillaume Delhumeau (gdelhum...@xwiki.com)
> Research & Development Engineer at XWiki SAS
> Committer on the XWiki.org project
>



-- 
Guillaume Delhumeau (gdelhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] [Brainstorming] Home Page concept (was Re: New Page Has No Parent)

2016-01-06 Thread Guillaume Lerouge
Hi,

On Wed, Jan 6, 2016 at 1:54 PM, Eduard Moraru <enygma2...@gmail.com> wrote:

> Hi Vincent,
>
> Thanks for creating a new thread, since that`s what I should have done
> myself.
>
> I approached this as a discussion about what is the good/sensible default
> that better fits 80-90% of the user's needs, as opposed to not having this
> default and the user ending up with "Main" (or whetever else) everywhere
> (i.e. cons of not doing Use Case 1).
>
> On Wed, Jan 6, 2016 at 10:39 AM, vinc...@massol.net <vinc...@massol.net>
> wrote:
>
> > Hi Edy and all,
> >
> > On 5 Jan 2016 at 11:52:24, Eduard Moraru (enygma2...@gmail.com(mailto:
> > enygma2...@gmail.com)) wrote:
> >
> > > Hi Randy,
> > >
> > > From your choice of words (and your continued usage of the now
> deprecated
> > > "spaces" macro on the homepage, as observed in the screenshot you`ve
> > > provided), I understand that you still see things in terms of "creating
> > > spaces" and "creating documents inside spaces" in 7.4 and, IMO, that`s
> > > really the issue.
> > >
> > > In case you`ve missed it from the release notes, starting with 7.2,
> we`ve
> > > introduced the notion of Nested Pages [1], which means that you no
> longer
> > > have the notion of "pages inside spaces", but always "pages inside
> > pages".
> > > Technically, it is actually implemented by always creating a "space"
> when
> > > you create a page from the UI, but the user should see it as if he is
> > > always creating a page.
> > >
> > > = Use Case 1 =
> > >
> > > When your users go to your homepage and create a new page "under the
> Main
> > > space", they are actually creating a nested page (old "space"), under
> the
> > > homepage (document called "Main") of your wiki. If you change [2] the
> > > homepage of your wiki to point to a different document instead (say
> > > "Some.Other.Homepage"), I`m fairly sure that you do not want your users
> > to
> > > start creating new pages as children of that page (e.g.
> > > "Some.Other.Homepage.NewUserPage"), because that is what the
> alternative
> > > would lead to.
> > >
> > > The logic behind the original decision of handling the homepage
> > differently
> > > was that, even as Guillaume was hinting, the homepage is seen as the
> > "root"
> > > of your wiki. Creating a page from the root should result in creating
> top
> > > level pages, not child pages. If you wanted to create a child page of
> > > something from the homepage, you would explicitly do so by selecting a
> > > parent. Not selecting a parent while on the homepage would logically
> > imply
> > > that you want to create a page in the wiki (i.e. top page).
> > >
> > > I`m curious why do you find it normal the other way around, i.e.
> landing
> > on
> > > the wiki (i.e. not navigating somewhere in particular) + creating a new
> > > page => resulting in creating a child page of the "Main" page (which
> > > happens to be the homepage).
> > >
> > > If you always create child pages of the homepage ("Main" page), on the
> > long
> > > run, all your URLs will be /Main/This/Page, /Main/That/Page,
> > > /Main/That/Other/Page, etc... but ultimately, what is this "Main", and
> > why
> > > is it that important to drag it along in all your page URLs? (of
> course,
> > > again, if you change your homepage to "Some.Other.Homepage", all your
> > urls
> > > will be prefixed by that!)
> > >
> > > = Use case 2 =
> > >
> > > Now, another way of looking at this would be that, for some reason, you
> > > *really* want to keep all your content under some top level page (e.g.
> as
> > > Vincent suggested, a "Content" container page), perhaps to separate it
> > from
> > > applications (which, for historic reasons, currently are also located
> in
> > > the top level) like Blog, Sandbox, etc. or any other reason.
> > >
> > > The only limitation in this usecase is if you also want to use that
> > > container page ("Main", "Content", etc.) as your homepage. In this
> case,
> > > indeed, I see no other solution but to modify the createinline.vm
> > template
> > > or for us to drop this behavior altogether.

Re: [xwiki-users] New Page Has No Parent

2016-01-04 Thread Guillaume Lerouge
Hi Randy,

thanks for your feedback on this! I'm happy to see that I wasn't the only
one who found this behavior counter-intuitive. It's very, very weird that
page creation from the home page behaves differently from everywhere else
on the wiki. It's particularly bad since that's the page users always end
up going back to. But the thing is, without this behavior it's not clear
how users would be able to create new top-level spaces... So if we bring
back the old behavior as-is we'd still have to find a solution for
top-level space creation.

A suggestion I had now that nested spaces are activated by default was to
make the home page of the wiki be "above" every other space. Said
differently, the home page would reside directly at
https:///xwiki/bin/view/
without anything else being mentioned. From that page you'd be able to
create top-level spaces, and every other page would behave as expected,
including Main.WebHome. I think this is what would feel the most natural,
but it causes many underlying issues, notably because a page with no
document reference cannot really exist in XWiki right now.

Note that we could also offer migration scripts, as discussed below, so
that content wouldn't be created in Main to begin with, but this still
leaves the problem open for old wikis with no clear content migration path.
Maybe we should strongly warn users not to upgrade to 7.4 from versions =<
7.1 without a lot of testing and until we provide a good migration path. We
could also start a page listing known issues.

Thanks,

Guillaume

On Wed, Dec 30, 2015 at 2:35 PM, Randy Havens <
randy.hav...@cityofrochester.gov> wrote:

> > Yes that’s correct. If you go in the main space and add a page it’ll
> correctly create a child page inside the Main space.
>
> How do I “go in the main space”? Until now, I was in the main space by
> default when I was at the homepage of my wiki. If I click on “Main” in the
> list of spaces, it takes me to that same homepage. From there, if I add a
> page it has no parent. If I click on another space in that list, it takes
> me to that space’s homepage. From there, if I create a new page the parent
> is that space. It’s not consistent.
>
> > For my information, could you explain why you wish that all your users
> create content pages in the Main space?
>
> That’s how it has been working since I first installed XWiki. I installed
> 6.3, and since then (up until pre-7.3) all new pages defaulted into the
> Main space unless the user entered a different space. I thought that was
> normal, but you make it sound like that’s not normal.
>
> > Why not, for example, have a Content space at the top level or some more
> semantic top level space name under which you’d put all your content?
>
> I thought about that as well, but then I need to transfer everything
> currently in “Main” into another space. I guess that would be possible, but
> I’d have to copy it all into the “Content” space and then delete it from
> “Main”. (Which might not be a bad idea anyway for other reasons)
>
> > One solution of course would be to introduce a configuration option,
> allowing to choose the reference of the Space into which to create new
> pages by default when clicking on “+” on the Home page.
>
> I think this is the best solution, honestly. Mostly because of the way
> that it worked before, but also because it would give the administrators an
> important choice.
>
> > I think I’d lean to having pages created in the Main space by default,
> as we had before.
>
> I would agree.
>
>
>
> Thanks for the reply and suggestions,
> Randy
>
>
>
>
> --
> View this message in context:
> http://xwiki.475771.n2.nabble.com/New-Page-Has-No-Parent-tp7597344p7597351.html
> Sent from the XWiki- Users mailing list archive at Nabble.com.
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] New Page Has No Parent

2015-12-30 Thread Guillaume "Louis-Marie" Delhumeau
At least we should not propose to create a top-level page if the user has
not the right to do it.

2015-12-30 9:07 GMT+01:00 vinc...@massol.net <vinc...@massol.net>:

> Hi Randy,
>
>
> On 29 Dec 2015 at 18:52:05, Randy Havens (randy.hav...@cityofrochester.gov
> (mailto:randy.hav...@cityofrochester.gov)) wrote:
>
> > That seems very counter-intuitive. It also is very inconsistent. It
> creates a
> > child by default when within a specific space, but not when on the home
> > page?
>
> Yes that’s correct. If you go in the main space and add a page it’ll
> correctly create a child page inside the Main space.
>
> > I somewhat follow the thought process behind this, but it causes a
> > huge inconsistency and a lot of confusion. From the link that you sent,
> it
> > seems that I am not alone in thinking that the old way was more
> intuitive.
> >
> > How can I make it so that it returns to that functionality? I am not
> going
> > to be able to instruct all of my users to put "Main" in the location
> before
> > creating a new page. Especially since some users have access to multiple
> > spaces, and it works as expected in other spaces.
>
> It also works like this for the Main space :) It’s only the Home page that
> is affected.
>
> For my information, could you explain why you wish that all your users
> create content pages in the Main space?
>
> Why not, for example, have a Content space at the top level or some more
> semantic top level space name under which you’d put all your content?
>
> Maybe the real underlying issue is that you wish to control where your
> users put content by default (whether in the Main space or some other
> Content space)? And you’d wish to avoid having lots of top level spaces
> created “by mistake”?
>
> On our side we have to balance the following 2 use cases:
> * UC1: Create new top level spaces by default when on the home page
> * UC2: Create new pages inside the Main space by default when on the home
> page
>
> Note that it’s only a question of default since the user can pick the
> parent when in the Create UI.
>
> One solution of course would be to introduce a configuration option,
> allowing to choose the reference of the Space into which to create new
> pages by default when clicking on “+” on the Home page. Note that this
> would allow admins to define a Content space where they’d want users to
> create content by default when on the home page.
>
> Now, even with a configuration option we’d still need to decide what the
> default would be :) Right now, for the sake of not having tons of top level
> spaces created by mistakes, I think I’d lean to having pages created in the
> Main space by default, as we had before.
>
> @Edy: WDYT? (asking Edy since he was the one who proposed the change and
> he may have some good arguments I haven’t mentioned above)
>
> Thanks
> -Vincent
>
> > Luckily, 7.4 is currently only running in a test environment, and my
> > production environment is still running 7.1.2. I don't plan on upgrading
> my
> > production environment until I can get this figured out. (aka - working
> the
> > way that my users and I are used to.)
>
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>



-- 
Guillaume Delhumeau (gdelhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] New Page Has No Parent

2015-12-29 Thread Guillaume "Louis-Marie" Delhumeau
Hi Andy.

It's actually a controversial feature: on the main page, we assume that
users don't necessary want to create a child of that page, meanwhile on
other pages, we assume that creating a child page is OK.

But some users already have reported this behavior as weird, and your
message is comforting them. If you want to see more:
http://markmail.org/message/dqrqsul32bs4h53w

So the short answer is: it's normal.

Thanks,



2015-12-29 14:13 GMT+01:00 Randy Havens <randy.hav...@cityofrochester.gov>:

> OK, I just did some of my own troubleshooting and got some new information.
>
> When I click the "+" icon to create a new page from my "Main" space, as
> mentioned the parent is blank by default. I used my admin account to go
> through with creating a new page with no parent, and that page became a
> space. That explains why my non-admin user gets "access denied", because my
> non-admin users don't have access to create new spaces. The question
> remains: Why is the "parent" field blank when I try to add a new page from
> my "Main" space, but not from the other spaces that I've created?
>
>
>
> --
> View this message in context:
> http://xwiki.475771.n2.nabble.com/New-Page-Has-No-Parent-tp7597344p7597346.html
> Sent from the XWiki- Users mailing list archive at Nabble.com.
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>



-- 
Guillaume Delhumeau (gdelhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] New Page Has No Parent

2015-12-29 Thread Guillaume "Louis-Marie" Delhumeau
Hello Randy.

I do not reproduce your problem. Does the user try to create terminal pages?

Thanks,

2015-12-28 22:51 GMT+01:00 Randy Havens <randy.hav...@cityofrochester.gov>:

> When I create a new page in my Main space, the "Parent" field defaults to
> empty, but when I create a new page in any other space, it defaults to the
> name of that space. When a user tries to post a new page with the parent
> empty, they get an "access denied" message, but if you put "Main" in the
> parent it works as expected. Is there a way to default this value to "Main"
> when not in another space, instead of having it default blank? This wasn't
> an issue up to XWiki 7.1.2, but it is an issue in 7.3 and 7.4 - when nested
> pages started getting worked on.
>
>
>
> --
> View this message in context:
> http://xwiki.475771.n2.nabble.com/New-Page-Has-No-Parent-tp7597344.html
> Sent from the XWiki- Users mailing list archive at Nabble.com.
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>



-- 
Guillaume Delhumeau (gdelhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


[xwiki-users] [ANN] XWiki 7.4 released

2015-12-28 Thread Guillaume "Louis-Marie" Delhumeau
The XWiki development team is proud to announce the availability of XWiki
7.4.

This is our last stabilization release for the XWiki 7.x cycle and the new
Long Term Support (LTS) version. It mainly brings polishing and
stabilization for the Nested Pages feature, especially in the UI. Among
other things, this release introduces a new notifications menu with the
watchlist actions inside. Application Within Minutes now creates a *Code*
and a *Data* page where the application content is stored. And it is now
possible to have template hierarchies and to add an redirection when a page
is renamed.

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/ReleaseNotesXWiki74

The following people have contributed code to this release (sorted
alphabetically):

* Andreas Jonsson
* Clemens Robbenhaar
* Ecaterina Moraru (Valica)
* Eduard Moraru
* Guillaume Delhumeau
* Jean SIMARD
* Manuel Smeria
* Marius Dumitru Florea
* Sergiu Dumitriu
* Thomas Mortagne
* Vincent Massol

Thanks for your support
-The XWiki dev team
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


[xwiki-users] [ANN] XWiki 7.4 Milestone 2 released

2015-12-16 Thread Guillaume "Louis-Marie" Delhumeau
The XWiki development team is proud to announce the availability of XWiki
7.4 Milestone 2.
This is our last stabilization branch for the XWiki 7.x Cycle. It brings
polishing and stabilization for the Nested Pages feature and the changes in
UI that resulted from it. It is now possible to have template hierarchies,
and to add an automatic redirect when a page is renamed.

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/ReleaseNotesXWiki74M2

The following people have contributed code to this release (sorted
alphabetically):

Guillaume Delhumeau
Sergiu Dumitriu
Marius Dumitru Florea
Vincent Massol
Eduard Moraru
Thomas Mortagne
Manuel Smeria

Thanks for your support
-The XWiki dev team
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Document Tree set Root to Current page

2015-12-04 Thread Guillaume Lerouge
Hi Darren,

I think you're looking for $doc.fullName ;-)

Don't forget to put it inside a {{velocity}} macro (I didn't check whether
this was the right parameter name):

{{velocity}}
{{documentTree root="$doc.fullName" /}}
{{/velocity}}

Thanks,

Guillaume

On Thu, Dec 3, 2015 at 7:44 PM, britincanada <he...@darrenwainwright.com>
wrote:

> Hey,
>
> A very new user to xWiki, I would like to add navigation of child sub-pages
> to the currently viewed page. It appears that the Document Tree macro is
> what I need, though I don't know what I should be putting in the root
> property to use the current page.
>
> I was going to add this to a template, so the page is going to be different
> every time.
>
> any help would be great.
>
> thanks
>
>
>
> --
> View this message in context:
> http://xwiki.475771.n2.nabble.com/Document-Tree-set-Root-to-Current-page-tp7597083.html
> Sent from the XWiki- Users mailing list archive at Nabble.com.
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Request: make linking easy

2015-11-27 Thread Guillaume Lerouge
Hi Anton,

thanks for your feedback. As you noticed, XWiki is currently undergoing
significant changes in the way we handle pages and all the associated kinks
have not been worked out yet. If I may, one solution for you could be to
switch back to XWiki Enterprise 7.1 for the moment, and upgrade at a later
point in time, once things are more stable with regards to nested pages.

Regarding the way pages are organized, while I agree that the tree
organization can cause confusion for users coming from MediaWiki, the power
and flexibility coming with this (cascading rights in particular) would be
missed by users going the other way round.

Now clearly there are some difficulties coming from the fact that some
pages are nested and others aren't (I started a separate thread on this
topic). Specifically, the fact that the syntax requires "WebHome" to be
explicitly mentioned is annoying and I hope we'll be able to fix it soon.

Out of curiosity, since you seem to be familiar with MediaWiki, is there a
specific reason why you decided to go with XWiki this time?

In any case, thanks for all the feedback! Getting a fresh point of view
from newcomers is very valuable, even though we can sometimes react a bit
defensively.

Best,

Guillaume

On Friday, 27 November 2015, vinc...@massol.net <vinc...@massol.net> wrote:

> Hi Anton,
>
> On 26 Nov 2015 at 20:44:35, Anton Hughes (a...@tradeworks.io <javascript:;>
> (mailto:a...@tradeworks.io <javascript:;>)) wrote:
>
> >
> > On 26 November 2015 at 20:33, vinc...@massol.net <javascript:;>(mailto:
> vinc...@massol.net <javascript:;>) wrote:
> > > It works. Create a page with [[test]]. You’ll see a question mark
> (wanted link). Click on it, add content and save. Navigate back to your
> first page. The link works.
> > >
> > > What you’re showing in the screenshots is orange and apples. In one
> link you link to a new page called MyExamplePage. And in the second one you
> link to a page named MyExamplePage.WebHome.
> > >
> > > In Mediawiki try create a page2 that exists (and a page1 that
> doesn’t). Then write in another page:
> > Youre missing my point.
> > I'm trying to point out how difficult it is, without prior knowledge, to
> do just a simple link.
> > You answer by giving me links to all sorts of docs.
> >
> > As I tried to illustrate, I have already created a page called
> MyExamplePage. Writing [[MyExamplePage]] does NOT link to it. To correctly
> link to it need to study documentation, and write a lot more.
> > The correct link is [[MyExamplePage>>doc:MyExamplePage.WebHome]]
> > This is not easy. This is not natural. This does not help collaboration.
> This does require studying documentation.
> >
> > Obviously for you, who use this product everyday, you think Im just
> complaining about nothing. But, dont take my word - just ask any normal
> user what ' [[MyExamplePage>>doc:MyExamplePage.WebHome]]' means. No one in
> my office has a clue.
> > A wiki is about making things simple for everyday users - but you are a
> heavy duty technical user. Xwiki has taken the concept of wiki and made it
> brittle and technical.
>
>
> We exchanged a lot of emails yesterday. Let me try to summarize my
> position:
>
> * I appreciate your feedback a lot, especially as it comes from someone
> not used to XWiki. This allows to have an external view different from ours
> which has been forged by years of using and developing XWiki.
>
> * We currently have a problem starting with XWiki 7.2. We have a mismatch
> between the XWiki internal model (which supports subwikis, nested spaces
> and pages) and our UI in which we’re trying to completely hide the concept
> of Spaces so that users only see Nested Pages (note that I’ve said Nested
> Pages and not Nested Spaces). The issue surfaces when you start using wiki
> links in markup, macros or scripting APIs, which all currently accept a
> Reference (i.e. subwikis, nested spaces and pages, as in
> wiki:space1.space2.page). So we map Nested Pages onto Nested Spaces by
> always creating pages in a page named WebHome and in a space named after
> the name of the page the user wants to use.
>
> * I don’t agree with you that having a single organization namespace is
> better than supporting hierarchies, and that the MediaWiki model is the
> best.
>
> * The format you mentioned above,
> i.e. [[MyExamplePage>>doc:MyExamplePage.WebHome]] is the canonical format.
> You can drop “doc:” (in which case XWiki assumes you reference a doc by
> default). It’s there because we support lots of various other references:
> urls, mailto, unc, etc. See the syntax guide for more.
>
> * The only complaint I know of (before XWiki 7.2) about the fo

Re: [xwiki-users] How to add a menu in the top menu?

2015-11-19 Thread Guillaume "Louis-Marie" Delhumeau
Hello.

First, I think you should create one page per UI extension. It's not a good
practice to have 2 UIExtension objects on the same wiki page.

Then, we cannot see your attachments, because the mailing list does not
allow them. You should use a web service (such as http://snag.gy/), upload
your images there, and then paste their URL on your emails.

Finally, I've tried to reproduce your issue, and indeed, there are missing
HTML elements in the top menu which make any addition bad located. I've
created the following issue http://jira.xwiki.org/browse/XWIKI-12841 and
I'm going to fix it quickly.

Sorry for the inconvenience and thanks for your report, it helps us to
improve the quality of the product.

Thanks,
Guillaume



2015-11-18 16:22 GMT+01:00 Guofeng Zhang <guofen...@gmail.com>:

> Vincent,
>
> I missed the link "how to add an UIX" on that page.
>
> By following the steps on Writing a simple UI Extension. I created two UI
> Extensions on a new page using  "org.xwiki.platform.topmenu.left" as the
> extension point ID, the order for the first (Some Text) is 5000, and
> another (Some Text 1) is 4000. They all displayed on the right part of the
> top menu.
>
> Some Text1 is displayed at the right of Some Text (it behaved like the
> description of Top Menu Right).
>
> see the attached.
>
> What did I do incorrectly?
>
> Thanks for your help very much.
>
> Guofeng
>
>
>
>
>
> On Mon, Nov 16, 2015 at 4:19 PM, vinc...@massol.net <vinc...@massol.net>
> wrote:
>
> > Hi Guofeng,
> >
> > On 14 Nov 2015 at 18:11:35, Guofeng Zhang (guofen...@gmail.com) wrote:
> >
> > Hi,
> >
> > I am trying XWiki 7.3.
> >
> > I want to add add a menu with icon in the top menu. I have read
> > http://platform.xwiki.org/xwiki/bin/view/ExtensionPoint/TopMenuLeft, but
> > still can not understand where to add the following:
> >
> > {{velocity}}{{html clean="false"}} ## we need clean="false" because we
> want
> >
> > to display the raw content
> > 
> >  > role="button" arias-haspopup="true" aria-expanded="false"> >
> >
> class="sr-only">$services.localization.render('core.menu.toggleNavigation')Some
> >
> > text
> > 
> > Some link
> > 
> > 
> > {{/html}}{{/velocity}}
> >
> > Could you give me advice where to add the above lines?
> >
> >
> > Just want to verify that you’ve read the tutorial linked from
> > http://platform.xwiki.org/xwiki/bin/view/ExtensionPoint/
> >
> >
> > Could you confirm that you’ve read it?
> >
> > Thanks!
> >
> > -Vincent
> >
> >
> >
> >
> > Thanks for your help very much.
> >
> > Guofeng
> >
> >
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>



-- 
Guillaume Delhumeau (gdelhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Strange behaviour when creating new pages => new spaces are created instead (xwiki 7.2)

2015-11-19 Thread Guillaume "Louis-Marie" Delhumeau
Hello Denis.

"This is not a bug, it's a feature" ;)

In XWiki 7.2, we have introduced the concept of "Nested Pages". Actually,
every time you create a page, you actually create a page called "WebHome"
in a new space. From the UI perspective, it acts as if we don't have the
"space" notion anymore, but only a hierarchy of pages.

I invite you to read:
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki72#HNestedPages

I hope it helps.

Thanks,

2015-11-19 12:08 GMT+01:00 <denis.germ...@isocel.info>:

> Hello,
>
> I'm running a fresh 7.2 XWiki install (RHEL 7, tomcat 7, postgreSQL 9.1)
> and I'm experiencing strange behaviour when I try to create new pages in a
> given space.
>
> If I use the big "+" sign on the top of the page in the space I want, the
> result is always the same : a new space is created instead of a new page.
>
> This is not a "parenting" problem, the space in question is indeed child
> of the parent space.
> I can try to change the location of the page in the "Location in the page
> hierarchy where this new page will be created." menu
>
> But it doesn't appear in the page list of the space, and it appears in the
> list of all the spaces.
>
> The template doesn't seem to be the problem (Page Type). I can use a page
> template or a blank page (default choice) in the page type.
>
> The only workaround that I found is to create a new page through the space
> WYSIWIG editor.
> I edit the home page of the space, then in the WYSIWIG editor I click on
> "Link" and then "XWiki Page". This way a link to a new unknown page is
> created in the space, and then and only then can I create a page inside
> the space.
>
> This doesn't seem normal. Can someone give me some insights on what might
> cause this ?
>
> Regards,
> Denis GERMAIN
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>



-- 
Guillaume Delhumeau (gdelhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Fw : Fw : Re: [myxwiki] new wiki request: coc

2015-10-01 Thread Guillaume Lerouge
Hi Pascal,

On Wed, Sep 30, 2015 at 4:25 PM, <pbasnews-thor...@yahoo.fr> wrote:

>
> > > created your wiki here:
> > > http://coc.myxwiki.org/xwiki/bin/view/Main/
>
> Hello,
>
> About my new site on myxwiki.org, I'm very disoriented about the
> customization of welcome page ...
> If i'm login as Admin, Main.WebHome show  only this text:
> <<<C'est un site web facile à éditer qui aidera les membres de votre
> équipe à mieux travailler ensemble. Ce wiki se compose de pages organisées
> par espaces. Vous êtes actuellement sur la page d'accueil (WebHome) de
> l'espace principal (Main).
> Vous pouvez utiliser le bac à sable afin de tester les fonctionnalités de
> votre wiki.>>
>
> When I'm login as admin if I edit my welcome page this message is
> displayed on top of gadget dashboard:
> < document différent,coc:WikiManager.Dashboard. Vos changements auront un
> impact sur toutes les pages incluant cette configuration de tableau de
> bord. Si vous souhaitez personnaliser cette page, éditez-la en mode WYSIWYG
> et configurez la macro "tableau de bord" avec un paramètre source vide.>>
> I don't understand what's meaning " configurez la macro "tableau de bord"
> avec un paramètre source vide"? I must edit the source of Main.Welcome and
> replace {{dashboard source="Main.Dashboard" /}} by {{dashboard source=""
> /}} ?
>
> If I follow the instruction like a normal user, I'm quickly lost: I can
> not follow this instruction and I obtain 2 different welcome page depending
> of language of my browser: english one with dashboard and the french one
> with the short text  "C'est un site web facile à éditer..."
>
> http://coc.myxwiki.org/xwiki/bin/view/Main/?language=fr
> http://coc.myxwiki.org/xwiki/bin/view/Main/?language=en
>
> In my advice, xwiki must be simplier to customize welcome page. It is the
> first impression the most important, isn'it?
>

I couldn't agree more with this one.

I've been thinking for a while now that we should have a standard wiki page
as the home and make the dashboard available from an icon on the app bar.
The current way it works right now is uselessly confusing.

Thanks,

Guillaume


> (I activated 2 langages on: coc.myxwiki.org, en and fr default)
>
>
> Thxs
>
> Pascal B
>
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Creating a new page creates a space instead

2015-08-11 Thread Guillaume Lerouge
Hi Tony,

thanks for your feedback on this subject. We're indeed working on making
nested spaces a default feature of XWiki as part of the 7.x release, which
we're aware will lead to inconsistencies and questions such as the one
you've asked. Let me try to summarize some of the thinking about this topic
below:

   - Up to XWiki Enterprise 7.1 (XE 7.1), there has been 2 ways to organize
   content in XWiki:
  - Wiki  Space  Page (which includes rights inheritance and
  administration features)
  - Page  Child page  Child page of child page  ... (which is used
  for hierarchical navigation purposes)
   - Note that both are independent: a page can have a parent page in a
   different space/wiki than its own


   - While this works, we've found that it can create confusion for
   end-users, leading to questions such as:
  - Should I create a wiki or a space for my team?
  - Which navigation should I put on my home page: list of spaces or
  treeview of pages?
  - Can I set rights on a page that is under a space?


   - At the same time, for a long time there have been discussions on the
   list about the future new model of XWiki, which would ideally include
   nested spaces, offering the following features:
  - Unified way to handle hierarchical navigation (Page  Sub-page 
  Sub-sub-page ...)
  - Navigation reflected in URLs (.../PageA/PageB/PageC)
  - Inheritance of access rights (rights on PageA apply to PageB and
  PageC, unless defined otherwise. Rights on PageB supersede those on PageA
  and also apply to PageC, and so on.)
   - We're taking this release and an opportunity to try and move from the
   previous way to this new way of organizing pages


   - In an ideal, going from the old to the new would imply a total rewrite
   of the model. Instead of pages and spaces, you would have an entity than is
   both a container and a document. That entity, probably called a node, would
   have its own content, associated properties, and a list of children. My
   (admittedly limited) understanding is that this is the way JCR
   
https://mailtrack.io/trace/link/eebf3b2ceeb0045df5570712a86a744e38aca807?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FContent_repository_API_for_Javasignature=7b905fbf6bd2a3a0
   works.


   - In the real world, in order not to break retro-compatibility with many
   existing features and applications we had to keep the concepts of Page
   and Space in XWiki while adapting them to emulate the desired
   functionality. Here's what we're doing to achieve this by default:
  - We're hiding the parent-child feature
  - When creating a new page, the system automatically creates
  Page.WebHome, which creates a space, though this is hidden in the URL
  (you only see .../Page/)
  - For advanced users, we added the ability to create terminal pages
  which are pages that are not spaces (as before) = this is meant
mostly for
  application creators

I hope this clarified things a it! To get back to your use case, if your
users are in simple mode (which is not your case since you're an admin)
they shouldn't see any of the complexity related to nested spaces. When
creating new pages, the only thing users should need to think about is the
location of the page in the hierarchy, as they would using a parent  child
relationship. However, since 7.2 is still in active development the UI
still has issues left that have not been addressed yet.

*Additional note:* if you're running your wiki in production, I would
recommend sticking with XE 7.1.1 for now, which is a stable release.

Best,

Guillaume

On Tue, Aug 11, 2015 at 1:47 AM, junglur t...@junglur.co.nz wrote:

 So I've been playing around a bit more, if I tick create Terminal page it
 seems to create a page as I had originally expected. Is there a way to turn
 off nested spaces or set Terminal page as default page type? I don't really
 want my end users creating a pile of nested spaces. I don't want it to be
 complicated for them, I just want them to be able to go addpage and then
 create a simple page, not a nested space.

 I don't really want them to have to remember to tick the Terminal page
 checkbox each time because I can imagine that they're going to
 forget...probably a lot haha and then I'm going to have to be tidying it up
 all the time.



 --
 View this message in context:
 http://xwiki.475771.n2.nabble.com/Creating-a-new-page-creates-a-space-instead-tp7595617p7595625.html
 Sent from the XWiki- Users mailing list archive at Nabble.com.
 ___
 users mailing list
 users@xwiki.org
 http://lists.xwiki.org/mailman/listinfo/users

___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


[xwiki-users] [ANN] XWiki 7.1.1 released

2015-06-17 Thread Guillaume Louis-Marie Delhumeau
The XWiki development team is proud to announce the availability of XWiki
7.1.1.

This is a stabilization release that fixes important bugs discovered in the
7.1 version.

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/ReleaseNotesXWiki711

The following people have contributed code to this release:

- Vincent Massol
- Guillaume Delhumeau

Thanks for your support
-The XWiki dev team
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


[xwiki-users] [myxwiki] XWiki Enterprise 7.1 Upgrade

2015-06-16 Thread Guillaume Louis-Marie Delhumeau
Subject:

Hi everyone,

myxwiki.org has been upgraded to XE 7.1. If you own a wiki hosted there you
should have a look at the release notes for this version at:
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki71 (note
that the bug concerning the upgrade of wikis has been fixed on the myxwiki
server).

You should automatically get an upgrade wizard for your wiki when you login
as admin.
For more details see the upgrade guide available at :
http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Upgrade#HUpgradingwikidocuments

To be notified of the myxwiki.org server upgrade you can follow myxwiki on
twitter:
http://twitter.com/myxwiki

Thanks,
-XWiki Community
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


[xwiki-users] [ANN] XWiki 7.0.1 released

2015-04-30 Thread Guillaume Louis-Marie Delhumeau
The XWiki development team is proud to announce the availability of XWiki
7.0.1.
This is a stabilization release that fixes important bugs discovered in the
previous 7.0 version.

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/ReleaseNotesXWiki701
Thanks
-The XWiki dev team
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Cross-wiki livetable

2015-04-29 Thread Guillaume Louis-Marie Delhumeau
Hello.

That could work if you create a custom resultPage (see:
http://extensions.xwiki.org/xwiki/bin/view/Extension/Livetable+Macro#HCustomJSON)
that would be a modified version of the current XWiki.LiveTableResults page
with a custom gridresult_buildRowsJSON macro that set the desired subwiki
on the query.

What you cannot do is a livetable accross different subwikis.


I hope it helps,

2015-04-29 16:11 GMT+02:00 Jamal ram...@gmail.com:

 Hi,

 I'd like to know if it's possible for a livetable on the main wiki to list
 pages from a subwiki that contain objects of a class defined on the
 subwiki.

 Thanks,

 Jamal



 --
 View this message in context:
 http://xwiki.475771.n2.nabble.com/Cross-wiki-livetable-tp7594795.html
 Sent from the XWiki- Users mailing list archive at Nabble.com.
 ___
 users mailing list
 users@xwiki.org
 http://lists.xwiki.org/mailman/listinfo/users




-- 
Guillaume Delhumeau (gdelhum...@xwiki.com)
Research  Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Readers type extension or feature

2015-03-09 Thread Guillaume Lerouge
Hi Mahomed,

this is doable if you activate the statistics module:

   -
   http://extensions.xwiki.org/xwiki/bin/view/Extension/Statistics+Application

First you need to activate it in the xwiki.cfg file:

   -
   
http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Configuration#%23HEnabling2FDisablingStatistics

Once the statistics are activated, every view action by every user is
recorded. Now all you need to do is write the code to retrieve the stats
about the specific page you're looking at, and put in in a panel.

You can find inspiration for this in the following extensions:

   -
   http://extensions.xwiki.org/xwiki/bin/view/Extension/Recently+Visited+Pages
   -
   http://extensions.xwiki.org/xwiki/bin/view/Extension/Most+Viewed+Articles
   -
   
http://extensions.xwiki.org/xwiki/bin/view/Extension/Number+Of+Active+Users+Per+Day+And+Per+Week

Best,

Guillaume

On Sun, Mar 8, 2015 at 10:36 PM, Mahomed Hussein maho...@custodiandc.com
wrote:

 Hi

 I’m a new user to XWiki here. Running 6.4.2. We recently setup mediawiki
 but due to some limitations (and then finding XWiki), we’ve decided to move
 to XWiki. One feature that we would REALLY love to have similar to
 mediawiki is the readers feature. It shows which registered users have
 viewed a page. I have done some Google searching and I have looked through
 the extensions but I cannot find anything. The closest extension I found is
 one that shows how to run a query to display the editors, but I couldn’t
 see a way to modify that to show the readers. This makes me think it might
 not be possible, but I know very little about the way the system works so I
 hope someone can help.

 Thanks in advance for your help and time.

 Kind regards,

 Mahomed
 ___
 users mailing list
 users@xwiki.org
 http://lists.xwiki.org/mailman/listinfo/users
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


[xwiki-users] [ANN] XWiki 6.4.2 released

2015-02-25 Thread Guillaume Louis-Marie Delhumeau
The XWiki development team is proud to announce the availability of XWiki
6.4.2.
This is a stabilization release that fixes important bugs discovered in the
6.4.1 version.

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/ReleaseNotesXWiki642

Thanks
-The XWiki dev team

-- 
Guillaume Delhumeau (gdelhum...@xwiki.com)
Research  Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


[xwiki-users] [ANN] XWiki 6.2.7 released

2015-02-25 Thread Guillaume Louis-Marie Delhumeau
The XWiki development team is proud to announce the availability of XWiki
6.2.7.
This is a stabilization release that fixes important bugs discovered in the
6.2.6 version.

You can download it here:
http://forge.ow2.org/project/showfiles.php?group_id=170

Make sure to review the release notes:
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki627

Thanks
-The XWiki dev team
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Creating a panel for all wikis

2015-02-02 Thread Guillaume Louis-Marie Delhumeau
2015-01-30 17:18 GMT+01:00 vinc...@massol.net vinc...@massol.net:



 On 30 Jan 2015 at 16:50:35, Jamal (ram...@gmail.com(mailto:
 ram...@gmail.com)) wrote:

  Thanks Vincent.
 
  This raises another question: if I create a new template wiki, or turn an
  existing wiki into a template, can I retroactively apply it to an
 existing
  subwiki?

 There’s no UI for this but I guess you could script it and use the exposed
 wiki script service to perform the copy.

 I was looking for documentation for that on extensions.xwiki.org but
 couldn’t find it.

 @GuillaumeD:
 - question 1: any idea where the doc could be for the various script
 services of the wiki modules?


Currently, there is this:
http://extensions.xwiki.org/xwiki/bin/view/Extension/Wiki+Application#HFordevelopers


 - question 2: do we have a script service API to perform the template copy?


Unfortunately no, but you can use WikiTemplateManager#applyTemplate() in a
Groovy script.



 Thanks
 -Vincent

 ___
 users mailing list
 users@xwiki.org
 http://lists.xwiki.org/mailman/listinfo/users




-- 
Guillaume Delhumeau (gdelhum...@xwiki.com)
Research  Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


[xwiki-users] [ANN] XWiki 6.2.5 released

2015-01-27 Thread Guillaume Louis-Marie Delhumeau
The XWiki development team is proud to announce the availability of XWiki
6.2.5.

This version is mostly a stabilization release which fix many bugs we have
discovered since XWiki 6.2.4. But it also brings some improvements on the
screen-width-responsiveness of the livetable in Flamingo.

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/ReleaseNotesXWiki625

Thanks
-The XWiki dev team
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Manage rights for author

2015-01-27 Thread Guillaume Lerouge
Hi Marc,

by default, the creator of a page has edit rights on that page. If that
users switches to advanced mode on their user profile, then go back to
their page, they will be able to see an Access rights option in the
Edit button.

Thanks,

Guillaume

On Tue, Jan 27, 2015 at 9:31 AM, Marc AUDEFROY audefroy.m...@gmail.com
wrote:

 Hi all!

 How could an author manage the rights on the pages he created? How put
 this default behavior?

 Thanks!

 Marc
 ___
 users mailing list
 users@xwiki.org
 http://lists.xwiki.org/mailman/listinfo/users
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] [VOTE] Enable default actions for the Flamingo top menu entries

2014-12-11 Thread Guillaume Louis-Marie Delhumeau
It's good to see in action, I like it!

Thanks for this.

2014-12-10 17:17 GMT+01:00 Marius Dumitru Florea 
mariusdumitru.flo...@xwiki.com:

 I committed my changes so that those that haven't voted yet can see it
 in action. Will revert if someone is against it.

 Thanks,
 Marius

 On Mon, Dec 8, 2014 at 11:07 PM, Guillaume Lerouge guilla...@xwiki.com
 wrote:
  +1
 
  Thanks a lot for all your effort on this Marius!
 
  Guillaume
 
  On Mon, Dec 8, 2014 at 1:18 PM, Guillaume Louis-Marie Delhumeau 
  gdelhum...@xwiki.com wrote:
 
  +1, looks good.
 
  2014-12-08 12:59 GMT+01:00 Marius Dumitru Florea 
  mariusdumitru.flo...@xwiki.com:
 
   On Sat, Dec 6, 2014 at 11:02 PM, Denis Gervalle d...@softec.lu
 wrote:
+1, ideally with a hover feedback very similar to the one of a
 dropdown
button.
  
   The color theme is responsible for the hover effect. A flat color
   theme will probably use a single color highlight, controlled by the
   @navbar-default-link-hover-bg LESS variable. A 3D color theme may use
   some gradients to achieve the 3D effect on hover. A minimalistic color
   theme (like Simplex) will just change the text color on hover, leaving
   the background transparent.
  
   This proposal/vote is about agreeing on:
   * displaying a small vertical bar between the menu label and toggle
   (using a color derived from the menu background) to indicate the
   separation between the two (especially for tablet devices where
   there's no hover)
   * hovering/activating the menu label and the toggle separately, as it
   happens with a drop down button (e.g. the Add button).
  
   Thanks,
   Marius
  
   
On Fri, Dec 5, 2014 at 6:59 PM, Pascal BASTIEN 
  pbasnews-xw...@yahoo.fr
wrote:
   
May I? (you send mail at user list)... then +1
On 6.3 I still use 6.2 menu (I modified the template on my xwiki)
   
I'm agree with you the 2 side of button must be better separate
 (with
color on hoover or a black vertical bar?).
   
IMO we must respect the same logic of actions button (an one-click
   default
action and drop down sub menu level at the right-side-click )
With CSS it should be possible to:- use 2 side button on big
 screen-
  use
GoTo menu on small screen
(with @media min-width)
   
Thxs
Pascal BASTIEN
  De : Marius Dumitru Florea mariusdumitru.flo...@xwiki.com
 À : XWiki Developers d...@xwiki.org; XWiki Users 
 users@xwiki.org
 Envoyé le : Vendredi 5 décembre 2014 17h20
 Objet : [xwiki-users] [VOTE] Enable default actions for the
 Flamingo
   top
menu entries
   
Hi everyone,
   
= Short Story =
   
I propose to change the behaviour of the top level menu from
 Flamingo
for tablet and desktop screens (so NOT for phones) to match the
behaviour we had in 6.2 BUT improving the separation between the
navigation links and the drop down toggle. The idea is that the top
level menu entries should behave like a drop down button (e.g. the
 Add
button) but without looking like one. You can see some screen
 shots at
http://jira.xwiki.org/browse/XWIKI-11517.
   
= Long Story =
   
I've heard complains that the current behaviour of the top level
 menu
from Flamingo skin is not perfect. The issue is that you need to
 click
twice to navigate. Ok, with a mouse you can use the middle click
(wheel) to open the link in a new tab but still it's annoying for
simple uses and for those that use the touch pad or a tablet.
   
An alternative I have investigated in
http://jira.xwiki.org/browse/XWIKI-11479 is to open the menu on
 hover
(on devices that support this of course). The result is quite nice
 and
effective but there is a problem: if you have a second horizontal
 menu
displayed under the top level menu then you'll have a hard time
hovering the second menu. So I decided to close XWIKI-11479 as
 Won't
Fix. For those that like the open-on-hover behaviour and which
 don't
plan to use a second menu I've published this extension
   
   
  
 
 http://extensions.xwiki.org/xwiki/bin/view/Extension/Hover+and+Default+Action+for+Flamingo+Menu
.
   
The other alternative to fix the problem is to go back to the
behaviour from 6.2. Precisely, each menu has two sides:
* on the left is the label which is a link used for navigation
* on the right there is a toggle (arrow) used to open the menu.
   
The problem with this, and the reason we change it in 6.3, was that
the label and the toggle were not separated very well so the user
could easily think they were doing the same action (opening the
 menu).
At the same time this separation felt unnatural on extra small
 screens
(phones) because you couldn't tap easily on the toggle (arrow).
   
The solution I propose is to:
* Keep the current behaviour for extra small screens (phones). That
means the use has to tap twice to navigate: one tap to open the
 menu
and another

Re: [xwiki-users] What would you like to see in the XWiki 7.x cycle?

2014-12-09 Thread Guillaume Lerouge
Hi,

On Tue, Dec 9, 2014 at 10:23 PM, Thomas Mortagne thomas.morta...@xwiki.com
wrote:

 On Tue, Dec 9, 2014 at 9:57 PM, Harald Ommang harald.omm...@verico.com
 wrote:
  Hi!
 
  In one way, I very much appreciate the relatively high frequency of
 updates done by the XWIKI crew. You are doing a great job, making sure that
 XWIKI is alive and kicking and always improving.
 
  The downside to this, is all the work needed to be done when upgrading.
 So, I don't do that very often. The basic part of installation/migration
 works very well, but when it comes to content, the upgrade procedure is
 messy, as I see it. It is a hassle to have to pick and choose between
 various parts when importing and exported XAR.
 
  I would very much suggest planning for a future where the parts that are
 XWIKI software are clearly separated from the parts where customers
 typically do modifications. Especially items like users and groups. It
 should be possible to have a more separated export/import so that you GET
 new versions of e.g. the admin pages, while still KEEPING your setup of
 users, groups, etc., without having to click on a million of checkboxes in
 the import.

 I don't really understand this comment, doing export/import is really
 not the standard way of doing an upgrade. In typical upgrade you
 backup everything if you want to be safe (or better you have automated
 backups and you don't really need to do it when you upgrade), upgrade
 the WAR part (if you use the Debian package then it's just about doing
 apt-get upgrade or install with a specific version), restart, XWiki
 upgrade the database shema automatically if needed and then you get
 the Distribution Wizard which download and upgrade the wiki pages with
 3 ways merge. Most of the time you don't have anything to do.


Sure, but to benefit from all those nice Distribution Wizard features,
Harald would first need to... upgrade to the latest version ;-)

Guillaume
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] [VOTE] Enable default actions for the Flamingo top menu entries

2014-12-08 Thread Guillaume Louis-Marie Delhumeau
 and
  background color) is strictly determined by the color theme. Some
  themes highlight the hovered menu items by changing their background
  color, others the text color and some do both. My changes are
  independent on this. We can of course improve the default color theme
  to better highlight the menu items. This is a different topic though.
 
  I'd like to commit this changes in 6.4. Here's my +1.
 
  Thanks,
  Marius
  ___
  users mailing list
  users@xwiki.org
  http://lists.xwiki.org/mailman/listinfo/users
 
 
 
  ___
  users mailing list
  users@xwiki.org
  http://lists.xwiki.org/mailman/listinfo/users
 
 
 
 
  --
  Denis Gervalle
  SOFTEC sa - CEO
  ___
  users mailing list
  users@xwiki.org
  http://lists.xwiki.org/mailman/listinfo/users
 ___
 users mailing list
 users@xwiki.org
 http://lists.xwiki.org/mailman/listinfo/users




-- 
Guillaume Delhumeau (gdelhum...@xwiki.com)
Research  Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] [VOTE] Enable default actions for the Flamingo top menu entries

2014-12-08 Thread Guillaume Lerouge
+1

Thanks a lot for all your effort on this Marius!

Guillaume

On Mon, Dec 8, 2014 at 1:18 PM, Guillaume Louis-Marie Delhumeau 
gdelhum...@xwiki.com wrote:

 +1, looks good.

 2014-12-08 12:59 GMT+01:00 Marius Dumitru Florea 
 mariusdumitru.flo...@xwiki.com:

  On Sat, Dec 6, 2014 at 11:02 PM, Denis Gervalle d...@softec.lu wrote:
   +1, ideally with a hover feedback very similar to the one of a dropdown
   button.
 
  The color theme is responsible for the hover effect. A flat color
  theme will probably use a single color highlight, controlled by the
  @navbar-default-link-hover-bg LESS variable. A 3D color theme may use
  some gradients to achieve the 3D effect on hover. A minimalistic color
  theme (like Simplex) will just change the text color on hover, leaving
  the background transparent.
 
  This proposal/vote is about agreeing on:
  * displaying a small vertical bar between the menu label and toggle
  (using a color derived from the menu background) to indicate the
  separation between the two (especially for tablet devices where
  there's no hover)
  * hovering/activating the menu label and the toggle separately, as it
  happens with a drop down button (e.g. the Add button).
 
  Thanks,
  Marius
 
  
   On Fri, Dec 5, 2014 at 6:59 PM, Pascal BASTIEN 
 pbasnews-xw...@yahoo.fr
   wrote:
  
   May I? (you send mail at user list)... then +1
   On 6.3 I still use 6.2 menu (I modified the template on my xwiki)
  
   I'm agree with you the 2 side of button must be better separate (with
   color on hoover or a black vertical bar?).
  
   IMO we must respect the same logic of actions button (an one-click
  default
   action and drop down sub menu level at the right-side-click )
   With CSS it should be possible to:- use 2 side button on big screen-
 use
   GoTo menu on small screen
   (with @media min-width)
  
   Thxs
   Pascal BASTIEN
 De : Marius Dumitru Florea mariusdumitru.flo...@xwiki.com
À : XWiki Developers d...@xwiki.org; XWiki Users users@xwiki.org
Envoyé le : Vendredi 5 décembre 2014 17h20
Objet : [xwiki-users] [VOTE] Enable default actions for the Flamingo
  top
   menu entries
  
   Hi everyone,
  
   = Short Story =
  
   I propose to change the behaviour of the top level menu from Flamingo
   for tablet and desktop screens (so NOT for phones) to match the
   behaviour we had in 6.2 BUT improving the separation between the
   navigation links and the drop down toggle. The idea is that the top
   level menu entries should behave like a drop down button (e.g. the Add
   button) but without looking like one. You can see some screen shots at
   http://jira.xwiki.org/browse/XWIKI-11517.
  
   = Long Story =
  
   I've heard complains that the current behaviour of the top level menu
   from Flamingo skin is not perfect. The issue is that you need to click
   twice to navigate. Ok, with a mouse you can use the middle click
   (wheel) to open the link in a new tab but still it's annoying for
   simple uses and for those that use the touch pad or a tablet.
  
   An alternative I have investigated in
   http://jira.xwiki.org/browse/XWIKI-11479 is to open the menu on hover
   (on devices that support this of course). The result is quite nice and
   effective but there is a problem: if you have a second horizontal menu
   displayed under the top level menu then you'll have a hard time
   hovering the second menu. So I decided to close XWIKI-11479 as Won't
   Fix. For those that like the open-on-hover behaviour and which don't
   plan to use a second menu I've published this extension
  
  
 
 http://extensions.xwiki.org/xwiki/bin/view/Extension/Hover+and+Default+Action+for+Flamingo+Menu
   .
  
   The other alternative to fix the problem is to go back to the
   behaviour from 6.2. Precisely, each menu has two sides:
   * on the left is the label which is a link used for navigation
   * on the right there is a toggle (arrow) used to open the menu.
  
   The problem with this, and the reason we change it in 6.3, was that
   the label and the toggle were not separated very well so the user
   could easily think they were doing the same action (opening the menu).
   At the same time this separation felt unnatural on extra small screens
   (phones) because you couldn't tap easily on the toggle (arrow).
  
   The solution I propose is to:
   * Keep the current behaviour for extra small screens (phones). That
   means the use has to tap twice to navigate: one tap to open the menu
   and another one on the Go to this XYZ.
   * On desktop and tablet enable the default action (navigation link) as
   in 6.2 but improve the separation so that the menu behaves as much as
   possible as a drop down button (e.g. the Add button) without looking
   like one. This means:
   ** You should understand there are two sides without hovering
   ** Separate hover and active state (e.g. the link is not hovered when
   the toggle is hovered)
  
   I've investigated *many* ways to achieve this and the result

[xwiki-users] [ANN] XWiki 6.3 released

2014-11-12 Thread Guillaume Louis-Marie Delhumeau
The XWiki development team is proud to announce the availability of XWiki
6.3.

This release provides a great stabilization of the Flamingo Skin, and
includes new themes and some improvements to manage them.

It also contains a new mail API and module to replace the old mailsender
plugin, a new dynamic tree widget that is progressively replacing all
existing trees in XWiki (Document Index, Navigation Panels, etc...), some
improvements on the Extension Manager as well as on the User Directory and
the Applications Panel.

Efforts have been made on the performances side, with good results on view
mode (except on the first loaded-page). We reach the same performances as
5.4.6, which was not the case during the 6.x cycle until now. This is a
first milestone to get even better!

Finally, and like every releases, a lot of bugs have been fixed.
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/ReleaseNotesXWiki63

Thanks
-The XWiki dev team
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] [xwiki-devs] [Discussion] Make XWiki Case Insensitive. WDYT?

2014-11-07 Thread Guillaume Lerouge
Hi Edy,

thanks for your message. From a forward-looking standpoint, I 100% agree
with you that switching XWiki to case-insensitive would be a good thing to
do. I've seen others (as well as myself) be lost because they were going to
.../xwiki/bin/view/Main/Xyy instead of .../xwiki/bin/view/Main/XYY and
vice-versa. If we were to make the decision today, I can't see a good
reason why not to go case-insensitive, especially when targeting business
users.

However we're not starting from a blank slate. There might be (I don't know
that there is, but there might be) legitimate use cases for a page named
Xyy vs a page named XYY, both in the same wiki. I'd like to have a
better idea of the consequences of this change, as well an analysis of a
public site such as xwiki.org to see whether this could be causing
unforeseen and other unexpected issues. In other words: what could go wrong?

Thanks,

Guillaume
ᐧ

On Fri, Nov 7, 2014 at 11:33 AM, Eduard Moraru enygma2...@gmail.com wrote:

 Hi users and devs,

 I would like to have your opinion on the topic of case sensitive vs case
 insensitive and which one you prefer in XWiki.

 Currently, XWiki is case sensitive. This means the same resource name
 (document name, space name, etc) can be written with either small letters
 or big letters or a mix.

 Examples: You can have both Main.Test and Main.test as 2 different
 documents. Also, you can have XWiki.Admin and XWiki.admin as 2
 different users. This also applies to URLs, as /Main/Test is different
 from /Main/test or /main/test, so all these 3 are different resources.

 Even from this short description, one can already identify possible
 problems of this approach.

 From the top 3 operating systems (Linux, Mac an Windows), only Linux is
 case sensitive, the other two (more user-focused Operating Systems) are
 both case insensitive.

 Since XWiki has one of its main targets the Enterprise users, it is safe to
 assume that the correct approach would be to also be more user-focused and
 simplify things and avoid confusions by being case insensitive as well.

 Also, a quick search on existing issues validates the need for this
 improvement:
 http://jira.xwiki.org/issues/?jql=text%20~%20%22case%20insensitive%22

 What do you think? Is it OK to keep XWiki case sensitive, or would you
 prefer it case insensitive? Bring arguments.

 I have also created a jira issue for this idea:
 http://jira.xwiki.org/browse/XWIKI-11412 to track it in the future.

 Thanks,
 Eduard
 ___
 devs mailing list
 d...@xwiki.org
 http://lists.xwiki.org/mailman/listinfo/devs
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Flaming Less to CSS processor

2014-10-27 Thread Guillaume Louis-Marie Delhumeau
Hi.

Yes the LESS compiler is running on the server, except for the preview box
of the Flamingo Theme Application.

You should be able to put any valid LESS code in the advanced section of
that application.

For example, if you want to set a bootstrap variable that the application
does not handle, you could add:

@modal-content-bg: red;

But you can also add new CSS classes, like:
.myClass{
  background-color: red;
}
and this class can use LESS functions and bootstrap mixins:
.myClass{
  background-color: darken(red, 10%); // LESS function
  .make-xs-column(12); // Bootstrap mixin
}

And the class will be added to the default style.css. I am updating
http://extensions.xwiki.org/xwiki/bin/view/Extension/Flamingo+Theme+Application

I hope this helps,

2014-10-27 16:01 GMT+01:00 Gerritjan Koekkoek gerritjankoekk...@gmail.com:

 Does the Less to CSS preprocessor in the Flamingo themes app run on the
 server?
 What documentation is available (or examples of what kind of Less code can
 be entered in the Advanced Less box?
 ___
 users mailing list
 users@xwiki.org
 http://lists.xwiki.org/mailman/listinfo/users




-- 
Guillaume Delhumeau (gdelhum...@xwiki.com)
Research  Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


[xwiki-users] [ANN] XWiki 5.4.6 released

2014-10-16 Thread Guillaume Louis-Marie Delhumeau
The XWiki development team is proud to announce the availability of XWiki
5.4.6.

This release is a stabilization version that fix important bugs discovered
in the 5.4.5 version.

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/ReleaseNotesXWiki546

Thanks
-The XWiki dev team
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] xwiki_vs_confluence

2014-09-25 Thread Guillaume Lerouge
Hi Alex,

thanks for your interest in XWiki! Out of curiosity, what would be the main
reasons why you're considering moving away from Confluence?

We're always interested in finding our more about what other wikis might do
better / worse (or just differently) from XWiki!

As for the migration, as stated by Thomas there's a module that you can use
for this.

Best,

Guillaume

On Thu, Sep 25, 2014 at 10:44 AM, Thomas Mortagne thomas.morta...@xwiki.com
 wrote:

 On Thu, Sep 25, 2014 at 10:33 AM, asteinberg asteinb...@dsw-it.de wrote:
  Hello Community,
 
 
 
  our company is looking for an alternative for our confluence wiki. It
 seems
  to me xwiki could be the right wiki for us.
 
  Now my question: Is there a way to migrate confluence with all insert
 files,
  sites and blogposts to xwiki?
 
 
 
  Thank you for your help.
 
 
 
  Best Regards,
 
  Alexander Steinberg
 
 
 
  ___
  users mailing list
  users@xwiki.org
  http://lists.xwiki.org/mailman/listinfo/users

 XWiki support importing confluence pages
 (
 http://extensions.xwiki.org/xwiki/bin/view/Extension/Filter+Confluence+XML+module
 )
 but not blog post yet. However it should not be too hard to do even if
 nobody I know has plan to work on it anytime soon (but I would gladly
 help anyone that would want to do it).

 --
 Thomas Mortagne
 ___
 users mailing list
 users@xwiki.org
 http://lists.xwiki.org/mailman/listinfo/users

___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] need advice about an extension developpment

2014-09-24 Thread Guillaume Louis-Marie Delhumeau
2014-09-23 14:37 GMT+02:00 Guillaume Louis-Marie Delhumeau 
gdelhum...@xwiki.com:

 Hi Pascal.

 2014-09-18 22:15 GMT+02:00 Pascal BASTIEN pbasnews-xw...@yahoo.fr:

 I'm pulling my hair out...

 If I hide the DIV #rightPanels (with class hidden or display none) the
 DIV contentcontainer is not automatically resized!


 Indeed it is not. Actually you need to change one class on the body tag
 to resize the main container.

 The class content means: left  right panels. hideleft means: only
 right panels and hideright the opposite.

 When there is no panels at all, the class hidelefthideright is used.


 I wonder why and above all I wonder how can I resize content side when
 rightPanels disapeared (with javascript and/or jquery).


 Just like how the panel wizard does: play with the body CSS classes.


Just to be clear: I mean play with the CSS classes via a JavaScript code ;)





 Any help will be apprecie :)

 Here two screenshot will be more explicite:
 http://snag.gy/zVIRU.jpg
 http://snag.gy/voZuE.jpg


 By the way, for  http://jira.xwiki.org/browse/XWIKI-10498
 http://tuljo.com/web-development/expanding-collapsing-sliding-div-jquery
 will help.


 Pascal B




 
  De : Pascal BASTIEN pbasnews-xw...@yahoo.fr
 À : Ecaterina Moraru (Valica) vali...@gmail.com; XWiki Users 
 users@xwiki.org
 Envoyé le : Mercredi 17 septembre 2014 21h40
 Objet : Re: [xwiki-users] need advice about an extension developpment


 Thxs you (again :-) )
 You have just confirmed what I was afraid of, I mean js + cookie.
 I will probably look into this collapsed menu , this week. but, I am not
 sure if this replies to your issue...
 If you like, I will show you the result... if I manage :-/



 
 De : Ecaterina Moraru (Valica) vali...@gmail.com
 À : Pascal BASTIEN pbasnews-xw...@yahoo.fr; XWiki Users 
 users@xwiki.org
 Envoyé le : Mercredi 17 septembre 2014 19h01
 Objet : Re: [xwiki-users] need advice about an extension developpment



 Hi Pascal,

 If you look at
 http://www.cssportal.com/css3-preview/showing-and-hiding-content-with-pure-css3.php
 the CSS code for making this work is using the :focus pseudo-class, which
 is triggered when the link is selected using the mouse pointer or keyboard.
 It's normal that if you navigate the focus of that element to be lost.

 If you want something persistent you must implement it with JS and
 cookies. CSS is not the tool to achieve these things.


 On this topic there is also this issue
 http://jira.xwiki.org/browse/XWIKI-10498 but this is not a priority and
 not sure when/who will try to fix it (maybe even you :) )

 Thanks,
 Caty




 On Wed, Sep 17, 2014 at 4:48 PM, Pascal BASTIEN pbasnews-xw...@yahoo.fr
 wrote:

 Hello,
 
 I try to writing an extension to add the right panel collapsible (with
 CSS only). Something like this:
 http://www.cssportal.com/css3-preview/demo/css-menu-ex4.html (hide and
 seek panel)
 explained here
 http://www.cssportal.com/css3-preview/showing-and-hiding-content-with-pure-css3.php
 I inserted code in rightpanels.vm and CSS but the limitation is when I
 navigate on another xwiki page/space the right panel is reset. My right
 panel is  not persistent.
 Do you have an advice to make my right panel persistent:
 - if user show panel and change current page, right panel  must be still
 open
 - if user hide panel and change current page right panel must be  still
 hide
 
 javascript (and cookie) are mandatory in my case?
 Do you have an elegant tip: an secret xwiki API ?
 
 Thxs
 
 Pascal B
 ___
 users mailing list
 users@xwiki.org
 http://lists.xwiki.org/mailman/listinfo/users
 
 ___
 users mailing list
 users@xwiki.org
 http://lists.xwiki.org/mailman/listinfo/users
 ___
 users mailing list
 users@xwiki.org
 http://lists.xwiki.org/mailman/listinfo/users




 --
 Guillaume Delhumeau (gdelhum...@xwiki.com)
 Research  Development Engineer at XWiki SAS
 Committer on the XWiki.org project




-- 
Guillaume Delhumeau (gdelhum...@xwiki.com)
Research  Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Can I send email to a group with xwiki 6?

2014-09-24 Thread Guillaume Louis-Marie Delhumeau
($groups=$groupsAPI.getAllLocalGroupsNames())
 #foreach($group in $groups)
   * [[$group]]
 #end

 ---
 Get the email of all users in a group (using velocity)
 ## This request
 ##set ($sql = , BaseObject as obj where obj.name=doc.fullName and
 obj.className='XWiki.XWikiGroups')
 ##set ($allGroups = $xwiki.searchDocuments($sql))
 ##  OR thisAPI
 #set($rightsAPI=$xwiki.rightsmanager)
 #set($groupsAPI=$rightsAPI.getGroupsApi())
 #set($allGroups=$groupsAPI.getAllLocalGroupsNames())

 #foreach ($group in $allGroups)
   * $group
   #set ($groupdoc = $xwiki.getDocument($group))
   ##set ($groupMembers =
 $util.sort($xwiki.rightsmanager.getAllMembersNamesForGroup($groupdoc.name
 )))
   #set ($groupMembers =
 $util.sort($xwiki.rightsmanager.getAllMembersNamesForGroup($group)))
   ## groupedoc.name $groupdoc.name
   ##set ($groupMembers = $xwiki.rightsmanager.getAllMembersNamesForGroup($
 groupdoc.name))
   #set ($groupMembers =
 $xwiki.rightsmanager.getAllMembersNamesForGroup($group))
   ##$groupMembers
   #foreach ($mem in $groupMembers)
 #set ($userdoc = $xwiki.getDocument($mem))
 ##set ($em = $userdoc.display(email,view,$mem)) $embr
 #set ($em = $userdoc.display(email,view,$mem))
 #if ($em != 'mailto:')
   $em
 #end
   #end
 #end
 -


 All Team Members on the Wiki (using velocity)

 #set ($sql = , BaseObject as obj where obj.name=doc.fullName and
 obj.className='XWiki.XWikiUsers')
 #set ($allUsers = $xwiki.searchDocuments($sql))
 #foreach ($user in $allUsers)
   #set ($userdoc = $xwiki.getDocument($user))
   #set ($mail = $userdoc.display(email,view,$user))
   #if ($mail != 'mailto:')
 $user $mail
   #end
 #end




 {{/velocity}}


 Pascal B



 
  De : Pascal BASTIEN pbasnews-xw...@yahoo.fr
 À : XWiki Users users@xwiki.org
 Envoyé le : Mardi 26 août 2014 10h23
 Objet : Re: [xwiki-users] Can I send email to a group with xwiki 6?



 Sorry I didn't take the time to writing this loop (another priorities on
 Xwiki)
 But I hope  to find some time to writing it... :-)



 
  De : Shaddy danigagli...@gmail.com
 À : users@xwiki.org
 Envoyé le : Mardi 26 août 2014 10h02
 Objet : Re: [xwiki-users] Can I send email to a group with xwiki 6?


 Pascal BASTIEN pbasnews-xwiki@... writes:
 
  Thxs. I will use a loop then.
 
  




 Hello everybody,

 I'm currently working on the same issue.

 Can you show how you managed to send an email to a group of users??

 Thank you very much.

 Daniele.

 ___
 users mailing list
 users@xwiki.org
 http://lists.xwiki.org/mailman/listinfo/users
 ___
 users mailing list
 users@xwiki.org
 http://lists.xwiki.org/mailman/listinfo/users




-- 
Guillaume Delhumeau (gdelhum...@xwiki.com)
Research  Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] need advice about an extension developpment

2014-09-23 Thread Guillaume Louis-Marie Delhumeau
Hi Pascal.

2014-09-18 22:15 GMT+02:00 Pascal BASTIEN pbasnews-xw...@yahoo.fr:

 I'm pulling my hair out...

 If I hide the DIV #rightPanels (with class hidden or display none) the DIV
 contentcontainer is not automatically resized!


Indeed it is not. Actually you need to change one class on the body tag
to resize the main container.

The class content means: left  right panels. hideleft means: only
right panels and hideright the opposite.

When there is no panels at all, the class hidelefthideright is used.


 I wonder why and above all I wonder how can I resize content side when
 rightPanels disapeared (with javascript and/or jquery).


Just like how the panel wizard does: play with the body CSS classes.



 Any help will be apprecie :)

 Here two screenshot will be more explicite:
 http://snag.gy/zVIRU.jpg
 http://snag.gy/voZuE.jpg


 By the way, for  http://jira.xwiki.org/browse/XWIKI-10498
 http://tuljo.com/web-development/expanding-collapsing-sliding-div-jquery
 will help.


 Pascal B




 
  De : Pascal BASTIEN pbasnews-xw...@yahoo.fr
 À : Ecaterina Moraru (Valica) vali...@gmail.com; XWiki Users 
 users@xwiki.org
 Envoyé le : Mercredi 17 septembre 2014 21h40
 Objet : Re: [xwiki-users] need advice about an extension developpment


 Thxs you (again :-) )
 You have just confirmed what I was afraid of, I mean js + cookie.
 I will probably look into this collapsed menu , this week. but, I am not
 sure if this replies to your issue...
 If you like, I will show you the result... if I manage :-/



 
 De : Ecaterina Moraru (Valica) vali...@gmail.com
 À : Pascal BASTIEN pbasnews-xw...@yahoo.fr; XWiki Users users@xwiki.org
 
 Envoyé le : Mercredi 17 septembre 2014 19h01
 Objet : Re: [xwiki-users] need advice about an extension developpment



 Hi Pascal,

 If you look at
 http://www.cssportal.com/css3-preview/showing-and-hiding-content-with-pure-css3.php
 the CSS code for making this work is using the :focus pseudo-class, which
 is triggered when the link is selected using the mouse pointer or keyboard.
 It's normal that if you navigate the focus of that element to be lost.

 If you want something persistent you must implement it with JS and
 cookies. CSS is not the tool to achieve these things.


 On this topic there is also this issue
 http://jira.xwiki.org/browse/XWIKI-10498 but this is not a priority and
 not sure when/who will try to fix it (maybe even you :) )

 Thanks,
 Caty




 On Wed, Sep 17, 2014 at 4:48 PM, Pascal BASTIEN pbasnews-xw...@yahoo.fr
 wrote:

 Hello,
 
 I try to writing an extension to add the right panel collapsible (with
 CSS only). Something like this:
 http://www.cssportal.com/css3-preview/demo/css-menu-ex4.html (hide and
 seek panel)
 explained here
 http://www.cssportal.com/css3-preview/showing-and-hiding-content-with-pure-css3.php
 I inserted code in rightpanels.vm and CSS but the limitation is when I
 navigate on another xwiki page/space the right panel is reset. My right
 panel is  not persistent.
 Do you have an advice to make my right panel persistent:
 - if user show panel and change current page, right panel  must be still
 open
 - if user hide panel and change current page right panel must be  still
 hide
 
 javascript (and cookie) are mandatory in my case?
 Do you have an elegant tip: an secret xwiki API ?
 
 Thxs
 
 Pascal B
 ___
 users mailing list
 users@xwiki.org
 http://lists.xwiki.org/mailman/listinfo/users
 
 ___
 users mailing list
 users@xwiki.org
 http://lists.xwiki.org/mailman/listinfo/users
 ___
 users mailing list
 users@xwiki.org
 http://lists.xwiki.org/mailman/listinfo/users




-- 
Guillaume Delhumeau (gdelhum...@xwiki.com)
Research  Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Report - 6.2-rc-1

2014-09-23 Thread Guillaume Louis-Marie Delhumeau
2014-09-18 17:38 GMT+02:00 Marius Dumitru Florea 
mariusdumitru.flo...@xwiki.com:

 Impressive work! Well done!


Indeed. I have seen a lot of created issues recently. It is a major help!

Thanks!



 Thanks,
 Marius

 On Thu, Sep 18, 2014 at 9:15 AM, Andreea Popescu
 andreea.pope...@xwiki.com wrote:
  Hello all,
 
  During the last few days we have conducted smoke testing on: Firefox 32,
  Chrome 37, IE8, IE9, IE10 and IE11. Also, I would like to mention that I
  have conducted no full test so far on this version. The next full text
 will
  most likely take place after version 6.2 is launched. If you wish for us
 to
  conduct a full test on a certain browser, we will gladly honour your
  request.
 
  This link offers an overview of the issues and improvements reported by
 the
  team on the 6.2-rc-1 version:
 
 http://jira.xwiki.org/issues/?jql=affectedVersion%20in%20%28%226.2-rc-1%22%29
 
  We shall continue testing for other issues and improvements.
  Have a good day!
 
  --
  Andreea Zenovia Popescu
  QA Engineer @XWiki
  ___
  users mailing list
  users@xwiki.org
  http://lists.xwiki.org/mailman/listinfo/users
 ___
 users mailing list
 users@xwiki.org
 http://lists.xwiki.org/mailman/listinfo/users




-- 
Guillaume Delhumeau (gdelhum...@xwiki.com)
Research  Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] [xwiki-devs] [UX] Wiki - Space - Page concepts pitch

2014-07-31 Thread Guillaume Louis-Marie Delhumeau
My 2 cents:

A wiki = a website (or a drive).
A space = a folder (BTW, the space icon is actually a folder icon!).
A page = a page inside that folder.

In XWiki, everything is a page, including the users and the applications.


2014-07-31 11:13 GMT+02:00 Ecaterina Moraru (Valica) vali...@gmail.com:

 Hi,

 We did some usability testing sessions and found out that one of the
 biggest problems users are facing is that they don't understand the Home -
 Wiki - Space - Page concepts.
 Because of this confusion:
 - they are creating a wiki instead of a space or a page,
 - they don't know where they are located when looking at a page (in the
 main wiki or in a subwiki),
 - they don't know how to navigate to the pages they've created,
 - very confused that we have a Main space in every wiki,
 - they are having a hard time making a difference between a space and an
 application,
 - hard to understand everything is a page,
 - etc.

 We could do many things in order to improve our navigation, but one thing I
 want us to focus in this mail thread is the explanation of Wiki - Space -
 Page concepts on the Main.WebHome.

 Currently the content of the Welcome Block is:

 = Welcome to your wiki =
 
  It's an easy-to-edit website that will help you work better together.
 This
  Wiki is made of //pages// sorted by //spaces//. You're currently in the
  **Main** space, looking at its home page (**WebHome**).
 
  Learn how to use XWiki with the [[Getting Started Guide]]


  You can then use the [[Sandbox space]] to try out your wiki's features.
 

 I would like to replace this message with an introductory text that explain
 the concepts (there were also some ideas that maybe we need some images to
 represent the hierarchy, etc.) and I need your opinion on this subject.

 So, how would you pitch the Wiki - Space - Page concepts to newcomers?

 Thanks,
 Caty
 ___
 devs mailing list
 d...@xwiki.org
 http://lists.xwiki.org/mailman/listinfo/devs

___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


Re: [xwiki-users] Last LibreOffice version

2014-07-25 Thread Guillaume Fenollar
Hello,

Yes it should IMO. LibreOffice is a very important element of a lot of
XWiki installations, I'm also speaking with my experience of xwiki.com
clients. Having last versions tested, and eventually the best last version
fully compatible with xwiki would be great.
I've been using 4.2 LO servers with last versions of XWiki without noticing
large issues, but haven't digged it enough so more testing would be very
useful.
Thank you,

Guillaume
Le 24 juil. 2014 12:52, Andreea Popescu andreea.pope...@xwiki.com a
écrit :

 Hello all,

 Lately, I have spent time testing the last LibreOffice version and noticed
 that several of its features are not visible in XWiki after they had been
 imported. This makes me ask your opinion regarding the necessity to
 establish a section on XWiki.org in which the LibreOffice compatibility
 would be visible to the community. Should such a section be established?

 Thank you,
 Andreea
 ___
 users mailing list
 users@xwiki.org
 http://lists.xwiki.org/mailman/listinfo/users

___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users


  1   2   3   4   5   6   7   8   >