Changes between Initial Version and Version 1 of Ticket #53014, comment 7
- Timestamp:
- 04/10/2021 10:25:57 AM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #53014, comment 7
initial v1 1 1 I have no idea what is the right way to know in time about new support features and sometimes it is difficult to understand if something isn't working during development and it caused by the absence of this support declaration. Most times I am looking in WordPress default themes and other popular themes for this piece of information and something learning new 'tricks' or possibilities I happened to miss along the way but I doubt that it is the right way to get the information. 2 3 The tricky bit is that plugins can use their own theme support declarations and it is difficult to find if you don't know what you are looking for. For example, if a theme isn't supporting 'woocommerce', WC will not be using templates from the theme's folder but the plugin has its own bits for compatibility with default themes and as result, if you will make a child theme for the default one, it will be using templates from child's folder. It is a bit confusing if you don't know that plugin can declare the support for the theme instead of the theme itself.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)