app/console doctrine:cache:clear contao.cache is not working

[ghost]

Issue by @WolfNik
May 26th, 2017, 14:45 GMT

installed managed edition but app/console doctrine:cache:clear contao.cache is not working, there is no console under app/ while I entered 3 times wrong password on install tool

[ghost]

Comment by @xchs
May 26th, 2017, 14:51 GMT

You have to run the scripts via vendor/bin/*, e.g.

vendor/bin/contao-console cache:clear

[ghost]

Comment by @WolfNik
May 26th, 2017, 15:02 GMT

that worked as a sudo and afterwards setting the ownership new.

Please change this on the error-message

[ghost]

Comment by @aschempp
May 26th, 2017, 15:21 GMT

What error message?

[ghost]

Comment by @WolfNik
May 26th, 2017, 15:23 GMT

When install is blocked it says please run: app/console doctrine:cache:clear contao.cache
(just enter 3 time a wrong password at the install screen)

This is not working.

vendor/bin/contao-console cache:clear was working but had to run as sudo and afterwards do a chown on the contao to the web-user in my case www-data:www-data

[ghost]

Comment by @aschempp
May 26th, 2017, 15:25 GMT

What do you mean by "install is blocked"? I have never seen such a message.

[ghost]

Comment by @WolfNik
May 26th, 2017, 15:28 GMT

install the managed edition, after installing and login go back to /contao/install.
Then you are asked for the install password.
Type 3 times a wrong one.
Then reload /contao/install again.
Now it says: Please run app/console doctrine:cache:clear contao.cache

This was not working for me

[ghost]

Comment by @aschempp
May 26th, 2017, 15:31 GMT

You're right, very strange. I have no idea why this command should fix the issue anyway :D

[ghost]

Comment by @WolfNik
May 26th, 2017, 15:34 GMT

Best solution would be to put an option to the system settings. But this command was not helpful and you find no advice when you search in google. So as a first step change the message to something working.

[ghost]

Comment by @leofeyer
May 30th, 2017, 09:49 GMT

This is actually just another reason why we should have a bin/console entry point.

The error message is correct for the SE but not for the ME. @contao/developers /cc

[ghost]

Comment by @leofeyer
July 13th, 2017, 17:09 GMT

As discussed in Mumble on July 13th, we should use a simple file locking similar to the Lexik maintenance bundle.

[ghost]

Comment by @srhinow
November 4th, 2017, 02:04 GMT

Contao 4.4.7
PHP 7.1

Das funktioniert bei mir für die Standart-Edition genauso wenig. Er rödelt zwar kurz nach dem Befehl aber die Block-Fehlermeldung bleibt die selbe.
Wenn ich den Befehlt mehrmals ausführe kommt auch immer:
% bin/console doctrine:cache:clear contao.cache Clearing the cache for the contao.cache provider of type Doctrine\Common\Cache\FilesystemCache
Aber die Sperre bleibt bestehen.

Auch was in der Anleitung (https://docs.contao.org/books/manual/current/de/01-installation/contao-installieren.html#das-contao-installtool) steht funktioniert nicht.

[ghost]

Comment by @fritzmg
November 4th, 2017, 11:58 GMT

@srhinow what the messages does not tell you is that the bin/console of Symfony runs in the dev environment by default (see bin/console#L18). Unlike in the Contao Managed Edition, where the contao-console runs in the prod environment by default. Thus if you want to unlock the Install Tool for the prod environment you actually have to run

bin/console doctrine:cache:clear contao.cache --env=prod

(or -e=prod).

If you want the bin/console to be run in the prod environment by default, then you have to set the SYMFONY_ENV environment variable (for the PHP CLI) to prod.

See also contao/core-bundle#1088

[ghost]

Comment by @srhinow
November 4th, 2017, 17:07 GMT

i think that i have the Standart-edition and i try all of eny comands with --env=prod and without as sudo and without.
Where is the SYMFONY_ENV -vaiable? Why can i not reset the install-pw in eny environment?
What is the different between standart-edition and the managed-edition. I just did want a current Contao 4 installation anymore.

[ghost]

Comment by @fritzmg
November 4th, 2017, 17:34 GMT

i think that i have the Standart-edition and i try all of eny comands with --env=prod and without as sudo and without.

Are you sure you have used the following command:

bin/console doctrine:cache:clear contao.cache --env=prod

This works as far as I have tested.

Where is the SYMFONY_ENV -vaiable?

It is an environment variable set by your operating system.

What is the different between standart-edition and the managed-edition. I just did want a current Contao 4 installation anymore.

If you just want Contao, you are probably better off with the managed edition. But that depends on your specific requirements.

[leofeyer]

Fixed in 828addd.

[aschempp]

Shouldn't the file be stored in the cache directory? I mean it's totally fine to remove the install lock if someone removes the cache? Or are we intending to allow locking of the install tool to make it unusable in general?

[leofeyer]

The latter. Just like the maintenance lock file, which we have moved out of the cache directory already for the exact same reason.