[xwiki-users] What would you like to see in the XWiki 7.x cycle?
Dear XWiki users, We’re getting close to the end of the XWiki 6.x cycle (6.4 is planned for the end of December) and in January we’ll start developing the XWiki 7.x cycle (which will last the whole 2015 year), starting with XWiki 7.0. Thus it’s time for the XWiki devs to start defining the global roadmap for XWiki 7.x. As XWiki users, I’d like to know if you have some needs for XWiki 7.x. What would you be interested in seeing in XWiki 7.x? I’d like to start some proposal on the xwiki devs list (for the XWiki 7.x cycle) around end of December so it would be nice if you could shoot your suggestion ideas fast so that we can take them into account in the discussion! :) Thanks a lot for your help and I hope you’re enjoying using XWiki! -Vincent Massol XWiki Committer
Hello. New XWiki user here. First, a big thanks, we are enjoying XWiki. :) We have a fairly common use case, using the wiki for documenting servers and systems, trying to build an SKMS ala ITIL. What i'd like to see is better formatting of text being cut & pasted from (mainly) Word. The single biggest issue I have heard complaints about is formatting. We are moving away from a Lotus Domino environment and here too the formatting is mangled (this may have everything to do with Domino and nothing with XWiki however) when doing copy/paste. I'd like tables to work like they do in Excel. When I press the tab key I want to move to the next field. I want to be able to size the table with my mouse in real-time. I want the columns to be plainly visible, not just the rows. I want numbered lists to be a core feature. Making text different colors and/or fonts should work like in a regular word processor, with a menu item in the WYSIWYG editor. That's from the top of my head, anyway. Have a great weekend. Regards, Daniel On Fri, Dec 5, 2014 at 1:17 PM, [email protected] <[email protected]> wrote:
Dear XWiki users,
We’re getting close to the end of the XWiki 6.x cycle (6.4 is planned for the end of December) and in January we’ll start developing the XWiki 7.x cycle (which will last the whole 2015 year), starting with XWiki 7.0.
Thus it’s time for the XWiki devs to start defining the global roadmap for XWiki 7.x.
As XWiki users, I’d like to know if you have some needs for XWiki 7.x. What would you be interested in seeing in XWiki 7.x?
I’d like to start some proposal on the xwiki devs list (for the XWiki 7.x cycle) around end of December so it would be nice if you could shoot your suggestion ideas fast so that we can take them into account in the discussion! :)
Thanks a lot for your help and I hope you’re enjoying using XWiki!
-Vincent Massol XWiki Committer
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Regards/Mvh Daniel Lundh
Hello, You invited us Vincent, then here my proposals. +10 to thanks Xwiki task force team (especially to support my harassment) WYSIWYG based on FckEditor better to work on tables IMO +1: "I want the columns to be plainly visible, not just the rows" especially when we edit a table Add tab "Source" on WYSIWYG editor in Blog and FAQ Add anchor lists on the page (a macros?) to add an link to an anchor #HAnchorTitle) and update anchor link when anchor target is renamed (difficult) & detect link with anchor when a page is renamed. Use pure CSS for xwiki menu (without JS) Last but not least: forbidden Vincent to awake devs at 2 hours in the morning on IRC xwiki chanel to chatting about an obscure xwiki code... ;-) Thxs for all. Pascal BASTIEN De : Daniel Lundh <[email protected]> À : XWiki Users <[email protected]> Envoyé le : Vendredi 5 décembre 2014 13h34 Objet : Re: [xwiki-users] What would you like to see in the XWiki 7.x cycle? Hello. New XWiki user here. First, a big thanks, we are enjoying XWiki. :) We have a fairly common use case, using the wiki for documenting servers and systems, trying to build an SKMS ala ITIL. What i'd like to see is better formatting of text being cut & pasted from (mainly) Word. The single biggest issue I have heard complaints about is formatting. We are moving away from a Lotus Domino environment and here too the formatting is mangled (this may have everything to do with Domino and nothing with XWiki however) when doing copy/paste. I'd like tables to work like they do in Excel. When I press the tab key I want to move to the next field. I want to be able to size the table with my mouse in real-time. I want the columns to be plainly visible, not just the rows. I want numbered lists to be a core feature. Making text different colors and/or fonts should work like in a regular word processor, with a menu item in the WYSIWYG editor. That's from the top of my head, anyway. Have a great weekend. Regards, Daniel On Fri, Dec 5, 2014 at 1:17 PM, [email protected] <[email protected]> wrote:
Dear XWiki users,
We’re getting close to the end of the XWiki 6.x cycle (6.4 is planned for the end of December) and in January we’ll start developing the XWiki 7.x cycle (which will last the whole 2015 year), starting with XWiki 7.0.
Thus it’s time for the XWiki devs to start defining the global roadmap for XWiki 7.x.
As XWiki users, I’d like to know if you have some needs for XWiki 7.x. What would you be interested in seeing in XWiki 7.x?
I’d like to start some proposal on the xwiki devs list (for the XWiki 7.x cycle) around end of December so it would be nice if you could shoot your suggestion ideas fast so that we can take them into account in the discussion! :)
Thanks a lot for your help and I hope you’re enjoying using XWiki!
-Vincent Massol XWiki Committer
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Regards/Mvh Daniel Lundh _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Hello, First I like previous feedbacks (on wysiwig, tables, etc). Then some random "ideas" of things I'd love to see in xwiki: - flavors ! ;-) - EDM ! I agree some extensions already go in this way, and it's better to have this as extension(s) and not in core, but maybe a default EDM oriented flavor could be very interesting for enterprises - more "inline" editing of some very standard pieces of the UI (editing a panel, editing the custom menu from Menu extension, customizing xwiki top menu, customizing page menu/actions, etc). Like an online editor of all content except page content ? Would be so nice to have a little pencil icon appear on hovering of a panel title ... :-) - better wysiwyg edition of some specific macros (include, etc), I suppose you see what I refer to - more easy customization of pdf export (possibility to choose a template at time of export and not only through url param, from a list, have some app to customize header/footer without having to customize skin prefs, manage a catalog of templates, etc) - have a way to assign a "label" to a set of pages revisions (ie, similar to a tag in mercurial, but on wiki pages). Then I could, for example, export a xar, but based on a specific "label". Or export a multi-page pdf, based on a label. (pretty useful, or even essential, for EDM flavor) More in terms of "extensions", so I'm not sure it fits here, but : - an extension to manage trainings (catalog, members, schedule) - managing distribution-lists (Exchange) - note that I might contribute something for this, if I can ... - roundtrip with DITA (import/wysiwyg-annotations-comments/export) (DITA is Darwin Information Typing Architecture) - move back to java 6 ! (no, that's a joke, sorry :D ) Note: these are my own "needs" (say, wishes) as wiki admin, I'll try to ask some users to get their feedbacks, Br, Jeremie 2014-12-05 15:13 GMT+01:00 Pascal BASTIEN <[email protected]>:
Hello,
You invited us Vincent, then here my proposals.
+10 to thanks Xwiki task force team (especially to support my harassment)
WYSIWYG based on FckEditor better to work on tables IMO +1: "I want the columns to be plainly visible, not just the rows" especially when we edit a table
Add tab "Source" on WYSIWYG editor in Blog and FAQ
Add anchor lists on the page (a macros?) to add an link to an anchor #HAnchorTitle) and update anchor link when anchor target is renamed (difficult) & detect link with anchor when a page is renamed. Use pure CSS for xwiki menu (without JS)
Last but not least: forbidden Vincent to awake devs at 2 hours in the morning on IRC xwiki chanel to chatting about an obscure xwiki code... ;-)
Thxs for all. Pascal BASTIEN
De : Daniel Lundh <[email protected]> À : XWiki Users <[email protected]> Envoyé le : Vendredi 5 décembre 2014 13h34 Objet : Re: [xwiki-users] What would you like to see in the XWiki 7.x cycle?
Hello.
New XWiki user here.
First, a big thanks, we are enjoying XWiki. :)
We have a fairly common use case, using the wiki for documenting servers and systems, trying to build an SKMS ala ITIL.
What i'd like to see is better formatting of text being cut & pasted from (mainly) Word. The single biggest issue I have heard complaints about is formatting. We are moving away from a Lotus Domino environment and here too the formatting is mangled (this may have everything to do with Domino and nothing with XWiki however) when doing copy/paste.
I'd like tables to work like they do in Excel. When I press the tab key I want to move to the next field. I want to be able to size the table with my mouse in real-time. I want the columns to be plainly visible, not just the rows.
I want numbered lists to be a core feature.
Making text different colors and/or fonts should work like in a regular word processor, with a menu item in the WYSIWYG editor.
That's from the top of my head, anyway.
Have a great weekend.
Regards, Daniel
On Fri, Dec 5, 2014 at 1:17 PM, [email protected] <[email protected]> wrote:
Dear XWiki users,
We’re getting close to the end of the XWiki 6.x cycle (6.4 is planned for the end of December) and in January we’ll start developing the XWiki 7.x cycle (which will last the whole 2015 year), starting with XWiki 7.0.
Thus it’s time for the XWiki devs to start defining the global roadmap for XWiki 7.x.
As XWiki users, I’d like to know if you have some needs for XWiki 7.x. What would you be interested in seeing in XWiki 7.x?
I’d like to start some proposal on the xwiki devs list (for the XWiki 7.x cycle) around end of December so it would be nice if you could shoot your suggestion ideas fast so that we can take them into account in the discussion! :)
Thanks a lot for your help and I hope you’re enjoying using XWiki!
-Vincent Massol XWiki Committer
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
--
Regards/Mvh Daniel Lundh
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
On Fri, Dec 5, 2014 at 2:34 PM, Daniel Lundh <[email protected]> wrote:
Hello.
New XWiki user here.
First, a big thanks, we are enjoying XWiki. :)
We have a fairly common use case, using the wiki for documenting servers and systems, trying to build an SKMS ala ITIL.
What i'd like to see is better formatting of text being cut & pasted from (mainly) Word. The single biggest issue I have heard complaints about is formatting. We are moving away from a Lotus Domino environment and here too the formatting is mangled (this may have everything to do with Domino and nothing with XWiki however) when doing copy/paste.
I'd like tables to work like they do in Excel. When I press the tab key I want to move to the next field. I want to be able to size the table with my mouse in real-time. I want the columns to be plainly visible, not just the rows.
I want numbered lists to be a core feature.
Making text different colors and/or fonts should work like in a regular word processor, with a menu item in the WYSIWYG editor.
This is already possible. http://platform.xwiki.org/xwiki/bin/view/Features/WysiwygEditor#HQuickRefere... . You need to enable it from the WYSIWYG editor section in the wiki administration. It's not very straightforward but this http://platform.xwiki.org/xwiki/bin/view/AdminGuide/WysiwygEditor#HPluginsan... can help. The rest is very good feedback. Thanks, Marius
That's from the top of my head, anyway.
Have a great weekend.
Regards, Daniel
On Fri, Dec 5, 2014 at 1:17 PM, [email protected] <[email protected]> wrote:
Dear XWiki users,
We’re getting close to the end of the XWiki 6.x cycle (6.4 is planned for the end of December) and in January we’ll start developing the XWiki 7.x cycle (which will last the whole 2015 year), starting with XWiki 7.0.
Thus it’s time for the XWiki devs to start defining the global roadmap for XWiki 7.x.
As XWiki users, I’d like to know if you have some needs for XWiki 7.x. What would you be interested in seeing in XWiki 7.x?
I’d like to start some proposal on the xwiki devs list (for the XWiki 7.x cycle) around end of December so it would be nice if you could shoot your suggestion ideas fast so that we can take them into account in the discussion! :)
Thanks a lot for your help and I hope you’re enjoying using XWiki!
-Vincent Massol XWiki Committer
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
--
Regards/Mvh Daniel Lundh _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Hi, I'd add some stuff, based on feedbacks from my (advanced) users: - they usually consider that readability of titles and sub-titles (headings) inside wiki pages is not very good, difficult to differentiate them - when they create new pages (by putting [[new page>>newpage]]), once new page created, they find difficult to add links to this same new page from other pages (have to remember the name). It seems they didn't know about the corresponding feature in wysiwyg editor ... - a smarter TOC macro, that would optionally include in TOC, content from child pages (child meaning here, linked from current page). The macro would in this case, update headings levels of included (linked) pages, so their min level correspond to current TOC level + 1 (not sure I'm clear ... but let's say that it would generate a coherent TOC, without having to renumber child pages headings) Not very new: some people have difficulties really understanding concepts of Space, page, how to name them, what happens when they enter a new page name, etc ... I added "Space Hierarchy" panel, but they seem even more confused :) (feedbacks based on 5.x) BR, Jeremie 2014-12-05 18:19 GMT+01:00 Marius Dumitru Florea < [email protected]>:
On Fri, Dec 5, 2014 at 2:34 PM, Daniel Lundh <[email protected]> wrote:
Hello.
New XWiki user here.
First, a big thanks, we are enjoying XWiki. :)
We have a fairly common use case, using the wiki for documenting servers and systems, trying to build an SKMS ala ITIL.
What i'd like to see is better formatting of text being cut & pasted from (mainly) Word. The single biggest issue I have heard complaints about is formatting. We are moving away from a Lotus Domino environment and here too the formatting is mangled (this may have everything to do with Domino and nothing with XWiki however) when doing copy/paste.
I'd like tables to work like they do in Excel. When I press the tab key I want to move to the next field. I want to be able to size the table with my mouse in real-time. I want the columns to be plainly visible, not just the rows.
I want numbered lists to be a core feature.
Making text different colors and/or fonts should work like in a regular word processor, with a menu item in the WYSIWYG editor.
This is already possible.
http://platform.xwiki.org/xwiki/bin/view/Features/WysiwygEditor#HQuickRefere... . You need to enable it from the WYSIWYG editor section in the wiki administration. It's not very straightforward but this
http://platform.xwiki.org/xwiki/bin/view/AdminGuide/WysiwygEditor#HPluginsan... can help.
The rest is very good feedback.
Thanks, Marius
That's from the top of my head, anyway.
Have a great weekend.
Regards, Daniel
On Fri, Dec 5, 2014 at 1:17 PM, [email protected] <[email protected]> wrote:
Dear XWiki users,
We’re getting close to the end of the XWiki 6.x cycle (6.4 is planned
for
the end of December) and in January we’ll start developing the XWiki 7.x cycle (which will last the whole 2015 year), starting with XWiki 7.0.
Thus it’s time for the XWiki devs to start defining the global roadmap for XWiki 7.x.
As XWiki users, I’d like to know if you have some needs for XWiki 7.x. What would you be interested in seeing in XWiki 7.x?
I’d like to start some proposal on the xwiki devs list (for the XWiki 7.x cycle) around end of December so it would be nice if you could shoot your suggestion ideas fast so that we can take them into account in the discussion! :)
Thanks a lot for your help and I hope you’re enjoying using XWiki!
-Vincent Massol XWiki Committer
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
--
Regards/Mvh Daniel Lundh _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Hello, Well, there are two main feedbacks usability that I have received about XWiki: - Difficult to insert images on the page ( The copy and paste of does not work). Some user preferred to write the page on Word and after that import the page in XWiki. - +1 - Better tables! Its hard to structure information on tables inside XWiki pages. +1 +10 to thanks Xwiki task force team DAnilo 2014-12-08 15:25 GMT-02:00 Jeremie BOUSQUET <[email protected]>:
Hi,
I'd add some stuff, based on feedbacks from my (advanced) users:
- they usually consider that readability of titles and sub-titles (headings) inside wiki pages is not very good, difficult to differentiate them - when they create new pages (by putting [[new page>>newpage]]), once new page created, they find difficult to add links to this same new page from other pages (have to remember the name). It seems they didn't know about the corresponding feature in wysiwyg editor ... - a smarter TOC macro, that would optionally include in TOC, content from child pages (child meaning here, linked from current page). The macro would in this case, update headings levels of included (linked) pages, so their min level correspond to current TOC level + 1 (not sure I'm clear ... but let's say that it would generate a coherent TOC, without having to renumber child pages headings)
Not very new: some people have difficulties really understanding concepts of Space, page, how to name them, what happens when they enter a new page name, etc ... I added "Space Hierarchy" panel, but they seem even more confused :)
(feedbacks based on 5.x)
BR, Jeremie
2014-12-05 18:19 GMT+01:00 Marius Dumitru Florea < [email protected]>:
On Fri, Dec 5, 2014 at 2:34 PM, Daniel Lundh <[email protected]> wrote:
Hello.
New XWiki user here.
First, a big thanks, we are enjoying XWiki. :)
We have a fairly common use case, using the wiki for documenting servers and systems, trying to build an SKMS ala ITIL.
What i'd like to see is better formatting of text being cut & pasted from (mainly) Word. The single biggest issue I have heard complaints about is formatting. We are moving away from a Lotus Domino environment and here too the formatting is mangled (this may have everything to do with Domino and nothing with XWiki however) when doing copy/paste.
I'd like tables to work like they do in Excel. When I press the tab key I want to move to the next field. I want to be able to size the table with my mouse in real-time. I want the columns to be plainly visible, not just the rows.
I want numbered lists to be a core feature.
Making text different colors and/or fonts should work like in a regular word processor, with a menu item in the WYSIWYG editor.
This is already possible.
http://platform.xwiki.org/xwiki/bin/view/Features/WysiwygEditor#HQuickRefere...
. You need to enable it from the WYSIWYG editor section in the wiki administration. It's not very straightforward but this
http://platform.xwiki.org/xwiki/bin/view/AdminGuide/WysiwygEditor#HPluginsan...
can help.
The rest is very good feedback.
Thanks, Marius
That's from the top of my head, anyway.
Have a great weekend.
Regards, Daniel
On Fri, Dec 5, 2014 at 1:17 PM, [email protected] <[email protected]
wrote:
Dear XWiki users,
We’re getting close to the end of the XWiki 6.x cycle (6.4 is planned for the end of December) and in January we’ll start developing the XWiki 7.x cycle (which will last the whole 2015 year), starting with XWiki 7.0.
Thus it’s time for the XWiki devs to start defining the global roadmap for XWiki 7.x.
As XWiki users, I’d like to know if you have some needs for XWiki 7.x. What would you be interested in seeing in XWiki 7.x?
I’d like to start some proposal on the xwiki devs list (for the XWiki 7.x cycle) around end of December so it would be nice if you could shoot your suggestion ideas fast so that we can take them into account in the discussion! :)
Thanks a lot for your help and I hope you’re enjoying using XWiki!
-Vincent Massol XWiki Committer
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
--
Regards/Mvh Daniel Lundh _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Danilo Amaral de Oliveira Engenheiro de Computação celular (11) 95282-3504
What I would like to see in XWiki 7.x: - A standard way of navigating the Wiki (I know there a several Extensions available, but this needs to be a basic feature of XWiki). This is my no. 1 complaint ;-). - Better layout, with numbered headers. This is the no. 1 complaint from our users. They are used to the way MS Word is able to format their documents. Numbered lists with blank lines for example. - A standard "Table of Contents", which displays the headers on a (large)page. This TOC should be "dockable"/"collapsable", iow always available to the users. - Automatic Update/Upgrade to latest XWiki version. -- View this message in context: http://xwiki.475771.n2.nabble.com/What-would-you-like-to-see-in-the-XWiki-7-... Sent from the XWiki- Users mailing list archive at Nabble.com.
jerem wrote
- they usually consider that readability of titles and sub-titles (headings) inside wiki pages is not very good, difficult to differentiate them
Why don't you use a "Style Sheet Extension" and completely define how each Header should look like? http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Skins http://platform.xwiki.org/xwiki/bin/view/DevGuide/SkinExtensionsTutorial -- View this message in context: http://xwiki.475771.n2.nabble.com/What-would-you-like-to-see-in-the-XWiki-7-... Sent from the XWiki- Users mailing list archive at Nabble.com.
WYSIWYG based on
FckEditor
PascalB wrote * *
better to work on tables IMO +1: "I want the columns to be plainly visible, not just the rows" especially when we edit a table
FckEditor? Or do you mean CKEditor <http://ckeditor.com/> ? -- View this message in context: http://xwiki.475771.n2.nabble.com/What-would-you-like-to-see-in-the-XWiki-7-... Sent from the XWiki- Users mailing list archive at Nabble.com.
+1 for numbered header +0 about TOC (user must be able to choose if he want a TOC on his page) In someone interested, on (my wiki), I use that to add numbered header and TOC:http://extensions.xwiki.org/xwiki/bin/view/Extension/TOC+Macro#HExample4:TOC... To add this code by default:---------------------------{{box cssClass="floatinginfobox" title="**Sommaire**"}} {{toc numbered="true" depth="3"/}} {{/box}} {{numberedheadings/}} //Voici le formatage type d'une page de l'Encyclopédie qu'il est conseillé d'appliquer. Si vous souhaitez conserver cette mise en page avec sommaire vous devez remplacer ce texte (et ne pas supprimer les macros ci-dessus).// = Titre de niveau un = Texte --------------------------- in all new doc of Encyclopédie space, I modify ./templates/editwysiwygnew.vm with--------------------------- ## Affiche un contenu type pour tous les nouveaux documents ouvert avec Wysiwyg #set($itemModLContenu = $xwiki.getDocument($escapetool.xml("Personnalisation.ModeleContenuEncyclopédie"))) #if ($tdoc.content == "" && $tdoc.space == $escapetool.xml("Encyclopédie")) $xwiki.getTextArea($itemModLContenu.getContent()) #else $xwiki.getTextArea($tdoc.content) #end ---------------------------Anyway, someone (who?) create a whishlist page on xwiki.org? Or is it useless? Thxs Pascal B De : Hamster <[email protected]> À : [email protected] Envoyé le : Mardi 9 décembre 2014 8h38 Objet : Re: [xwiki-users] What would you like to see in the XWiki 7.x cycle? What I would like to see in XWiki 7.x: - A standard way of navigating the Wiki (I know there a several Extensions available, but this needs to be a basic feature of XWiki). This is my no. 1 complaint ;-). - Better layout, with numbered headers. This is the no. 1 complaint from our users. They are used to the way MS Word is able to format their documents. Numbered lists with blank lines for example. - A standard "Table of Contents", which displays the headers on a (large)page. This TOC should be "dockable"/"collapsable", iow always available to the users. - Automatic Update/Upgrade to latest XWiki version. -- View this message in context: http://xwiki.475771.n2.nabble.com/What-would-you-like-to-see-in-the-XWiki-7-... Sent from the XWiki- Users mailing list archive at Nabble.com. _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
WYSIWYG based on
FckEditor
Yes you are right it is http://ckeditor.com/ (I was confused because I tested MoinMoin editor http://moinmo.in/FCKeditor and FckEditor probably changed his name) De : Hamster <[email protected]> À : [email protected] Envoyé le : Mardi 9 décembre 2014 9h06 Objet : Re: [xwiki-users] What would you like to see in the XWiki 7.x cycle? PascalB wrote * *
better to work on tables IMO +1: "I want the columns to be plainly visible, not just the rows" especially when we edit a table
FckEditor? Or do you mean CKEditor <http://ckeditor.com/> ? -- View this message in context: http://xwiki.475771.n2.nabble.com/What-would-you-like-to-see-in-the-XWiki-7-... Sent from the XWiki- Users mailing list archive at Nabble.com. _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Hi, 2014-12-09 9:00 GMT+01:00 Hamster <[email protected]>:
jerem wrote
- they usually consider that readability of titles and sub-titles (headings) inside wiki pages is not very good, difficult to differentiate them
Why don't you use a "Style Sheet Extension" and completely define how each Header should look like?
For the same reason you talked about numbered headings, because ideally I'd propose to have titles better by default :) BTW there's an extension to get numbered headings: http://extensions.xwiki.org/xwiki/bin/view/Extension/Numbered+Headings
http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Skins http://platform.xwiki.org/xwiki/bin/view/DevGuide/SkinExtensionsTutorial
-- View this message in context: http://xwiki.475771.n2.nabble.com/What-would-you-like-to-see-in-the-XWiki-7-... Sent from the XWiki- Users mailing list archive at Nabble.com. _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
jerem wrote
For the same reason you talked about numbered headings, because ideally I'd propose to have titles better by default :) BTW there's an extension to get numbered headings: http://extensions.xwiki.org/xwiki/bin/view/Extension/Numbered+Headings
True, my only concern is that the TOC Macro <http://extensions.xwiki.org/xwiki/bin/view/Extension/TOC+Macro> is maintained by the XWiki Development Team , but the Numbered Headings <http://extensions.xwiki.org/xwiki/bin/view/Extension/Numbered+Headings> is not (it's a contribution by Jeremie Bousquet). So future versions of XWIki might break the Numbered Headings. Those two extensions should idealy considered as one. :-) -- View this message in context: http://xwiki.475771.n2.nabble.com/What-would-you-like-to-see-in-the-XWiki-7-... Sent from the XWiki- Users mailing list archive at Nabble.com.
Hi! I'd add a list of proposals: 1. Add SRD documentation for XWiki 6.x 2. Some URLs are not shortened when using Tuckey's UrlRewriteFilter (even it is closed - there are some problems noted in tha last comment) 3. Admin Tools Application bug in Export pages with ' sign in page name 4. Broken cross-wiki links on page rename XWiki works fine in miltiwiki's environment, but page rename breaks cross-wiki links :( 5. Wiki to wiki rename in multiwiki environment 6. New ADD Link scenario in WYSIWYG editor - wiki -> Space -> Page -> Anchor selector in the WYSIWYG editor 7. XWiki.DeletedAttachments shows nothing when filesystem attachments are enabled. 8. Shrink Recycle Bin works only with main wiki and gives an error in attempt to purge all documents in recycle bin Kind regards, Dmitry Fri, 5 Dec 2014 19:19:52 +0200 от Marius Dumitru Florea <[email protected]>:
On Fri, Dec 5, 2014 at 2:34 PM, Daniel Lundh < [email protected] > wrote:
Hello.
New XWiki user here.
First, a big thanks, we are enjoying XWiki. :)
We have a fairly common use case, using the wiki for documenting servers and systems, trying to build an SKMS ala ITIL.
What i'd like to see is better formatting of text being cut & pasted from (mainly) Word. The single biggest issue I have heard complaints about is formatting. We are moving away from a Lotus Domino environment and here too the formatting is mangled (this may have everything to do with Domino and nothing with XWiki however) when doing copy/paste.
I'd like tables to work like they do in Excel. When I press the tab key I want to move to the next field. I want to be able to size the table with my mouse in real-time. I want the columns to be plainly visible, not just the rows.
I want numbered lists to be a core feature.
Making text different colors and/or fonts should work like in a regular word processor, with a menu item in the WYSIWYG editor.
This is already possible. http://platform.xwiki.org/xwiki/bin/view/Features/WysiwygEditor#HQuickRefere... . You need to enable it from the WYSIWYG editor section in the wiki administration. It's not very straightforward but this http://platform.xwiki.org/xwiki/bin/view/AdminGuide/WysiwygEditor#HPluginsan... can help.
The rest is very good feedback.
Thanks, Marius
That's from the top of my head, anyway.
Have a great weekend.
Regards, Daniel
On Fri, Dec 5, 2014 at 1:17 PM, [email protected] < [email protected] > wrote:
Dear XWiki users,
We’re getting close to the end of the XWiki 6.x cycle (6.4 is planned for the end of December) and in January we’ll start developing the XWiki 7.x cycle (which will last the whole 2015 year), starting with XWiki 7.0.
Thus it’s time for the XWiki devs to start defining the global roadmap for XWiki 7.x.
As XWiki users, I’d like to know if you have some needs for XWiki 7.x. What would you be interested in seeing in XWiki 7.x?
I’d like to start some proposal on the xwiki devs list (for the XWiki 7.x cycle) around end of December so it would be nice if you could shoot your suggestion ideas fast so that we can take them into account in the discussion! :)
Thanks a lot for your help and I hope you’re enjoying using XWiki!
-Vincent Massol XWiki Committer
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
--
Regards/Mvh Daniel Lundh _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
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. Best regards Harald Ommang Norway
On Tue, Dec 9, 2014 at 9:57 PM, Harald Ommang <[email protected]> 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.
Best regards Harald Ommang Norway _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne
Hi, On Tue, Dec 9, 2014 at 10:23 PM, Thomas Mortagne <[email protected]> wrote:
On Tue, Dec 9, 2014 at 9:57 PM, Harald Ommang <[email protected]> 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
Good, I was hoping I was wrong. If I am not completely wrong, my comment used to be valid...? What do you mean with "3 ways merge"? It is now clear to me that there is more to the Distribution Wizard than has (yet) met my eye :-) Harald -----Original Message----- From: users [mailto:[email protected]] On Behalf Of Thomas Mortagne Sent: 9. desember 2014 22:24 To: XWiki Users Subject: Re: [xwiki-users] What would you like to see in the XWiki 7.x cycle? On Tue, Dec 9, 2014 at 9:57 PM, Harald Ommang <[email protected]> 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.
Best regards Harald Ommang Norway _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-----Original Message----- From: users [mailto:[email protected]] On Behalf Of Guillaume Lerouge Sent: 9. desember 2014 22:29 To: XWiki Users Subject: Re: [xwiki-users] What would you like to see in the XWiki 7.x cycle? Hi, On Tue, Dec 9, 2014 at 10:23 PM, Thomas Mortagne <[email protected]> wrote:
On Tue, Dec 9, 2014 at 9:57 PM, Harald Ommang <[email protected]> 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
I might just do that, Guillaume :-) Harald _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
On Tue, Dec 9, 2014 at 10:28 PM, Guillaume Lerouge <[email protected]> wrote:
Hi,
On Tue, Dec 9, 2014 at 10:23 PM, Thomas Mortagne <[email protected]> wrote:
On Tue, Dec 9, 2014 at 9:57 PM, Harald Ommang <[email protected]> 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 ;-)
Distribution Wizard has been introduced in 4.2 so not really the latest version. And even before that export/import everything never really been standard upgrade process either.
Guillaume _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne
On Tue, Dec 9, 2014 at 10:31 PM, Harald Ommang <[email protected]> wrote:
Good, I was hoping I was wrong. If I am not completely wrong, my comment used to be valid...?
What do you mean with "3 ways merge"? It is now clear to me that there is more to the Distribution Wizard than has (yet) met my eye :-)
When you install a XAR extension (and the standard UI is a tree of XAR extension) each page get a 3 ways merge meaning that you get a merge between 3 versions: the previous standard version, what is currently in the database (i.e. you modifications) and the new standard version. That means that your changes are kept when you upgrade unless your changed conflict with a change between standard previous and new version in which case you can a detailed conflict UI where you can choose which version you want (and a proposed merge).
Harald
-----Original Message----- From: users [mailto:[email protected]] On Behalf Of Thomas Mortagne Sent: 9. desember 2014 22:24 To: XWiki Users Subject: Re: [xwiki-users] What would you like to see in the XWiki 7.x cycle?
On Tue, Dec 9, 2014 at 9:57 PM, Harald Ommang <[email protected]> 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.
Best regards Harald Ommang Norway _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne
Le 9 déc. 2014 22:37, "Thomas Mortagne" <[email protected]> a écrit :
On Tue, Dec 9, 2014 at 10:28 PM, Guillaume Lerouge <[email protected]>
wrote:
Hi,
On Tue, Dec 9, 2014 at 10:23 PM, Thomas Mortagne < [email protected]> wrote:
On Tue, Dec 9, 2014 at 9:57 PM, Harald Ommang <[email protected]
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 ;-)
Distribution Wizard has been introduced in 4.2 so not really the latest version. And even before that export/import everything never really been standard upgrade process either.
Sure, but you usually did reverse way : import new xwiki ui xar (and remember to uncheck standard pages customized, or have them overwritten). And yes, it was sometimes a hassle, and compared to that distribution wizard is really really great :)
Guillaume _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
I have say, upgrading makes me very nervous too..so, I'd definitely vote for anything that changes or enhances that process. So far, I'm terrified to even try an upgrade (currently on 5.4) since my wiki is production and we've done a fair bit of customized solutions to unique problems (likely not in a "supported" way maybe) . My fear is that some piece of code or settings will get overwritten which will break stuff and I won't know where to look to fix them. 😃 A wizard would be awesome to take the guess work out of it. As is, I've read some of the tutorials out there regarding upgrades several times but I'm not really able to determine the prescribed steps using those. I think at the end of the day I'm going to end up exporting my solutions as XAR's and then try importing them into an upgraded Xwiki environment too, since it seems easier to me.
On Dec 9, 2014, at 2:58 PM, Jeremie BOUSQUET <[email protected]> wrote:
Le 9 déc. 2014 22:37, "Thomas Mortagne" <[email protected]> a écrit :
On Tue, Dec 9, 2014 at 10:28 PM, Guillaume Lerouge <[email protected]>
wrote:
Hi,
On Tue, Dec 9, 2014 at 10:23 PM, Thomas Mortagne < [email protected]> wrote:
On Tue, Dec 9, 2014 at 9:57 PM, Harald Ommang <[email protected]
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 ;-)
Distribution Wizard has been introduced in 4.2 so not really the latest version. And even before that export/import everything never really been standard upgrade process either.
Sure, but you usually did reverse way : import new xwiki ui xar (and remember to uncheck standard pages customized, or have them overwritten). And yes, it was sometimes a hassle, and compared to that distribution wizard is really really great :)
Guillaume _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Hi Jason, On 10 Dec 2014 at 05:11:40, Jason Clemons ([email protected](mailto:[email protected])) wrote:
I have say, upgrading makes me very nervous too..
Have you ever tried using the Distribution Wizard?
so, I'd definitely vote for anything that changes or enhances that process. So far, I'm terrified to even try an upgrade (currently on 5.4) since my wiki is production and we've done a fair bit of customized solutions to unique problems (likely not in a "supported" way maybe) .
Well, first nobody should ever upgrade a wiki in production directly! You should make backups and do the upgrade on a staging server and then only move the instance to production.
My fear is that some piece of code or settings will get overwritten which will break stuff and I won't know where to look to fix them. 😃
A wizard would be awesome to take the guess work out of it.
err… The Distribution Wizard …. is a... wizard ;) You should give it a try! We do have some ideas in jira to make it even better but it’s already quite good in its current state.
As is, I've read some of the tutorials out there regarding upgrades several times but I'm not really able to determine the prescribed steps using those.
What tutorial? Could you give me the links?
I think at the end of the day I'm going to end up exporting my solutions as XAR's and then try importing them into an upgraded Xwiki environment too, since it seems easier to me.
The DW is generally a better solution to upgrades. Thanks -Vincent
On Dec 9, 2014, at 2:58 PM, Jeremie BOUSQUET wrote:
Le 9 déc. 2014 22:37, "Thomas Mortagne" a écrit :
On Tue, Dec 9, 2014 at 10:28 PM, Guillaume Lerouge
wrote:
Hi,
On Tue, Dec 9, 2014 at 10:23 PM, Thomas Mortagne < [email protected]> wrote:
On Tue, Dec 9, 2014 at 9:57 PM, Harald Ommang > >> 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 ;-)
Distribution Wizard has been introduced in 4.2 so not really the latest version. And even before that export/import everything never really been standard upgrade process either.
Sure, but you usually did reverse way : import new xwiki ui xar (and remember to uncheck standard pages customized, or have them overwritten). And yes, it was sometimes a hassle, and compared to that distribution wizard is really really great :)
Guillaume
Hi, Something I just met - as it's an "improvement" proposal I thought I could propose it here, but I may just create a jira if you think it's interesting: Would be great if there could be an option, in Attachments tab at pages bottom, to display attachments as a grid of thumbnails, instead of just a list. The best would be to by default reach current Attachments view, when clicking on Attachments tab (because it shows fastly), then have a little flag, button, or whatever, to choose a "thumbnail" view. This "thumbnail" view, could be the exact same kind of view as proposed by Attachments Selector Macro [1]. BTW it could be nice that this {{attachmentSelector/}} could be used as (or could rely on another extension that) merely displays attachments, without concept of saving the attachment name in a property in an XObject ... Use-case sample: when you import a .doc document, all images are set as attachments with automatic naming. Without thumbnail, it's quite hard then to retrieve a specific attachment without opening all of them one by one. BR, Jeremie [1] - http://extensions.xwiki.org/xwiki/bin/view/Extension/Attachment+Selector+Mac... 2014-12-10 9:46 GMT+01:00 [email protected] <[email protected]>:
Hi Jason,
On 10 Dec 2014 at 05:11:40, Jason Clemons ([email protected](mailto: [email protected])) wrote:
I have say, upgrading makes me very nervous too..
Have you ever tried using the Distribution Wizard?
so, I'd definitely vote for anything that changes or enhances that process. So far, I'm terrified to even try an upgrade (currently on 5.4) since my wiki is production and we've done a fair bit of customized solutions to unique problems (likely not in a "supported" way maybe) .
Well, first nobody should ever upgrade a wiki in production directly! You should make backups and do the upgrade on a staging server and then only move the instance to production.
My fear is that some piece of code or settings will get overwritten which will break stuff and I won't know where to look to fix them. 😃
A wizard would be awesome to take the guess work out of it.
err… The Distribution Wizard …. is a... wizard ;)
You should give it a try! We do have some ideas in jira to make it even better but it’s already quite good in its current state.
As is, I've read some of the tutorials out there regarding upgrades several times but I'm not really able to determine the prescribed steps using those.
What tutorial? Could you give me the links?
I think at the end of the day I'm going to end up exporting my solutions as XAR's and then try importing them into an upgraded Xwiki environment too, since it seems easier to me.
The DW is generally a better solution to upgrades.
Thanks -Vincent
On Dec 9, 2014, at 2:58 PM, Jeremie BOUSQUET wrote:
Le 9 déc. 2014 22:37, "Thomas Mortagne" a écrit :
On Tue, Dec 9, 2014 at 10:28 PM, Guillaume Lerouge
wrote:
Hi,
On Tue, Dec 9, 2014 at 10:23 PM, Thomas Mortagne < [email protected]> wrote:
On Tue, Dec 9, 2014 at 9:57 PM, Harald Ommang > >> 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 ;-)
Distribution Wizard has been introduced in 4.2 so not really the latest version. And even before that export/import everything never really been standard upgrade process either.
Sure, but you usually did reverse way : import new xwiki ui xar (and remember to uncheck standard pages customized, or have them overwritten). And yes, it was sometimes a hassle, and compared to that distribution wizard is really really great :)
Guillaume
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
On Wed, Dec 10, 2014 at 4:06 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hi,
Something I just met - as it's an "improvement" proposal I thought I could propose it here, but I may just create a jira if you think it's interesting: Would be great if there could be an option, in Attachments tab at pages bottom, to display attachments as a grid of thumbnails, instead of just a list. The best would be to by default reach current Attachments view, when clicking on Attachments tab (because it shows fastly), then have a little flag, button, or whatever, to choose a "thumbnail" view. This "thumbnail" view, could be the exact same kind of view as proposed by Attachments Selector Macro [1]. BTW it could be nice that this {{attachmentSelector/}} could be used as (or could rely on another extension that) merely displays attachments, without concept of saving the attachment name in a property in an XObject ...
Use-case sample: when you import a .doc document, all images are set as attachments with automatic naming. Without thumbnail, it's quite hard then to retrieve a specific attachment without opening all of them one by one.
There is http://extensions.xwiki.org/xwiki/bin/view/Extension/AttachmentGalleryMacro .
BR, Jeremie
[1] - http://extensions.xwiki.org/xwiki/bin/view/Extension/Attachment+Selector+Mac...
2014-12-10 9:46 GMT+01:00 [email protected] <[email protected]>:
Hi Jason,
On 10 Dec 2014 at 05:11:40, Jason Clemons ([email protected](mailto: [email protected])) wrote:
I have say, upgrading makes me very nervous too..
Have you ever tried using the Distribution Wizard?
so, I'd definitely vote for anything that changes or enhances that process. So far, I'm terrified to even try an upgrade (currently on 5.4) since my wiki is production and we've done a fair bit of customized solutions to unique problems (likely not in a "supported" way maybe) .
Well, first nobody should ever upgrade a wiki in production directly! You should make backups and do the upgrade on a staging server and then only move the instance to production.
My fear is that some piece of code or settings will get overwritten which will break stuff and I won't know where to look to fix them. 😃
A wizard would be awesome to take the guess work out of it.
err… The Distribution Wizard …. is a... wizard ;)
You should give it a try! We do have some ideas in jira to make it even better but it’s already quite good in its current state.
As is, I've read some of the tutorials out there regarding upgrades several times but I'm not really able to determine the prescribed steps using those.
What tutorial? Could you give me the links?
I think at the end of the day I'm going to end up exporting my solutions as XAR's and then try importing them into an upgraded Xwiki environment too, since it seems easier to me.
The DW is generally a better solution to upgrades.
Thanks -Vincent
On Dec 9, 2014, at 2:58 PM, Jeremie BOUSQUET wrote:
Le 9 déc. 2014 22:37, "Thomas Mortagne" a écrit :
On Tue, Dec 9, 2014 at 10:28 PM, Guillaume Lerouge
wrote:
Hi,
On Tue, Dec 9, 2014 at 10:23 PM, Thomas Mortagne < [email protected]> wrote:
> On Tue, Dec 9, 2014 at 9:57 PM, Harald Ommang > >> > 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 ;-)
Distribution Wizard has been introduced in 4.2 so not really the latest version. And even before that export/import everything never really been standard upgrade process either.
Sure, but you usually did reverse way : import new xwiki ui xar (and remember to uncheck standard pages customized, or have them overwritten). And yes, it was sometimes a hassle, and compared to that distribution wizard is really really great :)
Guillaume
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
2014-12-10 15:26 GMT+01:00 Marius Dumitru Florea < [email protected]>:
On Wed, Dec 10, 2014 at 4:06 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hi,
Something I just met - as it's an "improvement" proposal I thought I could propose it here, but I may just create a jira if you think it's interesting: Would be great if there could be an option, in Attachments tab at pages bottom, to display attachments as a grid of thumbnails, instead of just a list. The best would be to by default reach current Attachments view, when clicking on Attachments tab (because it shows fastly), then have a little flag, button, or whatever, to choose a "thumbnail" view. This "thumbnail" view, could be the exact same kind of view as proposed by Attachments Selector Macro [1]. BTW it could be nice that this {{attachmentSelector/}} could be used as (or could rely on another extension that) merely displays attachments, without concept of saving the attachment name in a property in an XObject ...
Use-case sample: when you import a .doc document, all images are set as attachments with automatic naming. Without thumbnail, it's quite hard then to retrieve a specific attachment without opening all of them one by one.
There is http://extensions.xwiki.org/xwiki/bin/view/Extension/AttachmentGalleryMacro
Yes, but it's still a "one by one" browser, not a grid of thumbnails, and it's not built-in the Attachment tab by default ... If it existed it could even be added to the File Manager Application [2], currently proposing a Tree and a Live Table view, it could also offer a Grid view with thumbnails why not ... [2] - http://extensions.xwiki.org/xwiki/bin/view/Extension/File+Manager+Applicatio...
.
BR, Jeremie
[1] -
http://extensions.xwiki.org/xwiki/bin/view/Extension/Attachment+Selector+Mac...
2014-12-10 9:46 GMT+01:00 [email protected] <[email protected]>:
Hi Jason,
On 10 Dec 2014 at 05:11:40, Jason Clemons ([email protected]
(mailto:
[email protected])) wrote:
I have say, upgrading makes me very nervous too..
Have you ever tried using the Distribution Wizard?
so, I'd definitely vote for anything that changes or enhances that process. So far, I'm terrified to even try an upgrade (currently on 5.4) since my wiki is production and we've done a fair bit of customized solutions to unique problems (likely not in a "supported" way maybe) .
Well, first nobody should ever upgrade a wiki in production directly! You should make backups and do the upgrade on a staging server and then only move the instance to production.
My fear is that some piece of code or settings will get overwritten which will break stuff and I won't know where to look to fix them. 😃
A wizard would be awesome to take the guess work out of it.
err… The Distribution Wizard …. is a... wizard ;)
You should give it a try! We do have some ideas in jira to make it even better but it’s already quite good in its current state.
As is, I've read some of the tutorials out there regarding upgrades several times but I'm not really able to determine the prescribed steps using those.
What tutorial? Could you give me the links?
I think at the end of the day I'm going to end up exporting my solutions as XAR's and then try importing them into an upgraded Xwiki environment too, since it seems easier to me.
The DW is generally a better solution to upgrades.
Thanks -Vincent
On Dec 9, 2014, at 2:58 PM, Jeremie BOUSQUET wrote:
Le 9 déc. 2014 22:37, "Thomas Mortagne" a écrit :
On Tue, Dec 9, 2014 at 10:28 PM, Guillaume Lerouge
wrote:
> Hi, > > On Tue, Dec 9, 2014 at 10:23 PM, Thomas Mortagne < [email protected]> > wrote: > >> On Tue, Dec 9, 2014 at 9:57 PM, Harald Ommang > >> >> 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 ;-)
Distribution Wizard has been introduced in 4.2 so not really the latest version. And even before that export/import everything never really been standard upgrade process either.
Sure, but you usually did reverse way : import new xwiki ui xar (and remember to uncheck standard pages customized, or have them overwritten). And yes, it was sometimes a hassle, and compared to that distribution wizard is really really great :)
> > Guillaume
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
2014-12-10 15:34 GMT+01:00 Jeremie BOUSQUET <[email protected]>:
2014-12-10 15:26 GMT+01:00 Marius Dumitru Florea < [email protected]>:
On Wed, Dec 10, 2014 at 4:06 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hi,
Something I just met - as it's an "improvement" proposal I thought I could propose it here, but I may just create a jira if you think it's interesting: Would be great if there could be an option, in Attachments tab at pages bottom, to display attachments as a grid of thumbnails, instead of just a list. The best would be to by default reach current Attachments view, when clicking on Attachments tab (because it shows fastly), then have a little flag, button, or whatever, to choose a "thumbnail" view. This "thumbnail" view, could be the exact same kind of view as proposed by Attachments Selector Macro [1]. BTW it could be nice that this {{attachmentSelector/}} could be used as (or could rely on another extension that) merely displays attachments, without concept of saving the attachment name in a property in an XObject ...
Use-case sample: when you import a .doc document, all images are set as attachments with automatic naming. Without thumbnail, it's quite hard then to retrieve a specific attachment without opening all of them one by one.
There is http://extensions.xwiki.org/xwiki/bin/view/Extension/AttachmentGalleryMacro
Yes, but it's still a "one by one" browser, not a grid of thumbnails, and it's not built-in the Attachment tab by default ... If it existed it could even be added to the File Manager Application [2], currently proposing a Tree and a Live Table view, it could also offer a Grid view with thumbnails why not ...
[2] - http://extensions.xwiki.org/xwiki/bin/view/Extension/File+Manager+Applicatio...
Generally speaking if you want, I could formulate as, "More widgets and views, for displaying or managing standard xwiki features / objects".
.
BR, Jeremie
[1] -
http://extensions.xwiki.org/xwiki/bin/view/Extension/Attachment+Selector+Mac...
2014-12-10 9:46 GMT+01:00 [email protected] <[email protected]>:
Hi Jason,
On 10 Dec 2014 at 05:11:40, Jason Clemons ([email protected]
(mailto:
[email protected])) wrote:
I have say, upgrading makes me very nervous too..
Have you ever tried using the Distribution Wizard?
so, I'd definitely vote for anything that changes or enhances that process. So far, I'm terrified to even try an upgrade (currently on 5.4) since my wiki is production and we've done a fair bit of customized solutions to unique problems (likely not in a "supported" way maybe) .
Well, first nobody should ever upgrade a wiki in production directly! You should make backups and do the upgrade on a staging server and then only move the instance to production.
My fear is that some piece of code or settings will get overwritten which will break stuff and I won't know where to look to fix them. 😃
A wizard would be awesome to take the guess work out of it.
err… The Distribution Wizard …. is a... wizard ;)
You should give it a try! We do have some ideas in jira to make it even better but it’s already quite good in its current state.
As is, I've read some of the tutorials out there regarding upgrades several times but I'm not really able to determine the prescribed steps using those.
What tutorial? Could you give me the links?
I think at the end of the day I'm going to end up exporting my solutions as XAR's and then try importing them into an upgraded Xwiki environment too, since it seems easier to me.
The DW is generally a better solution to upgrades.
Thanks -Vincent
On Dec 9, 2014, at 2:58 PM, Jeremie BOUSQUET wrote:
Le 9 déc. 2014 22:37, "Thomas Mortagne" a écrit : > > On Tue, Dec 9, 2014 at 10:28 PM, Guillaume Lerouge wrote: >> Hi, >> >> On Tue, Dec 9, 2014 at 10:23 PM, Thomas Mortagne < [email protected]> >> wrote: >> >>> On Tue, Dec 9, 2014 at 9:57 PM, Harald Ommang > >> >>> 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 ;-) > > Distribution Wizard has been introduced in 4.2 so not really the > latest version. And even before that export/import everything never > really been standard upgrade process either.
Sure, but you usually did reverse way : import new xwiki ui xar (and remember to uncheck standard pages customized, or have them overwritten). And yes, it was sometimes a hassle, and compared to that distribution wizard is really really great :)
> >> >> Guillaume
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
On Wed, Dec 10, 2014 at 4:37 PM, Jeremie BOUSQUET <[email protected]> wrote:
2014-12-10 15:34 GMT+01:00 Jeremie BOUSQUET <[email protected]>:
2014-12-10 15:26 GMT+01:00 Marius Dumitru Florea < [email protected]>:
On Wed, Dec 10, 2014 at 4:06 PM, Jeremie BOUSQUET <[email protected]> wrote:
Hi,
Something I just met - as it's an "improvement" proposal I thought I could propose it here, but I may just create a jira if you think it's interesting: Would be great if there could be an option, in Attachments tab at pages bottom, to display attachments as a grid of thumbnails, instead of just a list. The best would be to by default reach current Attachments view, when clicking on Attachments tab (because it shows fastly), then have a little flag, button, or whatever, to choose a "thumbnail" view. This "thumbnail" view, could be the exact same kind of view as proposed by Attachments Selector Macro [1]. BTW it could be nice that this {{attachmentSelector/}} could be used as (or could rely on another extension that) merely displays attachments, without concept of saving the attachment name in a property in an XObject ...
Use-case sample: when you import a .doc document, all images are set as attachments with automatic naming. Without thumbnail, it's quite hard then to retrieve a specific attachment without opening all of them one by one.
There is http://extensions.xwiki.org/xwiki/bin/view/Extension/AttachmentGalleryMacro
Yes, but it's still a "one by one" browser, not a grid of thumbnails, and it's not built-in the Attachment tab by default ... If it existed it could even be added to the File Manager Application [2], currently proposing a Tree and a Live Table view, it could also offer a Grid view with thumbnails why not ...
[2] - http://extensions.xwiki.org/xwiki/bin/view/Extension/File+Manager+Applicatio...
Generally speaking if you want, I could formulate as, "More widgets and views, for displaying or managing standard xwiki features / objects".
+1
.
BR, Jeremie
[1] -
http://extensions.xwiki.org/xwiki/bin/view/Extension/Attachment+Selector+Mac...
2014-12-10 9:46 GMT+01:00 [email protected] <[email protected]>:
Hi Jason,
On 10 Dec 2014 at 05:11:40, Jason Clemons ([email protected]
(mailto:
[email protected])) wrote:
I have say, upgrading makes me very nervous too..
Have you ever tried using the Distribution Wizard?
so, I'd definitely vote for anything that changes or enhances that process. So far, I'm terrified to even try an upgrade (currently on 5.4) since my wiki is production and we've done a fair bit of customized solutions to unique problems (likely not in a "supported" way maybe) .
Well, first nobody should ever upgrade a wiki in production directly! You should make backups and do the upgrade on a staging server and then only move the instance to production.
My fear is that some piece of code or settings will get overwritten which will break stuff and I won't know where to look to fix them. 😃
A wizard would be awesome to take the guess work out of it.
err… The Distribution Wizard …. is a... wizard ;)
You should give it a try! We do have some ideas in jira to make it even better but it’s already quite good in its current state.
As is, I've read some of the tutorials out there regarding upgrades several times but I'm not really able to determine the prescribed steps using those.
What tutorial? Could you give me the links?
I think at the end of the day I'm going to end up exporting my solutions as XAR's and then try importing them into an upgraded Xwiki environment too, since it seems easier to me.
The DW is generally a better solution to upgrades.
Thanks -Vincent
> On Dec 9, 2014, at 2:58 PM, Jeremie BOUSQUET wrote: > > Le 9 déc. 2014 22:37, "Thomas Mortagne" a écrit > : >> >> On Tue, Dec 9, 2014 at 10:28 PM, Guillaume Lerouge > wrote: >>> Hi, >>> >>> On Tue, Dec 9, 2014 at 10:23 PM, Thomas Mortagne < > [email protected]> >>> wrote: >>> >>>> On Tue, Dec 9, 2014 at 9:57 PM, Harald Ommang > >> >>>> 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 ;-) >> >> Distribution Wizard has been introduced in 4.2 so not really the >> latest version. And even before that export/import everything never >> really been standard upgrade process either. > > Sure, but you usually did reverse way : import new xwiki ui xar (and > remember to uncheck standard pages customized, or have them overwritten). > And yes, it was sometimes a hassle, and compared to that distribution > wizard is really really great :) > >> >>> >>> Guillaume
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Hi everyone, A lot of you have mentioned that they’d like to see the WYSIWYG editor improved in 7.x (especially table handling). Marius has done a proof of concept of integrating CKEditor into XWiki here: http://extensions.xwiki.org/xwiki/bin/view/Extension/CKEditor+Integration Would be great if you could try it out and let us know what you think about the result and about integrating it in XWiki by default. Please take into account that the work is not finished, see: http://extensions.xwiki.org/xwiki/bin/view/Extension/CKEditor+Integration#HF... Thanks -Vincent On 5 Dec 2014 at 13:17:42, [email protected] ([email protected](mailto:[email protected])) wrote:
Dear XWiki users,
We’re getting close to the end of the XWiki 6.x cycle (6.4 is planned for the end of December) and in January we’ll start developing the XWiki 7.x cycle (which will last the whole 2015 year), starting with XWiki 7.0.
Thus it’s time for the XWiki devs to start defining the global roadmap for XWiki 7.x.
As XWiki users, I’d like to know if you have some needs for XWiki 7.x. What would you be interested in seeing in XWiki 7.x?
I’d like to start some proposal on the xwiki devs list (for the XWiki 7.x cycle) around end of December so it would be nice if you could shoot your suggestion ideas fast so that we can take them into account in the discussion! :)
Thanks a lot for your help and I hope you’re enjoying using XWiki!
-Vincent Massol XWiki Committer
participants (12)
-
Daniel Lundh -
Danilo Oliveira -
Dmitry Bakbardin -
Guillaume Lerouge -
Hamster -
Harald Ommang -
Jason Clemons -
Jeremie BOUSQUET -
Marius Dumitru Florea -
Pascal BASTIEN -
Thomas Mortagne -
vincent＠massol.net