[xwiki-users] XWiki 3.4, error when exporting PDF
) at com.xpn.xwiki.web.ExportAction.render(ExportAction.java:69) ... 39 more * When I dig the tomcat logs, the error seems to be *[WIKUIURL/format=pdfpdfcover=1pdfcover=0pdftoc=1pdftoc=0comments=0attachments=0] WARN c.x.x.p.i.PdfURLFactory- Failed to save image for PDF export java.io.IOException: Failed to create temporary PDF export file with prefix [pdf], suffix [.] in directory [/opt/tomcat/xwiki34/apache-tomcat-7.0.22/work/Catalina/10.10.1.134/xwiki/YfUqLnp5]* However, the directory listed has enough permission for the user which is used when executing the tomcat.. *root@xwiki34:# ls -lah /opt/tomcat/xwiki34/apache-tomcat-7.0.22/work/Catalina/10.10.1.134/xwiki/ drwxr-xr-x 5 tomcatxwiki34 tomcatxwiki34 4.0K Feb 13 09:33 . drwxr-xr-x 8 tomcatxwiki34 tomcatxwiki34 4.0K Feb 3 13:05 .. drwxr-xr-x 2 tomcatxwiki34 tomcatxwiki34 4.0K Feb 3 13:08 charts drwxr-xr-x 2 tomcatxwiki34 tomcatxwiki34 4.0K Feb 3 13:08 svg drwxr-xr-x 4 tomcatxwiki34 tomcatxwiki34 4.0K Feb 3 14:27 xwiki.plugin.image * properties/conf: *xwiki.cfg:xwiki.temp.dir=/tmp/xwiki/ xwiki.cfg:xwiki.tmp.dir=/tmp xwiki.cfg:xwiki.work.dir=/opt/tomcat/xwiki34/xwiki/work-dir* And there is also sufficient permissions in these directories as well.. Is there any advises of where to find more information or how this could be fixed? With Regards, ari ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] XWiki Enterprise 3.0.36132 - upgrade to 3.4 ?
Hi.
I have XWiki Enterprise 3.0.36132 and would like to upgrade to latest
version. I have tried to upgrade directly to 3.4 but as it produced
error message I tried to upgrade in steps..
Upgrade to 3.1.1 was ok, no db migration was needed and installed the
.xar without problems. Then upgrade to 3.2.1 produced the following:
Servlet.service() for servlet [action] in context with path [/xwiki]
threw exception [com.xpn.xwiki.XWikiException: Error number 3 in 0:
Could not initialize main XWiki context
Wrapped Exception: Error number 3201 in 3: Exception while saving
document xwiki:XWiki.XWikiUsers
Wrapped Exception: Error number 3211 in 3: Exception while updating
archive XWiki.XWikiUsers
Wrapped Exception: Error number 0 in 3: Exception while hibernate execute
Wrapped Exception: could not load an entity:
[com.xpn.xwiki.doc.rcs.XWikiRCSNodeContent#component[docId,version1,version2]{docId=495778886,
version2=1, version1=2}]] with root cause
com.xpn.xwiki.XWikiException: Error number 3 in 0: Could not initialize
main XWiki context
Wrapped Exception: Error number 3201 in 3: Exception while saving
document xwiki:XWiki.XWikiUsers
Wrapped Exception: Error number 3211 in 3: Exception while updating
archive XWiki.XWikiUsers
Wrapped Exception: Error number 0 in 3: Exception while hibernate execute
Wrapped Exception: could not load an entity:
[com.xpn.xwiki.doc.rcs.XWikiRCSNodeContent#component[docId,version1,version2]{docId=495778886,
version2=1, version1=2}]
at com.xpn.xwiki.XWiki.getMainXWiki(XWiki.java:422)
at com.xpn.xwiki.XWiki.getXWiki(XWiki.java:491)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:136)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:116)
-
the hibernate configuration is
-
!DOCTYPE hibernate-configuration PUBLIC
-//Hibernate/Hibernate Configuration DTD//EN
http://www.hibernate.org/dtd/hibernate-configuration-3.0.dtd;
hibernate-configuration
session-factory
property name=show_sqlfalse/property
property name=use_outer_jointrue/property
property name=dbcp.defaultAutoCommitfalse/property
property name=dbcp.maxActive50/property
property name=dbcp.maxIdle5/property
property name=dbcp.maxWait3/property
property name=dbcp.whenExhaustedAction1/property
property name=dbcp.ps.whenExhaustedAction1/property
property name=dbcp.ps.maxActive20/property
property name=dbcp.ps.maxWait12/property
property name=dbcp.ps.maxIdle20/property
property name=jdbc.use_scrollable_resultsetfalse/property
property name=connection.useUnicodetrue/property
property name=connection.characterEncodingUTF-8/property
property
name=connection.urljdbc:postgresql://10.10.1.134/xwiki/property
property name=connection.usernamexwiki/property
property name=connection.password/property
property
name=connection.driver_classorg.postgresql.Driver/property
property
name=dialectorg.hibernate.dialect.PostgreSQLDialect/property
property
name=connection.provider_classcom.xpn.xwiki.store.DBCPConnectionProvider/property
property name=connection.pool_size2/property
property name=statement_cache.size2/property
mapping resource=xwiki.hbm.xml/
mapping resource=feeds.hbm.xml/
mapping resource=activitystream.hbm.xml/
/session-factory
/hibernate-configuration
-
Any help would be appreciated..
BR, ari
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] XWiki Enterprise 3.0.36132 - upgrade to 3.4 ?
On 03.02.2012 14:50, Ari wrote:
I have XWiki Enterprise 3.0.36132 and would like to upgrade to latest
version. I have tried to upgrade directly to 3.4 but as it produced
error message I tried to upgrade in steps..
Upgrade to 3.1.1 was ok, no db migration was needed and installed the
.xar without problems. Then upgrade to 3.2.1 produced the following:
Tried to upgrade to 3.3.1 with the following:
com.xpn.xwiki.XWikiException: Error number 0 in 3: Exception while
hibernate execute
Wrapped Exception: could not load an entity:
[com.xpn.xwiki.doc.rcs.XWikiRCSNodeContent#component[docId,version1,version2]{docId=495778886,
version2=1, version1=2}]
at
com.xpn.xwiki.store.XWikiHibernateBaseStore.execute(XWikiHibernateBaseStore.java:1110)
at
com.xpn.xwiki.store.XWikiHibernateBaseStore.executeRead(XWikiHibernateBaseStore.java:1140)
at
com.xpn.xwiki.store.XWikiHibernateVersioningStore.loadRCSNodeContent(XWikiHibernateVersioningStore.java:298)
at
com.xpn.xwiki.doc.rcs.XWikiRCSNodeInfo.getContent(XWikiRCSNodeInfo.java:175)
at
com.xpn.xwiki.doc.XWikiDocumentArchive.makePatch(XWikiDocumentArchive.java:138)
at
com.xpn.xwiki.doc.XWikiDocumentArchive.updateArchive(XWikiDocumentArchive.java:254)
at
com.xpn.xwiki.store.XWikiHibernateVersioningStore.updateXWikiDocArchive(XWikiHibernateVersioningStore.java:254)
at
com.xpn.xwiki.store.XWikiHibernateStore.saveXWikiDoc(XWikiHibernateStore.java:483)
at
com.xpn.xwiki.store.XWikiCacheStore.saveXWikiDoc(XWikiCacheStore.java:174)
at
com.xpn.xwiki.store.XWikiCacheStore.saveXWikiDoc(XWikiCacheStore.java:167)
at com.xpn.xwiki.XWiki.saveDocument(XWiki.java:1403)
at com.xpn.xwiki.XWiki.saveDocument(XWiki.java:1359)
at com.xpn.xwiki.XWiki.saveDocument(XWiki.java:1354)
at com.xpn.xwiki.XWiki.getUserClass(XWiki.java:3075)
at com.xpn.xwiki.XWiki.initializeMandatoryClasses(XWiki.java:840)
at com.xpn.xwiki.XWiki.initXWiki(XWiki.java:814)
at com.xpn.xwiki.XWiki.init(XWiki.java:740)
at com.xpn.xwiki.XWiki.getMainXWiki(XWiki.java:402)
at com.xpn.xwiki.XWiki.getXWiki(XWiki.java:488)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:136)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:116)
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:621)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:128)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:144)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.xwiki.container.servlet.filters.internal.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:217)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.xwiki.container.servlet.filters.internal.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:109)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168
Re: [xwiki-users] Upgrading from (ancient) XWiki Enterprise 1.9.4 to ... what?
On 09.06.2011 14:27, Sergiu Dumitriu wrote: or could I just upgrade to 1.9.4 - 2.7.x ? You should upgrade directly to the most recent version, but be careful to read the release notes for all major versions, paying attention to the upgrade notes. Thank for your help. Upgrade has been successfully completed! =) However, the one reason for the upgrade was the search which didn't work with scandinavian letters (say, öä). With high hopes I tested this, and got the same error.. What I do is simply enter word pöö to search-textfield and do the search. Result is that the site title and the search page header are: pöö. The search result page has following meta-info: meta http-equiv=Content-Type content=text/html; charset=UTF-8 / meta name=page content=Search/ meta name=version content=1.1/ meta name=gwt:property content=locale=fi / meta name=description content=Search: pöö / Server locale is en_US.UTF-8 XWiki is located at tomcat 5.5.23, the JAVA parameters are -Dfile.encoding=UTF-8 -Djava.awt.headless=true Can someone please help me, or point me into the right direction.. :-/ BR, ari ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Upgrading from (ancient) XWiki Enterprise 1.9.4 to ... what?
The wonderful article at http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Encoding saved the day. :) t: ari On 10.06.2011 12:05, Ari wrote: On 09.06.2011 14:27, Sergiu Dumitriu wrote: or could I just upgrade to 1.9.4 - 2.7.x ? You should upgrade directly to the most recent version, but be careful to read the release notes for all major versions, paying attention to the upgrade notes. Thank for your help. Upgrade has been successfully completed! =) However, the one reason for the upgrade was the search which didn't work with scandinavian letters (say, öä). With high hopes I tested this, and got the same error.. What I do is simply enter word pöö to search-textfield and do the search. Result is that the site title and the search page header are: pöö. The search result page has following meta-info: meta http-equiv=Content-Type content=text/html; charset=UTF-8 / meta name=page content=Search/ meta name=version content=1.1/ meta name=gwt:property content=locale=fi / meta name=description content=Search: pöö / Server locale is en_US.UTF-8 XWiki is located at tomcat 5.5.23, the JAVA parameters are -Dfile.encoding=UTF-8 -Djava.awt.headless=true Can someone please help me, or point me into the right direction.. :-/ BR, ari ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Upgrading from (ancient) XWiki Enterprise 1.9.4 to ... what?
On 10.06.2011 13:10, Sergiu Dumitriu wrote: On 06/10/2011 11:21 AM, Ari wrote: The wonderful article at http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Encoding saved the day. :) So, was it the Tomcat URIEncoding setting? I put that to the Connectors, and my quess is that it solved it because at all times the URI seemed ok, but now it also parsed as ok. I also upgraded the java5 to java6, but I'd say that the URIEncodind was THE thing. Thanks for the help! BR, ari t: ari On 10.06.2011 12:05, Ari wrote: On 09.06.2011 14:27, Sergiu Dumitriu wrote: or could I just upgrade to 1.9.4 - 2.7.x ? You should upgrade directly to the most recent version, but be careful to read the release notes for all major versions, paying attention to the upgrade notes. Thank for your help. Upgrade has been successfully completed! =) However, the one reason for the upgrade was the search which didn't work with scandinavian letters (say, öä). With high hopes I tested this, and got the same error.. What I do is simply enter word pöö to search-textfield and do the search. Result is that the site title and the search page header are: pöö. The search result page has following meta-info: meta http-equiv=Content-Type content=text/html; charset=UTF-8 / meta name=page content=Search/ meta name=version content=1.1/ meta name=gwt:property content=locale=fi / meta name=description content=Search: pöö / Server locale is en_US.UTF-8 XWiki is located at tomcat 5.5.23, the JAVA parameters are -Dfile.encoding=UTF-8 -Djava.awt.headless=true Can someone please help me, or point me into the right direction.. :-/ BR, ari ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] Upgrading from (ancient) XWiki Enterprise 1.9.4 to ... what?
Hi. Is there any hope to upgrade the ancient version (XWiki Enterprise) 1.9.4 to a newer, say 2.7.x or even to 3.0.x ? I found the archived release notes, but what steps are required? I mean that should I upgrade from 1.94 - 2.0 Milestone 1 2.0 Milestone 1 - 2.0 Milestone 2 . . 2.0.4 - 2.0.5 . . 2.7.1 - 2.7.2 or could I just upgrade to 1.9.4 - 2.7.x ? Any help would be highly appreciated! With Kind Regards, Ari Takku ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Why I chose Xwiki instead of other wikis
http://xoffice.xwiki.org/xwiki/bin/view/CodeBase/XmlRpcProxy and http://platform.xwiki.org/xwiki/bin/view/Features/XMLRPC, so similar, yet in totally different places The XmpRpcProxy page was created after you sent your first mail. I published that page, as a result of your mail, so that it potentially helps you. As you can see the notes in the page, it is only a draft. When completed(fully maps the xml-rpc modelapi) it will be linked/added to the platform page. Yeah, I know you created that to help me and I appreciate it. When I first looked at it, it striked me as being in a wrong place, that's why I chose it as an example. Little bit unfair, being draft and all, and you trying to help, sorry. :( The content of that page is actually very good, and will be a major help for anyone trying to use Xwiki XML/RPC from .NET -environment. Guillaume wrote: If you've got a little time, we'd be very happy to have you contribute the program you wrote on http://code.xwiki.org/ and improve the documentation in places where you found it confusing (adding details / links where needed). All you need to do this is an account on xwiki.org and then, well, it's a wiki ;-) That's a good point. Maybe I'll try to find time to contribute. I always forget it's a wiki ;) Cheers, Ari ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] Why I chose Xwiki instead of other wikis
Thanks for your feedback. I would be glad to know a bit more about what you were looking for, which wikis you tried and what made you choose XWiki rather than another system. This would help us understand better what makes XWiki stand out and what it lacks compared with other platforms. If you've got a little time, do you think you could tell us a bit about that? Many thanks in advance, Guillaume Ok, here's a small list of reasons why I chose Xwiki and not some other wiki. Before I begun searching for suitable wiki, I gathered a list of requirements that a wiki must have. Wikis that I tested or studied were: MediaWiki, TikiWiki, Xwiki and Confluence. Maybe some others too, but I don't remember ;) Here is that list and how different wikis fulfill those requirements: Requirement 1: Ability to transclude pages and sections of pages in other pages MediaWiki: Yes, support page transcluding natively and section transcluding can be added with plugin Xwiki: Supports page transcluding. Section macro was easy to do, and I got to do it just the way I like it :) Confluence: I think it supports transcluding. Not tested it though. Requirement 2: Support for hierarchical information ( tree-like ) MediaWiki: Very bad. Can be achieved using categories, but because Category is a namespace, category names must be unique which was unacceptable in mycase. Xwiki: Very flexible. Namespaces ( Spaces in Xwiki ) are easy to create and pages can be ordered hierarchically using page's parent -field. Requirement 3: Support for content localization/translation Mediawiki: None. AFAIK every language needs it's own Wiki. Xwiki: Built-in. Creating translated content is easy. Functions to retrieve translations still needs work, but are good enough to get the job done. Requirement 4: Flexible, easy to maintain user rights Mediawiki: User right management very restricted. Better with plugins but still poor. Xwiki: Superb! Very easy, yet powerful way to handle user rights. I really liked that user right has 3 options: allow, deny, neutral. This combined with user groups and spaces makes user rights management very enjoyable. TikiWiki: Frustratingly detailed. Has some very powerful features, but list of about 100 different user right parameters is very frustrating. (This opinion is based on very quick tests) Requirement 5: Ability make offline HTML dumps of wiki content MediaWiki: Possible (maybe with a plug-in, I don't remember) Xwiki: Supported natively. Yet, I decided to make my own XML Dump program which fetches content through XML/RPC interface. And now a list of pros and cons for every wiki I tested: Mediawiki: + Widely used, lots of help available + lots of plugins - hierarchical information support very bad - user right management limited and hard to comprehend TikiWiki: + Lots of features - User interface looks clumsy and is difficult to use ( maybe because I tested Xwiki just before this ;) - User rights management is overwhelming Confluence: ( not tested, opinions based on what I read about it) + seems finalized + used widely in enterprises and universities + XML/RPC interface - PRICE Xwiki: + Very slick UI + Macros / Programming capabilities + XML/RPC interface + User rights management + customer support - Seems in many ways incomplete/work in progress - Documention is scattered across the internets / help is very hard to find using Google. Most searches end up in Xwiki JIRA-pages. - Xwiki documentation pages seem disorientating. Even if I know theres some useful info there, it takes me 15mins to find it. (DevGuide, dev.xwiki.org, xwiki.org/Features) - Example: http://xoffice.xwiki.org/xwiki/bin/view/CodeBase/XmlRpcProxy and http://platform.xwiki.org/xwiki/bin/view/Features/XMLRPC, so similar, yet in totally different places - Scandinavian characters in pageIds don't seem to work I hope these lists are helpful to you. Despite some criticism I presented here, you have developed an amazing wiki. I think you should focus a little more on making documentation easy to find and read even for someone who is just starting to code or otherwise noob (such as me ;). Now it gives an impression that you have to be Linux-expert/super-coder/uber-nerd to be able to set up wiki and program it (which you don't need to be, it's actually quite simple). Best regards, Ari ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Translations cannot be fetched using XML/RPC interface
Hi, And thanks for your efforts regarding this issue. I found the problem which caused my translations not to work. I used getPage -method to get page details. Which returned translations ok. But after that, I used renderContent method without defining content, which resulted that function returning default language content. After I added content to method call, translated content is returned. So it was my fault, not Xwiki's. sorry :) Still, some things to consider: - should renderContent function also handle pageId so that language could be embedded in the end of pageId? Same way as getPage handles pageId. - getPages function returns PageSummaries with default language pageTitles. It would be convenient to call this function with language id, so that pagetitles would be in correct language. Now I have to loop through every pagesummary and get page title to get correct pageTitles to show on navigation tree. Thanks for superb customer support! Best regards, Ari -Original Message- From: users-boun...@xwiki.org [mailto:users-boun...@xwiki.org] On Behalf Of Florin Ciubotaru Sent: 18. maaliskuuta 2009 14:47 To: XWiki Users Subject: Re: [xwiki-users] Translations cannot be fetched using XML/RPC interface Hi, I recreated your scenario an published a basic XmlRpc proxy on this page: - http://xoffice.xwiki.org/xwiki/bin/view/CodeBase/XmlRpcProxy Getting the wiki content of a translated page seems to work fine. Here's how it can be used: Page pageInfo = proxy.GetPage(token, Main.WebHome?language=fr); String frenchContent = pageInfo.content; The language parameter value must be a value present in the translations array. Notes: - The translations array contains all available translations for that page, except the default language of the page. - The default language of the page is the default language of the wiki at the moment when the page is created. If ,in time, you change the wiki's default language, the page default language for the page will not change. - If you need the rendered content you will need to make another call to this API method: public String renderContent(String token, String space, String pageId, String content) throws Exception; Please let me know of your progress Thanks, Florin Ciubotaru Ari Oinas wrote: Ok, my setup is as follows: Xwiki Enterprise 1.71 installed on Apache Tomcat server (Win Xp Pro Sp3) and it's working fine. Im trying to create .NET Managed -application using C# (Visual Studio 2008) which connects to Xwiki and displays Xwiki content on a dialog. Im using CookComputing.XmlRpc -library. So far I've managed to do the following: - Connect and login successfully to Xwiki - Fetch pagesummaries, pages and attachments from Xwiki and displayed them in Windows.Forms.WebBrowser component. I have created a space in Xwiki which holds the pages I want to show in my application. (Space name contains spaces, is this a problem?) I have created a page inside this space and also translated it to another language. This page is displayed properly in Xwiki web-client. Page is created using Xwiki 1.0 syntax. If I debug my program and inspect PageSummary -properties, I can see that there is a translation called en in translations array. Best regards, paristo -Original Message- From: users-boun...@xwiki.org [mailto:users-boun...@xwiki.org] On Behalf Of Fabio Mancinelli Sent: 17. maaliskuuta 2009 15:07 To: XWiki Users Subject: Re: [xwiki-users] Translations cannot be fetched using XML/RPC interface On Mar 17, 2009, at 1:37 PM, Ari Oinas wrote: Hi, My problem is that I cannot fetch translated pages from Xwiki using XML/RPC interface. I have tried it like this: xwikiInterface.getPage(iToken, Space.Page + ?language=en); but it returns the default page. Hi, could you tell me your exact setup? I tried with a multilanguage wiki and a Main.WebHome translated in fr and it. rpc.getPage(Main.WebHome?language=en).getContent() - English rpc.getPage(Main.WebHome?language=it).getContent() - Italiano rpc.getPage(Main.WebHome?language=fr).getContent() - Français The available translations are accessible using the Page.getTranslations() In the previous example, this call returns [it, fr] (Maybe here we should explicitly add also the default translation) Let me know. Cheers, Fabio ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] Translations cannot be fetched using XML/RPC interface
Hi, My problem is that I cannot fetch translated pages from Xwiki using XML/RPC interface. I have tried it like this: xwikiInterface.getPage(iToken, Space.Page + ?language=en); but it returns the default page. My Xwiki-interface getPage method is defined as follows: [XmlRpcMethod(confluence1.getPage)] PageStruct getPage(String token, String pageId); I'm using C# language and Visual Studio 2008 and I currently have a working prototype of an application which fetches Xwiki-pages from remote Xwiki-installation. But now the problem is how to get also translated pages. Any help regarding this issue would be greatly appreciated. Best regards -paristo ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Translations cannot be fetched using XML/RPC interface
Ok, my setup is as follows: Xwiki Enterprise 1.71 installed on Apache Tomcat server (Win Xp Pro Sp3) and it's working fine. Im trying to create .NET Managed -application using C# (Visual Studio 2008) which connects to Xwiki and displays Xwiki content on a dialog. Im using CookComputing.XmlRpc -library. So far I've managed to do the following: - Connect and login successfully to Xwiki - Fetch pagesummaries, pages and attachments from Xwiki and displayed them in Windows.Forms.WebBrowser component. I have created a space in Xwiki which holds the pages I want to show in my application. (Space name contains spaces, is this a problem?) I have created a page inside this space and also translated it to another language. This page is displayed properly in Xwiki web-client. Page is created using Xwiki 1.0 syntax. If I debug my program and inspect PageSummary -properties, I can see that there is a translation called en in translations array. Best regards, paristo -Original Message- From: users-boun...@xwiki.org [mailto:users-boun...@xwiki.org] On Behalf Of Fabio Mancinelli Sent: 17. maaliskuuta 2009 15:07 To: XWiki Users Subject: Re: [xwiki-users] Translations cannot be fetched using XML/RPC interface On Mar 17, 2009, at 1:37 PM, Ari Oinas wrote: Hi, My problem is that I cannot fetch translated pages from Xwiki using XML/RPC interface. I have tried it like this: xwikiInterface.getPage(iToken, Space.Page + ?language=en); but it returns the default page. Hi, could you tell me your exact setup? I tried with a multilanguage wiki and a Main.WebHome translated in fr and it. rpc.getPage(Main.WebHome?language=en).getContent() - English rpc.getPage(Main.WebHome?language=it).getContent() - Italiano rpc.getPage(Main.WebHome?language=fr).getContent() - Français The available translations are accessible using the Page.getTranslations() In the previous example, this call returns [it, fr] (Maybe here we should explicitly add also the default translation) Let me know. Cheers, Fabio ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] xwiki rendering questions / suggestions
Hi Sergiu and Jean-Vincent. Sergiu Dumitriu wrote: Ari wrote: I've tried to figure out why the XWiki renders xwiki-headings as it does. E.g 1 Title One is rendered as 'h2 class=heading-1Title One/h2'. I would like to change this to be h1-element instead of h2-element. That was my decision, as in a document there is already a first-level heading, the document title. Having other elements as level 1 headings would mean that they have the same significance as the document title, which I think is wrong. Still, this should be configurable, and since the heading syntax is not yet finalized (http://jira.xwiki.org/jira/browse/XWIKI-1247) it can be changed. I see your point. I agree that in general it is a good approach to have only one H1-element in a web page. However, as I see it, wiki provided pages should be handled in this viewpoint as individual pages. What I mean is that if xwiki-framework provides some dynamic title, it should not hinder the user-provided content to contain H1-element (with xwiki syntax). E.g when I print a page from XWiki, the optimal result is that the page looks as if it was printed through OpenOffice.org - IMHO the containment (of a page) should not be restricted on the basis of what lies under the hood. I'd like to point out that previous statement holds true in the environment I am using the XWiki. Of course, if the feature could be configurable, it would be a win-win situation (of course, the debate would then concentrate on issue of default setting? ;-) ) PART 2 Another suggestion is that minor fix would be implemented in rendering. An example text and the rendered result: -- this is text before list. * this * is * list this is text after list. -- pthis is text before list./p ul class=star lithis/li liis/li lilist/li /ulthis is text after list. -- Radeox makes this extremely hard to do. Since it works with independent regular expressions, and not with grammars or state machines or something else that could know what a paragraph is, you can't write a regular expression that matches only the right things. The new rendering engine could solve this issue. Ok. I just wait and see. The reason I'm asking this is that this behaviour breaks the page structure (which leads to poor printing result). Fortunately there is the good-old-add-span/-workaround. You are somehow wrong in your example, as the actual rendering is: p/this is text before list. ul class=star ... Not even the first line of text is actually a paragraph, but because the page is not sent as valid XML, but html, the browser takes the freedom to actually put that line inside the paragraph, because it knows that an empty paragraph element is wrong and absurd. Ah. I think you are correct: I just copypasted the result from firefox source-viewer. In some time ago, it was Internet Exploder which did this fixing - now it seems that everybody's doing it. :) Thank you for your replies. With Regards, ari ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] xwiki rendering questions / suggestions
Hello. Jean-Vincent Drean wrote: On Wed, Jun 11, 2008 at 1:37 PM, Ari [EMAIL PROTECTED] wrote: As the description of this list goes: I would suggest that the xwiki rendering should be done in a straightforward way where syntax 1 would be h1, 1.1 h2, 1.1.1 h3 and so on. Yes the semantics of our titles aren't correct, if I remember well those titles are the default titles coming from Radeox (the rendering components we use which is not part of the XWiki project itself). BTW we are currently rewriting the whole rendering component so I think this issue will disappear in a near future, Vincent can you confirm ? I noticed just now that thunderbird had marked tons of users-list mail as junk so I didn't notice this until now. Happy to hear that problems may be solved as we upgrade our wiki to 1.5. Hopefully the PART2 bug is also fixed.. I could have fixed it but have no idea where to look for. With Regards, ari ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] xwiki rendering questions / suggestions
Vincent Massol wrote:
Hi Ari,
Would be great if you could open a jira issue for this and send us a
real patch. Don't forget that you'll need to modify all CSS files for
the various skins too.
Done:
http://jira.xwiki.org/jira/browse/XWIKI-2464
http://jira.xwiki.org/jira/browse/XWIKI-2465
I'm also worried this might break several custom skins done by users.
WDYT?
I think that this does not break anything. The CSS-files contain the
header info in general way (i.e. instead of H1 and H2 there is styles
for .heading-1, .heading-1-1, and so on.
I grepped recursively the installation I have (1.4) and even though few
files (see list below) contain some hard-coded values for headers, this
is IMHO irrelevant because they contain the similar (.heading-1) styles.
- skins/albatross/scripts/table/tablefilterNsort.js
- templates/viewattachrev.vm
- templates/passwd.vm
- templates/importinline.vm
- templates/renameStep1.vm
- templates/exportinline.vm
- templates/changemyavatar.vm
- wiki_editor/plugins/core.js
Regards,
ari
Thanks
-Vincent
On Jun 13, 2008, at 5:57 AM, Ari wrote:
Ari wrote:
I've tried to figure out why the XWiki renders xwiki-headings as it
does. E.g 1 Title One is rendered as 'h2 class=heading-1Title
One/h2'. I would like to change this to be h1-element instead of
h2-element.
I implemented the modifications for heading liftup. Modifications
include:
com.xpn.xwiki.render.XWikiWikiBaseRenderer#makeHeading
--
public static void makeHeading(StringBuffer stringBuffer, String
level, String text, Util util) {
// modified 12.06.2008
Integer parsedInt = Integer.parseInt(level);
Integer levelInt = Math.max((parsedInt-1), 1);
// end of modification
String anchor = makeAnchor(text, util);
stringBuffer.append(h);
stringBuffer.append(levelInt); // was: level
stringBuffer.append( id=\);
stringBuffer.append(anchor);
stringBuffer.append(\ );
stringBuffer.append(text);
stringBuffer.append(/h);
stringBuffer.append(levelInt); // was: level
stringBuffer.append();
}
--
com.xpn.xwiki.render.filter.XWikiHeadingFilter#handleMatch(MatchResult
result, FilterContext context)
--
public String handleMatch(MatchResult result, FilterContext
context)
{
String id = null;
String title = result.group(0);
String level = result.group(1);
// old way
//int level_i = (level.length() + 3) / 2;
// new way (12.06.2008)
int level_i = level.replaceAll(\\., ).length();
--
I'm not sure if the modification to
com.xpn.xwiki.render.XWikiWikiBaseRenderer#makeHeading is necessary,
but
the change for
com.xpn.xwiki.render.filter.XWikiHeadingFilter#handleMatch(MatchResult
is obvious.
This change is compatible with xwiki-core-1.4. I think that the
rendering is pretty completely rewritten in 1.5, but hopefully someone
finds this useful. Any corrections for possible misintepretations are
highly appreciated.
Regards,
ari
PS. Has someone knowledge about the bug in the rendering text after
list (-, *, #) ? (See rest of the post, PART 2)
As the description of this list goes: I would suggest that the xwiki
rendering should be done in a straightforward way where syntax 1
would
be h1, 1.1 h2, 1.1.1 h3 and so on.
PART 2
Another suggestion is that minor fix would be implemented in
rendering.
An example text and the rendered result:
--
this is text before list.
* this
* is
* list
this is text after list.
--
pthis is text before list./p
ul class=star
lithis/li
liis/li
lilist/li
/ulthis is text after list.
--
Also this is text after list should be rendered as paragraph. A
workaround is to write:
--
this is text before list.
* this
* is
* list
span
this is text after list.
--
pthis is text before list./p
ul class=star
lithis/li
liis/li
lilist/li
/ulspan
pthis is text after list./p
--
Same goes with lists with - * and #.
With Best Regards,
ari
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] xwiki rendering questions / suggestions
Hello Vincent. Vincent Massol wrote: On Jun 13, 2008, at 10:53 AM, Ari wrote: Vincent Massol wrote: Would be great if you could open a jira issue for this and send us a real patch. Don't forget that you'll need to modify all CSS files for the various skins too. Done: http://jira.xwiki.org/jira/browse/XWIKI-2464 http://jira.xwiki.org/jira/browse/XWIKI-2465 I grepped recursively the installation I have (1.4) and even though few files (see list below) contain some hard-coded values for headers, this is IMHO irrelevant because they contain the similar (.heading-1) styles. ok that's cool then. All you need then is good and tested patch. See http://dev.xwiki.org/xwiki/bin/view/Community/Contributing Thanks for the link (and for the help you've provided). I attached two patches in http://jira.xwiki.org/jira/browse/XWIKI-2464 Regards, Ari ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] xwiki rendering questions / suggestions
Ari wrote:
I've tried to figure out why the XWiki renders xwiki-headings as it
does. E.g 1 Title One is rendered as 'h2 class=heading-1Title
One/h2'. I would like to change this to be h1-element instead of
h2-element.
I implemented the modifications for heading liftup. Modifications include:
com.xpn.xwiki.render.XWikiWikiBaseRenderer#makeHeading
--
public static void makeHeading(StringBuffer stringBuffer, String
level, String text, Util util) {
// modified 12.06.2008
Integer parsedInt = Integer.parseInt(level);
Integer levelInt = Math.max((parsedInt-1), 1);
// end of modification
String anchor = makeAnchor(text, util);
stringBuffer.append(h);
stringBuffer.append(levelInt); // was: level
stringBuffer.append( id=\);
stringBuffer.append(anchor);
stringBuffer.append(\ );
stringBuffer.append(text);
stringBuffer.append(/h);
stringBuffer.append(levelInt); // was: level
stringBuffer.append();
}
--
com.xpn.xwiki.render.filter.XWikiHeadingFilter#handleMatch(MatchResult
result, FilterContext context)
--
public String handleMatch(MatchResult result, FilterContext context)
{
String id = null;
String title = result.group(0);
String level = result.group(1);
// old way
//int level_i = (level.length() + 3) / 2;
// new way (12.06.2008)
int level_i = level.replaceAll(\\., ).length();
--
I'm not sure if the modification to
com.xpn.xwiki.render.XWikiWikiBaseRenderer#makeHeading is necessary, but
the change for
com.xpn.xwiki.render.filter.XWikiHeadingFilter#handleMatch(MatchResult
is obvious.
This change is compatible with xwiki-core-1.4. I think that the
rendering is pretty completely rewritten in 1.5, but hopefully someone
finds this useful. Any corrections for possible misintepretations are
highly appreciated.
Regards,
ari
PS. Has someone knowledge about the bug in the rendering text after
list (-, *, #) ? (See rest of the post, PART 2)
As the description of this list goes: I would suggest that the xwiki
rendering should be done in a straightforward way where syntax 1 would
be h1, 1.1 h2, 1.1.1 h3 and so on.
PART 2
Another suggestion is that minor fix would be implemented in rendering.
An example text and the rendered result:
--
this is text before list.
* this
* is
* list
this is text after list.
--
pthis is text before list./p
ul class=star
lithis/li
liis/li
lilist/li
/ulthis is text after list.
--
Also this is text after list should be rendered as paragraph. A
workaround is to write:
--
this is text before list.
* this
* is
* list
span
this is text after list.
--
pthis is text before list./p
ul class=star
lithis/li
liis/li
lilist/li
/ulspan
pthis is text after list./p
--
Same goes with lists with - * and #.
With Best Regards,
ari
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] xwiki rendering questions / suggestions
Hello. My question / suggestion goes with two part. PART 1 I've tried to figure out why the XWiki renders xwiki-headings as it does. E.g 1 Title One is rendered as 'h2 class=heading-1Title One/h2'. I would like to change this to be h1-element instead of h2-element. At first I suspected that this change would require only small modification in some velocity template. It seems that I was wrong. My current guess is that this rendering is done somewhere in java (from xwiki.hbm.xml I tracked the doc.XWikiDocument and with that my guess is DefaultXWikiRenderingEngine.java). However, I don't know how/where I should change the code. Is there a flow-chart or something to describe the render-phase? As the description of this list goes: I would suggest that the xwiki rendering should be done in a straightforward way where syntax 1 would be h1, 1.1 h2, 1.1.1 h3 and so on. PART 2 Another suggestion is that minor fix would be implemented in rendering. An example text and the rendered result: -- this is text before list. * this * is * list this is text after list. -- pthis is text before list./p ul class=star lithis/li liis/li lilist/li /ulthis is text after list. -- Also this is text after list should be rendered as paragraph. A workaround is to write: -- this is text before list. * this * is * list span this is text after list. -- pthis is text before list./p ul class=star lithis/li liis/li lilist/li /ulspan pthis is text after list./p -- Same goes with lists with - * and #. With Best Regards, ari ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
