- xwiki-devs@xwiki.org - lists.xwiki.org

by antoine seilles

I use the addObject method to create new annotation, my plugin. When a user submit the form to add an annotation, i call addObject('annotationClass') . But, to invoke this method, user might have the edit right. And i'd like to have possibility to annotate with only comment right. How to create a method addAnnotation that need only comment right to be called? Thank for your time. Antoine

17 years, 7 months

3
3
0 0

[xwiki-devs] Secondary Store (Filesystem) propsal

by David Ward

All, Ludovic asked me to write this up on the wiki, but the page says that I should post it on the mailing list first (hopefully to get some initial feedback). There are a few difficulties that we run into when developing in xwiki: - Collision issues when having multiple editors dealing with a single page (it seems that most people tend to copy the code from the browser, edit it locally, then paste it back when dealing with larger code changes -- sometimes forgetting to copy again in case someone else changes something, sometimes xwiki forgets that the page is being edited by someone else). - Branching/deployment issues when moving from our development server to a staging server and finally to a production server (all files? how can one tell what files changed between them? etc.). - Branching/deployment issues when working with "fixes" to a current issue to be deployed to a "current version" production server vs. new implementations to go to a "next version" of the production server (various branching issues here). - Merging changes between different xwiki deployments (such as translation lookup page changes in production where the development page has been updated with new translation strings) In discussing some of this with Ludovic, he was intrigued by the idea of using a file system directory to hold non-data wiki pages ("application" pages) and asked me to write up a proposal describing the idea. The general idea would be to have a method (plugin?) where application wiki pages could be maintained outside of the wiki database. There would be a directory where wiki pages would be stored. - This directory could be maintained with any version control tool (eases issues with different branches where export/import has a number of issues) - xwiki would pull pages from this directory instead of the database when a page exists there. I think this could be done as a plugin that wraps the default plugin. A number of issues would have to be solved, some very similar to issues with other proposals such as the WebDAV Service: - File naming conventions - Current proposal (somewhat derived from WebDAV Service proposal) is: Space/ Page/ wiki.txt (maybe something more like Space.Page.vm to make editing multiple pages easier when you don't see the directory name like in most editors) attributes.xml (or could be split for some things title.txt, parent.txt, possibly in a subdirectory attributes/) attachments/ attach1.png objects/ object1.xml class/ class.xml lang_xx/ (for translated versions) wiki.txt attributes.xml attachments/ (?) attach1.png objects/ (?) object1.xml - Priority of stores - If there is a page on the file system and in the database, which takes priority? - One option here is to just have a configurable rule. - Another option is to have a thread doing one-way or bi-directional copying of the files if they are added/deleted/updated. - Queries - Right now the use of $xwiki.searchDocuments() (at least in our usage) assumes that it is talking to a hibernate query backend, which may be difficult to make work with a file store. - Possibly the option of having pages copied to the DB when they change on the filesystem resolves this as well. Feedback is more than welcome, David --

17 years, 7 months

1
0
0 0

[xwiki-devs] New product proposal and request for volunteers

by Sergiu Dumitriu

Hi everybody, On the mailing lists, we noticed several people trying to use XWiki in academic environments, requesting features such as support for mathematical equations or support for LaTeX. We took some time to design a product that would be great for writing scientific papers, identifying some important features, and some "would be nice to have" features. You can see the current design proposal at http://dev.xwiki.org/xwiki/bin/view/Design/SPAWN (feel free to send comment on the mailing list). Given the fact that this is not a product which can easily be sold, and that there are other more critical projects to work on for the moment, the core XWiki developers cannot dedicate much time on it. This is why we need help from the community. Whoever would like to use this product, and has the power and knowledge to work on in, please help us. If you are in an university as a student, you can propose one of the sub-applications as a project for one of your classes. If you are a teacher, you can propose some sub-applications as student projects. We can help with coordination, more detailed description/requirements, question answering, code review, etc. Some of the features require mostly programming skills, while others require more advanced research skills, like the positioned comments in a dynamic text (adapting some sequence alignment algorithms from bioinformatics seems the best idea for the moment, but also some fuzzy systems theory could be applied), or an automatic merge algorithm based on Operational Transformations, so some publications can come out of this, too. If we gather a few volunteers, I'll make the necessary Jira setup and mark the product as active. Regards, The XWiki dev team

17 years, 7 months

2
1
0 0

[xwiki-devs] [VOTE] Release XE 1.2.2

by Vincent Massol

Hi, I'd like to do a XE 1.2.2 release today or tomorrow. This is a bug fix release fixing 2 important areas: 1) automatic migration from old database (1.0 and pre 1.0) 2) Rights Mgmt issues with IE6 Here's the full release notes for the moment: Release Notes - XWiki Core - Version 1.2.2 ** Bug * [XWIKI-2064] - DBListClass and DBTreeListClass are building invalid SQL statements * [XWIKI-2065] - XWikiHibernateStore.deleteWiki don't works * [XWIKI-2066] - Migrator fails to upgrade sub wiki databases * [XWIKI-2074] - Database Migration fails when migrating from 1.0 or older directly to 1.2 without going through a 1.1 upgrade * [XWIKI-2076] - "Content is not allowed in prolog" error while migrating a database to 1.2 * [XWIKI-2078] - Missing translation entry for the title of the Group Admin page * [XWIKI-2079] - Fails to save document after migrating from a 1.0 or before database to 1.2 * [XWIKI-2080] - Server hangs while rendering certain pages ** New Feature * [XWIKI-2088] - Add a method to retrieve the e-mail address of a user ** Task * [XWIKI-2084] - Use the new Skins modules and package Dodo, Finch and Albatross in XE 1.2 branch I say "for the moment" since we have the following bugs fixed on trunk and not committed in the branch. Could the person in parenthesis please tell me whether their fix should also be on the 1.2 branch please: http://jira.xwiki.org/jira/browse/XWIKI-1621 (Artem) http://jira.xwiki.org/jira/browse/XWIKI-299 (Artem) http://jira.xwiki.org/jira/browse/XWIKI-1949 (Artem) http://jira.xwiki.org/jira/browse/XWIKI-2068 (Thomas) http://jira.xwiki.org/jira/browse/XWIKI-2097 (Sergiu) http://jira.xwiki.org/jira/browse/XWIKI-2056 (Sergiu) http://jira.xwiki.org/jira/browse/XWIKI-2052 (Jerome) http://jira.xwiki.org/jira/browse/XWIKI-2040 (Sergiu) Thanks -Vincent

17 years, 7 months

6
15
0 0

[xwiki-devs] Difficulty compling r7282

by Colin Tay

Hi all, I have tried to compile xwiki-platform with maven-2.1-SNAPSHOT. But faced difficulty compling xwiki-core and xwiki-patchservice. The error messages is as follow: [INFO] For artifact {com.xpn.xwiki.platform.tools:xwiki-verification-resources:null:jar}: The version cannot be empty. Thanks in adv, Colin ______________________________________________________________________ Search, browse and book your hotels and flights through Yahoo! Travel. http://sg.travel.yahoo.com

17 years, 7 months

3
2
0 0

[xwiki-devs] [ANN] XWiki Watch Milestone 3 Released

by Jerome Velociter

The XWiki development team is pleased to announce the release of XWiki Watch 1.0 Milestone 3. You can go grab it here : http://www.xwiki.org/xwiki/bin/view/Main/Download#HXWikiWatch This release include both bug fixes and new features, among which you can find : - Date range filter: you can select the date range (start date and end date) for the articles displayed in the list. - Email press review : the same press review you used to view as html or as pdf can now be sent over through email - other UI improvements and bugfixes. You can read the full release notes at: http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesWatch10M3 And the installation guide : http://code.xwiki.org/xwiki/bin/view/Applications/WatchApplication Have fun! The XWiki Watch development team

17 years, 7 months

1
0
0 0

[xwiki-devs] latest deployment from source failing

by Sachin Mittal

Hi, Very recently I update the source and built again and after I tried to access xwiki it failed with following stack trace: 2008-02-10 23:33:40,218 [] [http-9080-Processor25] WARN action.RequestProcessor - Unhandled Exception thrown: class java.lang.NullPointerException 2008-02-10 23:33:40,234 [] [http-9080-Processor25] ERROR [/xwiki].[action] - Servlet.service() for servlet action threw exception java.lang.NullPointerException at java.util.Hashtable.put(Unknown Source) at com.xpn.xwiki.web.Utils.prepareContext(Utils.java:266) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:111) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:117) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.cluster.tcp.ReplicationValve.invoke(ReplicationValve.java:346) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Unknown Source) In the code of Utils.java I see the following code added: // This is a temporary bridge so that non XWiki component classes can lookup XWiki // components. A ComponentManager instance has been set up in the Servlet Context and // we now populate the XWiki Context with it so that code can then use it to look up // components. // This is of course not necessary for XWiki components since they just need to implement // the Composable interface to get access to the Component Manager or better they simply // need to define the Components they require as field members and configure the Plexus // deployment descriptors (components.xml) so that they are automatically injected. ComponentManager componentManager = (ComponentManager) engine_context.getAttribute(ComponentManager.class.getName()); context.put(ComponentManager.class.getName(), componentManager); I debugged and checked that componentManager is being fetched as null. Can you please help me what I may be doing wrong. I have updated the jars xwiki-core-plexus-1.3-SNAPSHOT.jar and xwiki-core-component-1.3-SNAPSHOT.jar so I don't think it may be related to some old source. Thanks Sachin ----- http://www.assembla.com/wiki/show/sachin_mittal about me: -- View this message in context: http://www.nabble.com/latest-deployment-from-source-failing-tp15399312p1539… Sent from the XWiki- Dev mailing list archive at Nabble.com.

