Carolina Nymark

Perhaps a more general warning for $wp_customize->remove_section $wp_customize->remove_control

Hi! The internationalization guidelines, _which are linked in the message,_ explains why using PHP variables or dynamic content this way does not work: https://developer.wordpress.org/apis/handbook/internationalization/internationalization-guidelines/#variables gettext can not know what "$destination->name"...

A first version has been added with https://github.com/WordPress/theme-check/pull/280.

Current requirements for block themes are: Include theme.json. Include block-templates/index.html +requirements that apply to all themes: GPL compatible, secure, no remote resources, no JS or PHP errors, screenshot size and...

> I have found the following items failing on "[empty theme](https://github.com/WordPress/theme-experiments/tree/master/emptytheme)" which, while small, I expected to pass the bare minimum requirements: These are not requirements for block themes. Did...

It looks like the problem mentioned above is preventing block themes from being uploaded to the theme directory. The themes passes the checks locally, but during upload, the correct checks...

It depends on what format is decided on once the readme is parsed in the theme directory. https://meta.trac.wordpress.org/ticket/215#comment:41

I saw that the plugin directory checks for both but uses readme.txt if that exists. So I think it should be the same for themes.

This is already a check in https://github.com/WordPress/theme-check/blob/master/checks/class-file-check.php#L60. Is it not working?

See https://sv.wordpress.org/plugins/child-theme-check/ https://github.com/Zodiac1978/tl-template-checker