Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Couldn't install plugin" after updating from Craft 2 #4

Closed
JayBox325 opened this issue Feb 18, 2019 · 7 comments
Closed

"Couldn't install plugin" after updating from Craft 2 #4

JayBox325 opened this issue Feb 18, 2019 · 7 comments

Comments

@JayBox325
Copy link

  • Plugin version: 3.0.5.2
  • Craft version: 3.1.12
  • PHP version: 7.1.12
  • Database driver & version:

Describe the bug
After updating from Craft 2 site that used LinkVault to Craft 3, I have re-installed the Craft 3 version of LinkVault. The plugin installs perfectly via composer, however, when I click 'install' in the CMS I get "Plugin couldn't be installed".

@benjaminkohl
Copy link
Contributor

Do you see any errors in your error log pertaining to the failed installation?

@JayBox325
Copy link
Author

Exception: SQLSTATE[42S22]: Column not found: 1054 Unknown column ‘settings’ in ‘field list’
The SQL being executed was: SELECT `id`, `settings`, `handle`
FROM `craft_plugins`
WHERE (`handle`=‘linkVault’) AND (`version` < ‘3.0.0’)

@benjaminkohl
Copy link
Contributor

Thanks. May I have the stack trace that accompanied that error so I can figure out where it is taking place in the code?

@JayBox325
Copy link
Author

It appears that Craft 3 deletes the settings line in the SQL tables when it upgrades from Craft 2. So LinkVault looks for a line in the database that no longer exists.

@benjaminkohl
Copy link
Contributor

The settings column existed in Craft 3 but has apparently been removed in Craft 3.1 but I am having trouble tracking down a proper upgrade guide on how this should be handled if the plugin needs to make the jump from Craft 2 straight to Craft 3.1. I'm looking into it.

@JayBox325
Copy link
Author

No worries, we resolved it by adding the settings line back into the database while we installed LinkVault and just dropped it afterwards. At least we got to the bottom of it. Good luck!

@benjaminkohl
Copy link
Contributor

Ok, that is what I was just about to recommend, actually. I'm glad that worked! I'll add some additional checks to the upgrade process for Link Vault so others don't run into the same issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants