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.

Sign up for GitHub

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

Mention dual-admin transitory period in the backend customisation guide #141

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Mention dual-admin transitory period in the backend customisation guide #141

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions docs/customization/customizing-the-backend.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,22 @@ needs-diataxis-rewrite: true

This guide will teach you how to customize the Solidus admin panel.

## Transitioning from Spree::Admin to SolidusAdmin

Please note that currently there are two different admin engines running in parallel:

1. `solidus_backend` as required by default from the `solidus` gem, under the namespace `Spree::Admin`
2. `solidus_admin` as installed by default for new stores since solidus v4.3 and uses the namespace `SolidusAdmin`

SolidusAdmin routes have preference over Spree::admin if the following conditions are met:

1. The `Show Legacy UI` button is switched off at the bottom of the admin sidebar
2. The resource's action is implemented in SolidusAdmin
3. The routes are drawn and not excluded by the `SolidusAdmin::Config['enable_alpha_features']` flag

During this transitory period make sure you follow instructions that matches the actual admin engine being
used for the particular resource.

## Designing your feature

When adding a feature to the backend UI, it's important that you spend some time designing the ideal
Expand Down
16 changes: 16 additions & 0 deletions versioned_docs/version-4.3/customization/customizing-the-backend.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,22 @@ needs-diataxis-rewrite: true

This guide will teach you how to customize the Solidus admin panel.

## Transitioning from Spree::Admin to SolidusAdmin

Please note that currently there are two different admin engines running in parallel:

1. `solidus_backend` as required by default from the `solidus` gem, under the namespace `Spree::Admin`
2. `solidus_admin` as installed by default for new stores since solidus v4.3 and uses the namespace `SolidusAdmin`

SolidusAdmin routes have preference over Spree::admin if the following conditions are met:

1. The `Show Legacy UI` button is switched off at the bottom of the admin sidebar
2. The resource's action is implemented in SolidusAdmin
3. The routes are drawn and not excluded by the `SolidusAdmin::Config['enable_alpha_features']` flag

During this transitory period make sure you follow instructions that matches the actual admin engine being
used for the particular resource.

## Designing your feature

When adding a feature to the backend UI, it's important that you spend some time designing the ideal
Expand Down
16 changes: 16 additions & 0 deletions versioned_docs/version-4.4/customization/customizing-the-backend.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,22 @@ needs-diataxis-rewrite: true

This guide will teach you how to customize the Solidus admin panel.

## Transitioning from Spree::Admin to SolidusAdmin

Please note that currently there are two different admin engines running in parallel:

1. `solidus_backend` as required by default from the `solidus` gem, under the namespace `Spree::Admin`
2. `solidus_admin` as installed by default for new stores since solidus v4.3 and uses the namespace `SolidusAdmin`

SolidusAdmin routes have preference over Spree::admin if the following conditions are met:

1. The `Show Legacy UI` button is switched off at the bottom of the admin sidebar
2. The resource's action is implemented in SolidusAdmin
3. The routes are drawn and not excluded by the `SolidusAdmin::Config['enable_alpha_features']` flag

During this transitory period make sure you follow instructions that matches the actual admin engine being
used for the particular resource.

## Designing your feature

When adding a feature to the backend UI, it's important that you spend some time designing the ideal
Expand Down