-
Notifications
You must be signed in to change notification settings - Fork 38
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
[UX] System updates form: Merge the manual updates section into the main updates table #5085
Comments
PR up for review: backdrop/backdrop#3621 PS: I've cleaned up some bits of the code that we still assuming that we have separate sections for enabled/disabled modules - we now have a dedicated "Project status" column in the tableselect for that. |
I think this is an improvement, but I have some suggestions for improved text. I'll do the code review first. |
@jenlampton do you mind moving the discussion for this in #5089 instead? I feel that it might get really long 😅 |
...considering that:
Can we then please not block this UI improvement over the terminology clarification? |
Sorry @klonos, I hadn't seen (or forgotten about) the other issue. |
I like this suggestion. When there are several updates the core manual update can get lost further down the page. With this approach and the absence of a checkbox and the additional more text it brings the information for quickly to attention. Since the update settings have been set to not self-update, it's good to quickly see if a new update is available. |
Tested the PR and left comment with the PR. |
Thanks for testing @izmeez 🙏🏼 ...setting this to NW, to work on the issue you discovered in the PR. FTR, here's the issue for the benefit of others in this thread:
|
Yeah, that won't be able to be tested on the PR sandbox - you'll need to test that on your local. ...although, we could manually set edit: I've filed #6279 in order to explore ways to mock the backdrop core version, but only within the context of PR sandboxes |
...also, this PR introduces custom JS for the more/less toggle, which we don't need if #5090 gets merged. If this change here gets merged first, we'll need to update the PR over in #5090 to remove the custom JS we are introducing here, and instead use a more/less toggle based on a |
The form under
admin/config/system/updates
seems too busy when the "Manual updates" option is disabled, having two sections/tables, and some help text in between:How about something like this instead?:
So basically:
The text was updated successfully, but these errors were encountered: