This one is more or less a folow up to #2325 “How can we improve KANBOARD Plugins information?”
It would be great if you would tell oyur problems with particular Plugins here so that we can tryto find a solution (ask creator …) or at least warn other users that they might face off complications if they install those Plugins.
Ever heard the phrase, “Know enough to be dangerous”?
I know my code well enough to know someone took it, edited it not understanding it, and thought they could make something from it by changing a few things. Maybe they succeeded.
The source code:
Plugin.php is a dead giveaway, only I would ever name a variable “$wasmaster”!
To me, the concept of third-parties-based plug-ins (vs “modules” maintained in-tree in lockstep) is fundamentally flawed. They don’t always feel well-integrated, they overlap in featureset and have incompatibilities, they go unmaintained, etc.
I understand any app’s “core” maintainers wanting to externalize this code management cost and make it “somebody else’s problem”, but it’s a nightmare for users, as I’ve seen elsewhere (such as Firefox, WordPress, etc.). It boils down to https://pluginproblems.com
Somehow it works just fine on an instance using SQLite, but doesn’t work at all with one using MYSQL. Doesn’t even show on plugins page. Everything is the same but the database. Any idea ?
Yes. OK, some expertise required. A brief look into the debug log reveals:
2023-03-08 09:24:24] [critical] Subtaskdescription:
Unable to migrate schema for the plugin: Subtaskdescription => SQLSTATE[42000]:
Syntax error or access violation: 1101 BLOB, TEXT, GEOMETRY or JSON column 'due_description' can't have a default value
This is why the plugin doesn’t install. Obviously, the MySQL schema is faulty.
Edit the file Schema/Mysql.php and remove the part responsible for the problem.
$pdo->exec("ALTER TABLE `subtasks` ADD COLUMN `due_description` TEXT NOT NULL ");