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
Add a config option to metastore settings to stop forcing a redirect to the datasets view on dataset form submit.
Problem and Motivation
We have a redirect in metastore_admin.module that takes people back to the dataset view after saving a dataset form. This is quite difficult to disable/override, and in many cases may not be the desired behavior. For instance if using a draft workflow, the dataset author may not have permission to see that page at all.
Potential Benefits
More flexibility in user experience for different use cases.
Target Audience
End Users
Developers
Administrators
Other
Possible Implementation
Add a config option and a checkbox in one of the admin forms, check for this before adding the redirect in the submit function.
The text was updated successfully, but these errors were encountered:
Editors without access to the content overview page would need to rely on the local tasks menu to get to the datasets they manage. We don't currently expose these links in our decoupled frontend so would need to test this config with dkan_js_frontend uninstalled.
Feature Description
Add a config option to metastore settings to stop forcing a redirect to the datasets view on dataset form submit.
Problem and Motivation
We have a redirect in metastore_admin.module that takes people back to the dataset view after saving a dataset form. This is quite difficult to disable/override, and in many cases may not be the desired behavior. For instance if using a draft workflow, the dataset author may not have permission to see that page at all.
Potential Benefits
More flexibility in user experience for different use cases.
Target Audience
Possible Implementation
Add a config option and a checkbox in one of the admin forms, check for this before adding the redirect in the submit function.
The text was updated successfully, but these errors were encountered: