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.

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

Admin: Update admin notices to use 'notice notice-error' class #7800

Open
wants to merge 3 commits into
base: trunk
Choose a base branch
from

Conversation

im3dabasia
Copy link

Trac ticket: https://core.trac.wordpress.org/ticket/50402

This PR addresses by updating admin error notices to use the notice notice-error classes instead of the legacy error class. This change aligns error notice styling with current WordPress standards and improves visual consistency across the admin interface.

Replaces legacy 'error' class with 'notice notice-error' in admin error notices for consistency with WordPress standards.
Copy link

github-actions bot commented Nov 14, 2024

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props im3dabasia1, audrasjb, joedolson.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Copy link

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

Copy link
Contributor

@audrasjb audrasjb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR. These changes look good to me.

Copy link
Contributor

@joedolson joedolson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are some cases here that shouldn't be changed. Adding a code comment that indicates why they aren't changed would probably be help for future PRs, though.

@@ -131,7 +131,7 @@ function show_blog_form( $blogname = '', $blog_title = '', $errors = '' ) {
$errmsg_blogname_aria = '';
if ( $errmsg_blogname ) {
$errmsg_blogname_aria = 'wp-signup-blogname-error ';
echo '<p class="error" id="wp-signup-blogname-error">' . $errmsg_blogname . '</p>';
echo '<p class="notice notice-error" id="wp-signup-blogname-error">' . $errmsg_blogname . '</p>';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In wp-signup.php, these classes are defined in the wpmu_signup_stylesheet function added to wp_head. They aren't part of the WP Admin style group. While we could change the styles in the function, removing the .error class is likely to break custom styles implemented by sites. Should probably revert this change and go back to .error in this file.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In keeping with the original purpose of the ticket, however, do remove font-weight: 600 from the .mu_register .error class.

@im3dabasia
Copy link
Author

@joedolson , I have removed the changes related to the back-compat files.

Please let me know if you have any further feedback or suggestions for improvements.

@im3dabasia im3dabasia requested a review from joedolson January 30, 2025 07:08
@joedolson
Copy link
Contributor

Thanks, @im3dabasia!

Still need to update the error classes used in wp-signup.php, per my comments on that file.

Copy link
Contributor

@joedolson joedolson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The classes in wp-signup.php need to use a class referenced in the generated CSS for that file; I recommend keeping .error but changing the styles to remove font-weight: 600.

@@ -131,7 +131,7 @@ function show_blog_form( $blogname = '', $blog_title = '', $errors = '' ) {
$errmsg_blogname_aria = '';
if ( $errmsg_blogname ) {
$errmsg_blogname_aria = 'wp-signup-blogname-error ';
echo '<p class="error" id="wp-signup-blogname-error">' . $errmsg_blogname . '</p>';
echo '<p class="notice notice-error" id="wp-signup-blogname-error">' . $errmsg_blogname . '</p>';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In keeping with the original purpose of the ticket, however, do remove font-weight: 600 from the .mu_register .error class.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants