Weston Ruter

<p>This plugin consists of lab features and a testbed for improvements to Widgets and the Customizer.</p>
<p>Requires PHP 5.3+.</p>
<p><strong>Development of this plugin is done <a href="https://github.com/xwp/wp-customize-widgets-plus" rel="nofollow ugc">on GitHub</a>. Pull requests welcome. Please see <a href="https://github.com/xwp/wp-customize-widgets-plus/issues" rel="nofollow ugc">issues</a> reported there before going to the <a href="https://wordpress.org/support/plugin/customize-widgets-plus" rel="ugc">plugin forum</a>.</strong></p>
<p>Current features:</p>
<h4>Non-Autoloaded Widget Options</h4>
<p>Widgets are stored in options (normally). Multi-widgets store all of their instances in one big serialized array specific to that type. When there are many widgets of a given type, the size of the serialized array can grow very large. What’s more is that <code>WP_Widget</code> does not explicitly <code>add_option(... 'no' )</code> before calling <code>update_option()</code>, and so all of the settings get added with autoloading. This is very bad when using Memcached Object Cache specifically because it can result in the total <code>alloptions</code> cache key to become larger than 1MB and result in Memcached failing to store the value in the cache. On WordPress.com the result is a <a href="https://github.com/Automattic/vip-quickstart/blob/master/www/wp-content/mu-plugins/alloptions-limit.php" rel="nofollow ugc">“Matt’s fault” error</a> which has to be fixed by the VIP team. Widget settings should not be stored in serialized arrays to begin with; each widget instance should be stored in a custom post type. But until this is done we should stop autoloading options. See also <a href="https://core.trac.wordpress.org/ticket/26876" rel="nofollow ugc">#26876</a> and <a href="https://core.trac.wordpress.org/ticket/23909" rel="nofollow ugc">#23909</a>.</p>
<h4>Widget Number Incrementing</h4>
<p>Implements fixes for Core issue <a href="https://core.trac.wordpress.org/ticket/32183" rel="nofollow ugc">#32183</a> (Widget ID auto-increments conflict for concurrent users). The stored widget_number option provides a centralized auto-increment number for whenever a widget is instantiated, even widgets in the Customizer that are not yet saved.</p>
<h4>Efficient Multidimensional Setting Sanitizing</h4>
<p>Settings for multidimensional options and theme_mods are extremely inefficient to sanitize in Core because all of the Customizer settings registered for the subsets of the <code>option</code> or <code>theme_mod</code> need filters that are added to the entire value, meaning sanitizing one single setting will result in all filters for all other settings in that <code>option</code>/<code>theme_mod</code> will also get applied. This functionality seeks to improve this as much as possible, especially for widgets which are the worst offenders. Implements partial fix for <a href="https://core.trac.wordpress.org/ticket/32103" rel="nofollow ugc">#32103</a>.</p>
<h4>HTTPS Resource Proxy</h4>
<p>When <code>FORCE_SSL_ADMIN</code> is enabled (such as on WordPress.com), the Customizer will load the site into the preview iframe using HTTPS as well. If, however, external resources are being referenced which are not HTTPS, they will fail to load due to the browser’s security model raise mixed content warnings. This functionality will attempt to rewrite any HTTP URLs to be HTTPS ones via a WordPress-based proxy.</p>
<h4>Widget Posts</h4>
<p>Store widget instances in posts instead of options. Requires trunk due to patch committed in <a href="https://core.trac.wordpress.org/ticket/32474" rel="nofollow ugc">#32474</a>. More details forthcoming…</p>


Customize Widgets Plus

Lab features and a testbed for improvements to Widgets and the Customizer.

Customize Widgets Plus vs STAGGS – Product Configurator Toolkit