Hi,
Just realized that our new WYSIWYG editor will only work fine with our
xwiki 2.0 syntax since other wiki syntaxes are less powerful and won't
be able to express some complex structures (like embedding a document
inside a table cell) or simply like styling a portion of text.
Of course this is not a problem of the wysiwyg editor per see but in
practice it means that users using it for other syntaxes when they
save will get a different rendered result.
So I"m tempted to say that our GWT editor will only work for the xwiki
2.0 syntax and that for the other syntaxes users will have to use the
wiki editor.
WDYT?
Thanks
-Vincent
Hi,
I'm wondering if it is possible to use something else than a database
to store wiki pages.
My reasoning is to enable the following things:
* Enable people to produce and edit contents even when they are
disconnected from the network
* Enable people to edit and produce contents with their favorite text
editor instead of being bound to the Browser-Interface
I think this could be achieved with two ways:
* have the page contents stored in a version control system like git
or subversion instead of the database
* have a git (or subversion) protocol frontend to let users access and
write page data
Is something like that possible with xWiki, or even already available?
If not, what would it take to enable it?
I read something about Office (Openoffice/Word?) Integration - but
that would not cut it, because I think of people who do not like large
software packages, but favour small text editors. But maybe my ideas
could be implemented in a similar way as the Office connectors.
Henning
--
Henning Sprang
http://www.sprang.de | http://lazyb0y.blogspot.com/
Hello list,
I just realized that there seems to be very little executable code
interpreted in the document bundle documents.
I was simply trying to make a document that is declared as document-
bundle to be an include of another document and it did not work with
any of the include methods I found at
http://platform.xwiki.org/xwiki/bin/view/DevGuide/IncludeInVelocity
should it work?
But maybe no script is running in the programme that reads the
document-bundle in which case this is easily understandable.
Another reason for which it would be lovely to have scripting in
document-bundles is in bundles that repeat a lot. In Curriki this is
often the case because bundles come from different applications and
may, indeed, in the very long run, become different (e.g. because we
reach yet another language or...): here I would love that for English,
at least, it is explicitly written
key.name = $msg.get('other.key.name')
is that thinkable?
thanks in advance
paul
asiri (SVN) wrote:
> Author: asiri
> Date: 2009-01-07 16:47:31 +0100 (Wed, 07 Jan 2009)
> New Revision: 15130
>
> Modified:
> platform/core/trunk/pom.xml
> platform/core/trunk/xwiki-core/pom.xml
> Log:
> XAOFFICE-1: Develop the initial feature set for the Office Importer module
>
> * Added xwiki-officeimporter module to platform/core/trunk/pom.xml as a sub-module so that it's built when the core is built.
> * Added a dependency in xwiki-core to xwiki-officeimporter so that xwiki-officeimporter get's bundled into XE.
This dependency should have <scope>runtime</scope> to reduce build time,
because otherwise the library and its dependencies are added to the
classpath during compilation and tests.
> <dependency>
> <groupId>org.xwiki.platform</groupId>
> + <artifactId>xwiki-core-officeimporter</artifactId>
> + <version>${pom.version}</version>
> + </dependency>
This dependency should not be placed in the core, as it should be
inherited from officeimporter. If it isn't, then the officeimporter pom
is wrong.
> + <!-- Required by jodconverter; see http://www.slf4j.org/faq.html#maven2 -->
> + <dependency>
> + <groupId>org.slf4j</groupId>
> + <artifactId>slf4j-log4j12</artifactId>
> + <version>1.4.3</version>
> + <scope>test</scope>
> + </dependency>
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
DarthOps wrote:
> Hi,
>
> I've managed to get my watchlist to send out emails, the only problem is
> that the following is displayed within the email:
> Caused by: java.lang.NullPointerException
> at com.xpn.xwiki.XWiki.getServletPath(XWiki.java:4317)
This looks like a regression recently introduced. Other than
downgrading, I don't have any other suggestions for the moment, I'll
ping the responsible developer for a fix before 1.8M1.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hello,
do you receive my mails Sergiu?
I sent several questions to you but received no answer.
Tell me if you receive them or not because I wonder :)
regards
Pascal
Hi devs,
Following the release planning I would like to release 1.8M1.
Among other things, it introduce:
- Document convertSyntax API to convert a document from one syntax to
another + new 1.0 syntax to 2.0 syntax converter
- REST API
- Make it easier to disable footer information (comments, history, etc)
Here is my +1
--
Thomas Mortagne
If I want to use smtp.gmail.com as my "Admin Email" preference set in
http://localhost:8080/xwiki/bin/admin/XWiki/XWikiPreferences?editor=globala…;
the editor doesn't have the required fields or capabilities to provide
"authenticated SMTP" required by Gmail and numerous other mail providers per
http://mail.google.com/support/bin/answer.py?hl=en&answer=13287 ::
*Outgoing Mail (SMTP) Server - requires TLS:* smtp.gmail.com (use
> authentication)
> *Use Authentication*: Yes
> *Use STARTTLS*: Yes (some clients call this SSL)
> *Port*: 465 or 587
>
The error message emitted from "registration" indicates what's missing to
support authenticated SMTP:
Error number 10006 in 10: Could not send mail to server smtp.gmail.com
port 25 error code 530 (530 5.7.0 Must issue a STARTTLS command first.
27sm1167462wff.51
com.xpn.xwiki.XWikiException: Error number 10006 in 10: Could not send
mail to server smtp.gmail.com port 25 error code 530 (530 5.7.0 Must
issue a STARTTLS command first. 27sm1167462wff.51
Are there any plans to support this for 1.8 rc1 ? (I'm using 1.8 trunk, rev
15391)
It's not essential to do this, but it could end up being a fair amount of
extra admin work to get it working. One workaround would be to setup a local
SMTP server (bind only to localhost), set the
"Admin email" pref to 127.0.0.1 and then have the local SMTP server use TLS
to communicate with your organization's secure SMTP server.
Note that this issue is broader than just TLS-based SMTP. Most other SMTP
servers are no longer open and unauthenticated due to the issue of spam and
mail forgery. Setting up Xwiki with such an SMTP server results in the
following error on registration:
Error number 10006 in 10: Could not send mail to server
smtp.kawlich.eduport 25 error code 550 (550 5.7.1 ... Relaying denied.
Proper authentication
> required.
> com.xpn.xwiki.XWikiException: Error number 10006 in 10: Could not send mail
> to server smtp.kawlich.edu port 25 error code 550 (550 5.7.1 ... Relaying
> denied.
>
Niels
http://nielsmayer.com