Skip to content
This repository has been archived by the owner on Nov 16, 2021. It is now read-only.

Unsupported modules after fresh install #111

Open
andretux opened this issue Nov 17, 2019 · 1 comment
Open

Unsupported modules after fresh install #111

andretux opened this issue Nov 17, 2019 · 1 comment

Comments

@andretux
Copy link

Hi,
Today I installed Acquia Lightning with composer on my own server. I used Postgres database as MySQL did not work (It kept on jumping back to install.php after installation)
After successful installation, I went to the Reports -> Status report menu and it indicates that there was 1 Error and 1 Warning.
The warning is due to the Media Library Experimental module

The error indicated that there is at least one module that is unsupported. So I clicked on the "Unsupported release" link in the error message.
It took me to the Update page and listed 3 modules:

  • Media entity Instagram : installed version 8.x-2.0-alpha2, Recommended version 8.x-2.0
  • Media entity Twitter : installed version 8.x-2.0-alpha3, Recommended version 8.x-2.1
  • Simple OAuth (Unsupported) : Installed version 8.x-3.16, Recommended version 8.x-4.3

So I installed the updates and the system broke, complaining about missing classes. Seemed the Simple OAuth had problems (It did warn that the new version might not be backward compatible.)

So I removed it via composer and installed it again. Solved that issue.

But then Media entity instagram complained about a missing class when I go to the Status report. I tried to remove it and install it again, but that did not work.

Eventually, I dropped my database and started from scratch.

So now I have the installation working, but with these errors and the 3 modules that is listed to be updated.

Should I just leave them and when will I know to update them. Or should I only do updates via composer?

Thanks
Andre Truter

@phenaproxima
Copy link
Collaborator

phenaproxima commented Dec 8, 2019

Hi Andre, updates should be handled only via Composer. Lightning has constraints to ensure that incompatible modules are not installed.

I wouldn't worry too much about what the status page thinks -- Drupal core can be somewhat strict about that, but there is quite a bit more leeway in the real world. We do update modules in Lightning as often as possible; sometimes we will keep an old version around due to incompatibilities with other modules Lightning ships, which annoys the status page, but at least doesn't break your site.

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

No branches or pull requests

2 participants