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

verbesserte Usability bei Abhängikeiten und Meldung "don't install..." #542

Open
zonky2 opened this issue Apr 7, 2020 · 9 comments
Open
Labels
Milestone

Comments

@zonky2
Copy link

zonky2 commented Apr 7, 2020

verbesserte Usability bei Abhängikeiten und Meldung "don't install..."

Das Thema wurde auf Slack besprochen https://contao.slack.com/archives/CJT61P8R1/p1586246884061000

Bei Fehlermeldungen wie hier beschrieben https://community.contao.org/de/showthread.php?77635-Installationsprobleme-mit-Contao-4-9-Managed-Edition kommen (unbedarfte) User nicht weiter. Es gibt immer wiederkehrende Erklärungen, welche Einstellungen am CM vorgenommen werden müssen, damit die Installation bzw. Auflösung durch läuft.

Hier ist die Frage, wie das verbessert werden kann - Vorschläge:
Netzmacht:
Zwei Optimierungswünsche:

1.) Man kann auch nach dem Auswählen eines neuen Paketes auf Pakete aktualisieren klicken
2.a) Scheitert die Installation schlägt der CM vor es mit der Aktualisierung aller Pakete zu probieren (für den Fall, dass sie vorher nicht ausgewählt waren. )
2.b) Scheitert die Installation versucht der CM automatisch ein Update aller Pakete (bearbeitet)

zonky2: FAQ Button mit Link zu https://docs.contao.org/manual/de/installation/contao-manager/#haeufige-fragen-zum-contao-manager und Beschreibung zur Problemlösung

@fritzmg
Copy link
Contributor

fritzmg commented Apr 7, 2020

I also think that, in case of any errors (or just some identifiable errors?), the Contao Manager should offer the possibility to do a full composer update, including the latest changes, i.e. when you added a package, that would require a full composer update to be installed.

@fiedsch
Copy link

fiedsch commented Apr 7, 2020

Couldn't that (the full update) also be the default path as it is what most people (presumably) want anyway. (hope, I don't misunderstand the problem as I don't use the manager).

@fritzmg
Copy link
Contributor

fritzmg commented Apr 7, 2020

No, this would also update any other package.

@fiedsch
Copy link

fiedsch commented Apr 7, 2020

Yes, of course. But why would I regularly not want this. I was talking about a possible default---the option to only update a single package could also be there, but I fail to see why it has to be the default (which might be my lack of understanding 😨).

@fritzmg
Copy link
Contributor

fritzmg commented Apr 7, 2020

If I install a package via the Contao Manager, I don't expect any other package to be updated. Otherwise it would lead to unforeseen consequences.

@fiedsch
Copy link

fiedsch commented Apr 7, 2020

OK, so I always did it wrong and was lucky so far. Thanks @fritzmg

@fritzmg
Copy link
Contributor

fritzmg commented Apr 7, 2020

No, you did not do it wrong. If you wanted to update all packages, that's obviously fine ;).

@fiedsch
Copy link

fiedsch commented Apr 7, 2020

Most of the times I just wanted to add a package but did not mind if that updated all packages as a side effect (bc. updating all packages is what I would have done anyway at some later point). That was the base of my reasoning.

@aschempp
Copy link
Member

aschempp commented Jun 4, 2020

🤔 maybe we should offer an option to update all packages when installing one? Something like a dropdown (/dropup) on the "Apply" action?

@aschempp aschempp added this to the 1.3 milestone Jun 4, 2020
@aschempp aschempp modified the milestones: 1.3, 1.x Jul 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants