[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fWjgjFUR0Cu3E4hwh16mCdedcAaVenaWWeVw7d4o5fGQ":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":23,"download_link":24,"security_score":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28,"vulnerabilities":29,"developer":30,"crawl_stats":27,"alternatives":38,"analysis":144,"fingerprints":267},"wordpress-beta-tester","WordPress Beta Tester","4.0.0","Andy Fragen","https:\u002F\u002Fprofiles.wordpress.org\u002Fafragen\u002F","\u003Cp>This plugin provides an easy way to get involved with beta testing WordPress.\u003C\u002Fp>\n\u003Cp>Once installed it will enable you to upgrade your website to the latest Nightly, Beta, or Release Candidate at the click of a button using the built in upgrader.\u003C\u002Fp>\n\u003Cp>By default once enabled it switches your website onto the point release update channel.\u003C\u002Fp>\n\u003Cp>For the more adventurous there is the option to switch to the bleeding edge (trunk) of development.\u003C\u002Fp>\n\u003Cp>Don’t forget to backup before you start!\u003C\u002Fp>\n\u003Cp>Please enable auto-updates for this plugin to ensure future changes are properly handled with core updates.\u003C\u002Fp>\n\u003Ch3>Extra Settings\u003C\u002Fh3>\n\u003Cp>There is a setting to \u003Cstrong>Skip successful autoupdate emails\u003C\u002Fstrong>.  It functions to disable sending emails to the admin user for successful autoupdates. Only emails indicating failures of the autoupdate process are sent.\u003C\u002Fp>\n\u003Cp>There is a setting to \u003Cstrong>Skip bundled plugins and themes\u003C\u002Fstrong>. It functions to disable the installation of any plugins or themes that are bundled with the Core update.\u003C\u002Fp>\n\u003Cp>PRs are welcome on \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fafragen\u002Fwordpress-beta-tester\" rel=\"nofollow ugc\">GitHub\u003C\u002Fa>.\u003C\u002Fp>\n","Allows you to easily upgrade for testing the next versions of WordPress.",2000,539789,80,47,"2025-11-07T15:26:00.000Z","6.9.4","4.9","5.6",[20,21,22],"advanced","beta","testing","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwordpress-beta-tester\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwordpress-beta-tester.4.0.0.zip",100,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":31,"display_name":7,"profile_url":8,"plugin_count":32,"total_installs":33,"avg_security_score":34,"avg_patch_time_days":35,"trust_score":36,"computed_at":37},"afragen",12,42970,96,356,76,"2026-04-04T03:46:55.344Z",[39,56,75,100,123],{"slug":40,"name":41,"version":42,"author":43,"author_profile":44,"description":45,"short_description":46,"active_installs":47,"downloaded":48,"rating":26,"num_ratings":26,"last_updated":49,"tested_up_to":49,"requires_at_least":49,"requires_php":50,"tags":51,"homepage":53,"download_link":54,"security_score":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":55},"vk-plugin-beta-tester","VK Plugin Beta Tester","0.2.9","Vektor,Inc.","https:\u002F\u002Fprofiles.wordpress.org\u002Fvektor-inc\u002F","\u003Cp>This plugin aids with beta testing WordPress plugins hosted on \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002F\" rel=\"ugc\">wordpress.org\u003C\u002Fa>. After activation of this plugin, you can choose the plugins to show a beta notification at the setting page. Then, WordPress will notify you of new beta versions of selected plugins, not just new stable versions, and you’ll be able to upgrade to these beta versions with just one click within WordPress.\u003Cbr \u002F>\nMake sure to make frequent backups while you beta test plugins, and make sure to report bugs. Thanks for helping test plugins!\u003C\u002Fp>\n","VK Plugin Beta Tester is derived from \"Plugin Beta Tester\" WordPress Plugin, created by mitcho (Michael Yoshitaka Erlewine) Copyright 2013.",10,1535,"","5.6.0",[20,21,52,22],"plugins","https:\u002F\u002Fgithub.com\u002Fvektor-inc\u002Fvk-plugin-beta-tester","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fvk-plugin-beta-tester.0.2.9.zip","2026-03-15T10:48:56.248Z",{"slug":57,"name":58,"version":59,"author":60,"author_profile":61,"description":62,"short_description":63,"active_installs":26,"downloaded":64,"rating":26,"num_ratings":26,"last_updated":65,"tested_up_to":66,"requires_at_least":67,"requires_php":49,"tags":68,"homepage":72,"download_link":73,"security_score":74,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"beta-flags","Beta Flags … now with A\u002FB Testing!","1.3.0","Charles Jaimet","https:\u002F\u002Fprofiles.wordpress.org\u002Fcmjaimet\u002F","\u003Cp>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.\u003C\u002Fp>\n\u003Cp>A\u002FB 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).\u003C\u002Fp>\n\u003Ch3>The Basics of Beta Flags\u003C\u002Fh3>\n\u003Cp>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 \u003Ccode>data\u002Fbeta-flags.json\u003C\u002Fcode>. You may prefer to create a copy in the root of your theme, the same folder that contains functions.php (\u003Ccode>[theme]\u002Fbeta-flags.json\u003C\u002Fcode>).\u003C\u002Fp>\n\u003Cp>The JSON file follows the format below:\u003Cbr \u002F>\n    \u003Ccode>{\u003Cbr \u002F>\n    \"flags\": {\u003Cbr \u002F>\n        \"sidebar_web\": {\u003Cbr \u002F>\n            \"title\": \"Beta Flags IN THEME\",\u003Cbr \u002F>\n            \"description\": \"Add a sidebar to the post page\",\u003Cbr \u002F>\n            \"author\": \"Charles Jaimet\"\u003Cbr \u002F>\n        },\u003Cbr \u002F>\n        \"library_admin\": {\u003Cbr \u002F>\n            \"title\": \"Beta Flags QA: Plugin Admin Test\",\u003Cbr \u002F>\n            \"description\": \"For Beta Flag testing in admin interface\",\u003Cbr \u002F>\n            \"author\": \"Charles Jaimet\"\u003Cbr \u002F>\n        }\u003Cbr \u002F>\n    }\u003Cbr \u002F>\n}\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>Once you have activated the plugin (there are no special instructions for this), navigate to Tools > Beta Flags in the admin interface (\u003Ccode>\u002Fwp-admin\u002Ftools.php?page=beta-flags\u003C\u002Fcode>). Here you will find the flags from your JSON file if you have created it correctly.\u003C\u002Fp>\n\u003Cp>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…\u003C\u002Fp>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>The public function \u003Ccode>beta_flag_enabled( $key )\u003C\u002Fcode> will return a true|false value if the beta flag is enabled.\u003C\u002Fp>\n\u003Cp>Some examples:\u003Cbr \u002F>\n    \u003Ccode>if ( beta_flag_enabled( 'sidebar_web' ) ) {\u003Cbr \u002F>\n    get_sidebar();\u003Cbr \u002F>\n}\u003C\u002Fcode>\u003Cbr \u002F>\n    \u003Ccode>if ( beta_flag_enabled( 'new_design' ) ) {\u003Cbr \u002F>\n    wp_register_style( 'my_styles', '\u002Fassets\u002Fmy_styles.css', array(), '1.0.0', false );\u003Cbr \u002F>\n    wp_enqueue_style( 'my_styles' );\u003Cbr \u002F>\n}\u003C\u002Fcode>\u003Cbr \u002F>\n    \u003Ccode>if ( beta_flag_enabled( 'popup_offer' ) ) {\u003Cbr \u002F>\n    new PopupOffer( '10% Off', 0.1 );\u003Cbr \u002F>\n}\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>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.\u003Cbr \u002F>\n    \u003Ccode>if ( beta_flag_enabled( 'revised_sticky_video_for_youtube_widgets_v.1.0.5' ) ) {\u003Cbr \u002F>\n    get_sidebar();\u003Cbr \u002F>\n}\u003C\u002Fcode>\u003C\u002Fp>\n\u003Ch3>A\u002FB Testing\u003C\u002Fh3>\n\u003Cp>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?\u003C\u002Fp>\n\u003Cp>Enter A\u002FB testing.\u003C\u002Fp>\n\u003Cp>Check the A\u002FB 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”.\u003C\u002Fp>\n\u003Cp>Go to your website and refresh a few times. You will start to see some term and post links appearing with \u003Ccode>?ab=1\u003C\u002Fcode> appended to their URLs. (e.g. \u003Ccode>http:\u002F\u002Flocal.wordpress.test\u002Fhello-world\u002F?ab=1\u003C\u002Fcode>).\u003C\u002Fp>\n\u003Cp>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. \u003Ccode>http:\u002F\u002Flocal.wordpress.test\u002Fhello-world\u002F\u003C\u002Fcode>) they will see the page with the beta flag enabled.\u003C\u002Fp>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>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\u002FB testing campaign is outside the scope of a README file but there are plenty of good reference books and sites.\u003C\u002Fp>\n\u003Cp>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\u002FB Test box checked will be affected. Those with it unchecked will be controlled strictly by their Enabled box. Note also that checking A\u002FB Test on a flag that is disabled will have no effect. Off is off.\u003C\u002Fp>\n","Thanks to: James Williams, whose plugin inspired this one (https:\u002F\u002Fgithub.com\u002Fjamesrwilliams\u002Ffeature-flags)",1123,"2018-11-02T13:34:00.000Z","4.9.29","3.0",[69,57,70,71],"ab-testing","developers","feature-flags","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fbeta-flags\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fbeta-flags.zip",85,{"slug":76,"name":77,"version":78,"author":79,"author_profile":80,"description":81,"short_description":82,"active_installs":83,"downloaded":84,"rating":34,"num_ratings":85,"last_updated":86,"tested_up_to":16,"requires_at_least":87,"requires_php":88,"tags":89,"homepage":95,"download_link":96,"security_score":97,"vuln_count":98,"unpatched_count":26,"last_vuln_date":99,"fetched_at":28},"wp-reset","WP Reset","2.06","WebFactory","https:\u002F\u002Fprofiles.wordpress.org\u002Fwebfactory\u002F","\u003Cp>\u003Ca href=\"https:\u002F\u002Fwpreset.com\u002F\" rel=\"nofollow ugc\">WP Reset\u003C\u002Fa> quickly resets the site’s database to the default installation values without modifying any files. It deletes all customizations and content, or just chosen parts like theme settings. WordPress Reset is fast and safe to use thanks to the built-in snapshots which provide 1-click restore functionality. It has multiple fail-safe mechanisms so you can never accidentally lose data. WP Reset is extremely helpful for plugin and theme developers. It \u003Cstrong>speeds up testing & debugging\u003C\u002Fstrong> by providing a quick way to reset settings and re-test code. It’s the only WP development tool for non-developers that enables advanced reset.\u003C\u002Fp>\n\u003Cp>\u003Cspan class=\"embed-youtube\" style=\"text-align:center; display: block;\">\u003Ciframe loading=\"lazy\" class=\"youtube-player\" width=\"750\" height=\"422\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002FqMnkCW2PFoI?version=3&rel=0&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent\" allowfullscreen=\"true\" style=\"border:0;\" sandbox=\"allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox\">\u003C\u002Fiframe>\u003C\u002Fspan>\u003C\u002Fp>\n\u003Cp>For support please use the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fwp-reset\" rel=\"ugc\">official forum\u003C\u002Fa>, and if you need more information visit \u003Ca href=\"https:\u002F\u002Fwpreset.com\u002F\" rel=\"nofollow ugc\">wpreset.com\u003C\u002Fa> and be sure to check out the \u003Ca href=\"https:\u002F\u002Fwpreset.com\u002F\" rel=\"nofollow ugc\">roadmap\u003C\u002Fa> for the list of upcoming features.\u003C\u002Fp>\n\u003Cp>Access WP Reset admin page via the “Tools” menu.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Please read carefully before proceeding to understand what WP Reset does, and remember to always create a snapshot\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch4>Resetting will delete:\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>all posts, pages, custom post types, comments, media entries, users\u003C\u002Fli>\n\u003Cli>all default WP database tables\u003C\u002Fli>\n\u003Cli>all custom database tables that have the same prefix table prefix as the one defined in \u003Cem>wp-config.php\u003C\u002Fem> and used by default tables\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Resetting will not delete or modify:\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>media files – they remain in the \u003Cem>wp-uploads\u003C\u002Fem> folder untouched but will no longer be listed under Media in admin\u003C\u002Fli>\n\u003Cli>no files are touched; plugins, themes, uploads – everything stays\u003C\u002Fli>\n\u003Cli>site title, WordPress address, site address, site language and search engine visibility settings\u003C\u002Fli>\n\u003Cli>currently logged in user will be restored with the current username and password\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>What happens when I click the Reset button?\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>remember to always create a snapshot first or a full backup\u003C\u002Fli>\n\u003Cli>you will have to confirm the action one more time because there is NO UNDO\u003C\u002Fli>\n\u003Cli>everything will be reset; see bullets above for details\u003C\u002Fli>\n\u003Cli>site title, WordPress address, site address, site language, search engine visibility settings as well as the current user will be restored\u003C\u002Fli>\n\u003Cli>you will be logged out, automatically logged in and taken to the admin dashboard\u003C\u002Fli>\n\u003Cli>WP Reset plugin will be reactivated if that option is chosen in the post-reset options\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Undoing a reset\u003C\u002Fh4>\n\u003Cp>Before doing a reset, create a snapshot. The button is located right next to the reset button and it takes less than 10 seconds to create a snapshot. After reset is done, if you need to undo it simply restore the snapshot and that’s it.\u003C\u002Fp>\n\u003Ch4>WP-CLI support\u003C\u002Fh4>\n\u003Cp>WP Reset comes with full WP-CLI support. Help on our WP-CLI commands is available via \u003Cem>wp help reset\u003C\u002Fem>. By default the commands have to be confirmed but you can use the \u003Ccode>--yes\u003C\u002Fcode> option to skip confirmation. Instead of the active user, the first user with admin privileges found in the database will be restored after reset. Please be careful when using WP Reset with WP-CLI – as with using the GUI always make a snapshot or backup first.\u003C\u002Fp>\n\u003Cp>Currently supported WP-CLI commands:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>wp reset reset\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp reset version\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp reset delete\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp reset snapshots\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Database Snapshots\u003C\u002Fh4>\n\u003Cp>Database snapshot is a copy of all WP database tables, standard and custom ones, saved in the currently used database (as set by \u003Cem>wp-config.php\u003C\u002Fem>). Files are not saved or included in snapshots in any way.\u003Cbr \u002F>\nSnapshots are primarily a development tool. Although they can be used for backups (and downloaded as gzipped SQL dumps), we suggest finding a more suitable tool for doing backups of live sites. Use snapshots to find out what changes a plugin made to your database – what custom tables were created, modified, deleted or what changes were made to site’s settings. Or use it to quickly restore the development environment after testing database related changes.\u003Cbr \u002F>\nRestoring a snapshot does not affect other snapshots, or WP Reset settings. Snapshots can be compared to current database tables, restored (by overwriting current tables), exported ad gzipped SQL dumps, or deleted. Creating a snapshot on an average WordPress installation takes 1-2 seconds.\u003C\u002Fp>\n\u003Cp>\u003Cspan class=\"embed-youtube\" style=\"text-align:center; display: block;\">\u003Ciframe loading=\"lazy\" class=\"youtube-player\" width=\"750\" height=\"422\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002FxBfMmS12vMY?version=3&rel=0&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent\" allowfullscreen=\"true\" style=\"border:0;\" sandbox=\"allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox\">\u003C\u002Fiframe>\u003C\u002Fspan>\u003C\u002Fp>\n\u003Ch4>Multisite (WP-MU) Support\u003C\u002Fh4>\n\u003Cp>WP Reset has yet to be completely tested with multisite! Please be careful when using it with multisite enabled. We don’t recommend to resetting the main site. Sub-sites should be OK. We’re working on making WP Reset fully compatible with WP-MU. Till then please be careful. Thank you for understanding.\u003C\u002Fp>\n\u003Ch4>Partial Reset Tools\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Delete transients – deletes all transient related database entries. Including expired and non-expired transients, and orphaned timeout entries.\u003C\u002Fli>\n\u003Cli>Delete uploads – delete all files and folder in the \u002Fuploads\u002F folder.\u003C\u002Fli>\n\u003Cli>Delete plugins – deletes all plugins except WP Reset which remains active.\u003C\u002Fli>\n\u003Cli>Reset theme options – resets all options for all themes that use the WP theme mods API.\u003C\u002Fli>\n\u003Cli>Delete themes – deletes all themes.\u003C\u002Fli>\n\u003Cli>Empty or delete custom tables – empties (truncates) or deletes (drops) all custom database tables.\u003C\u002Fli>\n\u003Cli>Delete .htaccess file – deletes the .htaccess file. If you need to edit .htaccess without FTP use our free \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-htaccess-editor\u002F\" rel=\"ugc\">WP Htaccess Editor\u003C\u002Fa> plugin.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>GDPR compatibility\u003C\u002Fh4>\n\u003Cp>We are not lawyers. Please do not take any of the following as legal advice.\u003Cbr \u002F>\nWP Reset does not track, collect or process any user data on the front end. Nothing is logged or pushed to any 3rd parties. We also don’t use any 3rd party services or CDNs. All actions are performed in the admin and started exclusively on users’ request. If you opt to activate your PRO license in the plugin, some data will be shared with WebFactory Ltd; that’s clearly noted below the license activation form. Based on that, we feel it’s GDPR compatible, but again, please, don’t take this as legal advice.\u003C\u002Fp>\n\u003Ch4>Friends who helped us translate WP Reset\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>French – \u003Ca href=\"https:\u002F\u002Fwww.infrenchtranslation.com\u002F\" rel=\"nofollow ugc\">Jeff Inho\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If you’re having problems with SSL or HTTPS try our free \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-force-ssl\u002F\" rel=\"ugc\">WP Force SSL\u003C\u002Fa> plugin. It’s a great plugin to enable SSL or install SSL.\u003C\u002Fp>\n","WP Reset resets the entire site or selected parts using advanced reset options to default values. 100% safe to use with built-in restore function.",300000,9815290,994,"2026-01-06T20:10:00.000Z","4.0","5.2",[90,91,92,93,94],"advanced-wordpress-reset","reset","reset-database","reset-wordpress","wordpress-reset","https:\u002F\u002Fwpreset.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-reset.2.06.zip",89,6,"2025-10-06 00:00:00",{"slug":101,"name":102,"version":103,"author":104,"author_profile":105,"description":106,"short_description":107,"active_installs":108,"downloaded":109,"rating":110,"num_ratings":111,"last_updated":112,"tested_up_to":16,"requires_at_least":113,"requires_php":114,"tags":115,"homepage":121,"download_link":122,"security_score":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"acf-content-analysis-for-yoast-seo","ACF Content Analysis for Yoast SEO","3.2","Yoast","https:\u002F\u002Fprofiles.wordpress.org\u002Fyoast\u002F","\u003Cp>This plugin ensures that Yoast SEO analyzes all ACF content including Flexible Content and Repeaters.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fyoast.com\u002Fwordpress\u002Fplugins\u002F\" rel=\"nofollow ugc\">Yoast SEO for WordPress\u003C\u002Fa> content and SEO analysis does not take in to account the content of a post’s \u003Ca href=\"http:\u002F\u002Fwww.advancedcustomfields.com\u002F\" rel=\"nofollow ugc\">Advanced Custom Fields\u003C\u002Fa>. This plugin uses the plugin system of Yoast SEO for WordPress to hook into the analyser in order to add ACF content to the SEO analysis.\u003C\u002Fp>\n\u003Cp>This had previously been done by the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-seo-acf-content-analysis\u002F\" rel=\"ugc\">WordPress SEO ACF Content Analysis\u003C\u002Fa> plugin but that no longer works with Yoast 3.0. Kudos to \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fryuheixys\u002F\" rel=\"nofollow ugc\">ryuheixys\u003C\u002Fa>, the author of that plugin, for the original idea.\u003C\u002Fp>\n\u003Cp>This Plugin is compatible with the free ACF 4 Version as well as with the PRO Version 5. Please be aware that it ignores Pro Add-Ons for Version 4. In that case please upgrade to ACF PRO Version 5.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>If you have issues, please \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FYoast\u002Fyoast-acf-analysis\u002Fissues\" rel=\"nofollow ugc\">submit them on GitHub\u003C\u002Fa>\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>Previously called Yoast ACF Analysis.\u003C\u002Fp>\n\u003Ch3>Filters\u003C\u002Fh3>\n\u003Ch4>Remove specific field from scoring\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>add_filter( 'Yoast\\WP\\ACF\\blacklist_name', function ( $blacklist_name ) {\n    $blacklist_name->add( 'my-field-name' );\n    return $blacklist_name;\n});\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Remove field type from scoring\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>add_filter( 'Yoast\\WP\\ACF\\blacklist_type', function ( $blacklist_type ) {\n    \u002F\u002F text, image etc\n    $blacklist_type->add( 'text' );\n    $blacklist_type->add( 'image' );\n    return $blacklist_type;\n});\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Define custom field a specific heading value\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>add_filter( 'Yoast\\WP\\ACF\\headlines', function ( $headlines ) {\n    \u002F\u002F value from 1-6, 1=h1, 6=h6\n    $headlines['field_591eb45f2be86'] = 3;\n    return $headlines;\n});\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Change refresh rate\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>add_filter( 'Yoast\\WP\\ACF\\refresh_rate', function () {\n    \u002F\u002F Refresh rates in milliseconds\n    return 1000;\n});\n\u003C\u002Fcode>\u003C\u002Fpre>\n","WordPress plugin that adds the content of all ACF fields to the Yoast SEO score analysis.",100000,2538123,84,34,"2025-12-01T18:33:00.000Z","6.6","7.2.5",[116,117,118,119,120],"acf","advanced-custom-fields","analysis","seo","yoast","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Facf-content-analysis-for-yoast-seo\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Facf-content-analysis-for-yoast-seo.3.2.zip",{"slug":124,"name":125,"version":126,"author":127,"author_profile":128,"description":129,"short_description":130,"active_installs":108,"downloaded":131,"rating":132,"num_ratings":133,"last_updated":134,"tested_up_to":16,"requires_at_least":135,"requires_php":18,"tags":136,"homepage":139,"download_link":140,"security_score":141,"vuln_count":142,"unpatched_count":26,"last_vuln_date":143,"fetched_at":28},"advanced-custom-fields-font-awesome","Advanced Custom Fields: Font Awesome Field","5.0.2","Matt Keys","https:\u002F\u002Fprofiles.wordpress.org\u002Fmattkeys\u002F","\u003Cp>Add a \u003Ca href=\"http:\u002F\u002Ffontawesome.com\u002F\" rel=\"nofollow ugc\">Font Awesome\u003C\u002Fa> icon field type to Advanced Custom Fields.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Specify which FontAwesome icon sets to use (Solid, Regular, Light, Thin, Duotone, Duotone Sharp, Brands, and Custom Upload Icons) (Some features only available with FontAwesome 5.x or 6.x icons)\u003C\u002Fli>\n\u003Cli>Create your own custom filtered list of FontAwesome icons to use with your fields. Use different custom icon sets with different fields\u003C\u002Fli>\n\u003Cli>Returns Icon Element, Icon Class, Icon Unicode, or an Object including the element, class, unicode value, and SVG data (if applicable)\u003C\u002Fli>\n\u003Cli>Optionally enqueues Font Awesome in footer where needed (when a FontAwesome field is being used on the page))\u003C\u002Fli>\n\u003Cli>Integrates with the \u003Ca href=\"https:\u002F\u002Fdocs.fontawesome.com\u002Fapis\u002Fgraphql\" rel=\"nofollow ugc\">FontAwesome GraphQL\u003C\u002Fa> for loading your \u003Ca href=\"https:\u002F\u002Fdocs.fontawesome.com\u002Fweb\u002Fsetup\u002Fuse-kit\" rel=\"nofollow ugc\">FontAwesome Kits\u003C\u002Fa>, searching for icons, and loading the latest version of FontAwesome\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Note: It is recommended to let this plugin enqueue the latest version of Font Awesome on your front-end; or include the latest version yourself using your \u003Ca href=\"https:\u002F\u002Fdocs.fontawesome.com\u002Fweb\u002Fsetup\u002Fuse-kit\" rel=\"nofollow ugc\">FontAwesome Kit\u003C\u002Fa>; so that available icons in the admin area will be displayed properly on your sites front-end.\u003C\u002Fp>\n\u003Ch4>Compatibility\u003C\u002Fh4>\n\u003Cp>This ACF field type is compatible with:\u003Cbr \u002F>\n* ACF 5.7+\u003Cbr \u002F>\n* FontAwesome 4.x, 5.x, 6.x and 7.x fonts\u003C\u002Fp>\n\u003Ch3>Optional Configuration\u003C\u002Fh3>\n\u003Ch3>Filters\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>ACFFA_always_enqueue_fa\u003C\u002Fstrong>: Return true to always enqueue FontAwesome on the frontend, even if no ACF FontAwesome fields are in use on the page. This will enqueue FontAwesome in the header instead of the footer.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>ACFFA_admin_enqueue_fa\u003C\u002Fstrong>: Return false to stop enqueueing FontAwesome in the admin area. Useful if you already have FontAwesome enqueued by some other means.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>ACFFA_get_icons\u003C\u002Fstrong>: (Applies to FontAwesome 4.x and 5.x icons only) Filter the array of icons and icon details loaded from the database\u003C\u002Fli>\n\u003Cli>\u003Cstrong>ACFFA_get_fa_url\u003C\u002Fstrong>: Filter the URL used for enqueuing FontAwesome in the frontend and admin areas of the site.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>ACFFA_override_major_version\u003C\u002Fstrong>: Filter to manually set the ‘major’ version of FontAwesome to load (accepts either 4, 5, or 6). NOTE: This filter must be registered before any calls to ACF get_field() function are made.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>ACFFA_fa_api_key\u003C\u002Fstrong>: Filter to programmatically set the FontAwesome API key.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>ACFFA_fa_kit_token\u003C\u002Fstrong>: Filter to programmatically set the FontAwesome kit token.\u003C\u002Fli>\n\u003C\u002Ful>\n","Adds a new 'Font Awesome Icon' field to the popular Advanced Custom Fields plugin.",1665691,98,36,"2026-01-09T09:54:00.000Z","3.5",[116,117,137,138],"font-awesome","fontawesome","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fadvanced-custom-fields-font-awesome\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fadvanced-custom-fields-font-awesome.5.0.2.zip",99,1,"2026-02-18 00:00:00",{"attackSurface":145,"codeSignals":250,"taintFlows":260,"riskAssessment":261,"analyzedAt":266},{"hooks":146,"ajaxHandlers":246,"restRoutes":247,"shortcodes":248,"cronEvents":249,"entryPointCount":26,"unprotectedCount":26},[147,153,158,162,166,170,174,178,181,183,185,187,189,193,198,202,206,208,212,215,220,223,227,231,234,238,242],{"type":148,"name":149,"callback":150,"file":151,"line":152},"action","init","load_textdomain","src\\WPBT\\WPBT_Bootstrap.php",113,{"type":154,"name":155,"callback":156,"file":157,"line":14},"filter","wp_beta_tester_add_settings_tabs","add_settings_tab","src\\WPBT\\WPBT_Core.php",{"type":148,"name":159,"callback":160,"file":157,"line":161},"wp_beta_tester_add_settings","add_settings",48,{"type":148,"name":163,"callback":164,"priority":47,"file":157,"line":165},"wp_beta_tester_add_admin_page","add_admin_page",49,{"type":148,"name":167,"callback":168,"file":157,"line":169},"wp_beta_tester_update_settings","save_settings",50,{"type":154,"name":171,"callback":172,"file":157,"line":173},"wp_beta_tester_save_redirect","save_redirect_page",126,{"type":154,"name":175,"callback":176,"file":157,"line":177},"wp_sprintf_l","wpbt_sprintf_or",338,{"type":154,"name":155,"callback":156,"file":179,"line":180},"src\\WPBT\\WPBT_Extras.php",58,{"type":148,"name":159,"callback":160,"file":179,"line":182},59,{"type":148,"name":163,"callback":164,"priority":47,"file":179,"line":184},60,{"type":148,"name":167,"callback":168,"file":179,"line":186},61,{"type":154,"name":171,"callback":172,"file":179,"line":188},149,{"type":154,"name":190,"callback":191,"priority":47,"file":179,"line":192},"auto_core_update_send_email","closure",206,{"type":148,"name":194,"callback":195,"file":196,"line":197},"current_screen","add_help_tabs","src\\WPBT\\WPBT_Help.php",21,{"type":148,"name":199,"callback":160,"file":200,"line":201},"admin_init","src\\WPBT\\WPBT_Settings.php",66,{"type":148,"name":203,"callback":204,"file":200,"line":205},"network_admin_edit_wp_beta_tester","update_settings",68,{"type":148,"name":199,"callback":204,"file":200,"line":207},69,{"type":148,"name":209,"callback":210,"file":200,"line":211},"admin_head-plugins.php","action_admin_head_plugins_php",74,{"type":148,"name":213,"callback":210,"file":200,"line":214},"admin_head-update-core.php",75,{"type":148,"name":216,"callback":217,"file":218,"line":219},"update_option_wp_beta_tester_stream","action_update_option_wp_beta_tester_stream","src\\WPBT\\WP_Beta_Tester.php",57,{"type":154,"name":221,"callback":222,"priority":47,"file":218,"line":201},"core_version_check_query_args","set_core_update_channel_constant",{"type":154,"name":224,"callback":224,"priority":225,"file":218,"line":226},"update_footer",11,86,{"type":148,"name":228,"callback":229,"file":218,"line":230},"wp_dashboard_setup","add_dashboard_widget",90,{"type":148,"name":232,"callback":229,"file":218,"line":233},"wp_network_dashboard_setup",91,{"type":148,"name":235,"callback":236,"priority":47,"file":218,"line":237},"upgrader_process_complete","delete_feed_transient_on_upgrade",94,{"type":154,"name":239,"callback":240,"priority":47,"file":218,"line":241},"pre_site_transient_update_core","add_minimal_development_response",399,{"type":148,"name":243,"callback":191,"file":244,"line":245},"plugins_loaded","wp-beta-tester.php",35,[],[],[],[],{"dangerousFunctions":251,"sqlUsage":252,"outputEscaping":254,"fileOperations":26,"externalRequests":142,"nonceChecks":257,"capabilityChecks":258,"bundledLibraries":259},[],{"prepared":26,"raw":26,"locations":253},[],{"escaped":255,"rawEcho":26,"locations":256},56,[],5,2,[],[],{"summary":262,"deductions":263},"The wordpress-beta-tester plugin v4.0.0 exhibits a strong security posture based on the provided static analysis. The complete absence of dangerous functions, raw SQL queries, and unsanitized taint flows is a significant strength. The code correctly utilizes prepared statements for all SQL queries and ensures all output is properly escaped, minimizing risks of injection attacks and cross-site scripting (XSS). Furthermore, the presence of nonce checks and capability checks on its entry points indicates a commitment to secure access control. The plugin also demonstrates good practice by avoiding bundled libraries and performing file operations securely (none detected). The lack of any historical vulnerabilities, including critical or high severity ones, further reinforces its current secure state.\n\nWhile the plugin scores highly on many security metrics, a minor area of consideration is the single external HTTP request. Although not inherently a vulnerability, such requests can become a vector for attacks if the external resource is compromised or if data is transmitted insecurely. The limited number of entry points and the fact that none are found to be unprotected is excellent. In conclusion, this version of wordpress-beta-tester appears to be very secure, with no immediate critical or high-severity risks identified in the static analysis or its vulnerability history. The diligent use of security best practices in its code is commendable.",[264],{"reason":265,"points":258},"External HTTP request detected","2026-03-16T18:34:13.834Z",{"wat":268,"direct":273},{"assetPaths":269,"generatorPatterns":270,"scriptPaths":271,"versionParams":272},[],[],[],[],{"cssClasses":274,"htmlComments":275,"htmlAttributes":276,"restEndpoints":277,"jsGlobals":278,"shortcodeOutput":279},[],[],[],[],[],[]]