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
Nach Update von 4.13.16 auf 4.13.17 wird der Maintenance Modus nicht beendet #767
Comments
Korrekt, der Maintenance-Mode kann wie von planepix beschrieben beendet werden. Jedoch sind der Wartungsmodus und die DB-Migration weiterhin nicht verfügbar (siehe https://contao.slack.com/archives/CK4J0KNDB/p1678898132327549) |
Likely fixed by contao/contao#5879 |
Closing as this is not a bug in Contao Manager but in Contao (but thanks for reporting @planepix!) |
Closed
leofeyer
pushed a commit
to contao/contao
that referenced
this issue
Mar 16, 2023
Description ----------- In #5795 we added the `--queue` option to the `contao:crawl` command. However, we also defined the shortcut `q` for this option - which unfortunately is already used for the global `--quiet` option, thus resulting in the following error: ``` $ vendor/bin/contao-console contao:crawl --help 18:32:59 CRITICAL [console] Error thrown while running command ""contao:crawl" --help". Message: "An option with shortcut "q" already exists." ["exception" => Symfony\Component\Console\Exception\LogicException^ { …},"command" => ""contao:crawl" --help","message" => "An option with shortcut "q" already exists."] An option with shortcut "q" already exists. ``` This also breaks the Contao Manager since this error also occurs when running `list --format=json`: ``` $ vendor/bin/contao-console list --format=json 18:34:55 CRITICAL [console] Error thrown while running command "list --format=json". Message: "An option with shortcut "q" already exists." ["exception" => Symfony\Component\Console\Exception\LogicException^ { …},"command" => "list --format=json","message" => "An option with shortcut "q" already exists."] An option with shortcut "q" already exists. ``` This PR removes the shortcut from the option. This will likely fix contao/contao-manager#767 (and related issues with the Contao Manager). Commits ------- 975aa01 remove the q shortcut from contao:crawl a603251 fix tests
leofeyer
pushed a commit
to contao/core-bundle
that referenced
this issue
Mar 16, 2023
Description ----------- In #5795 we added the `--queue` option to the `contao:crawl` command. However, we also defined the shortcut `q` for this option - which unfortunately is already used for the global `--quiet` option, thus resulting in the following error: ``` $ vendor/bin/contao-console contao:crawl --help 18:32:59 CRITICAL [console] Error thrown while running command ""contao:crawl" --help". Message: "An option with shortcut "q" already exists." ["exception" => Symfony\Component\Console\Exception\LogicException^ { …},"command" => ""contao:crawl" --help","message" => "An option with shortcut "q" already exists."] An option with shortcut "q" already exists. ``` This also breaks the Contao Manager since this error also occurs when running `list --format=json`: ``` $ vendor/bin/contao-console list --format=json 18:34:55 CRITICAL [console] Error thrown while running command "list --format=json". Message: "An option with shortcut "q" already exists." ["exception" => Symfony\Component\Console\Exception\LogicException^ { …},"command" => "list --format=json","message" => "An option with shortcut "q" already exists."] An option with shortcut "q" already exists. ``` This PR removes the shortcut from the option. This will likely fix contao/contao-manager#767 (and related issues with the Contao Manager). Commits ------- 975aa015 remove the q shortcut from contao:crawl a6032518 fix tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ich habe auf die 4.13.17 aktualisiert. Beim Aufruf, die Datenbank zu aktualisieren, wird der Hinweis „Service unavailable” ausgegeben.
Sprich der Maintenance-Modus wird nicht beendet…
Unter „/vars” liegt dann „maintenance.html”. Die habe ich manuell gelöscht; danach konnte das Backend wie das Frontend wieder aufgerufen werden.
The text was updated successfully, but these errors were encountered: