Re: [xwiki-users] [Proposal][UX] Feedback for Visible Save buttons

[Denis GERMAIN]

Great proposition ! I like it.

I see that the subject has also diverted to the fact that you can "save and
continue" and "save and view". Some of our users are lost the first time as
they click "save and continue" and don't understand why they are still in
edit mode. Clarifying this would indeed be a good idea, even though they
usually get the distinction quickly after that.

Regards,
Denis

2017-04-26 17:01 GMT+02:00 Ecaterina Moraru (Valica) :

> On Wed, Apr 26, 2017 at 5:41 PM, Craig Wright  wrote:
>
> > Hi Caty,
> >
> > I am a fan of “B”.
> >
> > I like the idea of putting the changelog and autosave options above on a
> > preceding row. I would argue that for most users, their eyes only see the
> > leftmost buttons as the functionally useful area. Thus putting Cancel on
> > the far right effectively “hides” the button.
> >
>
> Yes, the most visible buttons are the ones on the left side and that's the
> purpose. We need people to see the Save button :)
> Now, 'summary' functionality is not mandatory when editing and can also be
> disabled from Administration - Editing.
> Having it on a separate line is not an option since we initial idea of the
> thread is to provide a fixed bottom bar, when the viewport is small. So
> there are all on a single bar in order to be compact.
>
>
> >
> > For the purposes of mobile, I think it is acceptable to hide the
> changelog
> > and autosave options on small-screen resolutions. (Such as when I am
> > editing from iPhone, I am highly unlikely to leave a changelog message
> > anyway.)
> >
>
> I haven't iterated much on the mobile version, but the mockup I have is
> http://design.xwiki.org/xwiki/bin/download/Proposal/
> IdeaVisibleSave/mobile.png
> It can be improved, and as you said we could decide that on mobile we can
> hide some functionality, but again hard to have stats to justify what is
> used/needed or not.
>
> Thanks,
> Caty
>
>
> > FWIW, taborder should be the following:
> >
> > 1. Edit input
> > 2. Changelog input
> > 3. Save button
> > 4. Preview button
> > 5. Cancel button
> > 6. Autosave option
> >
> > My $0.02. :)
> >
> > Thanks,
> > Craig
> >
> > > On Apr 26, 2017, at 2:20 PM, Ecaterina Moraru (Valica) <
> > vali...@gmail.com> wrote:
> > >
> > > Hi,
> > >
> > > On Wed, Apr 26, 2017 at 2:39 PM, Craig Wright  > > wrote:
> > >
> > >> Overall I like these changes. A couple of suggestions:
> > >>
> > >> No one in my community understands “Save and Continue” versus “Save
> and
> > >> View”. Dropping the “and Continue” is a great step, but I would go
> > farther
> > >> and give “Save and View” the emphasis color (blue, in this case). That
> > is
> > >> the more highly understood behavior. “Save” (and continue editing) is
> > >> useful but not as generally useful as “Save and View”. Especially if
> you
> > >> are dropping Preview.
> > >>
> > >> FWIW, I use Preview more often from WYSIWYG mode since there is not a
> > 1:1
> > >> translation of editor view to page view. Whereas, when I am editing
> > source,
> > >> I can predict how it will look most of the time. :)
> > >>
> > >> I would also move the Cancel button over next to the other buttons.
> If I
> > >> had to rate which buttons I use the most frequently, “Cancel” would be
> > at
> > >> the top, followed by “Save and View,” followed very very distantly by
> > “Save
> > >> and Continue."
> > >>
> > >>
> > > This is very interesting behavior. I would love to be able to have some
> > > usage stats, but with XWiki being installable and independently hosted,
> > > stats are always hard to get by.
> > >
> > > Personally I use "Save" a lot (I like to save often in order to not
> lose
> > > stuff), but I usually use the keyboard shortcut, not necessarily the
> > > button. It is true that 'Preview' in WYSIWYG has its usages, especially
> > > when using macros or nested macros, since the result is not accurate.
> > >
> > > Regarding "Save & View" I always do it as a final step, while I never
> use
> > > "Cancel" - i just navigate away or hit the browser's 'Back'.
> > >
> > > Also in terms of functionality the "Autosave" can be used instead of
> the
> > > "Save", so we can remove 'Save' (especially in case of advanced users).
> > >
> > > So the only stats I have are from the http://playground.xwiki.org <
> > http://playground.xwiki.org/> from the
> > > past 2 months. These are the top 3 pages edited, see
> > > http://design.xwiki.org/xwiki/bin/download/Proposal/IdeaVisibleSave/
> > UsageFebApr2017.png  xwiki/bin/download/Proposal/
> > IdeaVisibleSave/UsageFebApr2017.png>
> > >
> > > Now let's see the heatmaps:
> > > - Sandbox.WebHome:
> > > http://design.xwiki.org/xwiki/bin/download/Proposal/
> > IdeaVisibleSave/Sandbox-Home.png  > xwiki/bin/download/Proposal/IdeaVisibleSave/Sandbox-Home.png>
> > > - Sandbox.TestPage1:
> > > http://design.xwiki.org/xwiki/bin/download/Proposal/
> > 

Re: [xwiki-users] display page title and name(url) while creating a page

[Denis GERMAIN]

Jumping abord conversation, the URL friendly links part looks promising !

Users in my company tend to add a lot of special characters in their pages,
and having an option to strip those would really be useful for us.

I'm afraid I've not read the rest of the conversation so I won't bother you
further ;-)

Regards
Denis GERMAIN

2017-04-21 16:00 GMT+02:00 Vincent Massol <vinc...@massol.net>:

>
> > On 21 Apr 2017, at 15:36, Miroslav Galajda <miroslav.gala...@gmail.com>
> wrote:
> >
> > Hi,
> > the solution I've described is javascript based and runs on client-side.
> > From what I know, the component-based solution, which you propose, would
> > require to have url-friendly conversion component usable in java and not
> as
> > javascript code. Am I right?
>
> Yes you’re right but:
>
> 1) There’s also a Java API, see https://github.com/slugify/slugify
> 2) If we also offer a UIX then it can be implemented in a wiki page for
> example and you can use JS.
>
> Thanks
> -Vincent
>
> > On 21 April 2017 at 15:28, Vincent Massol <vinc...@massol.net> wrote:
> >
> >> Hi Miroslav,
> >>
> >>> On 21 Apr 2017, at 15:05, Miroslav Galajda <miroslav.gala...@gmail.com
> >
> >> wrote:
> >>>
> >>> Hi, let me enter into this conversion.
> >>> Some time ago I've asked for help how to solve problem with diacritics
> >> (or
> >>> accents) in page names when creating new pages so that the have
> >>> url-friendly names. You can search for "strip accents from page name
> used
> >>> in url" in xwiki users mailing list. I've got no hint or solution from
> >>> xwiki community till today.
> >>>
> >>> I've come with solution that ensures for simple users, creating
> >>> url-friendly names without requiring them to think about the concept of
> >> the
> >>> page name or page title. They simple enter the desired human readably
> >> page
> >>> name, and in the code behind of the page creation, I have made some
> >>> modifications in createinline.vm to hook into page creation process.
> The
> >>> modifications are mainly javascript based, where I've attache to submit
> >>> event of the "form#create", where I replace the entered "title" with
> the
> >>> one for url-friendly. And for url-friendly name I've used this
> javascript
> >>> based solution on https://pid.github.io/speakingurl/.
> >>> I've integrated this principle also into page creation process of FAQ
> and
> >>> Blog applications, which we are using in our xwiki installation.
> >>>
> >>> It would be nice if you could integrate this principle into xwiki so
> that
> >>> everyone can have nice url-friendly urls without worring about it. It
> is
> >>> also suitable for english speaking users. You don't have to worry about
> >>> entering spaces or other non-url allowed characters, which make url
> look
> >>> ugly.
> >>
> >> That looks very nice!
> >>
> >> One way forward I could think about:
> >> * We provide some Create script service to return a URL-friendly string.
> >> We introduce a component role for this. We refactor createinline.vm to
> use
> >> it and to display the URL.
> >> * You could then contribute your code as an extension that we make
> >> available on extensions.xwiki.org for users to install
> >> * We decide later on if we want to bundle it by default
> >>
> >> If we don’t agree about displaying the URL by default all the time then
> an
> >> option is to introduce a UIX in createinline.vm for that. And this
> could be
> >> implemented in your extension too for example or by default in XWiki
> >> (possibly with an Admin setting).
> >>
> >> WDYT?
> >>
> >> Thanks
> >> -Vincent
> >>
> >>>
> >>> Thank you
> >>>
> >>> Best regards
> >>> Miroslav Galajda
> >>>
> >>> On 21 April 2017 at 14:02, Vincent Massol <vinc...@massol.net> wrote:
> >>>
> >>>>
> >>>>> On 21 Apr 2017, at 13:52, Marius Dumitru Florea <
> >>>> mariusdumitru.flo...@xwiki.com> wrote:
> >>>>>
> >>>>> On Fri, Apr 21, 2017 at 2:16 PM, Vincent Massol <vinc...@massol.net>
> >>>> wrote:
> >>>>>
> >>>>>> Hi Caty,
> >>>>>&

Re: [xwiki-users] XWiki User Group Lyon ?

[Denis GERMAIN]

Hi

Lyon is a bit far from Bordeaux, sadly, otherwise we might have been
interested

Regards
Denis GERMAIN

2017-04-14 11:30 GMT+02:00 Thomas Mortagne <thomas.morta...@xwiki.com>:

> Cool, my first answer :)
>
> I just created https://groups.google.com/forum/#!forum/xwiki-user-
> group-lyon
> as a rally point for now, don't hesitate to add you as member. Will
> probably invest in a Meetup account once we have enough people
> interested.
>
> On Fri, Apr 14, 2017 at 11:13 AM, redactech <walaa.che...@ecrin.com>
> wrote:
> > Hi Thomas,
> >
> > I am in Grenoble and we have just started to use xwiki in our company. I
> > would be very interested to meet up with other people in the area to talk
> > about it, let me know if you organise something.
> >
> >
> >
> > --
> > View this message in context: http://xwiki.475771.n2.nabble.
> com/XWiki-User-Group-Lyon-tp7603474p7603488.html
> > Sent from the XWiki- Users mailing list archive at Nabble.com.
>
>
>
> --
> Thomas Mortagne
>

Re: [xwiki-users] [UX] Administration Improvements

[Denis GERMAIN]

We are running multiple flavors of Xwiki including 7.4.4 (production),
8.4.4 and 9.0

1. what sections are always needed and maybe we could prioritize them;
Users and Groups are the most heavily used menu in administration for us
We also rely heavily on Import/Exports

2. what sections could be grouped together, since they are related;

3. what sections are not relevant and could be removed (maybe because they
are too technical, or not needed or rarely used);
Creating subwikis is sometime used so it shouldn't be dropped (for us)
Templates are not often used but really important to us

4. if there are important recurring things missing from administration;
There is no easy way to troubleshoot users rights on a page. In other
words, sometime users set rights on "pages and children" OR "pages", and it
causes all sort of trouble
- some users can't see some pages but they should (due to misconfiugration
of the rights)
- some users can open pages with the direct link but can't navigate to it
a) I don't see why there is 2 types of rights on a page, I would personnaly
keep only "pages and children" rights and drop "page only" rights
b) To troubleshoot, I'd like to have a way to see why some users can see
the page and some don't, or to help me find where the problem is

5. other ideas?
I find the Template creation (with provider) procedure counter intuitive.
Maybe it could be simplified ?

2017-02-23 11:28 GMT+01:00 Ecaterina Moraru (Valica) :

> Thanks Stéphane for your answer. It's very helpful.
>
> Caty
>
> On Thu, Feb 23, 2017 at 12:15 PM, Stéphane LASSIRE  >
> wrote:
>
> > Hello,
> >
> > What a nice idea.
> > We are using a Xwiki 7.4.4 release.
> >
> > 1. what sections are always needed and maybe we could prioritize them;
> > -> Users / groups / right access / extensions / statistics
> >
> > 2. what sections could be grouped together, since they are related;
> > -> Configuration / Look / Email
> >
> > 3. what sections are not relevant and could be removed (maybe because
> they
> > are too technical, or not needed or rarely used);
> > -> wikis (we are using only 1 instance, so no need of multi configs for
> us)
> >
> > 4. if there are important recurring things missing from administration;
> > -> rights "inspector", not really to know the right of a page inside a
> > space
> > for all users and groups
> > -> activity of a group / user. I try to put a counter inside pages to see
> > if
> > it is accessed but it a basic solution. I would like to see how much some
> > pages are viewed. The statistics are limited on this part
> >
> > 5. other ideas?
> > -> see 4
> >
> > Thanks
> >
> > Cordialement
> >
> > Stéphane Lassire
> > Chargé de l'informatique et de la communication
> > Courriel : slass...@cesap.asso.fr
> >
> > -Message d'origine-
> > De : users [mailto:users-boun...@xwiki.org] De la part de Ecaterina
> Moraru
> > (Valica)
> > Envoyé : mardi 21 février 2017 16:15
> > À : XWiki Mailinglist; XWiki Mailinglist
> > Objet : [xwiki-users] [UX] Administration Improvements
> >
> > Hi,
> >
> > We are thinking about improving the Administration, so would be great to
> > hear your opinion about:
> > 1. what sections are always needed and maybe we could prioritize them; 2.
> > what sections could be grouped together, since they are related; 3. what
> > sections are not relevant and could be removed (maybe because they are
> too
> > technical, or not needed or rarely used); 4. if there are important
> > recurring things missing from administration; 5. other ideas?
> >
> > We are particularly interested in 1. and that is sections that are used
> > often and would love to know which are those (since they differ so much
> > depending on usage).
> >
> > Let us know,
> > Caty
> >
>

Re: [xwiki-users] Small attachments in DB, big ones in files?

[Denis GERMAIN]

As a pure curiosity, why do you need to differanciate big and small
attachements ? Is it for performance reasons ? Something else ?

2017-02-11 19:57 GMT+01:00 Lilianne E. Blaze :

> Hello,
> Yes, I read the documentation, that wasn't what I was asking.
> So, is it impossible? I can't be the first person that could use
> something like that.
>
> Greetings, L
>
> On 2/10/2017 9:12 PM, Mohamed Boussaa wrote:
> > Hello,
> >
> > XWiki offers the possibility to store your attachments in the database or
> > directly in the file system.
> >
> > See more details in this link:
> > http://platform.xwiki.org/xwiki/bin/view/AdminGuide/
> Attachments#HAttachmentStorage
> >
> > Regards,
> > Mohamed
> >
> > On Fri, Feb 10, 2017 at 8:34 PM, Lilianne E. Blaze <
> > lilia...@lilianne-blaze.net> wrote:
> >
> >> Hello,
> >> Is it possible to store attachments below a certain size inside a
> >> database, while storing bigger ones in files?
> >>
> >> I assume when using HSQL database it is usually preferred to store
> >> attachments in files?
> >>
> >> Greetings, Lilianne
> >>
> >
>
>

Re: [xwiki-users] [xwiki-devs] [ANN] First version of the XWiki docker packaging

[Denis GERMAIN]

Agreed,

The longer you leave it, the longer people might use it instead of the
official. As of today, the official isn't even the first to appear in the
list when you search for xwiki in dockerhub (but I suspect this will soon
change as people start pulling it).

And people who already have pulled it won't be affected aside from the fact
that they won't get updates, so no impact for them.

Regards,
Denis

2017-02-09 11:40 GMT+01:00 Vincent Massol :

> Ok so now that we have an official xwiki image on dockerhub at
> https://hub.docker.com/_/xwiki/ we need to decide what we do with
> https://hub.docker.com/r/xwiki/xwiki-mysql-tomcat/
>
> I think we should remove it to avoid confusion.
>
> Anyone having any issue with me removing it now? WDYT?
>
> Thanks
> -Vincent
>
> > On 16 Jan 2017, at 18:37, Vincent Massol  wrote:
> >
> > Hi everyone,
> >
> > I’ve started a first version of a XWiki docker packaging at
> https://github.com/xwiki-contrib/docker-xwiki and I’ve created an
> automated build on DockerHub at https://hub.docker.com/u/xwiki/. The goal
> is to provide an official packaging done by the XWiki dev team.
> >
> > Since I’m a recent user of Docker I’m sure I’ve made plenty of mistakes
> and not following some best practices, even though I’ve tried my best to do
> that ;)
> >
> > So it would be great if:
> > * Some users could try it out and let me know how it works
> > * Users could tell me what they’d expect in term of setup from a docker
> distribution.
> > * Some Docker experts review my code and let me know what I should
> improve!
> >
> > After I receive some confirmation that it works well-enough, my goal is
> to document it as an official way of installing xwiki on xwiki.org.
> >
> > Feel free to create jiras for ideas and bugs at
> http://jira.xwiki.org/browse/XDOCKER.
> >
> > Thanks a lot!
> > -Vincent
> >
> > PS: Note that I’m sure some will want a different DB, such as postgreSQL
> for example. That should be easy to do. Pull request accepted! :)
> >
>
>

Re: [xwiki-users] Mass query/replace after Mediawiki to Xwiki conversion

[Denis GERMAIN]

That's what I had in mind yes, but I didn't know what else to do until now.

The first piece of velocity code does work with "word" replacement but
doesn't really like replacing "{{{" or "{{code}}" macros (they are
interpreted before execution). I managed to do what I want with trial and
error (by changing the code a bit and escaping curly brackets) and it works
on a single page.

I also got a few timeouts while trying to generalize the process on all my
pages but it seems OK now. I checked a few pages out of the hundreds I have
migrated and they now have {{code}} tags.

Thanks for your help

2017-01-26 10:46 GMT+01:00 Thomas Mortagne <thomas.morta...@xwiki.com>:

> Plus updating the database directly is dangerous since it means out of
> sync caches and solr search index among other things.
>
> On Thu, Jan 26, 2017 at 10:28 AM, Denis GERMAIN <dt.germ...@gmail.com>
> wrote:
> > Thanks !
> >
> > I was trying to update directly the database table xwd_content from
> > public.xwikidoc but I haven't had much success yet (not to mention that
> > this is probably not a good idea).
> >
> > Denis GERMAIN
> >
> > 2017-01-26 9:50 GMT+01:00 Vincent Massol <vinc...@massol.net>:
> >
> >> Hi Denis,
> >>
> >> > On 24 Jan 2017, at 16:01, Denis GERMAIN <dt.germ...@gmail.com> wrote:
> >> >
> >> > Hello,
> >> >
> >> > After having succesfully migrated from a 300 pages mediawiki to xwiki
> >> > (which worked like a charm with the FilterStream app),
> >>
> >> Nice :)
> >>
> >> > I need to find a way
> >> > to automate modifications to the migrated xwiki pages.
> >> >
> >> > In mediawiki, I could create "highlighted boxes" in which I put code
> by
> >> > simply adding a space caracter as the very first caracter of each
> line.
> >> > FilterStream application converted this empty space to "}}}" and "{{{"
> >> > which is totally the right way to convert this from the MW syntax to
> >> XWiki
> >> > syntax, but doesn't fit my needs.
> >> >
> >> > Ideally, I'd like to convert every "{{{" tags to "{{code}}" and every
> >> "}}}"
> >> > tags to "{{/code}}"
> >> >
> >> > Do you have any idea how to achieve this ?
> >>
> >> I’ve created this FAQ entry for you:
> >> http://www.xwiki.org/xwiki/bin/view/FAQ/How%20to%
> 20search%20and%20replace%
> >> 20content%20programmatically
> >>
> >> I hope it answers your question :)
> >>
> >> Thanks
> >> -Vincent
> >>
> >> >
> >> > Regards
> >> > Denis GERMAIN
> >>
> >>
>
>
>
> --
> Thomas Mortagne
>

Re: [xwiki-users] Mass query/replace after Mediawiki to Xwiki conversion

[Denis GERMAIN]

Thanks !

I was trying to update directly the database table xwd_content from
public.xwikidoc but I haven't had much success yet (not to mention that
this is probably not a good idea).

Denis GERMAIN

2017-01-26 9:50 GMT+01:00 Vincent Massol <vinc...@massol.net>:

> Hi Denis,
>
> > On 24 Jan 2017, at 16:01, Denis GERMAIN <dt.germ...@gmail.com> wrote:
> >
> > Hello,
> >
> > After having succesfully migrated from a 300 pages mediawiki to xwiki
> > (which worked like a charm with the FilterStream app),
>
> Nice :)
>
> > I need to find a way
> > to automate modifications to the migrated xwiki pages.
> >
> > In mediawiki, I could create "highlighted boxes" in which I put code by
> > simply adding a space caracter as the very first caracter of each line.
> > FilterStream application converted this empty space to "}}}" and "{{{"
> > which is totally the right way to convert this from the MW syntax to
> XWiki
> > syntax, but doesn't fit my needs.
> >
> > Ideally, I'd like to convert every "{{{" tags to "{{code}}" and every
> "}}}"
> > tags to "{{/code}}"
> >
> > Do you have any idea how to achieve this ?
>
> I’ve created this FAQ entry for you:
> http://www.xwiki.org/xwiki/bin/view/FAQ/How%20to%20search%20and%20replace%
> 20content%20programmatically
>
> I hope it answers your question :)
>
> Thanks
> -Vincent
>
> >
> > Regards
> > Denis GERMAIN
>
>

[xwiki-users] Mass query/replace after Mediawiki to Xwiki conversion

[Denis GERMAIN]

Hello,

After having succesfully migrated from a 300 pages mediawiki to xwiki
(which worked like a charm with the FilterStream app), I need to find a way
to automate modifications to the migrated xwiki pages.

In mediawiki, I could create "highlighted boxes" in which I put code by
simply adding a space caracter as the very first caracter of each line.
FilterStream application converted this empty space to "}}}" and "{{{"
which is totally the right way to convert this from the MW syntax to XWiki
syntax, but doesn't fit my needs.

Ideally, I'd like to convert every "{{{" tags to "{{code}}" and every "}}}"
tags to "{{/code}}"

Do you have any idea how to achieve this ?

Regards
Denis GERMAIN

Re: [xwiki-users] Possible optimisations for xwiki/xwiki-mysql-tomcat docker image

[Denis GERMAIN]

I was confused also about the difference because for me also it shouldn't
be 1.6 GB but that's what "docker images" tells me. On dockerhub, it's the
"compressed size" so maybe compression could explain this ?

For the 300 MB, you have to take into account how the docker images are
built. In the Dockerfile, each time you write a line, you create a layer.
One of the error you made was to write the Dockerfile as you would write an
installation procedure.
It's more readable, but if you make multiple modifications on the
filesystem, you store it each time. The most costly one in this case is "RUN
chown -R tomcat8:tomcat8 /var/lib/tomcat8" which just changes the owner on
230 MB worth of data, thus adding 230 MB of nearly identical data as a new
layer.

You can view the impact of each layer here
https://microbadger.com/images/xwiki/xwiki-mysql-tomcat (you can also get a
html code to get a nice image for you repository).

Regards

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

> Hi Denis,
>
> > On 18 Jan 2017, at 15:46, Denis GERMAIN <dt.germ...@gmail.com> wrote:
> >
> > Hi list,
> >
> > Vincent Massol has asked for code review after official docker image
> > annoncement and though I am no Docker expert, I have found a few leads to
> > reduce image size and might have some suggestions to improve it.
> >
> > With 3 little changes I have gained about 500 MB, but I still have to
> make
> > sure everything still works.
> > - 200 of those MB where gained by a commonly used trick : adding
> > "--no-install-recommends" option to apt-get.
> > Some packages that are commonly installed with libreoffice might have
> been
> > skipped and I still have to determine if it's OK or not.
> >
> > - The other 300 MB are safe. Most of it comes from "RUN chown -R
> > tomcat8:tomcat8 /var/lib/tomcat8" being moved inside the same layer as
> the
> > curl xwiki.war && unzip.
>
> This is great! Thanks so much for reviewing it and proposing ideas :)
>
> For my knowledge, could you explain quickly how this wins 300MB (it seems
> magical :))?
>
> Also, the image take “only” 900MB (see https://hub.docker.com/r/
> xwiki/xwiki-mysql-tomcat/tags/) so I don’t understand why it takes 1.6GB
> for you.
>
> Thanks a lot
> -Vincent
>
> >
> > docker images
> > REPOSITORY   TAG IMAGE
> > IDCREATED SIZE
> > xwiki-mysql-tomcat   after
> > b05844c94dd07 seconds ago   1.157 GB
> > xwiki-mysql-tomcat       before
> > 174d549368d52 hours ago 1.689 GB
> >
> > As soon as I have checked this works, I'll do a pull request.
> > In the meantime, code is online on
> > https://github.com/zwindler/docker-xwiki-1/tree/clear_apt
> >
> > Regards
> > Denis GERMAIN
>
>

[xwiki-users] Possible optimisations for xwiki/xwiki-mysql-tomcat docker image

[Denis GERMAIN]

Hi list,

Vincent Massol has asked for code review after official docker image
annoncement and though I am no Docker expert, I have found a few leads to
reduce image size and might have some suggestions to improve it.

With 3 little changes I have gained about 500 MB, but I still have to make
sure everything still works.
- 200 of those MB where gained by a commonly used trick : adding
"--no-install-recommends" option to apt-get.
Some packages that are commonly installed with libreoffice might have been
skipped and I still have to determine if it's OK or not.

- The other 300 MB are safe. Most of it comes from "RUN chown -R
tomcat8:tomcat8 /var/lib/tomcat8" being moved inside the same layer as the
curl xwiki.war && unzip.

docker images
REPOSITORY   TAG IMAGE
IDCREATED SIZE
xwiki-mysql-tomcat   after
b05844c94dd07 seconds ago   1.157 GB
xwiki-mysql-tomcat   before
174d549368d52 hours ago 1.689 GB

As soon as I have checked this works, I'll do a pull request.
In the meantime, code is online on
https://github.com/zwindler/docker-xwiki-1/tree/clear_apt

Regards
Denis GERMAIN

Re: [xwiki-users] Filesystem Attachment Store Porter Extension missing

[Denis . Germain]

Thank you, it seems to be working.

Just so you know, the button on the top of the page in the snippet page 
still points to extension.xwiki.org and not snippets.xwiki.org, but can be 
found at the bottom of the page in the "Attachment" tab

Regards




De :Marius Dumitru Florea 
A : XWiki Users 
Date :  02/08/2016 10:18
Objet : Re: [xwiki-users] Filesystem Attachment Store Porter Extension 
missing
Envoyé par :"users" 



On Tue, Aug 2, 2016 at 9:55 AM,  wrote:

> I need to migrate a Wiki in Filesystem attachment Store mode because I
> have an existing wiki in which I need to import a big XAR file (>130MB)
>
> The procedure is explained here
> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Attachments
>
> "If you already have a wiki and want to take advantage of the Filesystem
> Attachment Store, you should use the Filesystem Attachment Porter to 
move
> your existing attachments onto the filesystem. "
>
>

> but the script seem to have been removed a few days/weeks ago ...
>
> 
http://extensions.xwiki.org/xwiki/bin/view/Extension/Filesystem+Attachment+Porter



Indeed. We recently extracted the snippets from extensions.xwiki.org and
moved them to snippets.xwiki.org . Unfortunately we didn't setup any
redirect from the old location to the new one. Sorry about this.


>
>
> How can I move from DB to FS ?
>

See
http://snippets.xwiki.org/xwiki/bin/view/Extension/Filesystem+Attachment+Porter

.


>
> Regards,
> ___
> 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

[xwiki-users] Filesystem Attachment Store Porter Extension missing

[Denis . Germain]

I need to migrate a Wiki in Filesystem attachment Store mode because I 
have an existing wiki in which I need to import a big XAR file (>130MB)

The procedure is explained here 
http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Attachments

"If you already have a wiki and want to take advantage of the Filesystem 
Attachment Store, you should use the Filesystem Attachment Porter to move 
your existing attachments onto the filesystem. "

but the script seem to have been removed a few days/weeks ago ...
http://extensions.xwiki.org/xwiki/bin/view/Extension/Filesystem+Attachment+Porter

How can I move from DB to FS ?

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

[xwiki-users] Removing old pages redirections

[Denis . Germain]

Hi,

I have trouble renaming pages because of an old redirection on my 7.4.2 
XWiki instance.

I'll try to summerize how it happened :
- First, a wiki page called "Framework" with a lot of subpages was 
created.
- Then, the users wanted to rearrange the subpages so they created a copy 
which they named Framework.new
- When they where happy with the new page, they renamed the initial 
Framework page in Framework.old. 
- Trying to rename Framework.new into Framework failed

My problem is that by default, when you rename a page (in this version of 
XWiki at least), the checkbox "Redirect to new page" is checked, 
effectivement creating a HTTP redirect when users are still using the old 
link. I understand the advantage of this method : you can have the page 
renamed without breaking the existing links.

But now Framework.new can't be renamed in Framework, as the 
Framework.WebHome URL points to Framework.old.WebHome. Even if I remove 
all the pages from Framework.old, I still can't rename it.

Is there a menu/velocity script to remove these redirections ?

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

[xwiki-users] AUTO : Denis Germain est absent (retour 15/06/2016)

[Denis . Germain]

Je suis absent(e) du bureau jusqu'au 15/06/2016

Je suis actuellement en congés.

En cas d'urgence, merci de contacter le Support Technique Isocel
support-techni...@isocel.info ou Tel: 05 24 54 99 61


Remarque : ceci est une réponse automatique à votre message  "[xwiki-users]
Filesize limits for fileUpload plugin" envoyé le 23/05/2016 05:16:36.

C'est la seule notification que vous recevrez pendant l'absence de cette
personne.

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

[xwiki-users] AUTO : Denis Germain est absent (retour 28/12/2015)

[Denis . Germain]

Je suis absent(e) du bureau jusqu'au 28/12/2015

Je suis actuellement en congés.

En cas d'urgence, merci de contacter le Support Technique Isocel
support-techni...@isocel.info ou Tel: 05 24 54 99 80


Remarque : ceci est une réponse automatique à votre message  "Re:
[xwiki-users] Documentation on Velocity binding for 'config' object?"
envoyé le 18/12/2015 15:08:53.

C'est la seule notification que vous recevrez pendant l'absence de cette
personne.

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

Re: [xwiki-users] Export to PDF java.lang.NullPointerException on some pages (possibly if images are too big)

[Denis . Germain]

Ok, thanks

I see that there is a reference to 
http://jira.xwiki.org/browse/XWIKI-12871

Is it really an objective of the 7.4 or might it be moved to another later 
release ?

Can I do about it beside waiting for 7.4 to be released ? Can I upgrade a 
component myself as a workaround ?

Regards



De :Thomas Mortagne <thomas.morta...@xwiki.com>
A : XWiki Users <users@xwiki.org>
Date :  02/12/2015 10:18
Objet : Re: [xwiki-users] Export to PDF java.lang.NullPointerException on 
some pages (possibly if images are too big)
Envoyé par :"users" <users-boun...@xwiki.org>



Looks like http://jira.xwiki.org/browse/XWIKI-8274. From what I
understand the image format is too recent for the old FOP 1.1 version
we are still using.

On Wed, Dec 2, 2015 at 10:02 AM,  <denis.germ...@isocel.info> wrote:
> When trying to export PDF some (not all) page of my XWiki 7.2, I get an
> error in the log and the PDF is never generated. HTML export works fine.
>
> Here are the first lines from the error :
>
> Dec  2 09:37:07 xwiki01 server: java.lang.NullPointerException: 
Parameter
> alpha must not be null
> Dec  2 09:37:07 xwiki01 server: at
> org.apache.fop.pdf.AlphaRasterImage.(AlphaRasterImage.java:57)
> ~[fop-1.1.jar:na]
> Dec  2 09:37:07 xwiki01 server: at
> org.apache.fop.pdf.AlphaRasterImage.(AlphaRasterImage.java:71)
> ~[fop-1.1.jar:na]
> Dec  2 09:37:07 xwiki01 server: at
> 
org.apache.fop.render.pdf.ImageRenderedAdapter.setup(ImageRenderedAdapter.java:127)
> ~[fop-1.1.jar:na]
> Dec  2 09:37:07 xwiki01 server: at
> org.apache.fop.pdf.PDFDocument.addImage(PDFDocument.java:816)
> ~[fop-1.1.jar:na]
> Dec  2 09:37:07 xwiki01 server: at
> 
org.apache.fop.render.pdf.AbstractPDFImageHandler.handleImage(AbstractPDFImageHandler.java:46)
> ~[fop-1.1.jar:na]
>
> I can't say for sure that the size of the images in those pages is the
> cause of the export failure, but just before the stacktrace, I get a few
> WARN
>
> Dec  2 09:37:06 xwiki01 server: 2015-12-02 09:37:06,773 [
> 
http://xwiki01:8080/xwiki/bin/export/White_Rabbit/Fabrication/GitLab+-+Manuel+d%27utilisation/WebHome?format=pdf=1=0=1=0=0=0

> ] WARN  o.a.f.a.FOUserAgent - Line 1 of a paragraph overflows the
> available area by 9000 millipoints. (See position 26:14146)
> Dec  2 09:37:07 xwiki01 server: 2015-12-02 09:37:07,104 [
> 
http://xwiki01:8080/xwiki/bin/export/White_Rabbit/Fabrication/GitLab+-+Manuel+d%27utilisation/WebHome?format=pdf=1=0=1=0=0=0

> ] ERROR o.a.f.a.FOUserAgent - Error while rendering page 3. Reason:
> java.lang.NullPointerException: Parameter alpha must not be null
> Dec  2 09:37:07 xwiki01 server: java.lang.NullPointerException: 
Parameter
> alpha must not be null
>
> Have you already seen this problem? I think I've found similar issues 
but
> for version 4.X back in 2012, though it was about "bad" PNG images then.
>
> Regards,
> Denis GERMAIN
>
>
>
>
>
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users



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