17 years, 7 months

2
2
0 0

[xwiki-devs] tiny_mce and wiki_editor (what are both used for)

by Sachin Mittal

Hi All, I have a small confusion. Currently I see that both tiny_mce and wiki_editor javascript files are included in the vm pages to render wysiwug text area (ie the wiki editor). Are both required? If yes then what are the roles these two play in wiki editor rendering? In the code say textarea_wysiwyg.vm I only see wiki editor getting initialized. So if someone can can give me some insight in these two javascript modules we import then it would be very helpful. If one of the module is redundant than can we exclude it from our deployment? Also in this case what about excluding from the svn itself. Thanks Sachin ----- http://www.assembla.com/wiki/show/sachin_mittal about me: -- View this message in context: http://www.nabble.com/tiny_mce-and-wiki_editor-%28what-are-both-used-for%29… Sent from the XWiki- Dev mailing list archive at Nabble.com.

17 years, 7 months

1
0
0 0

[xwiki-devs] [Proposal] Include Toucan skin as preview in XE 1.3M2 release in addition to Albatross

by Vincent Massol

The idea is to keep Albatross the default skin in 1.3M2 but package the Toucan skin so that users can easily use it and test it more. Then in 1.3RC1 we would make Toucan the default skin. We should keep the Albatross skin too I think and only remove it in 1.4 (i.e. users would download it from code.xwiki.org to get it). WDYT? Thanks -Vincent

17 years, 7 months

3
3
0 0

[xwiki-devs] [VOTE] Remove XWikInterface interface

by Vincent Massol

Right now this interface isn't used anywhere. It's a burden. It has lots of cruft methods, etc. I hereby propose to send it to the guillotine! In the future it'll be reborn as component interface when we split that mammoth XWiki java class into components. Here's my +1 Thanks -Vincent

17 years, 7 months

4
3
0 0

[xwiki-devs] [Proposal] XWiki Tools Reorganization

by Vincent Massol

Hi, I'm proposing a reorg of our tools releases. Here are the proposed changes: 1) Release each tool module separately from the others. This means creating one jira project per tools module. Since there'll be plenty I'll also create a new jira category called "XWiki Tools" 2) Remove the build-tools/ directory and move all tools directly in xwiki-platform-tools 3) Rename some tools as a consequence of 2). Here are the renames I propose: build-verifications --> xwiki-verification-resources build-xar-handlers --> xwiki-xar-handlers build-xar-plugin --> xwiki-xar-plugin build-xmldoc-update-plugin --> xwiki-xmldoc-update-plugin shared-tests --> xwiki-shared-tests xwiki-configuration-resources (no change) xwiki-jetty-resources (no change) packager --> xwiki-packager-plugin 4) Remove cryptpasswords and instead move it to the sandbox Let me know quickly what you think since I'd like to make those changes in the coming hours so that Jerome can release what he needs to XWiki Watch. Thanks -Vincent

17 years, 7 months

6
6
0 0

[xwiki-devs] few questions about plugins and rights

by antoine SEILLES

Well you can see progress of my experimentation based on xwiki platform there: http://apeiron.lirmm.fr:9006/xwiki I develop a plugin to annotate documents and use it to debate. And I still have some questions: How to add an url to an annotation (my plugin) ? Indeed we want to add annotation to annotation. And so we need to open an annotation as a document in xwikicontent div. Currently, to see the annotation form you need to get comment right. I have set this right allowed to xwikiallgroup. But, if you don't have the edit right, you cannot submit the form. Submitting the form call the method : $doc.getURL('objectadd') So how can i resolve this problem? Maybe creating a new method to add annotation? But how to do that? And last question, where can i see wiki editor comportment? Thank for your time Antoine SEILLES

17 years, 7 months

1
0
0 0

[xwiki-devs] annotation plugin: how to access properties of a plugin

by antoine SEILLES

I have an AnnotationPluginApi.java class and i have a method to get all the annotations associated to a document: public Vector getAnnotations(Document doc){ return doc.getObjects("AnnotationClass"); } Now i'd like to have a method to get all the annotations associated to a document having a specific value specified in parameters for one field : public Vector getAnnotations(Document doc, String field, String value) Wich should return all the annotations having the value "value" for the field "field". How to do that? In fact, how to access fields of my objects "AnnotationClass"? Thank for your time. Ps: in AnnotationPlugin i have this method: public BaseClass getAnnotationClass(XWikiContext context) throws XWikiException { XWikiDocument doc; XWiki xwiki = context.getWiki(); boolean needsUpdate = false; try { doc = xwiki.getDocument("XWiki.AnnotationClass", context); } catch (Exception e) { doc = new XWikiDocument(); doc.setSpace("XWiki"); doc.setName("AnnotationClass"); needsUpdate = true; } BaseClass bclass = doc.getxWikiClass(); bclass.setName("XWiki.AnnotationClass"); needsUpdate |= bclass.addTextField("author", "Author", 30); needsUpdate |= bclass.addDateField("created", "Created", "dd/MM/yyyy"); needsUpdate |= bclass.addTextAreaField("comment", "Comment", 40, 5); needsUpdate |= bclass.addTextAreaField("selection", "Selection", 40, 5); needsUpdate |= bclass.addTextAreaField("reformulation", "Reformulation", 40, 5); needsUpdate |= bclass.addNumberField("begin", "Begin", 100, "integer"); needsUpdate |= bclass.addNumberField("end", "End", 100, "integer"); needsUpdate |= bclass.addTextField("emotion", "Emotion", 30); needsUpdate |= bclass.addTextField("judgmentUniversel", "JudgmentUniversel", 30); needsUpdate |= bclass.addTextField("judgmentParticulier", "JudgmentParticulier", 30); needsUpdate |= bclass.addTextField("domain", "Domain", 30); String content = doc.getContent(); if ((content == null) || (content.equals(""))) { needsUpdate = true; doc.setContent("1 AnnotationClass"); } if (needsUpdate) xwiki.saveDocument(doc, context); return bclass; }

17 years, 7 months

4
6
0 0

[xwiki-devs] Lightbox proposals

by Evelina Slatineanu

From: Evelina Slatineanu [mailto:evelyne24@gmail.com] Sent: Thursday, February 07, 2008 5:05 PM To: 'XWiki Developers' Subject: Lightbox proposals Hello all, Due to the fact that we want to make the lightbox a standard feature for xwiki and the current lightbox used for Users & Groups management is not quite complete (and the code needs to be cleaned a little bit), I was thinking that we need a "multi-purpose" lightbox that could support Ajax but still work fine without it (which is not the case of the current one), that could load media files (for instance .swf, quicktime movies etc), .pdf, pages containing frames, inline content (no Ajax) etc. Therefore we would need a nicer lightbox. So, there are 2 proposals from me: 1. To spend some time improving the current lightbox to support all the above (which will mean practically re-writing it FROM SCRATCH and will take some time - one, two weeks or more, depending of my time, as my priority now is Chronopolys) 2. Use one of the existing lightboxes that I found on the Internet (customized for xwiki), like: - LightWindow (using prototype and scriptaculous), which is quite complete and MIT - licenced http://www.wildbit.com/labs/modalbox/ - A lightbox based on yui library (which is already in the albatross and probably will remain.is quite a nice library imo), like the one below, which has the nice feature of being "movable": http://test.thecodecentral.com/demos/lightboxrev/lightbox.html - ModalBox, another lightbox using prototype + scriptaculous, which looks nice but I am not sure about the licence http://test.thecodecentral.com/demos/lightboxrev/lightbox.html and there are more out there on the web :P Personaly, I think the one with most features is LightWindow, but that would mean to keep scriptaculous framework . So, I would like your opinions on this matter (ideas, suggestions, maybe some other lightbox features you would like to have as standard in xwiki etc) Thanks, Evelina

