Custom /admin route

[asctime]

Hi there,

With the current overlap between solidus_backend and solidus_admin
it seems very difficult to reliably remap the entire asset to a different folder

For example (in 4.4.6) my understanding is it should be a simple matter in routes.rb
mount SolidusAdmin::Engine, at: '/_foobar', constraints...
prior to mount Spree::Core::Engine, at: '..whatever..'

This does not seem to work correctly. 'admin' still opens normally and '/_foobar' is 404. Also after clear-clobber, contradicting route table output when checked from command prompt:

mount SolidusAdmin::Engine, at: '/_foobar'
rails routes shows /_foobar
yet:
/admin works
/_foobar may 404 or render with broken assets depending on route interception

We are currently option testing and would like admin relocated (rather than mirrored/aliased) to custom loc to avoid exposing legacy scanner-targeted default paths in production routing.

Any suggestions?

[jarednorman]

The new admin (solidus_admin) is still a work in progress and in investigating I found some issues with mounting it at a different path:

1. /admin keeps responding to solidus_backend:

   The legacy backend draws its routes directly into Spree::Core::Engine.routes, so get "/admin" is always present regardless of where (or whether) SolidusAdmin::Engine is mounted. What you're seeing at /admin may be solidus_backend, not SolidusAdmin.

2. /_foobar 404s (cookie constraint):

   The install generator adds a constraint tied to the solidus_admin cookie, which is intended to toggle between the two admins at the same path. If your browser has a solidus_admin=false cookie from a previous session, the constraint blocks /_foobar entirely and I think you'll get a 404.

3. Broken functionality at /_foobar (hardcoded paths in SolidusAdmin):

   Even when the engine renders correctly at the custom path, several things break because /admin is hardcoded in the engine itself:

   • admin/app/components/solidus_admin/ui/forms/address/fields/country_and_state/component.js:9: a Stimulus controller fires fetch('/admin/countries/${countryId}/states') with an absolute hardcoded path, so the country/state dropdown on address forms
     will always request /admin/... regardless of mount point
   • admin/lib/solidus_admin/configuration.rb:189: the default logout_link_path is "/admin/logout"
   • admin/lib/solidus_admin/configuration.rb:88,151: navigation active-state matching checks path.start_with?("/admin/products/"), so nav items won't highlight correctly
   • admin/config/routes.rb:24: a route constraint checks request.path != "/admin/products/new", which is wrong at any other mount point

There's definitely some work that could be done support a new mountpoint, but I don't know if that's necessarily a priority right now because using SolidusAdmin must be in conjunction with solidus_backend to get complete functionality currently. When we get to the point that you could run only SolidusAdmin, fixing these issues becomes much more of a priority.

[asctime]

@jarednorman Thank you for your thorough examples.

Yes I was starting to really suspect this was indeed the status .. but best to keep an open mind on such things until confirmed.

NW think we can address this other ways in meantime, don't want to be fighting the framework ha ha
Thanks again for taking the time to investigate and explain what's happening under the hood.