search

contao / contao-manager

Contao Manager
GNU Lesser General Public License v3.0
85 stars 33 forks source link

Contao Manager 1.4.3: package list shows "unknown version" and outdated version updates #646

Closed Smurffson closed 3 years ago

Smurffson commented 3 years ago

Contao Manager 1.4.3 shows some packages as "unknown version" in menu "package". And on one it reports a wrong update version. In my current installation following packages are affected:

Bundle "terminal42/contao-password-validation" is installed in version 1.0.7 and CM shows me an available update to version 1.0.0.

I didn't upgrade my other Contao 4.x installations yet.

What I tried so far:

dp-designpilot commented 3 years ago

I have the same Problem, aschempp can you fix this ?

itnomic commented 3 years ago

Same problem on all my websites with Contao Manager 1.4.3. No Problems before update

soweit-ok commented 3 years ago

The same bug in all my installations since Contao-Manager update to 1.4.3. Update of individual bundles still works. If several bundles are updated at the same time, the database can no longer be updated with the install tool. It The log file then contains dbal fatal error messages (no database connection).

I tried to fix the dbal driver to version 12.1 in composer.lock. Because of this symfony bug in version 13.0. Unfortunately it was unsuccessful. I couldn't find a cause of the "Unknown Version" bug. The composer.lock file lists the correct installed version numbers. Packagist references and Github URLs are also correct.

It doesn't seem like a good idea to me that the Contao Manager update is forced and won't start otherwise. Why is it necessary? Therefore, all Contao installations are affected by every bug and, especially in the case of large projects with many installed bundles and individual solutions, the analysis can be time-consuming to determine whether the cause is wrong own code or a bug in the Contao core or a bug in an extension bundle.

mp-itconsulting commented 3 years ago

I also have the same problem since forced update to 1.4.3. I also think that is not the best idea or even required to force the update and otherwise refuse from starting. Update should be optional! There are other options in case an update is really required.

aschempp commented 3 years ago

Please be aware that this is only a display problem. Package installation is not affected, so any package-related isssues should be a separate ticket.

I tried to fix #637 which lead to this issue.

kgollmer commented 3 years ago

Just to be clear: will this issue affect updates I'm trying to run (install outdated versions if I tried to update a package)?

mlwebworker commented 3 years ago

No, is only a display problem.