4 Sep
2007
4 Sep
'07
8:22 a.m.
On Wed, Aug 29, 2007 at 10:49:34AM +0200, Thomas Drevon wrote:
Pavel Kolesnikov wrote:
What do you suggest for customizing things that are stored in .vm files
in the skins directory rather than the database?
The other thing that I find makes updates significantly harder is if you
update pre-defined pages. For example, editing Blog.Macros causes me to
go through some pain every time I do an update.
Paul
--
End dual-measurement, let's finish going metric!
http://gometric.us/
http://www.metric.org/
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
One more question: is there any
mechanism/best-practice how to keep my
Xwiki extensions (plugins, Xwiki classes, templates, ...) isolated somehow
to make future upgrades of Xwiki as easy as possible?
Yes. In my opinion, only do changes to your xwiki instance by
1. Editing pages (e.g. html or velocity). These changes consists of
updating your database, and will thus survive an xwiki update. However,
should the database structure change (dunno how often this happens) you
are of course in trouble.
2. Write homebrew java plugins (package as jar and copy into
WEB-INF/lib/) which you invoke from xwiki pages.
Under no circumstance edit .vm files. This may seem like at decent idea
at first, but will gradually make upgrade something you will try to
avoid. Which of course is the opposite of progress.