[wp-trac] [WordPress Trac] #35395: Provide a better gateway for code-based theme customizations with the Customizer

[WordPress Trac]

#35395: Provide a better gateway for code-based theme customizations with the
Customizer
-----------------------------------------+-------------------------
 Reporter:  celloexpressions             |       Owner:  johnregan3
     Type:  feature request              |      Status:  closed
 Priority:  normal                       |   Milestone:  4.7
Component:  Customize                    |     Version:
 Severity:  normal                       |  Resolution:  fixed
 Keywords:  has-screenshots needs-patch  |     Focuses:
-----------------------------------------+-------------------------

Comment (by westonruter):

 @sebastian.pisula a couple reasons why a custom post type. Theme mods are
 stored in options and they are autoloaded. If a large amount of CSS gets
 added, then this will increase the size of the `alloptions` cache. For
 sites that use Memcached object cache, the size of the `alloptions` cache
 and (especially on WordPress.com) the sum of all options must not approach
 1MB or else the `alloptions` cache will cease to cache at all, and the
 site will crash if it is getting any traffic.

 A more positive reason for using a custom post type is that it allows us
 to make use of post revisions to do versioning of the CSS. Jetpack also
 used a custom post type for storing CSS.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/35395#comment:74>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform