From: Jay R. <ja...@gm...> - 2013-05-23 03:45:32
|
I managed to kill comments by editing module.config.php, but I'm not sure I did it the right way. How should it be done? On Wed, May 22, 2013 at 2:46 PM, Demian Katz <dem...@vi...>wrote: > For comments, if you are using VuFind 2.0, you can disable the comments > tab through the module.config.php – that’s relatively easy (let me know if > you need more specific details and I can look them up). In 1.x, you’ll > have to do theme hacks.**** > > ** ** > > For tags, in either 1.x or 2.x, it’s going to take some theme changes to > get rid of them – they’re in quite a few different places. If you’re going > to go to all that trouble (at least if you’re working with the 2.x code, > since it will continue to evolve), it might make sense to implement a > mechanism to disable them from configuration so that we can get the feature > into the main codebase and it will continue to work properly in the future > as more things get added as well. If you’re interested in doing that, I’d > be happy to discuss my thoughts on how to make it happen.**** > > ** ** > > - Demian**** > > ** ** > > *From:* Jay Roos [mailto:ja...@gm...] > *Sent:* Wednesday, May 22, 2013 3:41 PM > *To:* vuf...@li... > *Subject:* [VuFind-General] Disabling comments/tagging**** > > ** ** > > We'd like to disable comments and tagging. I see a couple related issues > in jira that are unresolved.**** > > ** ** > > Is there a sledgehammer way to disable them?**** > > ** ** > > The worst case I'm thinking is that I'll have to heavily edit the them to > disable those features.**** > |