The main thing that the install script does is generate baseline Apache and SolrMarc configurations in your local directory. If you have customized any of those things, re-running
install might overwrite them. But if you're nervous, the best thing to do is make a backup of the "local" subdirectory of your install -- then you can diff the old versions against the new ones and be confident that nothing important was lost.
From: Brad Busenius [firstname.lastname@example.org]
Sent: Friday, February 22, 2013 4:10 PM
To: Demian Katz
Subject: Re: [VuFind-Tech] OAI import oddnesses
Thanks Demian! I had read the module documentation but didn't realize this would need to be a module. I appreciate your advice. I see that I will need to re-run the install script in order to do this. I'm a little nervous about doing that. Do I need to
On 2/22/13 1:37 PM, Demian Katz wrote:
To override code, you need to use a custom module rather than the local directory -- the custom module gives you your own namespace in which to write code, and your own module.config.php
where you can register your own objects in place of the default ones in the VuFind module. It's a bit more overhead than just replacing a file in a local directory (alas, given the nature of PHP, this was the best we could do), but it should meet your needs.
For more details, see:
If you still have questions, feel free to ask them here.
Yeah, I'm curios if it is possible to override the horizon.php file by creating a copy in /local
/module/VuFind/src/VuFind/ILS/Driver. On my first attempt it appears I cannot. Is the local directory only for config files or will it work for other
files as well?
On 2/22/13 9:57 AM, Tod Olson wrote:
I think you're quite right about not exploding on semicolons. *If* we VuFind::explode at all, it should be on " -- ".
Just to clarify something, as we're still getting used to the PHP and it's coming up in other contexts: if we want to locally override module/VuFind/src/VuFind/XSLT/Import/VuFind.php while testing the bug fix, can we just drop in a local/module/VuFind/src/VuFind/XSLT/Import/VuFind.php?
On Feb 22, 2013, at 9:01 AM, Demian Katz <email@example.com>
Instead of DOMDocument::createElement() better use:
Creating a new DOMText does encode the ampersand.
Thanks for figuring this out, David!
Tod, do you want to send me a patch to commit to master based on David's observations?
In the long term, I think you don't want to be exploding subject headings on semicolons (that's probably an artifact from some other metadata arrangement), but it would be nice to fix this bug while we're thinking about it.
Let me know if you need any more action on my part!
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
Vufind-tech mailing list