-
-
Notifications
You must be signed in to change notification settings - Fork 315
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
Updated from 3.0 to 3.2 and getting "No route matches [GET] "/admin/dashboard" #1244
Comments
Do other routes like |
Hi Thomas, The other routes render fine. Even It seems the issue is isolated to the Thanks in advance, David |
Is the solution maybe to re-introduce the mount point get method such as:
I haven't had a chance to try this (dependency issues), but I saw something similar in the |
This was referenced Nov 24, 2017
tvdeyen
added a commit
to tvdeyen/alchemy_cms
that referenced
this issue
Nov 24, 2017
Since 871e77e we allow to set a custom admin path (ie. `/backend` instead of `/admin`). The default is set to `/admin` and since the admin dashboard redirect rule from `/admin` to `/admin/dashboard` uses this value the redirect destination is a root path. This causes no problems, unless you mount Alchemy at some other path (`/cms` instead of just `/`). Because the redirect rule has a leading slash the Rails router does not take the mount path into account and redirects to `/admin/dashboard` instead of `/cms/admin/dashboard`. Closes AlchemyCMS#1244
tvdeyen
added a commit
to tvdeyen/alchemy_cms
that referenced
this issue
Nov 24, 2017
Since 871e77e we allow to set a custom admin path (ie. `/backend` instead of `/admin`). The default is set to `/admin` and since the admin dashboard redirect rule from `/admin` to `/admin/dashboard` uses this value the redirect destination is a root path. This causes no problems, unless you mount Alchemy at some other path (`/cms` instead of just `/`). Because the redirect rule has a leading slash the Rails router does not take the mount path into account and redirects to `/admin/dashboard` instead of `/cms/admin/dashboard`. Closes AlchemyCMS#1244
tvdeyen
added a commit
to tvdeyen/alchemy_cms
that referenced
this issue
Nov 24, 2017
Since 871e77e we allow to set a custom admin path (ie. `/backend` instead of `/admin`). The default is set to `/admin` and since the admin dashboard redirect rule from `/admin` to `/admin/dashboard` uses this value the redirect destination is a root path. This causes no problems, unless you mount Alchemy at some other path (`/cms` instead of just `/`). Because the redirect rule has a leading slash the Rails router does not take the mount path into account and redirects to `/admin/dashboard` instead of `/cms/admin/dashboard`. Closes AlchemyCMS#1244
tvdeyen
added a commit
to tvdeyen/alchemy_cms
that referenced
this issue
Nov 24, 2017
Since 871e77e we allow to set a custom admin path (ie. `/backend` instead of `/admin`). The default is set to `/admin` and since the admin dashboard redirect rule from `/admin` to `/admin/dashboard` uses this value the redirect destination is a root path. This causes no problems, unless you mount Alchemy at some other path (`/cms` instead of just `/`). Because the redirect rule has a leading slash the Rails router does not take the mount path into account and redirects to `/admin/dashboard` instead of `/cms/admin/dashboard`. Closes AlchemyCMS#1244
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I am upgrading from Alchemy 3.2 to 3.4.2. When I try to log in to the admin portal I get:
No route matches [GET] "/admin/dashboard
I have Alchemy mounted as:
I go to
/content/admin
(which previously worked fine to access the admin portal) and I see a 301 redirect to/admin/dashboard
The CMS pages are rending fine using their previous URLs like
/content/partners
. This issue only seems to affect the admin pages.I tried setting
Alchemy.admin_path = '/content/admin'
but that's worse, I getAlchemy::Page not found "/content/admin"
.I am using rails 4.2.8.
Should I set
admin_path
if I am pointing at/content
?From routes.rb:
Thanks in advance for all help upgrading.
David
The text was updated successfully, but these errors were encountered: