Bug 23300 - Plugins display as permanently "DISABLED"
Summary: Plugins display as permanently "DISABLED"
Status: RESOLVED DUPLICATE of bug 23222
Alias: None
Product: Koha
Classification: Unclassified
Component: System Administration (show other bugs)
Version: Main
Hardware: All All
: P5 - low major (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-11 12:03 UTC by Andrew Isherwood
Modified: 2019-07-15 09:12 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Isherwood 2019-07-11 12:03:36 UTC
All plugins are currently displaying as "DISABLED".

This appears to be due to the use of the condition:

[% IF ( plugin.enabled ) %]

in plugins-home.tt, which was added in Bug 22053 and presumably worked then. As far as I can see, there is no property or method on the plugin object called "enabled", hence it always failing.

Recently an "is_enabled" method was added to the plugin object in Bug 21073, I'm guessing this is what the template should be using.
Comment 1 Katrin Fischer 2019-07-13 10:39:25 UTC
Hi Andrew,

is this a duplicate to bug 23222 or a side effect? (add depends?)
Comment 2 Andrew Isherwood 2019-07-15 09:12:13 UTC
It appears to be a duplicate, I failed to discover it before I logged this one, sorry, good find!

I'll close this one as a duplicate.

*** This bug has been marked as a duplicate of bug 23222 ***