Make WordPress Core

Opened 17 years ago

Closed 17 years ago

Last modified 3 months ago

#10795 closed defect (bug) (fixed)

Call to screen_icon() in incorrect place in wp-admin/tools.php

Reported by: johnbillion's profile johnbillion Owned by:
Milestone: 2.9 Priority: low
Severity: trivial Version: 2.8.4
Component: Administration Keywords: has-patch
Focuses: Cc:

Description

screen_icon() should come after the opening <div class="wrap">

Attachments (1)

10795.patch (369 bytes) - added by johnbillion 17 years ago.

Download all attachments as: .zip

Change History (15)

@johnbillion
17 years ago

#1 @johnbillion
17 years ago

  • Keywords has-patch added

Patch

#2 @azaozz
17 years ago

  • Resolution set to fixed
  • Status changed from new to closed

(In [11940]) screen_icon() after <div class="wrap">, props johnbillion, fixes #10795

#3 @azaozz
17 years ago

  • Milestone changed from Unassigned to 2.9

@wildworks commented on PR #10909:


3 months ago
#5

  • Copy all icons, but check whether the public field is true in the icon registry.
  • When copying icons, if the public field is not true, do not copy the icon. Additionally, remove icons not marked as 'public' => true from the manifest.php file.

Perhaps the latter approach is ideal if we don't want to ship internal icons entirely into core, but it may be a bit more complicated. What do you think?

@mcsf Since we're getting close to the Beta 1 release and the former approach is simpler, I’ve committed 970944b using that approach. I’d appreciate your thoughts.

@mcsf commented on PR #10909:


3 months ago
#6

@mcsf Since we're getting close to the Beta 1 release and the former approach is simpler, I’ve committed 970944b using that approach. I’d appreciate your thoughts.

Sorry, I thought I had submitted a reply but apparently not. Yes, that's what I would prefer!

@wildworks commented on PR #10909:


3 months ago
#7

Update:

  • 7b941e456b0c4e7e9603c13c6b8ee27f75cc8d82: I skipped the failing tests because there are no public icons in manifest.php yet. Once the Gutenberg commit hash is updated, we'll be able to re-enable the skipped tests. At first, I thought about registering a mock icon, but after reading this comment, I realized that that approach wasn't the right one.
  • 15a38c31b97e5988027998e2319e05e48d1434f9: I added a ticket tag.

@mcsf commented on PR #10909:


3 months ago
#8

  • 7b941e4: I skipped the failing tests because there are no public icons in manifest.php yet. Once the Gutenberg commit hash is updated, we'll be able to re-enable the skipped tests. At first, I thought about registering a mock icon, but after reading this comment, I realized that that approach wasn't the right one.

Awesome, thanks. For the record, I just tested building WordPress with an updated Gutenberg ref, removed the tests' skip instructions, and I can confirm that the tests pass with the right manifest. 👍

@mcsf commented on PR #10909:


3 months ago
#9

I think we should be good to go. What else is missing for this initial commit?

@mcsf commented on PR #10909:


3 months ago
#10

It looks almost good, but I overlooked an important point: the text domain of the icon in the manifest.php file is gutenberg, so it will not be translatable in core. Would it be difficult to remove this text domain during the build process?

Great point. Will explore this after a call I'm on!

@wildworks commented on PR #10909:


3 months ago
#11

@mcsf, I think I've probably addressed all of that, but feel free to update!

@mcsf commented on PR #10909:


3 months ago
#12

@mcsf, I think I've probably addressed all of that, but feel free to update!

Oh, I didn't realise! I only realised you had already done this when I tried to push and had merge conflicts. 😅 In any case, thanks! Looks exactly like what I had.

@mcsf commented on PR #10909:


3 months ago
#13

Sorry for the confusion! But I think this PR is ready 👍

P.S. I'm planning to make some adjustments to how manifest.php works to avoid shipping unnecessary icon sets in core. I'll be submitting a PR in Gutenberg soon.

I wanted to get this big patch committed once and for all, but I have since reviewed your manifest.php PR, so this is a heads-up that I'll commit a follow-up to remove the ! ( $icon_data['public'] ?? false ) guard.

@wildworks commented on PR #10909:


3 months ago
#14

this is a heads-up that I'll commit a follow-up to remove the "! ( $icon_datapublic? ?? false )" guard.

Thank you! I was going to let you know that too 😄

Note: See TracTickets for help on using tickets.