get_body_class() does not include page-{slug}-php

[westonruter]

I have a Glossary page whose slug is "glossary". I created a page-glossary.php to utilize the new WP 2.9 functionality. I was expecting that "page-glossary-php" to be listed among the classNames but instead "page-template-default" was included. Maybe this would better be manifested as a "page-slug-glossary" className just as there is a "page-id-XX".

All enhancements are punted to 3.0.

added page-slug-xxxxx as a class name for all pages, not just for pages with custom page template file.

The slug should get passed through sanitize_html_class() to ensure only valid characters are used, as is done for the other slug-based class names. See 11331.diff.

Passes slug through sanitize_html_class()

Same as 11331.diff, but with spaces added to calls in that function. Separate issue, sure, but it's localized, trivial, and one step towards coding standards compliance.

See #8446

I'm not sure about this. With this patch, we may be generating some very long class names, and I don't think we use slugs anywhere else in body|post_class.

We already support page template names and page IDs, we don't support post slugs for example, only post IDs.

(In [13468]) Add some whitespace to get_body_class(). props coffee2code. Clarify fallback parameter in sanitize_html_class(). see #11331

Replying to nacin:

I'm not sure about this. With this patch, we may be generating some very long class names, and I don't think we use slugs anywhere else in body|post_class.

I agree.

If you really need this, you have the 'body_class' filter.

Besides, you can add extra CSS from your page-glossary.php template:

<?php

function extra_styles() {
  wp_enqueue_style('glossary', get_bloginfo('stylesheet_directory') . '/glossary.css');
}
add_action('wp_print_styles', 'extra_styles');

get_header();

...