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

BUG: logout and new login required after installation #52

Closed
creative-resort opened this issue Nov 24, 2019 · 6 comments
Closed

BUG: logout and new login required after installation #52

creative-resort opened this issue Nov 24, 2019 · 6 comments

Comments

@creative-resort
Copy link

creative-resort commented Nov 24, 2019

After installing the plugin via composer for Neos 5.0.4 with demo site, Flow 6.0.5, PHP 7.3 and after flushing the cache,
a still logged in user will see a re-login form overlay after clicking on the yoast parameter tab (right sidebar).
Logging in here, doesn't allow access to the Yoast tab, however and the login form is displayed again and again.
Reloading the page in the browser shows, that the user is logged in, as other areas can be accessed without a problem.

Only after explicitly logging out and in again, the Yoast parameters tab is accessible.

@Sebobo
Copy link
Collaborator

Sebobo commented Nov 25, 2019

Hi,

thanks for creating the issue!

I know about this problem but I'm not sure if I can actually solve it in this package.
Currently the only way to prevent this is to flush the session cache after installation. Until there is a good solution I will add this to the readme for now.

@creative-resort
Copy link
Author

Ok. 😄
Maybe someone from the Neos core team has an idea.
There probably even are other extensions, that face a similar issue and already have a solution.
@skurfuerst Who is the right person to ask?

@Sebobo
Copy link
Collaborator

Sebobo commented Nov 25, 2019

I am from the core team ;)
And I already discuss it with the others.
Right now there is no simple solution, so I will create an issue for the core and link those.

@Sebobo
Copy link
Collaborator

Sebobo commented Nov 25, 2019

You can do the following after the first installation on production:

./flow flow:cache:flushone Flow_Session_Storage    
./flow flow:cache:flushone Flow_Session_MetaData

@Sebobo
Copy link
Collaborator

Sebobo commented Nov 25, 2019

There is actually a shorthand command for this use case when the behaviour was changed at the time:

./flow flow:session:destroyAll

@Sebobo
Copy link
Collaborator

Sebobo commented Nov 25, 2019

@Sebobo Sebobo closed this as completed Jun 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants