In Sage 9.0.10 : Using: add_editor_style(asset_path('styles/tinymce.css')); asset_path(‘styles/tinymce.css’) would output: http://lorem.test/wp-content/themes/my-theme/dist/styles/tinymce_e8ca3004.css But in Sage 10.3.1 (Bud 6.4.5): Using: $asset = \Roots\asset(‘css/tinymce.css’); add_editor…

You are right, the filename indicates that these styles should be used for the TinyMCE (Classic) editor. When that tinymce.css is from an entrypoint (in the bud.config.mjs, entry()), you don’t add the styles/ directory, but rather just use its entrypoint name (+ .css): \Roots\asset('tinymce.css')…

Unfortunately, your link isn’t helpful. The problem I’m facing comes from \Roots\asset(‘’) IMO.

Thank you for help ! This indeed solves it. :pray: I assumed specifying a directory would be required.

Getting Started
Releases
Support us

WP Packages is our new WPackagist replacement that's 17x faster and updates every 5 minutes

Roots Discourse

Sage 10 \Roots\asset() vs Sage 9 asset_path()

sage

bud, sage10

strarsis January 16, 2023, 8:35am 2

Bud build development & asset() function bud

Note that for Gutenberg the editor styles needs to be added by relative path, see this example (related trac issue #55728 (baseURL missing for remotely fetched editor styles) – WordPress Trac)

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled