Re: [VuFind-General] Disabling comments/tagging

[Demian K. <dem...@vi...>]

I expect that a stable VuFind 2.0 release will be out next month.  A couple of sites are already using development versions of the code in production successfully.  Unless you're planning on making deep, complex changes to the search system, I think you would be pretty safe to start experimenting with it now and then update to the final released 2.0 code in late June.

- Demian
________________________________
From: Chrispin Simasiku Sitali [lib...@gm...]
Sent: Friday, May 24, 2013 2:55 AM
To: Jay Roos
Cc: Demian Katz; vuf...@li...
Subject: Re: [VuFind-General] Disabling comments/tagging

Is Vufind2 stable enough to use in production?


On 23 May 2013 15:24, Jay Roos <ja...@gm...<mailto:ja...@gm...>> wrote:
That's what I did. Thanks.


On Thu, May 23, 2013 at 7:31 AM, Demian Katz <dem...@vi...<mailto:dem...@vi...>> wrote:
The easiest way is to adjust the recorddriver_tabs section to eliminate all references to comments – that will turn off the comments tab and thus make all comments-related functionality inaccessible.

- Demian

From: Jay Roos [mailto:ja...@gm...<mailto:ja...@gm...>]
Sent: Wednesday, May 22, 2013 11:45 PM
To: Demian Katz
Cc: vuf...@li...<mailto:vuf...@li...>
Subject: Re: [VuFind-General] Disabling comments/tagging

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...<mailto: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...<mailto:ja...@gm...>]
Sent: Wednesday, May 22, 2013 3:41 PM
To: vuf...@li...<mailto: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.



------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
_______________________________________________
VuFind-General mailing list
VuF...@li...<mailto:VuF...@li...>
https://lists.sourceforge.net/lists/listinfo/vufind-general




--
Charles Lwanga College of Education,
P. O. Box 660193,
Monze,
ZAMBIA.

Mobile: +26 0979 869471
SKYPE: Libsitali