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

Update InstallCommand.php #700

Closed
wants to merge 1 commit into from
Closed

Update InstallCommand.php #700

wants to merge 1 commit into from

Conversation

SignetPlanet
Copy link

New install (and new to asgard), installer referred to going to /backend which failed. Then I found in the bugs history someone else found this and the solution was to go to /en/backend. If I go to the main front page it showed the correct link. Figured it should also be in the console installer to prevent confusion.

Referenced old path to the admin backend
@nWidart
Copy link
Member

nWidart commented Apr 18, 2019

I think this is an issue with a package, which isn't redirecting properly.

@SignetPlanet
Copy link
Author

Not sure what you are saying. This is hardcoded in this file and I changed it to reflect past changes that didn't catch this.

@nWidart
Copy link
Member

nWidart commented Apr 20, 2019

I'm saying it shouldn't be in this file, and that the redirect should happen automatically.

@SignetPlanet
Copy link
Author

No redirect happened. I just get error messages immediately after installing. Until that is fixed why not merge this change of the console's outputted message so a new user isn't confused when they install it and see wrong/broken info displayed. If I instead go to the front end it has a correct link to take me to backend. But once in backend the links at the top right also give links without /en/ so they break as well giving me error pages.

@SignetPlanet
Copy link
Author

Oh, I should mention it is a plain install of Asgard,U didn't install any other packages. It just gives me a bunch of errors right after installing.

@nWidart
Copy link
Member

nWidart commented Jul 6, 2019

This is an error with the package handling localization. We don't want to hardcode a locale there, I believe.

@nWidart nWidart closed this Jul 6, 2019
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

Successfully merging this pull request may close these issues.

None yet

2 participants