Opened 2 years ago
Last modified 2 years ago
#60734 new enhancement
Deregistering Open Sans
| Reported by: | ecv80 | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Awaiting Review |
| Component: | Script Loader | Version: | 6.4.3 |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description (last modified by )
I have wasted an entire day trying to figure out why my Open Sans styles were not applying. This is counterproductive/suboptimal.
As it turns out, Open Sans was packed in WP back in 2014, which is fine by me. More info: #28478
However it is not immediately obvious one needs to wp_deregister_style('open-sans'); before he can register his own style.
Please, consider making an exception and make wp_register_style() automatically wp_deregister_style(X) if X equals 'open-sans'. Otherwise consider other courses of action that may prevent others from incurring in the same problem I did.
Thanks.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Hi and welcome to WordPress Core Trac!
When [37361] removed Open Sans from the admin, the script loader continued to register the 'open-sans' handle for any themes or plugins already using the stylesheet (ticket:36753#comment:6).
Directory searches found plugins and themes referring to an 'open-sans' style. Some of them enqueue/print the old Core stylesheet, some deregister it, and some make their own stylesheet.