Backstage - Customizer Demo Access
| 开发者 |
pixelgrade
vlad.olaru |
|---|---|
| 更新时间 | 2019年11月8日 17:27 |
| PHP版本: | 5.4.0 及以上 |
| WordPress版本: | 5.3.0 |
| 版权: | GPL v2.0 (or later) |
| 版权网址: | 版权信息 |
详情介绍:
- For most the default HTML and CSS styling will be just fine. You can customize the button text.
- You can choose to provide your own button HTML and CSS.
- Or you can go all custom and handle the button yourself.
- WordPress core controls;
- Colors and fonts controls;
- Layout and behavioral controls like content width or blog layout.
- Works with regular, single installations;
- Works with Multisite setups; you can activate the plugin network-wide or per-blog.
- File uploads are not allowed; due to this, any controls that need file upload will not be allowed to be modified;
- Any time a visitor leaves the Customizer, any customization is lost and when he or she enters again, all will start clean;
安装:
Plugins → Add New screen in your WordPress dashboard, or by using the following steps:
- Download the plugin via WordPress.org.
- Upload the ZIP file through the
Plugins → Add New → Uploadscreen in your WordPress dashboard. - Activate the plugin through the
Pluginsmenu in WordPress. - Head over to
Appearance → Backstage(orNetwork Settings → Backstageif network-wide activated) and set it up.
常见问题:
Is this safe to use in production?
We believe so. To put our money where our mouth is, we use it in production on our own demo multisite installation. We've strived to close off any endpoints that WordPress uses to save things (mainly the changeset logic specific to the Customizer experience).
Without changesets how is the experience consistent with a real scenario?
There is no point in showcasing a customization experience that is not consistent with the real one. We couldn't agree more. That is why we've studied the Customizer JavaScript logic and found ways to maintain the same results without saving anything in the database.
When I navigate in the preview window, customizations don't get applied?
Sometimes, WordPress themes will come with custom JavaScript that will bind to click events and stop their propagation. Due to this, the Customizer (not our's) logic can't catch that click and go the proper way of refreshing the preview window. We really have not way around that.
Can I choose to hide certain Customizer sections or panels?
The plugin doesn't provide this functionality as it is quite difficult to map it to a set of configuration options. But it should be quite straight forward to code a function that "removes" panels, sections or controls when the special pseudo-guest user is logged in.
I am a developer. Can I easily change how things work?
We are also developers (and designers, and marketers, and support people...) just like you. We know how important it is that plugins get coded in an open, thoughtful manner that is friendly towards those that have custom requirements. The plugin provides actions and filters in all the right places allowing you to introduce custom logic just about anywhere, if the need arises.
更新日志:
- 2019-11-08
- Prevent aggressive sanitization for custom code fields.
- 2019-11-07
- Allow POST method also for REST API endpoint.
- 2019-11-06
- Added support for injecting custom CSS and JS in the Customizer.
- Added support for UTF-8 characters in the button text.
- Added support for extra query arguments to the REST API endpoint.
- Made sure that settings data in conditionally hidden fields is persistent so you wouldn't lose you custom code.
- 2019-10-08
- Added new settings and logic for enabling a REST API endpoint to fetch the secure customizer access link.
- Update CMB2 dependency to latest version (2.6.0).
- 2019-10-07
- Improved behaviour when working within multisite settings and the plugin is activated on a per site basis.
- Improved security checks to prevent edge-cases on multisite installations.
- Added upgrade routines for smoother plugin updates.
- Tested with WordPress 5.2.3.
- 2018-12-10
- Added frame busting when in an iframe because the Customizer doesn't play well when opened in an iframe.
- Tested with WordPress 5.0.
- 2018-10-05
- Initial release