-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CSS is not generated when switching to a FSE theme #1673
Comments
@HardeepAsrani, I can no longer reproduce this issue. Do you think that this change #1827 can help with other themes? |
@Soare-Robert-Daniel You can't reproduce it anymore with any themes at all? |
Everything seems to work fine. I was also tested with Neve FSE. ℹ️ A problem when testing this behavior is that Starter Sites use neve var CSS, which becomes invalid when you change the theme. |
If that's the case then we can close the PR and issue as issue with CSS variables won't be solved anyway. Perhaps maybe @Codeinwp/qa-team can take a look with the current version of WordPress.org to confirm they also aren't able to reproduce the issue? |
@Soare-Robert-Daniel @HardeepAsrani Tested and i also wasn't able to reproduce it. Feel free to close this ✔️ |
🎉 This issue has been resolved in version 2.4.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Description
When transferring to an FSE theme, the custom CSS for the Home page (in Pages) is not generated.
Step-by-step reproduction instructions
If you import some content via Template Cloud, you will have content on the Home page then, if you switch to the FSE theme (e.g.: Raft), the editor will put the original content in a Post Content block.
If you go to FSE Editor and select the Front Page then view it, you will notice that the custom styling for the original content is missing.
To fix this, go to Pages > Home, where the original content is, and press Update. This will trigger the CSS generation for the page.
Screenshots, screen recording, code snippet or Help Scout ticket
No response
Environment info
https://pastebin.com/i0f7Scax
Is the issue you are reporting a regression
No
The text was updated successfully, but these errors were encountered: