necessity of changing plugin itself and plugin update issues

[MrDys]

CODEBASE-33: In order to add some info to solr.yml, I had to make changes in the blacklight plugin:

I didn't want to add my vars to blacklight.rb, I wanted to make a separate class to load the stuff. (I called it display_fields.rb)

I couldn't do this at the level of my rails app - it didn't work.

I had to change the plugin: add lib/display_fields.rb and change init.rb

When Vernon was trying to make some local mods that involved init.rb, he ran into the same problem. See blacklight-dev list emails from Vernon and me week of 3/9/2009.

Ideally, sites would be able to make these sorts of changes and not have to be in the plugin itself. Why? A1: we at Stanford, for whatever reason, have been unable to run the following:

script/plugin update blacklight
script/plugin update (full svn url to blacklight)

the only thing that has worked is

script/plugin update --force (full svn url to blacklight)

the later would step on local mods to the plugin, no?

[MrDys]

Original reporter: ndushay

[MrDys]

: Closing as we've mostly resolved the display fields configuration issues and the plugin installation issues are separate and I believe on Bess's list.