Changes between Initial Version and Version 1 of Ticket #35395, comment 71
- Timestamp:
- 10/19/2016 07:38:22 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #35395, comment 71
initial v1 17 17 It stores the custom css in the db as follows: 18 18 19 - master css, shop css (ie. woocommcerce) and archive css (per post_type) is stored in wp_options unique to the theme (or child-theme) so that switching themes applies the proper and unique css to appr priate pages19 - master css, shop css (ie. woocommcerce) and archive css (per post_type) is stored in wp_options unique to the theme (or child-theme) so that switching themes applies the proper and unique css to appropriate pages 20 20 - a. such as mycss_master_mythemename, mycss_shop_mythemename... 21 21 22 - post/page/single css is stored in thepost_meta also unique to the theme/child-theme22 - post/page/single css is stored in post_meta also unique to the theme/child-theme 23 23 - a. such as mycss_mythemename_postid 24 24 25 This allows for full freedom or custom css code site wide, across a common group of posts/pages or individually and prioritized accordingly.25 This allows for full freedom for custom css code site wide, across a common group of posts/pages or individually and prioritized accordingly. 26 26 27 27 The live preview uses inline style elements (with unique ids) for the real time "live" previewing when code in the editor is changed but on the front end I'm using wp_enqueue_styles with a doctype wrapper to properly use wp standard practices.