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

Enhancement: Cleaning up and restyling jetpack related banner notices within wp-admin #3841

Merged
merged 7 commits into from
May 23, 2016

Conversation

jeffgolenski
Copy link
Member

@jeffgolenski jeffgolenski commented May 18, 2016

Enhancement: Cleaning up and restyling jetpack related banner notifications within wp-admin (but outside new jetpack dashboard) - match the core notification styles. Not altering current logic, just cleaning them up, visually. Will revisit these soon.

Connection Banner Before:
screen shot 2016-05-18 at 1 55 28 pm

Connection Banner After:
Adopts wp-admin core styles with some very slight, lightweight adjustments...

screen shot 2016-05-20 at 2 49 37 pm
screen shot 2016-05-20 at 2 52 27 pm

Manage Banner After
screen shot 2016-05-20 at 3 19 48 pm

screen shot 2016-05-20 at 3 23 32 pm

Connection Banner: cleaning up scss and verbiage changes for the
connection banner displayed within /wp-admin/plugins/
@jeffgolenski jeffgolenski changed the title Enhancement: Cleaning up and restyling jetpack related banner notifications within wp-admin Enhancement: Cleaning up and restyling jetpack related banner notices within wp-admin May 18, 2016
Management Banner: cleaning up styles and verbiage of the centralized
management banner that’s displayed in /wp-admin/ if the manage feature
is inactive.
ID Crisis Banner: Removing styling since it won't be used anymore. cc
@dereksmart
Jetpack Banners: cleaning un-needed scss and adopting more core styles.
Included removing some html elements and adding certain classes to
elements.
Connect Banner: testing different images & building out structure
Banner Notices: cleaning up code and removing images - they don’t work
well in the banners, as is.
<div id="message" class="updated jetpack-message jp-banner" style="display:block !important;">
<a class="jp-banner__dismiss" href="<?php echo esc_url( $dismiss_and_deactivate_url ); ?>" title="<?php esc_attr_e( 'Dismiss this notice and deactivate Jetpack.', 'jetpack' ); ?>"></a>
<div id="message" class="updated jp-banner">
<a href="<?php echo esc_url( $dismiss_and_deactivate_url ); ?>" class="notice-dismiss" title="Dismiss this notice."></a>
Copy link
Member

Choose a reason for hiding this comment

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

need to translate the title

- making sure titles of dismiss buttons are translatable
- ensuring out-going links are https
- writing proper php for to link to jetpack dashboard from within the
connection banner (learn more)
@dereksmart
Copy link
Member

Looks so much better! LGTM

@jeffgolenski jeffgolenski merged commit ad59dfa into master May 23, 2016
@jeherve jeherve deleted the enhance/style-connection-notices branch May 24, 2016 08:14
@jeherve jeherve restored the enhance/style-connection-notices branch June 15, 2016 12:16
@jeherve jeherve deleted the enhance/style-connection-notices branch June 15, 2016 12:17
jeherve pushed a commit that referenced this pull request Aug 20, 2019
The warning about Jetpack Protect's network activation warning is not dismissible.

It is also not pretty :)

Both have been problems since #3841.

* Use markup compatible with Core's notices.
* Hook some JS into Core's notice dismissal to handle changing saved state.
jeherve added a commit that referenced this pull request Aug 23, 2019
* Protect: Dismissible Network Activation Warning

The warning about Jetpack Protect's network activation warning is not dismissible.

It is also not pretty :)

Both have been problems since #3841.

* Use markup compatible with Core's notices.
* Hook some JS into Core's notice dismissal to handle changing saved state.

* Escape translations.

Co-Authored-By: Miguel Lezama <[email protected]>


Co-authored-by: Jeremy Herve <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants