Changes between Initial Version and Version 1 of Ticket #63086, comment 18
- Timestamp:
- 03/15/2025 10:14:10 AM (19 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #63086, comment 18
initial v1 2 2 > @SirLouen I tested your snippet and I can see the difference after switching: the warning and value of `$is_block_theme` is `false` when using the `plugins_loaded` callback. Is that the difference you're talking about? 3 3 4 I'm not 1000% because I have not read all the context, but this is just a notice .4 I'm not 1000% because I have not read all the context, but this is just a notice `_doing_it_wrong`. It's not "protecting" anything but the developer to code wrongly. 5 5 6 This is not a warning and is not an error checker to raise an exception. It's not "protecting" anything but the developer to code wrongly. 6 It's merely a developer notice that is informing of what you are saying here: 7 7 8 It's merely a developer notice that is informing of what you are saying here: "Themes are not yet loaded at this point, therefore the `$is_block_theme` is always going to be `false`, so please, gently move your `is_block_theme` call forward to a point where the call to `is_block_theme`, makes real sense.8 > Themes are not yet loaded at this point, therefore the `$is_block_theme` is always going to be `false`, so please, gently move your `is_block_theme` call forward to a point where the call to `is_block_theme`, makes real sense.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)