#25946 closed enhancement (fixed)
Twenty Fourteen: General code cleanup
Reported by: | obenland | Owned by: | |
---|---|---|---|
Milestone: | 3.8 | Priority: | normal |
Severity: | normal | Version: | 3.8 |
Component: | Bundled Theme | Keywords: | has-patch |
Focuses: | Cc: |
Description
Major development is done, now follows the polishing phase.
Lets round up all the bits and pieces that can be shaved off to make Twenty Fourteen in all regards the exemplary theme that it is expected to be.
Attachments (19)
Change History (56)
#9
@
11 years ago
Attached a patch.
- Remove
singular
body class when a page is set to be the front page. - Minor style tweaks.
#11
@
11 years ago
Minor style adjustment for navigations and a new lighter pattern-dark graphic which makes easier to change the background color of the featured image content.
#15
@
11 years ago
I've added my efforts at consistent code / function calls for the themes js files and added sample header/comment/documentation at the top where it was missing.
Patch 25946.10 added
#17
@
11 years ago
From what I can see, the standardized jQuery function wrapper in [26332] is possibly a change in behavior.
The new form is a self-invoking closure function with the advantage of being able to use $
in the function again.
The old form however is/was a short form of jQuery's ready() method (as in jQuery(document).ready(...)
) which is used to be sure that the contained code is run once the DOM is ready.
Now, I'm not an expert in jQuery or JS, but I wanted to bring it up so that the JS experts can maybe weigh in. There's some jQuery code in those calls that queries some DOM elements, so I could imagine that waiting for the ready
event is a good idea.
#21
@
11 years ago
In 25946.10.diff: filtering false
suggests the filter expects a boolean value, but we expect an array. Use an existing function instead.
#23
@
11 years ago
In 25946.12.diff: both style.css and ie.css use Genericons, so let's not forget to declare the dependancy.
#24
@
11 years ago
In 25946.13.diff: wp_enqueue_scripts
does not run in the admin, so twentyfourteen-lato
is not registered and thus not enqueued in twentyfourteen_admin_fonts
. Patch makes user Lato is enqueued in admin_print_scripts.
#25
follow-up:
↓ 29
@
11 years ago
Sorry for hi-jacking the thread like this. I'm looking at twentyfourteen_paging_nav
and there's some pretty interesting stuff there: html_entity_decode, wp_parse_str, WP_Rewrite -- definitely something I wouldn't expect a default theme to do, and also page
is the default base, but that can easily be changed, so instead of hard-coding it, we should use $wp_rewrite->pagination_base
.
However, given all that magic going on there, I think we should remove it all and write our own simple pagination function for Twenty Fourteen. One that simply uses get_pagenum_link()
. Another option would be to play nice and add support for WP-PageNavi, like many themes do. A third option would be to write a patch for a better paginate_links()
. Thoughts?
#26
@
11 years ago
In 25946.14.diff: Update editor stylesheet to reflect recent changes made in the main stylesheet.
#27
@
11 years ago
In 25946.15.diff, Tweak the vertical space for list items in the primary and footer widgets.
#28
in reply to:
↑ 22
@
11 years ago
Replying to kovshenin:
In 25946.11.diff prefix the genericons stylesheet handle.
IIRC, we decided to leave it un-prefixed to avoid duplication in case a third party uses Genericons (like Genericon'd or others).
#29
in reply to:
↑ 25
@
11 years ago
Replying to kovshenin:
A third option would be to write a patch for a better
paginate_links()
.
Yes, this. :) I was actually working on a patch for that during the WCLDN contributor day. But even if we'd move it into core, it would not be compatible with 3.6 and 3.7.
#33
@
11 years ago
- Resolution set to fixed
- Status changed from new to closed
Please open new tickets for new issues.
Remove unused class name.