You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using Grav v1.7.45, Admin v1.10.45 and Flex Objects v1.3.6.
I am trying to enable Configuration for my flex object. Within my blueprint I have set a value for config.admin.router.actions.configure.path. The 'Configuration' button appears in the flex directory page in admin, however, the button leads to the base URL, not the expected path. I have followed the example
To replicate, I installed a fresh instance of Grav and Flex Objects plugin. I created a flex object in user/blueprints/flex-objects/test.yaml and set the configure path as instructed in the documentation.
I can manually access the configuration page with http://localhost/admin/test/configure, but not with the 'Configuration' button in admin.
Am I missing something?
The text was updated successfully, but these errors were encountered:
Currey
changed the title
Configuration button in admin links to base URL rather than specified admin.router.configure.path
Configuration button in admin links to base URL rather than specified admin.router.actions.configure.path
Mar 22, 2024
Using Grav v1.7.45, Admin v1.10.45 and Flex Objects v1.3.6.
I am trying to enable Configuration for my flex object. Within my blueprint I have set a value for
config.admin.router.actions.configure.path
. The 'Configuration' button appears in the flex directory page in admin, however, the button leads to the base URL, not the expected path. I have followed the exampleTo replicate, I installed a fresh instance of Grav and Flex Objects plugin. I created a flex object in
user/blueprints/flex-objects/test.yaml
and set the configure path as instructed in the documentation.I can manually access the configuration page with
http://localhost/admin/test/configure
, but not with the 'Configuration' button in admin.Am I missing something?
The text was updated successfully, but these errors were encountered: