Re: [xwiki-users] MySQL storage using MyISAM engine.
On 14/01/10 11:29 PM, Thomas Mortagne wrote: On Thu, Jan 14, 2010 at 13:16, Mathias Herberts mathias.herberts+xwiki-us...@gmail.com wrote: Hi, I have an instance of XWiki Enterprise v2.1.1 deployed using a MySQL database. I've noticed that the engine used in MySQL is MyISAM and was wondering if there was a particular reason why InnoDB was not the engine of choice. Won't the use of MyISAM prove troublesome if lots of attachments are added to the Wiki? MyISAM uses a single file for all data in a table, and thus all attachements being stored in the same table, this MyISAM file might grow huge, which is usually not something suitable. Any past experience with attachement heavy Wiki instances using MySQL for storage? Any plan of using InnoDB in the near future? XWiki does not choose any specific MySQL engine AFAIK. it just ask for a table to the server and the server choose he default one. Or maybe hibernate generate initialization script with MyISAM explicitly but it would be weird. Maybe you can choose the MySQL engine in the hibernate configuration file to make sure it's using InnoDB. MyISAM is the default storage engine for MySQL. You can set it to something different if you wish, within the mysql server: http://dev.mysql.com/doc/refman/5.1/en/storage-engine-setting.html Thanks, Mathias. ___ 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] Fonts in PDF export documents
Is there a way to set the font for the entire document that is to be
exported? I've tried setting body { font-family: Arial; } which causes
the error:
org.apache.fop.fo.ValidationException:
{http://www.w3.org/1999/XSL/Format}block; is not a valid child of
fo:root! (See position 5:27)
at
org.apache.fop.events.ValidationExceptionFactory.createException(ValidationExceptionFactory.java:38)
at
org.apache.fop.events.EventExceptionManager.throwException(EventExceptionManager.java:54)
at
org.apache.fop.events.DefaultEventBroadcaster$1.invoke(DefaultEventBroadcaster.java:152)
BTW, I am working on the patch to have the DatabaseList accept XWQL as
the query ...
Regards,
Nigel
Using XE 2.1.1
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] XWQL in DatabaseLists
Hello, I really like the idea of database lists as it gives me the ability to relate pages (objects) together without much effort. However, I have found it very difficult to use these lists easily as it requires an understanding of not only HQL (which isn't hard) and of the Hibernate-mapped schema, which to my knowledge is not available. Is this hibernate-mapped API / Schema (java objects) published somewhere? It has also occurred to me that an even easier option would be to use XWQL in the DatabaseList query specification. Is this possible somehow? Regards, Nigel Running XE 1.9.3 ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Is there a simpler way to upgrade between versions?
Sergiu Dumitriu wrote: On 11/02/2009 10:08 AM, Guillaume Lerouge wrote: Hi Nigel, On Mon, Nov 2, 2009 at 3:09 AM, Nigel Smithsubscripti...@nianca.netwrote: Hello, I'm a very keen and happy user of xwiki. We use it for our corporate intranet and our users love it! Glad to hear that :-) I generally move directly between major versions as soon as convenient. The factor that has the most bearing on when we upgrade is the ease with which we can move between new versions. I remember seeing an items relating to simpler installation. I'd like to ask when that is scheduled to be worked on, and perhaps share some of my experiences in upgrading and some suggestions. A part of it (related to import) is being worked on right now. The work on a full-fledged Extension Manager has not started yet. I'd like to give you an idea of what has to be done to move between versions. It's a bit long, so bear with me, but here it is: * Download the latest xwiki xar to your local machine * Download the latest xwiki war to the machine which will run xwiki. * Backup the entire xwiki installation directory (the one that contains the directories database, jetty, lucene etc), and move the old directory aside (rename to xwiki.old) * //We do this to easily be able to get the jetty, hsql, etc dirs back in place//: Restore the backed up xwiki directory, thus putting the xwiki dir back in place * Delete the directory xwiki/webapps/xwiki * In xwiki/webapps, create an xwiki directory * Unzip the xwiki war in the xwiki/webapps/xwiki directory * //Getting our corp logo back//: Copy xwiki.old/webapps/xwiki/skins/toucan/mywiki.jpg to xwiki/webapps/xwiki/skins/toucan/mywiki.jpg * //Next few steps: need to merge old config with new config//: Do a diff between xwiki.old/webapps/xwiki/WEB-INF/xwiki.cfg and xwiki/webapps/xwiki/WEB-INF/xwiki.cfg. Update xwiki/webapps/xwiki/WEB-INF/xwiki.cfg as needed. * Do a diff between xwiki.old/webapps/xwiki/WEB-INF/xwiki.properties and xwiki/webapps/xwiki/WEB-INF/xwiki.properties. Update xwiki/webapps/xwiki/WEB-INF/xwiki.properties as needed. * Do a diff between xwiki.old/webapps/xwiki/WEB-INF/hibernate.cfg.xml and xwiki/webapps/xwiki/WEB-INF/hibernate.cfg.xml. Update xwiki/webapps/xwiki/WEB-INF/hibernate.cfg.xml as needed. * //This is the part we fear the most, for we might accidentally delete some configuration that we need and we would need to start the whole process again//: Start XWiki and import the default wiki xar. Be careful of what you import - read the instructions at http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Installation#HUpgradingwikidocuments . ** The normally excluded pages from import are: *** XWiki.XWikiPreferences *** XWiki.XWikiGroups *** XWiki.XWikiAdminGroup *** XWiki.WebPreferences *** XWiki.WebHome *** XWiki.XWikiUsers *** XWiki.XWikiAllGroup *** XWiki.DefaultSkin *** Main.WebHome *** Panels.QuickLinks *** Panels.Search * //We customise the PDF cover//: The PDF covers files has been manually modified. Do a diff between xwiki.old/webapps/xwiki/templates/pdfcover.vm and xwiki/webapps/xwiki/templates/pdfcover.vm. Merge the differences. * //We customise the PDF footer//: The PDF footers file has been modified by hand. Do a diff between xwiki.old/webapps/xwiki/templates/pdffooter.vm and xwiki/webapps/xwiki/templates/pdffooter.vm. Merge the differences. * //We do this to be able to specify the PDF template to use in Export as PDF//: The Menuitems have to be edited by hand, so that PDFs are exported using the correct stylesheet. Do a diff between xwiki.old/webapps/xwiki/templates/menuview.vm and xwiki/webapps/xwiki/templates/menuview.vm. Merge the differences (there should only be one line).As you can see, there are quite a few steps, and it normally takes 1/2hr - 1hr to complete. Note that we will move to MySQL eventually, but the performance of HSQL is OK ATM. Thanks for the feedback. This may not be the most optimal upgrade path, so if there are any clear improvements you can see, please let me know. The part that needs to be improved upon the most, in my opinion, is the import default XAR step because it is easy to overwrite an important page. I would like to put in a big vote for separating information that can be modified by the user from information that xwiki needs to be able to operate, that comes with default xwiki. Perhaps making certain pages system pages so that it is clear that if a page is modified it may interrupt the operation of the wiki, and may be difficult to upgrade. Definitely. This is the most dangerous part and it has triggered manny mistakes in the past. One of the XWiki developers is currently working on a patch that will improve the way the import works: imported pages will add a version to existing pages instead of overriding them. He should be able to commit his patch in the 2.1 timeframe.
[xwiki-users] Is there a simpler way to upgrade between versions?
Hello, I'm a very keen and happy user of xwiki. We use it for our corporate intranet and our users love it! I generally move directly between major versions as soon as convenient. The factor that has the most bearing on when we upgrade is the ease with which we can move between new versions. I remember seeing an items relating to simpler installation. I'd like to ask when that is scheduled to be worked on, and perhaps share some of my experiences in upgrading and some suggestions. I'd like to give you an idea of what has to be done to move between versions. It's a bit long, so bear with me, but here it is: * Download the latest xwiki xar to your local machine * Download the latest xwiki war to the machine which will run xwiki. * Backup the entire xwiki installation directory (the one that contains the directories database, jetty, lucene etc), and move the old directory aside (rename to xwiki.old) * //We do this to easily be able to get the jetty, hsql, etc dirs back in place//: Restore the backed up xwiki directory, thus putting the xwiki dir back in place * Delete the directory xwiki/webapps/xwiki * In xwiki/webapps, create an xwiki directory * Unzip the xwiki war in the xwiki/webapps/xwiki directory * //Getting our corp logo back//: Copy xwiki.old/webapps/xwiki/skins/toucan/mywiki.jpg to xwiki/webapps/xwiki/skins/toucan/mywiki.jpg * //Next few steps: need to merge old config with new config//: Do a diff between xwiki.old/webapps/xwiki/WEB-INF/xwiki.cfg and xwiki/webapps/xwiki/WEB-INF/xwiki.cfg. Update xwiki/webapps/xwiki/WEB-INF/xwiki.cfg as needed. * Do a diff between xwiki.old/webapps/xwiki/WEB-INF/xwiki.properties and xwiki/webapps/xwiki/WEB-INF/xwiki.properties. Update xwiki/webapps/xwiki/WEB-INF/xwiki.properties as needed. * Do a diff between xwiki.old/webapps/xwiki/WEB-INF/hibernate.cfg.xml and xwiki/webapps/xwiki/WEB-INF/hibernate.cfg.xml. Update xwiki/webapps/xwiki/WEB-INF/hibernate.cfg.xml as needed. * //This is the part we fear the most, for we might accidentally delete some configuration that we need and we would need to start the whole process again//: Start XWiki and import the default wiki xar. Be careful of what you import - read the instructions at http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Installation#HUpgradingwikidocuments . ** The normally excluded pages from import are: *** XWiki.XWikiPreferences *** XWiki.XWikiGroups *** XWiki.XWikiAdminGroup *** XWiki.WebPreferences *** XWiki.WebHome *** XWiki.XWikiUsers *** XWiki.XWikiAllGroup *** XWiki.DefaultSkin *** Main.WebHome *** Panels.QuickLinks *** Panels.Search * //We customise the PDF cover//: The PDF covers files has been manually modified. Do a diff between xwiki.old/webapps/xwiki/templates/pdfcover.vm and xwiki/webapps/xwiki/templates/pdfcover.vm. Merge the differences. * //We customise the PDF footer//: The PDF footers file has been modified by hand. Do a diff between xwiki.old/webapps/xwiki/templates/pdffooter.vm and xwiki/webapps/xwiki/templates/pdffooter.vm. Merge the differences. * //We do this to be able to specify the PDF template to use in Export as PDF//: The Menuitems have to be edited by hand, so that PDFs are exported using the correct stylesheet. Do a diff between xwiki.old/webapps/xwiki/templates/menuview.vm and xwiki/webapps/xwiki/templates/menuview.vm. Merge the differences (there should only be one line).As you can see, there are quite a few steps, and it normally takes 1/2hr - 1hr to complete. Note that we will move to MySQL eventually, but the performance of HSQL is OK ATM. This may not be the most optimal upgrade path, so if there are any clear improvements you can see, please let me know. The part that needs to be improved upon the most, in my opinion, is the import default XAR step because it is easy to overwrite an important page. I would like to put in a big vote for separating information that can be modified by the user from information that xwiki needs to be able to operate, that comes with default xwiki. Perhaps making certain pages system pages so that it is clear that if a page is modified it may interrupt the operation of the wiki, and may be difficult to upgrade. The next most important thing to be improved is the storage of configuration that now sits in xwiki.cfg and xwiki.properties. This is difficult to migrate between versions. If this was automatically migrated between versions like the pages are, this would be much easier to manage. At our office we have a large system written in Java and we solved a similar problem using the Java Preferences API. Being able to fully customise the PDF layout (not just the stylesheet) inside xwiki, and also specify a default PDF style sheet to use during export would be #3 on my list. I'm interested in hearing some thoughts. Regards, Nigel ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] PDF styling
Hi there, How does one go about changing the styling of the exported PDFs? Thanks, Nigel ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
