Theme_support( 'html5' ) was called incorrectly. HTML5

Johnty · November 8, 2023, 4:53am

I have been using ClassicPress V2.0 since it became available.
I have installed every update available for ClassicPress and used the LazyPress theme
Everything worked fine until several updates ago I get this message when I use the lazyPress theme, and I have had to revert to the Twenty Eleven theme.
The message: Notice: Function add_theme_support( ‘html5’ ) was called incorrectly. HTML5 is the default Please see Debugging in ClassicPress for more information. (This message was added in version CP-2.0.0.) in /home/mid49380/public_html/wp-includes/functions.php on line 5874
I am not a programmer and have no idea how to fix whatever is causing this problem.
Please help me, regards John

ElisabettaCarrara · November 8, 2023, 9:03am

@viktor and @MattyRob does this have to do with that thing you did to deprecate previous versions of html?
It seems that.

Simone · November 8, 2023, 9:04am

Deprecation notice: Version 1.7 is the last version to support XHTML. HTML5 will be the default doctype. Make sure your theme does not use XHTML. Themes will no longer need to declare HTML5 support using add_theme_support( 'html5', array() ) function.

This is from ClassicPress 1.7.
If you want you can get rid of the deprecation notice by removing from cosmobit’s functions.php add_theme_support( 'html5' ,.....

MattyRob · November 8, 2023, 9:30am

This is all linked to the changes we made for better HTML5 compatibility by default:

github.com/ClassicPress/ClassicPress-v2

Remove XHTML for a More Consistent HTML5 Markup

ClassicPress:develop ← DangitRick:xhtml-excision

opened 05:03PM - 04 Sep 23 UTC

DangitRick

+1914 -2443

## Description This pull request includes many small changes intended to remove… XHTML markup in favor of HTML5 equivalents. ## Motivation and context HTML5 became the "next standard" for markup on the web back in 2007, with XHTML being obsolesced. By removing XHTML code from core, we are free to move forward with full HTML5 markup and practices, with more consistent code and less PHP to choose between markup alternatives. It also gets us closer to pages with clean markup that validates on the W3C's validator. ## What's Left to Do? I don't know JavaScript, so I did not modify any JS files, though many showed up when searching for "/>" for example. Posts still output closing slashes, such as `<hr />`, when self-closing elements are used. I also avoided touching files that were obviously part of third party packages, such as SimplePie or PHPmailer. ## How has this been tested? On both my local and live installations, everything appears to be working smoothly. Using a test site with content from FakerPress, the W3C validator's results went from a couple dozen errors and warnings down to just a few. ## Types of changes * Remove closing slashes from self-closing elements * Remove double-barreled boolean attributes in favor of their simpler forms (e.g., prefer `selected` over `selected="selected"` * Remove `current_theme_supports('html5')` and all logic related to it in favor of just using HTML5 * Remove `text/css` and `text/javascript` `type` attributes from `script` and `link` tags. * Remove assorted `role` attributes on HTML5 elements such as `nav` or `header` where the role is already implied by the markup * Remove `novalidate` attributes from forms to enable client-side browser-based validation, providing users with instant form feedback while saving on system resources

The _doing_it_wrong() call should only ever trigger if WP_DEBUG is true and that is not advised on production sites. It is unclear where this message is being see - is it on screen or in log files?

Either way, it is worth checking in wp-config.php file to make sure WP_DEBUG is not being used.

tradesouthwest · November 8, 2023, 6:32pm

@Johnty If you like the TwentyEleven theme then I have a child theme for it that is made specifically for ClassicPress. If you want to try it you can download at: Elevenwider Child Theme for Twentyeleven – ClassicPress Themes by TSW

system · November 10, 2023, 6:32pm

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.