17 years, 7 months

1
0
0 0

[xwiki-devs] xwikisql plugin released

by rssh

Good day community. Bridge between xwiki and legacy relational databases can be interesting for some applications. I just wrote plugin for this: http://xwikisql.gradsoft.ua (Hope, this plugin can be integrated into general xwiki infrastructure) Regards! -- Ruslan Shevchenko GradSoft. http://www.gradsoft.ua

17 years, 7 months

2
2
0 0

[xwiki-devs] Releasing platform-tools

by Jerome Velociter

Hello devs, In a previous mail, I said I was going to release platform-tools/ (see http://tinyurl.com/2khge6). There were a last minute change as Vincent proposed me to integrate in that release a maven plugin I wrote for XWiki Watch. The plugin is now integrated, it allows to attach files to xwiki XML documents within the build process. Will release this afternoon. Jérôme.

17 years, 7 months

1
0
0 0

[xwiki-devs] rights to addObject

by antoine

Is there a right level required to call the method $doc.getURL('objectadd')? I have a form showed only to user with comment right.. But when they submit this form, if they don't have an admin or maybe edit right, they have an error "...not allowed to access this page...". So how can i call the method $doc.getURL('objectadd') or something that would have the same effect but with only comment right? Thank you

17 years, 7 months

1
0
0 0

[xwiki-devs] Plugin API on code.xwiki.org

by Sergiu Dumitriu

Hi, I think it would be better to publish the plugin API javadoc on the XWiki site, instead of manually putting some pseudo java interface in a {code} block. We do the same for the platform-core, by uploading the generated javadoc jar and using the zipexplorer plugin to show the index page. Sergiu

17 years, 7 months

2
2
0 0

[xwiki-devs] Evaluating curriki plugins (how to)

by Sachn Mittal

Hi, I would like to evaluate certain plugins for my work namely (invitationmanager, currikispacemanager and spacemanager). I was going to some of the previous threads on curriki and found that we plan to migrate these plugins to xwiki core at a later date. So until these are done how can we test and evaluate these plugins. I am building xwiki directly from source and I have build the core platform and added enterprise app on top of it. One way to test is to build the curriki product itself. But since I have been working on the core app for some time and have made several extensions on top of it, I would like to continue with the same. So to test these plugins what applications or pages under xwiki\xwiki-product-curriki\wiki\src\main\resources do I need to import. I am fairly comfortable with xwiki architecture so I can do most myself, I just need to know how can I get started on this front with the three plugins. Thanks Sachin Mittal -- View this message in context: http://www.nabble.com/Evaluating-curriki-plugins-%28how-to%29-tp15138138p15… Sent from the XWiki- Dev mailing list archive at Nabble.com.

17 years, 7 months

5
8
0 0

Re: [xwiki-devs] [xwiki-notifications] r7312 - xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/objects/classes

by Sergiu Dumitriu

We could use commons-lang/DateUtils.parse, which accepts an array of patterns, and tries them in order. vmassol (SVN) wrote: > Author: vmassol > Date: 2008-02-06 12:47:28 +0100 (Wed, 06 Feb 2008) > New Revision: 7312 > > Modified: > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/objects/classes/DateClass.java > Log: > Better error reporting. We should never output stack trace for non fatal errors. > > > > Modified: xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/objects/classes/DateClass.java > =================================================================== > --- xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/objects/classes/DateClass.java 2008-02-06 11:16:03 UTC (rev 7311) > +++ xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/objects/classes/DateClass.java 2008-02-06 11:47:28 UTC (rev 7312) > @@ -31,6 +31,8 @@ > import com.xpn.xwiki.web.XWikiMessageTool; > import org.apache.ecs.xhtml.input; > import org.apache.ecs.xhtml.link; > +import org.apache.commons.logging.Log; > +import org.apache.commons.logging.LogFactory; > import org.dom4j.Element; > > import java.text.ParseException; > @@ -39,9 +41,12 @@ > import java.util.Locale; > import java.util.Map; > > -public class DateClass extends PropertyClass { > +public class DateClass extends PropertyClass > +{ > + private static final Log LOG = LogFactory.getLog(DateClass.class); > > - public DateClass(PropertyMetaClass wclass) { > + public DateClass(PropertyMetaClass wclass) > + { > super("date", "Date", wclass); > setSize(20); > setDateFormat("dd/MM/yyyy HH:mm:ss"); > @@ -125,16 +130,23 @@ > return property; > } > > + SimpleDateFormat sdf = new SimpleDateFormat("yyyy-MM-dd HH:mm:ss.S"); > try { > - SimpleDateFormat sdf = new SimpleDateFormat("yyyy-MM-dd HH:mm:ss.S"); > property.setValue(sdf.parse(value)); > } catch (ParseException e) { > + SimpleDateFormat sdf2 = new SimpleDateFormat("EEE MMM d HH:mm:ss z yyyy", Locale.US); > try { > - e.printStackTrace(); > - SimpleDateFormat sdf = new SimpleDateFormat("EEE MMM d HH:mm:ss z yyyy", Locale.US); > - property.setValue(sdf.parse(value)); > + if (LOG.isWarnEnabled()) { > + LOG.warn("Failed to parse date [" + value + "] using format [" > + + sdf.toString() + "]. Trying again with format [" > + + sdf2.toString() + "]"); > + } > + property.setValue(sdf2.parse(value)); > } catch (ParseException e2) { > - e2.printStackTrace(); > + if (LOG.isWarnEnabled()) { > + LOG.warn("Failed to parse date [" + value + "] using format [" > + + sdf2.toString() + "]. Defaulting to the current date."); > + } > property.setValue(new Date()); > } > } >

17 years, 7 months

2
1
0 0

[xwiki-devs] bug with '\' in wysiwyg

by Daniel Bertinshaw

Hi When you enter a '\' into the wysiwyg editor it doesn't render right in the normal view and converts it to '\' in the wikicode which it then treats and an escape sequence. The stopgap is that we use \ in the wikicode, but this isn't very good for low tech users. Any plans to alter this in future releases, and better yet, a quick fix I could implement in the MCE code (im not much for javascript)

17 years, 7 months

1
0
0 0

Re: [xwiki-devs] [xwiki-notifications] r7299 - in xwiki-products/xwiki-watch/trunk: gwt/src/main/java/com/xpn/xwiki/watch/client gwt/src/main/java/com/xpn/xwiki/watch/client/data gwt/src/main/java/com/xpn/xwiki/watch/client/ui/dialog gwt/src/main/java/com/xpn/xwiki/watch/client/ui/wizard gwt/src/main/java/com/xpn/xwiki/watch/public wiki/src/main/resources/WatchCode

by Sergiu Dumitriu

Anca, you forgot to run native2ascii on the french translation file lucaa (SVN) wrote: > Author: lucaa > Date: 2008-02-05 17:33:27 +0100 (Tue, 05 Feb 2008) > New Revision: 7299 > > Added: > xwiki-products/xwiki-watch/trunk/gwt/src/main/java/com/xpn/xwiki/watch/client/ui/dialog/PressReviewMailDialog.java > xwiki-products/xwiki-watch/trunk/wiki/src/main/resources/WatchCode/SendPressReviewEmail > Removed: > xwiki-products/xwiki-watch/trunk/gwt/src/main/java/com/xpn/xwiki/watch/client/ui/wizard/PressReviewMailDialog.java > Modified: > xwiki-products/xwiki-watch/trunk/gwt/src/main/java/com/xpn/xwiki/watch/client/Constants.java > xwiki-products/xwiki-watch/trunk/gwt/src/main/java/com/xpn/xwiki/watch/client/data/DataManager.java > xwiki-products/xwiki-watch/trunk/gwt/src/main/java/com/xpn/xwiki/watch/public/Watch.css > xwiki-products/xwiki-watch/trunk/wiki/src/main/resources/WatchCode/PressReview > xwiki-products/xwiki-watch/trunk/wiki/src/main/resources/WatchCode/Translations > xwiki-products/xwiki-watch/trunk/wiki/src/main/resources/WatchCode/Translations.fr > Log: > > XWATCH-13: Allow to send a press review by email > Added the SendPressReviewEmail document that uses the mailsender plugin and the PressReview document to generate and send the press review by email. Changed PressReview formatting to match the email requirements, the DataManager to include a email sending function and the PressReviewMailDialog to invoke it. Also styled the PressReviewMailDialog. > [snip] > Modified: xwiki-products/xwiki-watch/trunk/wiki/src/main/resources/WatchCode/Translations.fr > =================================================================== > --- xwiki-products/xwiki-watch/trunk/wiki/src/main/resources/WatchCode/Translations.fr 2008-02-05 14:09:55 UTC (rev 7298) > +++ xwiki-products/xwiki-watch/trunk/wiki/src/main/resources/WatchCode/Translations.fr 2008-02-05 16:33:27 UTC (rev 7299) > @@ -285,6 +285,12 @@ > watch.email.mailcontent=Editez le contenu qui sera envoy� avec la Revue de Presse > watch.email.mailcontentdefault=Vous avez re�u une Revue de Presse depuis XWiki Watch. Elle inclut les articles suivants: > watch.email.notimplemented=Cette fonction n'est pas disponible dans la version Beta afin d'emp�cher le spam. > +watch.email.invitation=Veuillez renseigner les donn�es relatives a votre email > +watch.email.success=La revue de presse a �t� envoy� avec succ�s aux adresses email suivantes: > +watch.email.dialogtitle=R�sultat de l'envoi > +watch.chooseproutput.noselection=Vous n'avez pas choisi le format de la revue de presse > +watch.email.noaddress=Vous n'avez renseign� aucune adresse mail > +watch.email.error=L'envoi email de la revue de presse a echou� pour la raison suivante: > > watch.pressreviewforspace=XWiki Watch Revue de Presse pour l'espace > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > notifications mailing list > notifications(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/notifications

17 years, 7 months

1
0
0 0

[xwiki-devs] Warning: <iframe> escaping malformed URI reference

by Raffaele Viola

Hi all, im using this macro to include HTML file into my page #macro(displayppt $zipname $htmlname) #set ($url = $xwiki.zipexplorer.getFileLink($doc, "$zipname", "$htmlname")) <iframe src="$url" frameborder="0" scrolling="0" width="800" height="600"></iframe> #end It works but when I try to export my page in PDF the generated PDF doesn't contains the included file and in the console appears something like Warning: <iframe> escaping malformed URI reference. the URI /xwiki/bin/download/Discussione/MasterPlan/Piano%20Principale.zip/Piano Principale.htm is traslated in: file:/C:/workspace%2Dxwiki/apache%2Dtomcat%2D5.5.25/work/Catalina/localhost/xwiki/h5khbL0n/ Discussione.MasterPlan.Piano Principale.zip/Piano Principale.htm Regards Raffo

17 years, 7 months

3
4
0 0

[xwiki-devs] [VOTE] Allow includes/excludes filtering using the maven xar plugin

by Jerome Velociter

Hello devs, I propose to introduce the possibility of configuring our maven xar plugin to define lists of includes/excludes when performing xar or unxar. I've created a JIRA issue for it : http://jira.xwiki.org/jira/browse/XTOOLS-22 with a patch attached. I would like to apply it and release platform-tools, so that we can use it in watch next release (by the end of the week). My +1 Regards, Jérôme

17 years, 7 months

5
5
0 0

[xwiki-devs] XE/Platform 1.2.2

by Thomas Mortagne

Hi, In Core 1.2.1 I committed a wrong patch for XWikiHibernateStore.deleteWiki (see http://jira.xwiki.org/jira/browse/XWIKI-2065) so I will need to release a 1.2.2 for XEM 1.1 that need this feature. So I ask for everyone to take care of committing XE/Platform bugs fixes in trunks and branch 1.2. If no ones need 1.2.2 before, I plan to release XE 1.2.2 with XEM 1.1 planned in something like starting or middle of next month. Thanks, -- Thomas Mortagne

17 years, 7 months

3
3
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs