Beloved XWiki users,
The XWiki Development Team has decided to stop maintaining XWiki Office and XWiki Eclipse. The truth is that these 2 projects have been dormant for a long time now since there were no active developers on them. Thus we decided to move them to XWiki Contrib where any contributor can participate (you just need to ask to get access there), in the hope that someone will continue working on them.
For more details on what XWiki Contrib is check http://contrib.xwiki.org
The two projects can now be found at:
* http://extensions.xwiki.org/xwiki/bin/view/Extension/XWiki+Eclipse
* http://extensions.xwiki.org/xwiki/bin/view/Extension/XWiki+Office
I personally think that both XEclipse and XOffice are great integrations of XWiki in third party tools. The XWiki Dev Team is just lacking resources and is spread too thin to continue to work on them in a quality manner.
On the upside, this means we're now continuing our focus on XWiki Enterprise and XWiki Enterprise Manager and very soon we even hope to drop the XWiki Enterprise Manager distribution in order to have only XWiki Enterprise and everything else will just be extensions (http://extensions.xwiki.org) that can be installed in it (including Workspaces which is the basis for the current XWiki Enterprise Manager distribution).
If you have any questions feel free to ask here!
Thanks
-Vincent Massol on behalf of the XWiki Development Team
Hello,
+1 for proposal 3.
Raluca.
On Tue, Apr 30, 2013 at 12:02 PM, Vincent Massol <vincent(a)massol.net> wrote:
> Hi devs,
>
> Following this thread http://markmail.org/thread/vw3derowozijqalr it
> seems clear that we need to introduce a better syntax for links and images
> in XWiki Syntax 2.2 (in order to cope with use cases such as
> http://jira.xwiki.org/jira/browse/XRENDERING-290).
>
> The need is to be able to plug new reference type handlers without
> breaking backward compatibility in XWiki Syntax 2.2 (since right now with
> XWiki Syntax 2.0 and 2.1 adding a new type reference handler would break
> backward compatibility).
>
> So here are various proposals to that effect for XWiki Syntax 2.2 (I've
> only kept the interesting proposals from the previous thread). Please vote
> for the one you prefer or add new solutions if you have other better ideas.
>
> Proposal 1
> =========
>
> Force XWiki Syntax 2.2 to *ALWAYS* use the full form when creating a link
> or image, i.e. all links would need to be written: [[label>>type:reference]]
>
> Examples:
> * [[label>>doc:space.page]]
> * [[label>>doc:wiki:space.page]]
> * [[label>>path:/some/path]]
> * [[label>>url:http://xwiki.org]]
> * [[label>>user:evalica]]
> * [[image:doc:wiki:space.page@image.png]]
> * [[image:icon:someicon.png]]
>
> CONS:
> * Harder to write links to documents which is the main use case
>
> Proposal 2
> =========
>
> Same as with XWiki Syntax 2.1 but for links or images to subwikis force
> the user to use the "doc:" notation
>
> Examples:
> * [[label>>space.page]] or [[label>>doc:space.page]]
> * [[label>>doc:wiki:space.page]]
> * [[label>>>path:/some/path]]
> * [[label>>http://xwiki.org]] or [[label>>>url:http://xwiki.org]]
> * [[label>>user:evalica]]
> * [[image:doc:wiki:space.page@image.png]]
> * [[image:icon:someicon.png]]
>
> PRO:
> * Still easy to reference docs and images in the current wiki
> * Close to current XWiki Syntax 2.1
>
> CONS:
> * Harder to write links to documents in subwikis (for workspaces users for
> example, see example of xwiki.org)
>
> Proposal 3
> =========
>
> Always define the type as a link or image parameter, i.e. separate subwiki
> notation from type.
>
> Examples:
> * [[label>>space.page]] or [[label>>space.page||type="doc"]]
> * [[label>>wiki:space.page]] or [[label>>wiki:space.page||type="doc"]]
> * [[label>>>/some/path||type="path"]]
> * [[label>>http://xwiki.org]] or [[label>>>http://xwiki.org||type="url"]]
> * [[label>>evalica||type="user"]]
> * [[image:wiki:space.page@image.png]] or [[image:wiki:space.page@image.png
> ||type="doc"]]
> * [[image:someicon.png||type="icon"]]
>
> PRO:
> * Still easy to reference docs
> * Clear separation between subwiki and types
>
> CONS:
> * Harder to write typed links
> * Harder to write references in non xwiki/2.x syntax that would not
> support link parameters
>
> Thanks
> -Vincent
>
>
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
Forwarding to users list since it's interesting to know what users think about this for the new XWiki Syntax 2.2 too.
Please give your opinion.
Thanks
-Vincent
Begin forwarded message:
> From: Vincent Massol <vincent(a)massol.net>
> Subject: [VOTE] New Link and Image syntax for XWiki Syntax 2.2
> Date: April 30, 2013 11:02:43 AM GMT+02:00
> To: XWiki Developers <devs(a)xwiki.org>
>
> Hi devs,
>
> Following this thread http://markmail.org/thread/vw3derowozijqalr it seems clear that we need to introduce a better syntax for links and images in XWiki Syntax 2.2 (in order to cope with use cases such as http://jira.xwiki.org/jira/browse/XRENDERING-290).
>
> The need is to be able to plug new reference type handlers without breaking backward compatibility in XWiki Syntax 2.2 (since right now with XWiki Syntax 2.0 and 2.1 adding a new type reference handler would break backward compatibility).
>
> So here are various proposals to that effect for XWiki Syntax 2.2 (I've only kept the interesting proposals from the previous thread). Please vote for the one you prefer or add new solutions if you have other better ideas.
>
> Proposal 1
> =========
>
> Force XWiki Syntax 2.2 to *ALWAYS* use the full form when creating a link or image, i.e. all links would need to be written: [[label>>type:reference]]
>
> Examples:
> * [[label>>doc:space.page]]
> * [[label>>doc:wiki:space.page]]
> * [[label>>path:/some/path]]
> * [[label>>url:http://xwiki.org]]
> * [[label>>user:evalica]]
> * [[image:doc:wiki:space.page@image.png]]
> * [[image:icon:someicon.png]]
>
> CONS:
> * Harder to write links to documents which is the main use case
>
> Proposal 2
> =========
>
> Same as with XWiki Syntax 2.1 but for links or images to subwikis force the user to use the "doc:" notation
>
> Examples:
> * [[label>>space.page]] or [[label>>doc:space.page]]
> * [[label>>doc:wiki:space.page]]
> * [[label>>>path:/some/path]]
> * [[label>>http://xwiki.org]] or [[label>>>url:http://xwiki.org]]
> * [[label>>user:evalica]]
> * [[image:doc:wiki:space.page@image.png]]
> * [[image:icon:someicon.png]]
>
> PRO:
> * Still easy to reference docs and images in the current wiki
> * Close to current XWiki Syntax 2.1
>
> CONS:
> * Harder to write links to documents in subwikis (for workspaces users for example, see example of xwiki.org)
>
> Proposal 3
> =========
>
> Always define the type as a link or image parameter, i.e. separate subwiki notation from type.
>
> Examples:
> * [[label>>space.page]] or [[label>>space.page||type="doc"]]
> * [[label>>wiki:space.page]] or [[label>>wiki:space.page||type="doc"]]
> * [[label>>>/some/path||type="path"]]
> * [[label>>http://xwiki.org]] or [[label>>>http://xwiki.org||type="url"]]
> * [[label>>evalica||type="user"]]
> * [[image:wiki:space.page@image.png]] or [[image:wiki:space.page@image.png||type="doc"]]
> * [[image:someicon.png||type="icon"]]
>
> PRO:
> * Still easy to reference docs
> * Clear separation between subwiki and types
>
> CONS:
> * Harder to write typed links
> * Harder to write references in non xwiki/2.x syntax that would not support link parameters
>
> Thanks
> -Vincent
>
>
I'm writing custom listener to send e-mail after document updates
according to:
http://platform.xwiki.org/xwiki/bin/view/DevGuide/GroovyNotificationTutorial and: http://xwiki.475771.n2.nabble.com/Send-an-email-in-an-event-listener-td7579…
Although adding attachment is working in Velocity as described in:
http://extensions.xwiki.org/xwiki/bin/view/Extension/Mail+Sender+Plugin
Similar approach in Groovy raises exception:
java.lang.ClassCastException: com.xpn.xwiki.doc.XWikiAttachment cannot
be cast to com.xpn.xwiki.api.Attachment
at
com.xpn.xwiki.plugin.mailsender.MailSenderPlugin.createMimeMultipart(MailSenderPlugin.java:391) ~[xwiki-platform-mailsender-4.5.jar:na]
at
com.xpn.xwiki.plugin.mailsender.MailSenderPlugin.createMimeMessage(MailSenderPlugin.java:327) ~[xwiki-platform-mailsender-4.5.jar:na]
at
com.xpn.xwiki.plugin.mailsender.MailSenderPlugin.sendMails(MailSenderPlugin.java:726) ~[xwiki-platform-mailsender-4.5.jar:na]
at
com.xpn.xwiki.plugin.mailsender.MailSenderPlugin.sendMail(MailSenderPlugin.java:673) ~[xwiki-platform-mailsender-4.5.jar:na]
at
com.xpn.xwiki.plugin.mailsender.MailSenderPlugin.sendMail(MailSenderPlugin.java:659) ~[xwiki-platform-mailsender-4.5.jar:na]
at
com.xpn.xwiki.plugin.mailsender.MailSenderPluginApi.sendMail(MailSenderPluginApi.java:171) [xwiki-platform-mailsender-4.5.jar:na]
at
com.xpn.xwiki.plugin.mailsender.MailSenderPluginApi.sendTextMessage(MailSenderPluginApi.java:98) [xwiki-platform-mailsender-4.5.jar:na]
at com.xpn.xwiki.plugin.mailsender.MailSender
$sendTextMessage.call(Unknown Source)
[xwiki-platform-mailsender-4.5.jar:na]
at EmailSenderListener.onEvent(Script22.groovy:34) [script:na]
...
and line is: def attachments = source.getAttachmentList()
What should I do?
Thanks!
Valdis
We have a XWiki 5.0m1 wiki farm, relatively recently upgraded from 3.5
Having created a new subwiki for a new project, and spent a couple of days
creating content in it, I noticed that the profile pics from the global
users were not showing up
I tried to create a local user with the same name (we had only global users
until this point), but this did not work and I therefore deleted the local
user page
Unfortunately XWiki presented a confirmation dialog (for the delete) which I
did not process mentally until after I had pressed confirm
This dialog said that since this was the only page in the XWiki space, it
would delete all the documents in the XWiki space !
Sure enough the XWiki space seems now to have been deleted in the sub wiki
:-(
(Seems that this is rather a serious bug - as this was clearly not the only
page in the XWiki space)
Good news the photos for the global users now displays properly, bad news
the admin application and presumably everything else in the XWiki space in
the subwiki (e.g. macros) are now gone
Since there is no admin application in the sub wiki I cannot re-import the
XWiki pages from the XAR
I can equally neither export the pages in the new sub wiki to reimport in a
backed up version, without the new sub wiki
Can you recommend any course of action which will enable me to export my
content pages from the new wiki or import a XAR of the administration
application, without the administration application already being installed
in the sub wiki
(PS the main wiki is intact)
Thanks for your help
Tim
--
View this message in context: http://xwiki.475771.n2.nabble.com/Sub-wiki-delete-of-only-sub-wiki-user-del…
Sent from the XWiki- Users mailing list archive at Nabble.com.
Hi all,
I want to use "Navigation Menu Wiki Macro"
http://extensions.xwiki.org/xwiki/bin/view/Extension/Navigation+Menu+Wiki+M…
to make vertical and horizontal menus in all wiki.
But I could not use the panel with this content:
{{menutype="vertical"position="right"id="panelmenu"}}
* [[Main>>Main.WebHome]]
* [[Sandbox>>Sandbox.WebHome]]
** [[Sandbox.TestPage1]]
** [[Sandbox.TestPage2]]
** [[Sandbox.TestPage3]]
* [[Blog>>Blog.WebHome]]
{{/menu}}
How could I define a new panel for this purpose?
Regards,
--
*Viet Hoang*
Hi,
I'm creating pages using the Restful API.
I'd like to provide a comment (summary) to describe the modification so that
it is displayed in the history.
Any hint on how to do this ?
Regards,
Stephane Thibaudeau
--
View this message in context: http://xwiki.475771.n2.nabble.com/Rest-provide-a-summary-whne-creating-a-pa…
Sent from the XWiki- Users mailing list archive at Nabble.com.