Title: Beta Flags … now with A/B Testing! Author: Charles Jaimet Published: 2018 年 10 月 17 日 Last modified: 2018 年 11 月 2 日 --- 搜尋外掛 這個外掛**並未在最新的 3 個 WordPress 主要版本上進行測試**。開發者可能不再對這個 外掛進行維護或提供技術支援，並可能會與更新版本的 WordPress 產生使用上的相容性問題。 ![](https://ps.w.org/beta-flags/assets/icon-256x256.jpg?rev=1958254) # Beta Flags … now with A/B Testing! 由 [Charles Jaimet](https://profiles.wordpress.org/cmjaimet/) 開發 [下載](https://downloads.wordpress.org/plugin/beta-flags.zip) * [詳細資料](https://tw.wordpress.org/plugins/beta-flags/#description) * [使用者評論](https://tw.wordpress.org/plugins/beta-flags/#reviews) * [開發資訊](https://tw.wordpress.org/plugins/beta-flags/#developers) [技術支援](https://wordpress.org/support/plugin/beta-flags/) ## 外掛說明 Beta Flags allow developers to manage the release of new features. Instead of having code execute as soon as it is deployed to the production environment. You can now wrap it in a beta flag conditional and activate it from the back end. A/B Testing works very similarly, except that instead of turning a code block on or off, they allow you to turn it on 50% of the time. This uses a slight variant on the URL used to display a post or term page, which can then be tracked in an analytics service (e.g. Adobe Omniture, Google 360). ### The Basics of Beta Flags To create a new beta flag, open the configuration JSON file. A copy of this file is provided with this plugin and is stored at `data/beta-flags.json`. You may prefer to create a copy in the root of your theme, the same folder that contains functions. php (`[theme]/beta-flags.json`). The JSON file follows the format below: `{ "flags": { "sidebar_web": { "title":" Beta Flags IN THEME", "description": "Add a sidebar to the post page", "author":" Charles Jaimet" }, "library_admin": { "title": "Beta Flags QA: Plugin Admin Test"," description": "For Beta Flag testing in admin interface", "author": "Charles Jaimet"}}} Each flag is defined by a key (e.g. sidebar_web, library_admin), representing an object with a title, description, and author. The key must be unique, and is used throughout to identify the given flag. Once you have activated the plugin (there are no special instructions for this), navigate to Tools > Beta Flags in the admin interface (`/wp-admin/tools.php?page =beta-flags`). Here you will find the flags from your JSON file if you have created it correctly. A note about JSON, the easiest mistake to make is to put a comma after the last element in an array or object. This will break the JSON but is easy enough to fix when you know what to look for. Kinda like forgetting a semi-colon in PHP. Stupid semi-colons… When you first load the plugin, and any time after you update the JSON file, you should return to this admin screen. New flags are disabled by default, and can only be enabled here. Check the box in the Enabled column beside each flag you want to turn on. Click Save Changes when done. In your theme or other plugins, you can use these beta flag keys to control feature execution by wrapping a conditional around the relevant code. Try to group your wrapped code into a single function, method, or class to avoid littering your theme with beta flag conditionals. The public function `beta_flag_enabled( $key )` will return a true|false value if the beta flag is enabled. Some examples: `if ( beta_flag_enabled( 'sidebar_web' ) ) { get_sidebar(); } if( beta_flag_enabled( 'new_design' ) ) { wp_register_style( 'my_styles', '/assets/my_styles. css', array(), '1.0.0', false ); wp_enqueue_style( 'my_styles' ); } if ( beta_flag_enabled(' popup_offer' ) ) { new PopupOffer( '10% Off', 0.1 ); } I suggest using beta flag keys that make sense and convey their purpose. Adding a version number never hurt, either. There is no character limit, so go nuts. ` if ( beta_flag_enabled( 'revised_sticky_video_for_youtube_widgets_v.1.0.5' ) ) { get_sidebar(); } ### A/B Testing Now you have your beta flags and you’ve embedded them in your code. The feature works as expected and you have it running on production. Is it better than what it replaced? Enter A/B testing. Check the A/B Test box beside the flag you want to test in the admin interface ( see screen shot below), and check the “Enable beta testing” box at the bottom of the flag list, then click “Save Changes”. Go to your website and refresh a few times. You will start to see some term and post links appearing with `?ab=1` appended to their URLs. (e.g. `http://local.wordpress. test/hello-world/?ab=1`). When a visitor follows one of these links they will see your page with the beta flag disabled. When they follow the normal URL without the query string (e.g. `http:// local.wordpress.test/hello-world/`) they will see the page with the beta flag enabled. The query string is randomly appended 50% of time, so two visitors may follow the same link in the sidebar or menu, and one will get the flag turned on and one will get it turned off. Because the URL matches the state of the beta flag, you will be able to see in your analytics service which experience visitors engaged with more. Implementing an effective A/B testing campaign is outside the scope of a README file but there are plenty of good reference books and sites. As long as the “Enable beta testing” box is checked, post and term URLs on your site will get this query string treatment. Only beta flags that have the A/B Test box checked will be affected. Those with it unchecked will be controlled strictly by their Enabled box. Note also that checking A/B Test on a flag that is disabled will have no effect. Off is off. ## 螢幕擷圖 * [[ * Beta Flag configuration screesn. * [[ * Managing A/B test setup. ## 使用者評論 這個外掛目前沒有任何使用者評論。 ## 參與者及開發者 以下人員參與了開源軟體〈Beta Flags … now with A/B Testing!〉的開發相關工作。 參與者 * [ Charles Jaimet ](https://profiles.wordpress.org/cmjaimet/) [將〈Beta Flags … now with A/B Testing!〉外掛本地化為台灣繁體中文版](https://translate.wordpress.org/projects/wp-plugins/beta-flags) ### 對開發相關資訊感興趣？ 任何人均可[瀏覽程式碼](https://plugins.trac.wordpress.org/browser/beta-flags/)、 查看 [SVN 存放庫](https://plugins.svn.wordpress.org/beta-flags/)，或透過 [RSS](https://plugins.trac.wordpress.org/log/beta-flags/?limit=100&mode=stop_on_copy&format=rss) 訂閱[開發記錄](https://plugins.trac.wordpress.org/log/beta-flags/)。 ## 中繼資料 * 版本 **1.3.0** * 最後更新 **8 年前** * 啟用安裝數 **少於 10 次** * WordPress 版本需求 ** 3.0 或更新版本 ** * 已測試相容的 WordPress 版本 **4.9.29** * 語言 * [English (US)](https://wordpress.org/plugins/beta-flags/) * 標籤: * [a/b testing](https://tw.wordpress.org/plugins/tags/ab-testing/)[developers](https://tw.wordpress.org/plugins/tags/developers/) [feature flags](https://tw.wordpress.org/plugins/tags/feature-flags/) * [進階檢視](https://tw.wordpress.org/plugins/beta-flags/advanced/) ## 評分 這個項目尚無任何評論記錄。 [Your review](https://wordpress.org/support/plugin/beta-flags/reviews/#new-post) [查看全部使用者評論](https://wordpress.org/support/plugin/beta-flags/reviews/) ## 參與者 * [ Charles Jaimet ](https://profiles.wordpress.org/cmjaimet/) ## 技術支援 使用者可在技術支援論壇提出意見反應或使用問題。 [檢視技術支援論壇](https://wordpress.org/support/plugin/beta-flags/)