If your local customizations are completely separated from the core, I would expect both approaches to yield the same results. However, if you modified a core file, then the direction of the copy would make a difference.

One thought that might explain your problem: somewhere between VuFind 2 beta and 2.1.1, themes were changed to use a theme.config.php file in place of a theme.ini; you might have to port that configuration over to the new format in order for VuFind to recognize the theme.

- Demian

From: Martin Fuchs [mfuchs@subkom.de]
Sent: Saturday, November 23, 2013 10:21 AM
To: vufind-tech@lists.sourceforge.net
Subject: [VuFind-Tech] Update from VuFind2 Beta to VuFind2.1.1

To the VuFind-List

We tried the Update by 2 approaches.


1) New Installation of VuFind2.1.1. (on a local windows system) and then

copy of local themes and local php's from our VuFind2 Beta to the new VuFind2.1.1

And configuring of VuFind2.1.1 to work with our local themes and php's.


2) Recursive Copy of the downloaded VuFind2.1. into our existing central Linux-VuFindBeta


The first approach worked, the second approach failed.

We got the error "ourtheme.thm" could not be found in installation.php#112, ...., see below


We thought that both approaches should lead to the same results.


Are there conceptual problems with the second approach? Or were there just some mistakes in our execution of the second approach?

Which approach is recommended for future vufind2-updates?



Uncaught exception 'Exception' with message 'Cannot load theme:

ourtheme' in



VuFindTheme\\Initializer->init()\n#1 [internal function]:



call_user_func(Object(Closure), Object(Zend\\Mvc\\MvcEvent))\n#3



Object(Zend\\Mvc\\MvcEvent), Object(Closure))\n#4



Object(Zend\\Mvc\\MvcEvent), Object(Closure))\n#5


Zend\\Mvc\\Application->run()\n#6 {main}\n  thrown in /usr/local/vufind2/module/VuFindTheme/src/VuFindTheme/Initializer.php on line 192