[xwiki-users] Export to PDF java.lang.NullPointerException on some pages (possibly if images are too big)

[Denis . Germain]

When trying to export PDF some (not all) page of my XWiki 7.2, I get an 
error in the log and the PDF is never generated. HTML export works fine.

Here are the first lines from the error :

Dec  2 09:37:07 xwiki01 server: java.lang.NullPointerException: Parameter 
alpha must not be null
Dec  2 09:37:07 xwiki01 server: at 
org.apache.fop.pdf.AlphaRasterImage.(AlphaRasterImage.java:57) 
~[fop-1.1.jar:na]
Dec  2 09:37:07 xwiki01 server: at 
org.apache.fop.pdf.AlphaRasterImage.(AlphaRasterImage.java:71) 
~[fop-1.1.jar:na]
Dec  2 09:37:07 xwiki01 server: at 
org.apache.fop.render.pdf.ImageRenderedAdapter.setup(ImageRenderedAdapter.java:127)
 
~[fop-1.1.jar:na]
Dec  2 09:37:07 xwiki01 server: at 
org.apache.fop.pdf.PDFDocument.addImage(PDFDocument.java:816) 
~[fop-1.1.jar:na]
Dec  2 09:37:07 xwiki01 server: at 
org.apache.fop.render.pdf.AbstractPDFImageHandler.handleImage(AbstractPDFImageHandler.java:46)
 
~[fop-1.1.jar:na]

I can't say for sure that the size of the images in those pages is the 
cause of the export failure, but just before the stacktrace, I get a few 
WARN

Dec  2 09:37:06 xwiki01 server: 2015-12-02 09:37:06,773 [
http://xwiki01:8080/xwiki/bin/export/White_Rabbit/Fabrication/GitLab+-+Manuel+d%27utilisation/WebHome?format=pdf=1=0=1=0=0=0
] WARN  o.a.f.a.FOUserAgent - Line 1 of a paragraph overflows the 
available area by 9000 millipoints. (See position 26:14146)
Dec  2 09:37:07 xwiki01 server: 2015-12-02 09:37:07,104 [
http://xwiki01:8080/xwiki/bin/export/White_Rabbit/Fabrication/GitLab+-+Manuel+d%27utilisation/WebHome?format=pdf=1=0=1=0=0=0
] ERROR o.a.f.a.FOUserAgent - Error while rendering page 3. Reason: 
java.lang.NullPointerException: Parameter alpha must not be null
Dec  2 09:37:07 xwiki01 server: java.lang.NullPointerException: Parameter 
alpha must not be null

Have you already seen this problem? I think I've found similar issues but 
for version 4.X back in 2012, though it was about "bad" PNG images then.

Regards,
Denis GERMAIN





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

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

[Denis . Germain]

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

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

[Denis . Germain]

I see. This is what happens when you "forget" to read release notes. 
Though you'll notice I carefully avoided the word "bug", in case this was 
normal and I was mistaken ;-)

I guess will have to find out if we can change our way of organising 
information because the spaces being irrelevant is a BIG change. 

Especially we used the widget that listed all the pages of a given space. 
This was massively used by the differents teams to find quickly their own 
information in their own space. 
Now I don't know how to do that.

Thanks and sorry for the inconveniance.

Denis GERMAIN




De :"Guillaume \"Louis-Marie\" Delhumeau" <gdelhum...@xwiki.com>
A : XWiki Users <users@xwiki.org>
Date :  19/11/2015 13:06
Objet : Re: [xwiki-users] Strange behaviour when creating new pages => new 
spaces are created instead (xwiki 7.2)
Envoyé par :"users" <users-boun...@xwiki.org>



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

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