bubokko
Forum Replies Created
-
Forum: Developing with WordPress
In reply to: How to tell wp-env that my project is a theme?@dmsnell I checked and indeed my theme was interpreted correctly, however it wasn’t selected as a default theme. I needed to select it in wp-admin myself. Is this expected?
I’d like to understand if, historically, this wp-env warning wasn’t there? It’s a little misleading if it says that it could not determine if it’s a theme or a plugin, while at the same time interpreting the theme correctly. Not sure if it’s a bug or a feature 🙂
Forum: Developing with WordPress
In reply to: How to tell wp-env that my project is a theme?@dmsnell I downloaded newest WordPress (6.4.1), copied the folder of Twenty Twenty-Four theme, pasted it in my ~/www directory as ~/www/my-theme, so my-theme is the root of the theme, for example style.css is at ~/www/my-theme/style.css. Then I ran wp-env start on the ~/www/my-theme/ folder, but got the warning nevertheless.
Forum: Developing with WordPress
In reply to: How to tell wp-env that my project is a theme?@DennisSnell I even tried to copy existing built-in theme and rename it, but I’m still getting this warning. It makes me curious, not gonna lie. Is wp-env supposed to acknowledge a theme by style.css headers? That’s what I thought, but it doesn’t seem to be working. Also tried to copy Akismet as another project, but it also raised that warning. Am I missing something?