On Sun, Jan 18, 2009 at 4:34 PM, Sergiu Dumitriu <sergiu(a)xwiki.com> wrote:
> Asiri Rathnayake wrote:
> >>> + #set($fragments=$attachmentUrl.split($attachmentSignature))
> >>> + #if($listtool.size($fragments) == 2)
> >>> + #set($prefix=$listtool.get($fragments, 0))
> >>> + #set($suffix=$listtool.get($fragments, 1))
> >>> + #set($davUrl="$prefix$webdavSignature$suffix")
> >>> + <span class="xwikibuttonlinks"><a class="deletelink"
> >>
> href="javascript:davEdit('$davUrl')">$msg.get("webdaveditattachment")</a></span>
> >>
> >> You should escape $davUrl, because if it contains ' or " it will break.
> >
> >
> > I tried to do this but for some reason the url got changed to an invalid
> one
> > once i escaped it. It's kind of weird, the local application tried to
> open
> > some url like /home/asiri/http://..... I'm still not sure why this
> happens.
> >
>
> How exactly did you try to escape it? A simple .replaceAll('"',
> '"').replaceAll("'", ''') should do it.
Fixed.
Thanks.
- Asiri
Hello Xwiki-Devs,
I am not quite sure if this one is just a stupid question I haven't been
able to find an answer for, or if it is just impossible.
Situation is this: If you hava a link in a page e.g. "[GrannySmith]" and
and this page doesn't exist yet (so it'll get a questionmark as marker),
as soon as somebody clicks on that link xwiki will suggest to create a
new Page or go straight to the editor. So far so clear. Now for instance
I have a xwiki class called "Apple" can I create a link that mandates
that the newly created page should be of the class "Apple" (respectively
should have an object of "Apple")? Or is there any other way to
accomplish this?
thanks and greetings
Jonas
---------- Forwarded message ----------
From: Asiri Rathnayake <asiri.rathnayake(a)gmail.com>
Date: Fri, Jan 16, 2009 at 12:37 PM
Subject: Re: [xwiki-notifications] r15438 - enterprise/trunk
enterprise/trunk/wiki platform/core/trunk/xwiki-core/src/main/resources
platform/web/trunk/standard/src/main/webapp/templates
platform/xwiki-applications/trunk platform/xwiki-applications/trunk/webd
To: XWiki Notifications <notifications(a)xwiki.org>
Hi Segiu,
> > + #set($documentUrl=$doc.getExternalURL("download"))
> > + #set($attachmentUrl="$documentUrl/$attach.filename")
> > + #set($attachmentSignature="/xwiki/bin/download/")
> > + #set($webdavSignature="/xwiki/webdav/spaces/")
>
> This isn't safe. It is possible to change this completely. Better use:
>
>
> #set($attachmentSignature="${request.contextPath}${request.servletPath}/download/")
> #set($webdavSignature="${request.contextPath}/webdav/spaces/")
>
Fixed.
Also, this doesn't work with the new "virtualwiki-as-path" URLs.
I don't think webdav supports "virtualwiki-as-path" configuration yet. I'll
have to look into it.
> > + #set($fragments=$attachmentUrl.split($attachmentSignature))
> > + #if($listtool.size($fragments) == 2)
> > + #set($prefix=$listtool.get($fragments, 0))
> > + #set($suffix=$listtool.get($fragments, 1))
> > + #set($davUrl="$prefix$webdavSignature$suffix")
> > + <span class="xwikibuttonlinks"><a class="deletelink"
> href="javascript:davEdit('$davUrl')">$msg.get("webdaveditattachment")</a></span>
>
> You should escape $davUrl, because if it contains ' or " it will break.
I tried to do this but for some reason the url got changed to an invalid one
once i escaped it. It's kind of weird, the local application tried to open
some url like /home/asiri/http://..... I'm still not sure why this happens.
> Added: platform/xwiki-applications/trunk/webdav/pom.xml
> > ===================================================================
> > --- platform/xwiki-applications/trunk/webdav/pom.xml
> (rev 0)
> > +++ platform/xwiki-applications/trunk/webdav/pom.xml 2009-01-15 10:00:35
> UTC (rev 15438)
> > @@ -0,0 +1,14 @@
>
> Don't forget to add our License header (for all files in this app).
>
Fixed.
> > + InstallTrigger.install( {"FoXWiki" :"
> https://addons.mozilla.org/en-US/firefox/downloads/file/39674/foxwiki-1.0b-…
> "});
>
> Isn't there a version-independent URL, so that we don't have to release
> application-webdav each time we release foxwiki?
Unfortunately no, the url has to point to an xpi file. But this is not a
problem since Firefox automatically detects extension updates. And since
FoXWiki is hosted in addons.mozilla.org this is done automatically. All we
have to do is release the new version in addons.mozilla.org and users will
be notifed of the existance of a newer version.
Thanks.
- Asiri
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
JV which have you deleted this issue?
Generally speaking we shouldn't delete any issue (I guess we should
configure jira to remove delete permissions). We can close them as
"won't fix" or "invalid" instead.
-Vincent
On Jan 12, 2009, at 5:41 PM, Jean-Vincent Drean (JIRA) wrote:
>
> [ http://jira.xwiki.org/jira/browse/XPWATCHLIST-43?page=com.atlassian.jira.pl…
> ]
>
> Jean-Vincent Drean deleted XPWATCHLIST-43:
> ------------------------------------------
>
>
>> Remove sanitizeWatchlist from the plugin
>> ----------------------------------------
>>
>> Key: XPWATCHLIST-43
>> URL: http://jira.xwiki.org/jira/browse/XPWATCHLIST-43
>> Project: XWiki Watch List Application
>> Issue Type: Task
>> Reporter: Jean-Vincent Drean
>>
>> This method was meant to handle the migration between watchlist 1.2
>> and 1.3, since the last released version is 1.11 we need to remove
>> it (it makes xwiki init slower).
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the
> administrators: http://jira.xwiki.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/software/jira
Thanks
-Vincent
http://xwiki.comhttp://xwiki.orghttp://massol.net
Hi VIncent,
On Mon, Jan 12, 2009 at 2:13 PM, Vincent Massol <vincent(a)massol.net> wrote:
> Hi Asiri,
>
> This is good (the move to components for filters) except for one very
> important thing: now if some module implements some filter components
> using that interface they'll be used automagically by the HTMLCleaner.
> This makes the HTML Cleaner non safe with a non predictable behavior.
>
> Imagine for ex that in the office importer you implement the
> CleaningFilter interface and expose the implementations as components.
> These filters will be used even when not doing office imports.
>
> So +1 for components but you need a way to control which filters are
> used for a cleaning operation now.
I didn't think of this. For the moment I have changed the components.xml to
inject only those filters we require for DefaultHTMLCleaner. But yes, we
should have a mechanism to dynamically specify which filters we need to
apply...
Thanks.
- Asiri
>
>
> Thanks
> -Vincent
>
> On Jan 12, 2009, at 12:38 AM, asiri (SVN) wrote:
>
> > Author: asiri
> > Date: 2009-01-12 00:38:10 +0100 (Mon, 12 Jan 2009)
> > New Revision: 15346
> >
> > Added:
> > platform/core/trunk/xwiki-xml/src/main/java/org/xwiki/xml/html/
> > filter/
> > platform/core/trunk/xwiki-xml/src/main/java/org/xwiki/xml/html/
> > filter/CleaningFilter.java
> > platform/core/trunk/xwiki-xml/src/main/java/org/xwiki/xml/internal/
> > html/filter/
> > platform/core/trunk/xwiki-xml/src/main/java/org/xwiki/xml/internal/
> > html/filter/DocTypeCleaningFilter.java
> > platform/core/trunk/xwiki-xml/src/main/java/org/xwiki/xml/internal/
> > html/filter/LineBreakCleaningFilter.java
> > platform/core/trunk/xwiki-xml/src/main/java/org/xwiki/xml/internal/
> > html/filter/ListCleaningFilter.java
> > Removed:
> > platform/core/trunk/xwiki-xml/src/main/java/org/xwiki/xml/internal/
> > html/CleaningFilter.java
> > platform/core/trunk/xwiki-xml/src/main/java/org/xwiki/xml/internal/
> > html/DocTypeCleaningFilter.java
> > platform/core/trunk/xwiki-xml/src/main/java/org/xwiki/xml/internal/
> > html/ListCleaningFilter.java
> > Modified:
> > platform/core/trunk/xwiki-xml/pom.xml
> > platform/core/trunk/xwiki-xml/src/main/java/org/xwiki/xml/internal/
> > html/DefaultHTMLCleaner.java
> > platform/core/trunk/xwiki-xml/src/main/resources/META-INF/plexus/
> > components.xml
> > platform/core/trunk/xwiki-xml/src/test/java/org/xwiki/xml/
> > XMLUtilsTest.java
> > platform/core/trunk/xwiki-xml/src/test/java/org/xwiki/xml/internal/
> > html/DefaultHTMLCleanerTest.java
> > Log:
> > XWIKI-3101: Replace invalid xhtml <br/> elements with <div
> > class="wikimodel-emptyline"/> in DefaultHTMLCleaner
> > XWIKI-3094: Errornous rendering of xhtml content with <br/
> > >[newline]<p> sequence
> >
> > * LineBreakCleaningFilter implements the above functionality.
> > * Adding LineBreakCleaningFilter caused a fan-out of 21 in
> > DefaultHTMLCleaner. To overcome this problem CleaningFilter
> > implementations were made components and they are now injected via
> > plexus into DefaultHTMLCleaner (refer to components.xml) Necessary
> > package restructuring was done.
> > * Added tests to verify the behaviour of LineBreakCleaningFilter.
>
> [snip]
>
>
>
>
>
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
The XWiki development team is pleased to announce the release of XWiki
Eclipse 1.2 RC1.
Go grab it at http://xeclipse.xwiki.org
XWiki Eclipse 1.2 RC1 introduces several bug fixes and major
improvements such as syntax highlighting and completion, support for
objects and translations and much more.
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXEclipse12RC1
Thanks
-The XWiki dev team
Hi Asiri,
This is good (the move to components for filters) except for one very
important thing: now if some module implements some filter components
using that interface they'll be used automagically by the HTMLCleaner.
This makes the HTML Cleaner non safe with a non predictable behavior.
Imagine for ex that in the office importer you implement the
CleaningFilter interface and expose the implementations as components.
These filters will be used even when not doing office imports.
So +1 for components but you need a way to control which filters are
used for a cleaning operation now.
Thanks
-Vincent
On Jan 12, 2009, at 12:38 AM, asiri (SVN) wrote:
> Author: asiri
> Date: 2009-01-12 00:38:10 +0100 (Mon, 12 Jan 2009)
> New Revision: 15346
>
> Added:
> platform/core/trunk/xwiki-xml/src/main/java/org/xwiki/xml/html/
> filter/
> platform/core/trunk/xwiki-xml/src/main/java/org/xwiki/xml/html/
> filter/CleaningFilter.java
> platform/core/trunk/xwiki-xml/src/main/java/org/xwiki/xml/internal/
> html/filter/
> platform/core/trunk/xwiki-xml/src/main/java/org/xwiki/xml/internal/
> html/filter/DocTypeCleaningFilter.java
> platform/core/trunk/xwiki-xml/src/main/java/org/xwiki/xml/internal/
> html/filter/LineBreakCleaningFilter.java
> platform/core/trunk/xwiki-xml/src/main/java/org/xwiki/xml/internal/
> html/filter/ListCleaningFilter.java
> Removed:
> platform/core/trunk/xwiki-xml/src/main/java/org/xwiki/xml/internal/
> html/CleaningFilter.java
> platform/core/trunk/xwiki-xml/src/main/java/org/xwiki/xml/internal/
> html/DocTypeCleaningFilter.java
> platform/core/trunk/xwiki-xml/src/main/java/org/xwiki/xml/internal/
> html/ListCleaningFilter.java
> Modified:
> platform/core/trunk/xwiki-xml/pom.xml
> platform/core/trunk/xwiki-xml/src/main/java/org/xwiki/xml/internal/
> html/DefaultHTMLCleaner.java
> platform/core/trunk/xwiki-xml/src/main/resources/META-INF/plexus/
> components.xml
> platform/core/trunk/xwiki-xml/src/test/java/org/xwiki/xml/
> XMLUtilsTest.java
> platform/core/trunk/xwiki-xml/src/test/java/org/xwiki/xml/internal/
> html/DefaultHTMLCleanerTest.java
> Log:
> XWIKI-3101: Replace invalid xhtml <br/> elements with <div
> class="wikimodel-emptyline"/> in DefaultHTMLCleaner
> XWIKI-3094: Errornous rendering of xhtml content with <br/
> >[newline]<p> sequence
>
> * LineBreakCleaningFilter implements the above functionality.
> * Adding LineBreakCleaningFilter caused a fan-out of 21 in
> DefaultHTMLCleaner. To overcome this problem CleaningFilter
> implementations were made components and they are now injected via
> plexus into DefaultHTMLCleaner (refer to components.xml) Necessary
> package restructuring was done.
> * Added tests to verify the behaviour of LineBreakCleaningFilter.
[snip]
I go on compiling XWiki under windows until I get back my beloved linux
platform :)... Finally, it appears not to be so trivial... Last week, I
found 2 minor issues but this last one is a blocking one.
When you build wysiwyg under windows, the gwt-maven plugin generates a
script "compile.cmd" in order to compile GWT code.
But, when it launches the script, you get an error "Line too long"...
And this is true, due to the huge number of dependencies with long
directories, the Classpath variables are too long for Windows... I love
Windows :):):)
Apparently, this is a well known bug of gwt-maven but seems not easy to
solve or not enough important to be solved :)
Anyway, until this bug is solved or if somebody finds a clever workaround
solution, it will remain impossible to compile wysiwyg under windows.
This is disturbing because, if you don't compile WYSIWYG, you can compile XE
without any problem but when you launch the server, you get a weird error
such as "Can't find class file RemoteService" and the jetty server don't
bind to classic port 8080.
So the only solution I found is to remove "wysiwyg" module from profile "xe"
in xwiki-web.
best regards
Pascal
The XWiki development team is pleased to announce the release of XWiki
Enterprise 1.7.1. This is a bugfix and minor enhancements release
following XE 1.7.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
WYSIWYG and Rendering 2.0 Improvements :
* You can now upload and insert image in your documents from the WYSIWYG
* You can create tables and manage them (row/columns addition and
deletion) from the WYSIWYG.
* Added support for explicit line breaks (\\) in XWiki Syntax 2.0
Important bug fixes:
* XWIKI-2988: The way to synchronize several LDAP groups with the
same XWiki group is wrong
* XWIKI-3024: XWiki authenticator load
xwiki.authentication..createuser in place of
xwiki.authentication.createuser from xwiki.cfg file
* XWIKI-3023: Timeout when trying to connect to Penrose LDAP server
* XWIKI-3010: By default the size of "ldap_group_mapping" field in
XWikiPreferences is too short
* Many WYSIWYG bugs fixed
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise171
Thanks
-The XWiki dev team
Hi Devs,
The office importer module has reached a point where it can be integrated
into XWiki's UI:
Currently there are two UI's provided by office importer:
1. The Wysiwyg plugin which should be integrated to Wysiwyg UI (obviously) :
http://91.121.237.216/xwiki/bin/view/Main/
2. The office importer application :
http://91.121.237.216/xwiki/bin/view/Import/
We need to decide how we will allow users to discover the office importer
application from the main UI. Following are some options:
a) Add the "import" action to one of our existing menus
Problem: I don't see any existing menus where "import" will fit in.
b) Add a new menu named "Import" into the main menu bar. like { | Edit |
show | print | import | actions | watch }
Problem: existing menus and their menu items always refer to actions
performed on the current document (wiki page) while importing is about
importing an office document to a new wiki page.
Possible solution : We can change the office importer slightly so that it
overwrites the current wiki page with the imported document.
Any other options ?
Thanks.
- Asiri
Dear all,
I've finished to refactor the rest subsystem and I propose to move it to
the trunk for inclusion in 1.8M1.
It doesn't support all the URIs of the API (see
http://dev.xwiki.org/xwiki/bin/view/Design/RestfulAPI for details) but
still I think it's good to have it included.
Here it is my +1
-Fabio