Hello, I am testing XWiki (2.1.1, PostgreSQL, XP SP3) for our organisation and I am running into some problems with the office import feature. The document and am trying to import is an odt document with one line. This is the stack trace I get : 8-Feb-2010 4:05:09 PM net.sf.jodconverter.office.OfficeConnection connect INFO: connected: 'socket,host=127.0.0.1,port=8100,tcpNoDelay=1' 2010-02-08 16:06:45,787 [http://localhost:8082/xwiki/bin/view/XWiki/OfficeImporterResults] ERROR rterVelocityContextInit ializer - Error while performing conversion. org.xwiki.officeimporter.OfficeImporterException: Error while performing conversion. at org.xwiki.officeimporter.internal.openoffice.DefaultOpenOfficeDocumentConverter.convert(DefaultOpenOfficeDocu mentConverter.java:181) at org.xwiki.officeimporter.internal.builder.DefaultXHTMLOfficeDocumentBuilder.build(DefaultXHTMLOfficeDocumentB uilder.java:84) at org.xwiki.officeimporter.internal.DefaultOfficeImporter.importStream(DefaultOfficeImporter.java:125) at org.xwiki.officeimporter.internal.OfficeImporterVelocityBridge.importDocument(OfficeImporterVelocityBridge.ja va:97) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke(UberspectImpl.java:389) at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:378) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:270) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:252) at org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:493) at org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:71) at org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:142) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:87) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:336) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:106) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:336) at org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:191) at org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:156) at com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:116) at com.xpn.xwiki.render.XWikiVelocityRenderer.render(XWikiVelocityRenderer.java:93) at com.xpn.xwiki.render.DefaultXWikiRenderingEngine.renderText(DefaultXWikiRenderingEngine.java:272) at com.xpn.xwiki.render.DefaultXWikiRenderingEngine.renderText(DefaultXWikiRenderingEngine.java:202) at com.xpn.xwiki.render.DefaultXWikiRenderingEngine.renderText(DefaultXWikiRenderingEngine.java:170) at com.xpn.xwiki.render.DefaultXWikiRenderingEngine.renderDocument(DefaultXWikiRenderingEngine.java:159) at com.xpn.xwiki.doc.XWikiDocument.getRenderedContent(XWikiDocument.java:566) at com.xpn.xwiki.doc.XWikiDocument.getRenderedContent(XWikiDocument.java:583) at com.xpn.xwiki.api.Document.getRenderedContent(Document.java:475) at sun.reflect.GeneratedMethodAccessor258.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke(UberspectImpl.java:389) at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:378) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:270) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:252) at org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:493) at org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:71) at org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:142) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:336) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:106) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:336) at org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:191) at org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:156) at com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:116) at com.xpn.xwiki.XWiki.parseTemplate(XWiki.java:1710) at com.xpn.xwiki.XWiki.parseTemplate(XWiki.java:1631) at com.xpn.xwiki.api.XWiki.parseTemplate(XWiki.java:657) at sun.reflect.GeneratedMethodAccessor86.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke(UberspectImpl.java:389) at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:378) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:270) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:252) at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:332) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) at org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:212) at org.apache.velocity.runtime.directive.RuntimeMacro.render(RuntimeMacro.java:247) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:175) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:87) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:336) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:106) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:336) at org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:191) at org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:156) at com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:116) at com.xpn.xwiki.XWiki.parseTemplate(XWiki.java:1710) at com.xpn.xwiki.XWiki.parseTemplate(XWiki.java:1631) at com.xpn.xwiki.web.Utils.parseTemplate(Utils.java:123) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:224) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:115) 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.doPost(ActionServlet.java:432) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166) at com.xpn.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:152) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:117) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:68) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at com.xpn.xwiki.web.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:295) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:536) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:930) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) Caused by: net.sf.jodconverter.office.OfficeException: could not complete task at net.sf.jodconverter.office.ManagedProcessOfficeManager.execute(ManagedProcessOfficeManager.java:95) at net.sf.jodconverter.OfficeDocumentConverter.convert(OfficeDocumentConverter.java:71) at org.xwiki.officeimporter.internal.openoffice.DefaultOpenOfficeDocumentConverter.convert(DefaultOpenOfficeDocu mentConverter.java:178) ... 111 more Caused by: java.util.concurrent.ExecutionException: java.lang.reflect.UndeclaredThrowableException at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source) at java.util.concurrent.FutureTask.get(Unknown Source) at net.sf.jodconverter.office.ManagedProcessOfficeManager.execute(ManagedProcessOfficeManager.java:90) ... 113 more Caused by: java.lang.reflect.UndeclaredThrowableException at $Proxy33.loadComponentFromURL(Unknown Source) at net.sf.jodconverter.AbstractConversionTask.execute(AbstractConversionTask.java:58) at net.sf.jodconverter.office.ManagedProcessOfficeManager$2.run(ManagedProcessOfficeManager.java:85) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: com.sun.star.loader.CannotActivateFactoryException: loading component library failed: file:///C:/Program%20Fi les/OpenOffice.org%203/program/../Basis/program/i18npool.uno.dll at com.sun.star.lib.uno.environments.remote.Job.remoteUnoRequestRaisedException(Job.java:182) at com.sun.star.lib.uno.environments.remote.Job.execute(Job.java:148) at com.sun.star.lib.uno.environments.remote.JobQueue.enter(JobQueue.java:344) at com.sun.star.lib.uno.environments.remote.JobQueue.enter(JobQueue.java:313) at com.sun.star.lib.uno.environments.remote.JavaThreadPool.enter(JavaThreadPool.java:101) at com.sun.star.lib.uno.bridges.java_remote.java_remote_bridge.sendRequest(java_remote_bridge.java:652) at com.sun.star.lib.uno.bridges.java_remote.ProxyFactory$Handler.request(ProxyFactory.java:154) at com.sun.star.lib.uno.bridges.java_remote.ProxyFactory$Handler.invoke(ProxyFactory.java:136) ... 9 more I have checked that i18npool.uno.dll is on my system and it is at the specified path. So how can I fix my problem ? Thanks Simon Glet -- View this message in context: http://n2.nabble.com/Office-import-error-tp4537228p4537228.html Sent from the XWiki- Users mailing list archive at Nabble.com.
Hi, As you have understood it seems the problem is with your OOo installation. Can you try removing your existing OOo installation and installing the latest version from http://www.openoffice.org? This will most probably fix the issue. - Asiri
Hi Asiri, I currently use the latest version of OO (3.1.1 Build 9420). What else can I check ? Thanks Simon Glet On Mon, Feb 8, 2010 at 9:20 PM, Asiri Rathnayake <[email protected]> wrote:
Hi,
As you have understood it seems the problem is with your OOo installation. Can you try removing your existing OOo installation and installing the latest version from http://www.openoffice.org? This will most probably fix the issue.
- Asiri _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Hi, On Tue, Feb 9, 2010 at 7:16 PM, Simon Glet <[email protected]> wrote:
Hi Asiri,
I currently use the latest version of OO (3.1.1 Build 9420). What else can I check ?
Well, you can try un-installing openoffice and reinstalling. But I doubt this will help. Next thing you can try is use jodconverter directly and try to convert your document from odt to html. Here is the link: http://code.google.com/p/jodconverter/ How to use it: http://code.google.com/p/jodconverter/wiki/GettingStarted If the command-line conversion fails for your document, then the error should probably be reported to jodconverter users list. Thanks. - Asiri
Thanks Simon Glet
On Mon, Feb 8, 2010 at 9:20 PM, Asiri Rathnayake <[email protected]> wrote:
Hi,
As you have understood it seems the problem is with your OOo installation. Can you try removing your existing OOo installation and installing the latest version from http://www.openoffice.org? This will most probably fix the issue.
- Asiri _______________________________________________ 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 Asiri, I am a little confused by the quality of XWiki 2.1.1. At this point I find that there are many features that don't work properly or at all : - Office plugin (the office 2007 ribbon has a very buggy behavior) - Document import (There is no documentation about version compatibility between the different elements) - Usage with SQL Server 2005 is impossible. Works fine with PostgreSQL though. I can't continue testing such a product. To bad, it looked very good. Best Regards Simon Glet On Tue, Feb 9, 2010 at 12:15 PM, Asiri Rathnayake <[email protected]> wrote:
Hi,
On Tue, Feb 9, 2010 at 7:16 PM, Simon Glet <[email protected]> wrote:
Hi Asiri,
I currently use the latest version of OO (3.1.1 Build 9420). What else can I check ?
Well, you can try un-installing openoffice and reinstalling. But I doubt this will help.
Next thing you can try is use jodconverter directly and try to convert your document from odt to html.
Here is the link:
http://code.google.com/p/jodconverter/
How to use it:
http://code.google.com/p/jodconverter/wiki/GettingStarted
If the command-line conversion fails for your document, then the error should probably be reported to jodconverter users list.
Thanks.
- Asiri
Thanks Simon Glet
On Mon, Feb 8, 2010 at 9:20 PM, Asiri Rathnayake <[email protected]> wrote:
Hi,
As you have understood it seems the problem is with your OOo installation. Can you try removing your existing OOo installation and installing the latest version from http://www.openoffice.org? This will most probably fix the issue.
- Asiri _______________________________________________ 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 Simon, On Tue, Feb 9, 2010 at 7:08 PM, Simon Glet <[email protected]> wrote:
Hi Asiri,
I am a little confused by the quality of XWiki 2.1.1. At this point I find that there are many features that don't work properly or at all :
I'm sorry to hear that. I'm pretty sure that if you're ready to spend a bit more time on this we can help you overcome the issues you're facing and help make XWiki a better product as a result. Open-Source software such as XWiki improves thanks to the feedback of its users and you can help us make more useful to the community. - Office plugin (the office 2007 ribbon has a very buggy behavior)
Would you be ok to describe the problems you're experiencing in more detail and post screenshots and / or steps to reproduce on http://jira.xwiki.org/ ? I'm sure that Florin, the lead developer on XOffice, would be happy to help you make things work.
- Document import (There is no documentation about version compatibility between the different elements)
I have to agree that documentation isn't one of XWiki's strongest assets. However I've been using the document import feature on several XE 2.1.1 instances where it works just fine thus I'm pretty sure you can make it work too. Asiri suggested several steps to debug, have you tried following them?
- Usage with SQL Server 2005 is impossible. Works fine with PostgreSQL though.
Is SQL Server 2005 a hard requirement? Which errors do you meet? Would you agree to report those errors on http://jira.xwiki.org/ ? Do you need XWiki to work with a product released 5 years ago that much? What's not enough it works fine with PostgreSQL? I can't continue testing such a product. To bad, it looked very good.
It is and your feedback could help us make it that much better. I'd be very happy if you were to agree to reconsider your current stance and give a little of your time to the community in order to help us make XWiki fit your needs. Guillaume
Best Regards Simon Glet
On Tue, Feb 9, 2010 at 12:15 PM, Asiri Rathnayake <[email protected]> wrote:
Hi,
On Tue, Feb 9, 2010 at 7:16 PM, Simon Glet <[email protected]> wrote:
Hi Asiri,
I currently use the latest version of OO (3.1.1 Build 9420). What else can I check ?
Well, you can try un-installing openoffice and reinstalling. But I doubt this will help.
Next thing you can try is use jodconverter directly and try to convert your document from odt to html.
Here is the link:
http://code.google.com/p/jodconverter/
How to use it:
http://code.google.com/p/jodconverter/wiki/GettingStarted
If the command-line conversion fails for your document, then the error should probably be reported to jodconverter users list.
Thanks.
- Asiri
Thanks Simon Glet
On Mon, Feb 8, 2010 at 9:20 PM, Asiri Rathnayake <[email protected]> wrote:
Hi,
As you have understood it seems the problem is with your OOo installation. Can you try removing your existing OOo installation and installing the latest version from http://www.openoffice.org? This will most
probably
fix
the issue.
- Asiri _______________________________________________ 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
-- Guillaume Lerouge Product Manager - XWiki SAS Skype: wikibc Twitter: glerouge http://guillaumelerouge.com/
Hi, On Wed, Feb 10, 2010 at 1:06 AM, Guillaume Lerouge <[email protected]>wrote:
Hi Simon,
On Tue, Feb 9, 2010 at 7:08 PM, Simon Glet <[email protected]> wrote:
Hi Asiri,
I am a little confused by the quality of XWiki 2.1.1. At this point I find that there are many features that don't work properly or at all :
I'm sorry to hear that. I'm pretty sure that if you're ready to spend a bit more time on this we can help you overcome the issues you're facing and help make XWiki a better product as a result. Open-Source software such as XWiki improves thanks to the feedback of its users and you can help us make more useful to the community.
- Office plugin (the office 2007 ribbon has a very buggy behavior)
Would you be ok to describe the problems you're experiencing in more detail and post screenshots and / or steps to reproduce on http://jira.xwiki.org/? I'm sure that Florin, the lead developer on XOffice, would be happy to help you make things work.
- Document import (There is no documentation about version compatibility between the different elements)
I have to agree that documentation isn't one of XWiki's strongest assets. However I've been using the document import feature on several XE 2.1.1 instances where it works just fine thus I'm pretty sure you can make it work too. Asiri suggested several steps to debug, have you tried following them?
- Usage with SQL Server 2005 is impossible. Works fine with PostgreSQL though.
Is SQL Server 2005 a hard requirement? Which errors do you meet? Would you agree to report those errors on http://jira.xwiki.org/ ? Do you need XWiki to work with a product released 5 years ago that much? What's not enough it works fine with PostgreSQL?
I can't continue testing such a product. To bad, it looked very good.
It is and your feedback could help us make it that much better. I'd be very happy if you were to agree to reconsider your current stance and give a little of your time to the community in order to help us make XWiki fit your needs.
+ XWiki SAS <http://www.xwiki.com> offers support and hosting packages to meet all your XWiki needs. This will also benefit the XWiki opensource project :) - Asiri
+ XWiki SAS <http://www.xwiki.com> offers support and hosting packages to meet all your XWiki needs. This will also benefit the XWiki opensource project :)
- Asiri
Asiri : With such a statement, one might think that it is difficult to setup in order to need commercial support :-) Guillaume : As much as I agree that user feedback is crucial to a project's quality, 2.1.1 is a production release not a rc or beta so such problems should not occur. As we are looking for an immediate usage, I can't see myself going to management with such visible features not working. Nevertheless, in the next few days I will document the encountered problems on your bug tracking system. Best Regards Simon Glet On Tue, Feb 9, 2010 at 3:21 PM, Asiri Rathnayake <[email protected]> wrote:
Hi,
On Wed, Feb 10, 2010 at 1:06 AM, Guillaume Lerouge <[email protected]>wrote:
Hi Simon,
On Tue, Feb 9, 2010 at 7:08 PM, Simon Glet <[email protected]> wrote:
Hi Asiri,
I am a little confused by the quality of XWiki 2.1.1. At this point I find that there are many features that don't work properly or at all :
I'm sorry to hear that. I'm pretty sure that if you're ready to spend a bit more time on this we can help you overcome the issues you're facing and help make XWiki a better product as a result. Open-Source software such as XWiki improves thanks to the feedback of its users and you can help us make more useful to the community.
- Office plugin (the office 2007 ribbon has a very buggy behavior)
Would you be ok to describe the problems you're experiencing in more detail and post screenshots and / or steps to reproduce on http://jira.xwiki.org/? I'm sure that Florin, the lead developer on XOffice, would be happy to help you make things work.
- Document import (There is no documentation about version compatibility between the different elements)
I have to agree that documentation isn't one of XWiki's strongest assets. However I've been using the document import feature on several XE 2.1.1 instances where it works just fine thus I'm pretty sure you can make it work too. Asiri suggested several steps to debug, have you tried following them?
- Usage with SQL Server 2005 is impossible. Works fine with PostgreSQL though.
Is SQL Server 2005 a hard requirement? Which errors do you meet? Would you agree to report those errors on http://jira.xwiki.org/ ? Do you need XWiki to work with a product released 5 years ago that much? What's not enough it works fine with PostgreSQL?
I can't continue testing such a product. To bad, it looked very good.
It is and your feedback could help us make it that much better. I'd be very happy if you were to agree to reconsider your current stance and give a little of your time to the community in order to help us make XWiki fit your needs.
+ XWiki SAS <http://www.xwiki.com> offers support and hosting packages to meet all your XWiki needs. This will also benefit the XWiki opensource project :)
- Asiri _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Hi Simon, On Tue, Feb 9, 2010 at 9:50 PM, Simon Glet <[email protected]> wrote:
+ XWiki SAS <http://www.xwiki.com> offers support and hosting packages to meet all your XWiki needs. This will also benefit the XWiki opensource project :)
- Asiri
Asiri : With such a statement, one might think that it is difficult to setup in order to need commercial support :-)
Indeed :-) We actually never voluntarily made XWiki complicated to use, which is a nice testimonial to our Open-Source commitment while at the same time an acknowledgement of our current QA & usability flaws. Guillaume :
As much as I agree that user feedback is crucial to a project's quality, 2.1.1 is a production release not a rc or beta so such problems should not occur. As we are looking for an immediate usage, I can't see myself going to management with such visible features not working. Nevertheless, in the next few days I will document the encountered problems on your bug tracking system.
I see. Indeed, given your short deployment timeframe recommending XWiki would be a bit risky. When do you plan to put your new collaboration solution in production? Anyway, thanks for taking the time to provide us with your feedback, I'm looking forward to your additions to JIRA. I'd be interested in knowing which piece of software you'll be using instead of XWiki and which feature made you choose it instead of XWiki (besides the issues listed above obviously). Guillaume Best Regards
Simon Glet
On Tue, Feb 9, 2010 at 3:21 PM, Asiri Rathnayake <[email protected]> wrote:
Hi,
On Wed, Feb 10, 2010 at 1:06 AM, Guillaume Lerouge <[email protected] wrote:
Hi Simon,
On Tue, Feb 9, 2010 at 7:08 PM, Simon Glet <[email protected]> wrote:
Hi Asiri,
I am a little confused by the quality of XWiki 2.1.1. At this point I find that there are many features that don't work properly or at all :
I'm sorry to hear that. I'm pretty sure that if you're ready to spend a bit more time on this we can help you overcome the issues you're facing and help make XWiki a better product as a result. Open-Source software such as XWiki improves thanks to the feedback of its users and you can help us make more useful to the community.
- Office plugin (the office 2007 ribbon has a very buggy behavior)
Would you be ok to describe the problems you're experiencing in more detail and post screenshots and / or steps to reproduce on http://jira.xwiki.org/? I'm sure that Florin, the lead developer on XOffice, would be happy to help you make things work.
- Document import (There is no documentation about version compatibility between the different elements)
I have to agree that documentation isn't one of XWiki's strongest assets. However I've been using the document import feature on several XE 2.1.1 instances where it works just fine thus I'm pretty sure you can make it work too. Asiri suggested several steps to debug, have you tried following them?
- Usage with SQL Server 2005 is impossible. Works fine with PostgreSQL though.
Is SQL Server 2005 a hard requirement? Which errors do you meet? Would you agree to report those errors on http://jira.xwiki.org/ ? Do you need XWiki to work with a product released 5 years ago that much? What's not enough it works fine with PostgreSQL?
I can't continue testing such a product. To bad, it looked very good.
It is and your feedback could help us make it that much better. I'd be very happy if you were to agree to reconsider your current stance and give a little of your time to the community in order to help us make XWiki fit your needs.
+ XWiki SAS <http://www.xwiki.com> offers support and hosting packages to meet all your XWiki needs. This will also benefit the XWiki opensource project :)
- Asiri _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Guillaume Lerouge Product Manager - XWiki SAS Skype: wikibc Twitter: glerouge http://guillaumelerouge.com/
Hi, On Wed, Feb 10, 2010 at 2:20 AM, Simon Glet <[email protected]> wrote:
+ XWiki SAS <http://www.xwiki.com> offers support and hosting packages to meet all your XWiki needs. This will also benefit the XWiki opensource project :)
- Asiri
Asiri : With such a statement, one might think that it is difficult to setup in order to need commercial support :-)
There is a huge number of XWiki deployments around the web and within organizations. Therefor, I had to assume that here the problem is you are unable to configure XWiki correctly so that it works as expected. This is why I suggested you get some support :) - Asiri
Hi Simon, On 2/9/2010 8:08 PM, Simon Glet wrote:
Hi Asiri,
I am a little confused by the quality of XWiki 2.1.1. At this point I find that there are many features that don't work properly or at all :
- Office plugin (the office 2007 ribbon has a very buggy behavior)
You are probably using a french version of Windows. I know XOffice it's generally buggy on it, but I need more info in order to fix it. Re: Your french accents issue is now fixed. Please wait for the next update or release in order to have it working. Florin Ciubotaru
- Document import (There is no documentation about version compatibility between the different elements) - Usage with SQL Server 2005 is impossible. Works fine with PostgreSQL though.
I can't continue testing such a product. To bad, it looked very good.
Best Regards Simon Glet
On Tue, Feb 9, 2010 at 12:15 PM, Asiri Rathnayake <[email protected]> wrote:
Hi,
On Tue, Feb 9, 2010 at 7:16 PM, Simon Glet<[email protected]> wrote:
Hi Asiri,
I currently use the latest version of OO (3.1.1 Build 9420). What else can I check ?
Well, you can try un-installing openoffice and reinstalling. But I doubt this will help.
Next thing you can try is use jodconverter directly and try to convert your document from odt to html.
Here is the link:
http://code.google.com/p/jodconverter/
How to use it:
http://code.google.com/p/jodconverter/wiki/GettingStarted
If the command-line conversion fails for your document, then the error should probably be reported to jodconverter users list.
Thanks.
- Asiri
Thanks Simon Glet
On Mon, Feb 8, 2010 at 9:20 PM, Asiri Rathnayake <[email protected]> wrote:
Hi,
As you have understood it seems the problem is with your OOo
installation.
Can you try removing your existing OOo installation and installing the latest version from http://www.openoffice.org? This will most probably
fix
the issue.
- Asiri _______________________________________________ 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 Florin, I have checked the latest version and french accents work well. I might add that the fix was done very quickly. My Windows XP regional setting is set to English-Ca, all my applications are in english but we communicate in french ;-). In the next few days, I will reinstall XWiki with the latest XOffice plugin and document the problems on your tracking system. Best Regards Simon Glet On Wed, Feb 10, 2010 at 3:42 AM, Florin Ciubotaru <[email protected]> wrote:
Hi Simon,
On 2/9/2010 8:08 PM, Simon Glet wrote:
Hi Asiri,
I am a little confused by the quality of XWiki 2.1.1. At this point I find that there are many features that don't work properly or at all :
- Office plugin (the office 2007 ribbon has a very buggy behavior)
You are probably using a french version of Windows. I know XOffice it's generally buggy on it, but I need more info in order to fix it. Re: Your french accents issue is now fixed. Please wait for the next update or release in order to have it working.
Florin Ciubotaru
- Document import (There is no documentation about version compatibility between the different elements) - Usage with SQL Server 2005 is impossible. Works fine with PostgreSQL though.
I can't continue testing such a product. To bad, it looked very good.
Best Regards Simon Glet
On Tue, Feb 9, 2010 at 12:15 PM, Asiri Rathnayake <[email protected]> wrote:
Hi,
On Tue, Feb 9, 2010 at 7:16 PM, Simon Glet<[email protected]> wrote:
Hi Asiri,
I currently use the latest version of OO (3.1.1 Build 9420). What else can I check ?
Well, you can try un-installing openoffice and reinstalling. But I doubt this will help.
Next thing you can try is use jodconverter directly and try to convert your document from odt to html.
Here is the link:
http://code.google.com/p/jodconverter/
How to use it:
http://code.google.com/p/jodconverter/wiki/GettingStarted
If the command-line conversion fails for your document, then the error should probably be reported to jodconverter users list.
Thanks.
- Asiri
Thanks Simon Glet
On Mon, Feb 8, 2010 at 9:20 PM, Asiri Rathnayake <[email protected]> wrote:
Hi,
As you have understood it seems the problem is with your OOo
installation.
Can you try removing your existing OOo installation and installing the latest version from http://www.openoffice.org? This will most probably
fix
the issue.
- Asiri _______________________________________________ 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
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Hi Simon, Some words from a long-time user of XWiki ... I think the issues you encountered might be linked also to the fact that these features rely on external tools (oo, ms office...), and also they are quite "recent" in xwiki history. So for sure, all integration issues might not have been encountered / fixed already. Of course if you need mainly these features, it might be a problem, but with some fixes there is no reason they won't work. For the rest, I must say that on the other side, and even with some (known) flaws, xwiki is not comparable to other wikis I know. No one offers such liberty and customization possibilities. I use it for some years now at work (since v0.9) and migrated regularly to last versions, and progression is incredible, in terms of features and usability. A good basis is now in place, and I think not much is needed to have a nearly perfect tool :) But, again, this tool might need some involvement in order to get its best, even if it's more and more "plug & play". I'll take an example, in my office we use a specific configuration management tool very uncommon, and that is integrated with nothing else. In wiki I could very easily create some macros to help users create links on various sources, reports and such in this scm tool. The wysiwyg editor works really well now, and the new macro displays in a dialog with parameters I defined, though I didn't code anything for the display. This is really helpful and really easy to put in place. I don't know much other tools, but I don't think you can do this kind of thing so easily... For now I did not install oO server for office import though, but I plan to. Best regards, Jeremie 2010/2/9 Simon Glet <[email protected]>
Hi Asiri,
I am a little confused by the quality of XWiki 2.1.1. At this point I find that there are many features that don't work properly or at all :
- Office plugin (the office 2007 ribbon has a very buggy behavior) - Document import (There is no documentation about version compatibility between the different elements) - Usage with SQL Server 2005 is impossible. Works fine with PostgreSQL though.
I can't continue testing such a product. To bad, it looked very good.
Best Regards Simon Glet
On Tue, Feb 9, 2010 at 12:15 PM, Asiri Rathnayake <[email protected]> wrote:
Hi,
On Tue, Feb 9, 2010 at 7:16 PM, Simon Glet <[email protected]> wrote:
Hi Asiri,
I currently use the latest version of OO (3.1.1 Build 9420). What else can I check ?
Well, you can try un-installing openoffice and reinstalling. But I doubt this will help.
Next thing you can try is use jodconverter directly and try to convert your document from odt to html.
Here is the link:
http://code.google.com/p/jodconverter/
How to use it:
http://code.google.com/p/jodconverter/wiki/GettingStarted
If the command-line conversion fails for your document, then the error should probably be reported to jodconverter users list.
Thanks.
- Asiri
Thanks Simon Glet
On Mon, Feb 8, 2010 at 9:20 PM, Asiri Rathnayake <[email protected]> wrote:
Hi,
As you have understood it seems the problem is with your OOo installation. Can you try removing your existing OOo installation and installing the latest version from http://www.openoffice.org? This will most
probably
fix
the issue.
- Asiri _______________________________________________ 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
Jeremie, I see your point but I wasn't expecting that much involvement ;-) BTW, as you speak of customization, I was wondering how to hide the "Import Office Document" menu. By not offering the option, users will not get frustrated and would more easily accept the system. Thanks Simon Glet On Wed, Feb 10, 2010 at 4:56 AM, Jeremie BOUSQUET <[email protected]> wrote:
Hi Simon,
Some words from a long-time user of XWiki ...
I think the issues you encountered might be linked also to the fact that these features rely on external tools (oo, ms office...), and also they are quite "recent" in xwiki history. So for sure, all integration issues might not have been encountered / fixed already. Of course if you need mainly these features, it might be a problem, but with some fixes there is no reason they won't work.
For the rest, I must say that on the other side, and even with some (known) flaws, xwiki is not comparable to other wikis I know. No one offers such liberty and customization possibilities. I use it for some years now at work (since v0.9) and migrated regularly to last versions, and progression is incredible, in terms of features and usability. A good basis is now in place, and I think not much is needed to have a nearly perfect tool :) But, again, this tool might need some involvement in order to get its best, even if it's more and more "plug & play".
I'll take an example, in my office we use a specific configuration management tool very uncommon, and that is integrated with nothing else. In wiki I could very easily create some macros to help users create links on various sources, reports and such in this scm tool. The wysiwyg editor works really well now, and the new macro displays in a dialog with parameters I defined, though I didn't code anything for the display. This is really helpful and really easy to put in place. I don't know much other tools, but I don't think you can do this kind of thing so easily... For now I did not install oO server for office import though, but I plan to.
Best regards, Jeremie
2010/2/9 Simon Glet <[email protected]>
Hi Asiri,
I am a little confused by the quality of XWiki 2.1.1. At this point I find that there are many features that don't work properly or at all :
- Office plugin (the office 2007 ribbon has a very buggy behavior) - Document import (There is no documentation about version compatibility between the different elements) - Usage with SQL Server 2005 is impossible. Works fine with PostgreSQL though.
I can't continue testing such a product. To bad, it looked very good.
Best Regards Simon Glet
On Tue, Feb 9, 2010 at 12:15 PM, Asiri Rathnayake <[email protected]> wrote:
Hi,
On Tue, Feb 9, 2010 at 7:16 PM, Simon Glet <[email protected]> wrote:
Hi Asiri,
I currently use the latest version of OO (3.1.1 Build 9420). What else can I check ?
Well, you can try un-installing openoffice and reinstalling. But I doubt this will help.
Next thing you can try is use jodconverter directly and try to convert your document from odt to html.
Here is the link:
http://code.google.com/p/jodconverter/
How to use it:
http://code.google.com/p/jodconverter/wiki/GettingStarted
If the command-line conversion fails for your document, then the error should probably be reported to jodconverter users list.
Thanks.
- Asiri
Thanks Simon Glet
On Mon, Feb 8, 2010 at 9:20 PM, Asiri Rathnayake <[email protected]> wrote:
Hi,
As you have understood it seems the problem is with your OOo installation. Can you try removing your existing OOo installation and installing the latest version from http://www.openoffice.org? This will most
probably
fix
the issue.
- Asiri _______________________________________________ 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
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Hi, On Wed, Feb 10, 2010 at 10:00 PM, Simon Glet <[email protected]> wrote:
Jeremie,
I see your point but I wasn't expecting that much involvement ;-) BTW, as you speak of customization, I was wondering how to hide the "Import Office Document" menu. By not offering the option, users will not get frustrated and would more easily accept the system.
We are still working on an application manager that allows you to install / uninstall whole apps. But for the moment you can delete XWiki.OfficeImporter page and the menu item will dissapear. - Asiri
On Feb 10, 2010, at 5:30 PM, Simon Glet wrote:
Jeremie,
I see your point but I wasn't expecting that much involvement ;-) BTW, as you speak of customization, I was wondering how to hide the "Import Office Document" menu. By not offering the option, users will not get frustrated and would more easily accept the system.
With the latest XE version (2.2RC1 or even better 2.2RC2 being released right now, will be avail in 2-3 hours) if the office importer page (XWiki.OfficeImporter) is not present the menu item will not be shown. So you can rename that page or delete it (you'd then need to reimport the officeimporter XAR later on if you want it again in this case). Of course you can also customize the menu vm files to define the rules you want. Thanks -Vincent
Thanks Simon Glet
On Wed, Feb 10, 2010 at 4:56 AM, Jeremie BOUSQUET <[email protected]> wrote:
Hi Simon,
Some words from a long-time user of XWiki ...
I think the issues you encountered might be linked also to the fact that these features rely on external tools (oo, ms office...), and also they are quite "recent" in xwiki history. So for sure, all integration issues might not have been encountered / fixed already. Of course if you need mainly these features, it might be a problem, but with some fixes there is no reason they won't work.
For the rest, I must say that on the other side, and even with some (known) flaws, xwiki is not comparable to other wikis I know. No one offers such liberty and customization possibilities. I use it for some years now at work (since v0.9) and migrated regularly to last versions, and progression is incredible, in terms of features and usability. A good basis is now in place, and I think not much is needed to have a nearly perfect tool :) But, again, this tool might need some involvement in order to get its best, even if it's more and more "plug & play".
I'll take an example, in my office we use a specific configuration management tool very uncommon, and that is integrated with nothing else. In wiki I could very easily create some macros to help users create links on various sources, reports and such in this scm tool. The wysiwyg editor works really well now, and the new macro displays in a dialog with parameters I defined, though I didn't code anything for the display. This is really helpful and really easy to put in place. I don't know much other tools, but I don't think you can do this kind of thing so easily... For now I did not install oO server for office import though, but I plan to.
Best regards, Jeremie
2010/2/9 Simon Glet <[email protected]>
Hi Asiri,
I am a little confused by the quality of XWiki 2.1.1. At this point I find that there are many features that don't work properly or at all :
- Office plugin (the office 2007 ribbon has a very buggy behavior) - Document import (There is no documentation about version compatibility between the different elements) - Usage with SQL Server 2005 is impossible. Works fine with PostgreSQL though.
I can't continue testing such a product. To bad, it looked very good.
Best Regards Simon Glet
On Tue, Feb 9, 2010 at 12:15 PM, Asiri Rathnayake <[email protected]> wrote:
Hi,
On Tue, Feb 9, 2010 at 7:16 PM, Simon Glet <[email protected]> wrote:
Hi Asiri,
I currently use the latest version of OO (3.1.1 Build 9420). What else can I check ?
Well, you can try un-installing openoffice and reinstalling. But I doubt this will help.
Next thing you can try is use jodconverter directly and try to convert your document from odt to html.
Here is the link:
http://code.google.com/p/jodconverter/
How to use it:
http://code.google.com/p/jodconverter/wiki/GettingStarted
If the command-line conversion fails for your document, then the error should probably be reported to jodconverter users list.
Thanks.
- Asiri
Thanks Simon Glet
On Mon, Feb 8, 2010 at 9:20 PM, Asiri Rathnayake <[email protected]> wrote:
Hi,
As you have understood it seems the problem is with your OOo installation. Can you try removing your existing OOo installation and installing the latest version from http://www.openoffice.org? This will most
probably
fix
the issue.
- Asiri
Wow that was fast ! Thanks to Asiri and Vincent. Simon Glet On Wed, Feb 10, 2010 at 11:36 AM, Vincent Massol <[email protected]> wrote:
On Feb 10, 2010, at 5:30 PM, Simon Glet wrote:
Jeremie,
I see your point but I wasn't expecting that much involvement ;-) BTW, as you speak of customization, I was wondering how to hide the "Import Office Document" menu. By not offering the option, users will not get frustrated and would more easily accept the system.
With the latest XE version (2.2RC1 or even better 2.2RC2 being released right now, will be avail in 2-3 hours) if the office importer page (XWiki.OfficeImporter) is not present the menu item will not be shown. So you can rename that page or delete it (you'd then need to reimport the officeimporter XAR later on if you want it again in this case).
Of course you can also customize the menu vm files to define the rules you want.
Thanks -Vincent
Thanks Simon Glet
On Wed, Feb 10, 2010 at 4:56 AM, Jeremie BOUSQUET <[email protected]> wrote:
Hi Simon,
Some words from a long-time user of XWiki ...
I think the issues you encountered might be linked also to the fact that these features rely on external tools (oo, ms office...), and also they are quite "recent" in xwiki history. So for sure, all integration issues might not have been encountered / fixed already. Of course if you need mainly these features, it might be a problem, but with some fixes there is no reason they won't work.
For the rest, I must say that on the other side, and even with some (known) flaws, xwiki is not comparable to other wikis I know. No one offers such liberty and customization possibilities. I use it for some years now at work (since v0.9) and migrated regularly to last versions, and progression is incredible, in terms of features and usability. A good basis is now in place, and I think not much is needed to have a nearly perfect tool :) But, again, this tool might need some involvement in order to get its best, even if it's more and more "plug & play".
I'll take an example, in my office we use a specific configuration management tool very uncommon, and that is integrated with nothing else. In wiki I could very easily create some macros to help users create links on various sources, reports and such in this scm tool. The wysiwyg editor works really well now, and the new macro displays in a dialog with parameters I defined, though I didn't code anything for the display. This is really helpful and really easy to put in place. I don't know much other tools, but I don't think you can do this kind of thing so easily... For now I did not install oO server for office import though, but I plan to.
Best regards, Jeremie
2010/2/9 Simon Glet <[email protected]>
Hi Asiri,
I am a little confused by the quality of XWiki 2.1.1. At this point I find that there are many features that don't work properly or at all :
- Office plugin (the office 2007 ribbon has a very buggy behavior) - Document import (There is no documentation about version compatibility between the different elements) - Usage with SQL Server 2005 is impossible. Works fine with PostgreSQL though.
I can't continue testing such a product. To bad, it looked very good.
Best Regards Simon Glet
On Tue, Feb 9, 2010 at 12:15 PM, Asiri Rathnayake <[email protected]> wrote:
Hi,
On Tue, Feb 9, 2010 at 7:16 PM, Simon Glet <[email protected]> wrote:
Hi Asiri,
I currently use the latest version of OO (3.1.1 Build 9420). What else can I check ?
Well, you can try un-installing openoffice and reinstalling. But I doubt this will help.
Next thing you can try is use jodconverter directly and try to convert your document from odt to html.
Here is the link:
http://code.google.com/p/jodconverter/
How to use it:
http://code.google.com/p/jodconverter/wiki/GettingStarted
If the command-line conversion fails for your document, then the error should probably be reported to jodconverter users list.
Thanks.
- Asiri
Thanks Simon Glet
On Mon, Feb 8, 2010 at 9:20 PM, Asiri Rathnayake <[email protected]> wrote: > Hi, > > As you have understood it seems the problem is with your OOo installation. > Can you try removing your existing OOo installation and installing the > latest version from http://www.openoffice.org? This will most
probably
fix > the issue. > > - Asiri
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Hi, Just to end this thread, I upgraded to OpenOffice 3.2.0 from 3.1.1 and after creating the missing directory (http://jira.xwiki.org/jira/browse/XAOFFICE-44), import-export works fine. Great !!! Best Regards Simon Glet On Wed, Feb 10, 2010 at 11:40 AM, Simon Glet <[email protected]> wrote:
Wow that was fast !
Thanks to Asiri and Vincent. Simon Glet
On Wed, Feb 10, 2010 at 11:36 AM, Vincent Massol <[email protected]> wrote:
On Feb 10, 2010, at 5:30 PM, Simon Glet wrote:
Jeremie,
I see your point but I wasn't expecting that much involvement ;-) BTW, as you speak of customization, I was wondering how to hide the "Import Office Document" menu. By not offering the option, users will not get frustrated and would more easily accept the system.
With the latest XE version (2.2RC1 or even better 2.2RC2 being released right now, will be avail in 2-3 hours) if the office importer page (XWiki.OfficeImporter) is not present the menu item will not be shown. So you can rename that page or delete it (you'd then need to reimport the officeimporter XAR later on if you want it again in this case).
Of course you can also customize the menu vm files to define the rules you want.
Thanks -Vincent
Thanks Simon Glet
On Wed, Feb 10, 2010 at 4:56 AM, Jeremie BOUSQUET <[email protected]> wrote:
Hi Simon,
Some words from a long-time user of XWiki ...
I think the issues you encountered might be linked also to the fact that these features rely on external tools (oo, ms office...), and also they are quite "recent" in xwiki history. So for sure, all integration issues might not have been encountered / fixed already. Of course if you need mainly these features, it might be a problem, but with some fixes there is no reason they won't work.
For the rest, I must say that on the other side, and even with some (known) flaws, xwiki is not comparable to other wikis I know. No one offers such liberty and customization possibilities. I use it for some years now at work (since v0.9) and migrated regularly to last versions, and progression is incredible, in terms of features and usability. A good basis is now in place, and I think not much is needed to have a nearly perfect tool :) But, again, this tool might need some involvement in order to get its best, even if it's more and more "plug & play".
I'll take an example, in my office we use a specific configuration management tool very uncommon, and that is integrated with nothing else. In wiki I could very easily create some macros to help users create links on various sources, reports and such in this scm tool. The wysiwyg editor works really well now, and the new macro displays in a dialog with parameters I defined, though I didn't code anything for the display. This is really helpful and really easy to put in place. I don't know much other tools, but I don't think you can do this kind of thing so easily... For now I did not install oO server for office import though, but I plan to.
Best regards, Jeremie
2010/2/9 Simon Glet <[email protected]>
Hi Asiri,
I am a little confused by the quality of XWiki 2.1.1. At this point I find that there are many features that don't work properly or at all :
- Office plugin (the office 2007 ribbon has a very buggy behavior) - Document import (There is no documentation about version compatibility between the different elements) - Usage with SQL Server 2005 is impossible. Works fine with PostgreSQL though.
I can't continue testing such a product. To bad, it looked very good.
Best Regards Simon Glet
On Tue, Feb 9, 2010 at 12:15 PM, Asiri Rathnayake <[email protected]> wrote:
Hi,
On Tue, Feb 9, 2010 at 7:16 PM, Simon Glet <[email protected]> wrote:
> Hi Asiri, > > I currently use the latest version of OO (3.1.1 Build 9420). What else > can I check ? >
Well, you can try un-installing openoffice and reinstalling. But I doubt this will help.
Next thing you can try is use jodconverter directly and try to convert your document from odt to html.
Here is the link:
http://code.google.com/p/jodconverter/
How to use it:
http://code.google.com/p/jodconverter/wiki/GettingStarted
If the command-line conversion fails for your document, then the error should probably be reported to jodconverter users list.
Thanks.
- Asiri
> > Thanks > Simon Glet > > On Mon, Feb 8, 2010 at 9:20 PM, Asiri Rathnayake > <[email protected]> wrote: >> Hi, >> >> As you have understood it seems the problem is with your OOo > installation. >> Can you try removing your existing OOo installation and installing the >> latest version from http://www.openoffice.org? This will most probably > fix >> the issue. >> >> - Asiri
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
Hi Simon, On Fri, Feb 12, 2010 at 3:36 PM, Simon Glet <[email protected]> wrote:
Hi,
Just to end this thread, I upgraded to OpenOffice 3.2.0 from 3.1.1 and after creating the missing directory (http://jira.xwiki.org/jira/browse/XAOFFICE-44), import-export works fine. Great !!!
Glad to see you stick with XWiki long enough to put the effort needed to make things work fine... Now you'll be rewarded for your patience ;-) Looking forward to more useful feedback about XWiki, Guillaume
Best Regards Simon Glet
On Wed, Feb 10, 2010 at 11:40 AM, Simon Glet <[email protected]> wrote:
Wow that was fast !
Thanks to Asiri and Vincent. Simon Glet
On Wed, Feb 10, 2010 at 11:36 AM, Vincent Massol <[email protected]> wrote:
On Feb 10, 2010, at 5:30 PM, Simon Glet wrote:
Jeremie,
I see your point but I wasn't expecting that much involvement ;-) BTW, as you speak of customization, I was wondering how to hide the "Import Office Document" menu. By not offering the option, users will not get frustrated and would more easily accept the system.
With the latest XE version (2.2RC1 or even better 2.2RC2 being released
right now, will be avail in 2-3 hours) if the office importer page (XWiki.OfficeImporter) is not present the menu item will not be shown. So you can rename that page or delete it (you'd then need to reimport the officeimporter XAR later on if you want it again in this case).
Of course you can also customize the menu vm files to define the rules
you want.
Thanks -Vincent
Thanks Simon Glet
On Wed, Feb 10, 2010 at 4:56 AM, Jeremie BOUSQUET <[email protected]> wrote:
Hi Simon,
Some words from a long-time user of XWiki ...
I think the issues you encountered might be linked also to the fact
that
these features rely on external tools (oo, ms office...), and also they are quite "recent" in xwiki history. So for sure, all integration issues might not have been encountered / fixed already. Of course if you need mainly these features, it might be a problem, but with some fixes there is no reason they won't work.
For the rest, I must say that on the other side, and even with some (known) flaws, xwiki is not comparable to other wikis I know. No one offers such liberty and customization possibilities. I use it for some years now at work (since v0.9) and migrated regularly to last versions, and progression is incredible, in terms of features and usability. A good basis is now in place, and I think not much is needed to have a nearly perfect tool :) But, again, this tool might need some involvement in order to get its best, even if it's more and more "plug & play".
I'll take an example, in my office we use a specific configuration management tool very uncommon, and that is integrated with nothing else. In wiki I could very easily create some macros to help users create links on various sources, reports and such in this scm tool. The wysiwyg editor works really well now, and the new macro displays in a dialog with parameters I defined, though I didn't code anything for the display. This is really helpful and really easy to put in place. I don't know much other tools, but I don't think you can do this kind of thing so easily... For now I did not install oO server for office import though, but I plan to.
Best regards, Jeremie
2010/2/9 Simon Glet <[email protected]>
Hi Asiri,
I am a little confused by the quality of XWiki 2.1.1. At this point I find that there are many features that don't work properly or at all :
- Office plugin (the office 2007 ribbon has a very buggy behavior) - Document import (There is no documentation about version compatibility between the different elements) - Usage with SQL Server 2005 is impossible. Works fine with PostgreSQL though.
I can't continue testing such a product. To bad, it looked very good.
Best Regards Simon Glet
On Tue, Feb 9, 2010 at 12:15 PM, Asiri Rathnayake <[email protected]> wrote: > Hi, > > On Tue, Feb 9, 2010 at 7:16 PM, Simon Glet <[email protected]> wrote: > >> Hi Asiri, >> >> I currently use the latest version of OO (3.1.1 Build 9420). What else >> can I check ? >> > > Well, you can try un-installing openoffice and reinstalling. But I doubt > this will help. > > Next thing you can try is use jodconverter directly and try to convert your > document from odt to html. > > Here is the link: > > http://code.google.com/p/jodconverter/ > > How to use it: > > http://code.google.com/p/jodconverter/wiki/GettingStarted > > If the command-line conversion fails for your document, then the error > should probably be reported to jodconverter users list. > > Thanks. > > - Asiri > > >> >> Thanks >> Simon Glet >> >> On Mon, Feb 8, 2010 at 9:20 PM, Asiri Rathnayake >> <[email protected]> wrote: >>> Hi, >>> >>> As you have understood it seems the problem is with your OOo >> installation. >>> Can you try removing your existing OOo installation and installing the >>> latest version from http://www.openoffice.org? This will most probably >> fix >>> the issue. >>> >>> - Asiri
users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Guillaume Lerouge Product Manager - XWiki SAS Skype: wikibc Twitter: glerouge http://guillaumelerouge.com/
Hi, On Fri, Feb 12, 2010 at 8:06 PM, Simon Glet <[email protected]> wrote:
Hi,
Just to end this thread, I upgraded to OpenOffice 3.2.0 from 3.1.1 and after creating the missing directory (http://jira.xwiki.org/jira/browse/XAOFFICE-44), import-export works fine. Great !!!
I wonder if these issues are caused by lack of admin privileges (looks like file permission issues). Do you have admin privileges on the xp machine you are testing on? Anyway, I'll do some tests on a XP SP3 machine to verify these claims asap. - Asiri
PS: IMHO XWiki gets very little testing on windows platforms (except for XWord). I do not know why I feel so reluctant to test XE on windows.. *yawns* - Asiri
Hi Asiri, I have admin privileges on my machine but if it might be a lock on the file... I might have had OO already running for file edition and if that process was using a file need by the OO server that would probably explain dll loading problem. Just in case, I restarted the OO server on XWiki after lauching an OO instance to edit some random file and the import still works fine. Thanks for your input. Simon Glet On Fri, Feb 12, 2010 at 11:10 AM, Asiri Rathnayake <[email protected]> wrote:
PS: IMHO XWiki gets very little testing on windows platforms (except for XWord). I do not know why I feel so reluctant to test XE on windows.. *yawns*
- Asiri _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
participants (6)
-
Asiri Rathnayake -
Florin Ciubotaru -
Guillaume Lerouge -
Jeremie BOUSQUET -
Simon Glet -
Vincent Massol