[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fTZNHU6fVTVy3pXksRtilvuqKt8lP7bEGDFzhmUPJ0Ck":3},{"slug":4,"display_name":5,"profile_url":6,"plugin_count":7,"total_installs":8,"avg_security_score":9,"avg_patch_time_days":10,"trust_score":11,"computed_at":12,"plugins":13},"webheadllc","webheadcoder","https:\u002F\u002Fprofiles.wordpress.org\u002Fwebheadllc\u002F",6,95150,100,649,79,"2026-04-04T00:35:23.151Z",[14,41,63,84,101,119],{"slug":15,"name":16,"version":17,"author":5,"author_profile":6,"description":18,"short_description":19,"active_installs":20,"downloaded":21,"rating":22,"num_ratings":23,"last_updated":24,"tested_up_to":25,"requires_at_least":26,"requires_php":27,"tags":28,"homepage":34,"download_link":35,"security_score":36,"vuln_count":37,"unpatched_count":38,"last_vuln_date":39,"fetched_at":40},"contact-form-7-multi-step-module","Contact Form 7 Multi-Step Forms","4.6","\u003Cp>Add multi-step forms to Contact Form 7 with full data persistence between pages and a single email on final submission. Upgrade to Pro to submit 5MB forms through sessionStorage, conditional step-skipping, and priority support.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>The Original Contact Form 7 Multi-Step Plugin\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Since 2012, this has been the go-to multi-step solution for Contact Form 7 users. It’s built for reliability and trusted on thousands of sites. Split your CF7 form across multiple pages, preserve data between steps, and send one complete email at the end.\u003C\u002Fp>\n\u003Cp>It’s been running quietly on thousands of sites through every major WordPress and CF7 release. If you need multi-step forms with CF7, this is where most people start.\u003C\u002Fp>\n\u003Cp>See it in action at \u003Ca href=\"https:\u002F\u002Fwebheadcoder.com\u002Fcontact-form-7-multi-step-form\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fwebheadcoder.com\u002Fcontact-form-7-multi-step-form\u002F\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>Requires \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcontact-form-7\u002F\" rel=\"ugc\">Contact Form 7\u003C\u002Fa> (5.2 or above) by Rock Lobster Inc. (Takayuki Miyoshi).\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Usage\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Col>\n\u003Cli>\n\u003Cp>Create one page or post for each step in your multi-step form process.  If you have 3 steps, create 3 pages\u002Fposts.  You will need the urls to these when creating your forms.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Create a Contact Form 7 form.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Place your cursor at the end of the form.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>On the “Form” tab of the Contact Form 7 form, click on the button named “multistep”.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>In the window that pops up, check the checkbox next to “First Step” if this is the first step of your multi step forms.  If this is your last step in the multi step forms, check the “Last Step” checkbox.  All other checkboxes are optional.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>The Next Page URL is the url that contains your next form.  If this form is the last step, you can leave the URL field blank.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Click “Insert Tag”\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Save your completed form and place the form’s shortcode into the appropriate Page\u002FPost you created in step 1.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Repeat for \u003Cstrong>each form\u003C\u002Fstrong> in your multi-step form process.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>On the last step, you probably would want to send an email.  Make sure to check the “Send Email” checkbox in step 5.  On the Mail Tab, simply enter the mail-tags as you normally would.  For example if your first form has the field \u003Ccode>your-email\u003C\u002Fcode> you can include \u003Ccode>[your-email]\u003C\u002Fcode> in the Mail tab on your last form.  Note:  CF7 will see this as an error because \u003Ccode>your-email\u003C\u002Fcode> may not be displayed on the current form.  You can safely ignore this error.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>\u003Cstrong>Multistep Tag Options\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Name\u003C\u002Fstrong> – The name of this multistep form-tag.  This is required, but is currently not being used.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>First Step\u003C\u002Fstrong> – Besides marking the first step of your multistep forms, this allows any form to act as the first step and show when no previous data has ben submitted.  This is useful when you want some users to skip the first step.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Last Step\u003C\u002Fstrong> – Besides marking the last step of you multistep forms, this clears the data from user’s browsers.  Once they submit this form they won’t see their data populating the forms anymore.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Send Email\u003C\u002Fstrong> – If this is checked the form will send an email like a normal Contact Form 7 submission.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Skip Save\u003C\u002Fstrong> – If you use Flamingo or CFDB7 to save submissions to the database this prevents saving this form submission.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Next Page URL\u003C\u002Fstrong> – This is the URL your users will go to after the form is submitted.\u003C\u002Fp>\n\u003Cp>[multistep multistep-123 last_step send_email skip_save “\u002Fthank-you”]\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Additional Tags\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[multiform \"your-name\"]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The \u003Ccode>multiform\u003C\u002Fcode> form-tag can be used to display a field from a previous step.  Replace \u003Ccode>your-name\u003C\u002Fcode> with the name of your field.  This is only for use on the Form tab, this tag will not work in the Mail tab.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[previous \"Go Back\"]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The \u003Ccode>previous\u003C\u002Fcode> form-tag can be used to display a button to go to a previous step.  Replace \u003Ccode>Go Back\u003C\u002Fcode> with text you want to show in the button.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Messages Tab\u003C\u002Fstrong>\u003Cbr \u002F>\nWhen a visitor to your site visits the 4th step in your multi step form without filling out the 1st step, the message “Please fill out the form on the previous page.” will be displayed.  You can change this on each form in the Messages tab.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What this plugin DOES NOT do:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>This plugin does not support file uploads on every form.  If you need to use file uploads make sure to place it on the last step.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>This plugin does not load another form on the same page.  It only works when the forms are on separate pages.  Many have asked to make it load via ajax so all forms can reside on one page.  This plugin does not support that.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>PRO Version\u003C\u002Fstrong>\u003Cbr \u002F>\nIf you expect to have a lot of data submitted through your multi-step forms, the Pro version may be able to help you better.  The PRO version uses Session Storage so it is able to handle roughly 1,000 times more data for your multiple forms.  In total it can handle about 5MB vs 4KB in the free version.  \u003Cstrong>Currently the Pro version REQUIRES the WordPress REST API and Contact Form 7 AJAX Submission to be enabled.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Another feature the Pro version offers is the ability to skip steps with the “Contact Form 7 – Conditional Fields plugin”.  \u003Ca href=\"https:\u002F\u002Fwebheadcoder.com\u002Fcontact-form-7-multi-step-forms\u002F#pro\" rel=\"nofollow ugc\">Learn more here.\u003C\u002Fa>\u003C\u002Fp>\n","Enables the Contact Form 7 plugin to create multi-page, multi-step forms.",50000,821068,84,49,"2026-02-16T17:47:00.000Z","6.9.4","4.7","",[29,30,31,32,33],"cf7","contact-form-7","multi-page-form","multistep-form","persist","http:\u002F\u002Fwww.mymonkeydo.com\u002Fcontact-form-7-multi-step-module\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcontact-form-7-multi-step-module.4.6.zip",99,1,0,"2019-02-25 00:00:00","2026-03-15T15:16:48.613Z",{"slug":42,"name":43,"version":44,"author":5,"author_profile":6,"description":45,"short_description":46,"active_installs":47,"downloaded":48,"rating":49,"num_ratings":50,"last_updated":51,"tested_up_to":52,"requires_at_least":53,"requires_php":27,"tags":54,"homepage":60,"download_link":61,"security_score":9,"vuln_count":38,"unpatched_count":38,"last_vuln_date":62,"fetched_at":40},"clear-cache-for-widgets","Clear Cache for Me","2.4.2","\u003Cp>W3 Total Cache and WP Super Cache are great caching plugins, but they do not know when a widget is updated.  WPEngine is the best place to host your WordPress installation, but their caching system is no smarter when it comes to updating widgets and menus.  I created this plugin because my website did not see any changes when saving widgets or menus using these caching systems.  Clear Cache For Me will purge ALL your cache each time you do a save without having to press an additional button.  It may be overkill, which may be why it’s not built in, but some people need simplicity.\u003C\u002Fp>\n\u003Cp>In addition to clearing those pesky caching engines, Clear Cache for Me can force your browser to reload your current theme’s CSS and JS files.  I modify my theme’s CSS and JS files every so often and always have trouble with the browser not getting the latest version.  So now after clicking on the “Clear Cache Now!” button on the dashboard the browser will be forced to reload the current theme’s CSS and JS files.  If you do not click the “Clear Cache Now!” button, the browser will cache the CSS and JS files like it normally does.\u003C\u002Fp>\n\u003Cp>The popular Qode themes has a options to set your own custom CSS and JS.  Sometimes you may not see your changes for a long while because your browser is trying to get the cached file.  Whenever you save your Qode’s options, the CSS and JS files will be forced to reload in the browser on the public side.\u003C\u002Fp>\n\u003Cp>Works with the following caching plugins:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Autoptimize\u003C\u002Fli>\n\u003Cli>Breeze Cache\u003C\u002Fli>\n\u003Cli>Cache Enabler\u003C\u002Fli>\n\u003Cli>GoDaddy Cache\u003C\u002Fli>\n\u003Cli>Kinsta Cache\u003C\u002Fli>\n\u003Cli>LiteSpeed Cache\u003C\u002Fli>\n\u003Cli>Elementor (CSS cache)\u003C\u002Fli>\n\u003Cli>Premium Addons for Elementor\u003C\u002Fli>\n\u003Cli>SiteGround SuperCacher\u003C\u002Fli>\n\u003Cli>Super Page Cache\u003C\u002Fli>\n\u003Cli>WP Fastest Cache\u003C\u002Fli>\n\u003Cli>WP Optimize Cache\u003C\u002Fli>\n\u003Cli>WP Rocket\u003C\u002Fli>\n\u003Cli>WP Super Cache\u003C\u002Fli>\n\u003Cli>W3 Total Cache\u003C\u002Fli>\n\u003Cli>WPEngine Cache\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Clears all cache for following actions (requires a caching system above to be active):\u003C\u002Fp>\n\u003Cul>\n\u003Cli>When Widgets are saved.\u003C\u002Fli>\n\u003Cli>When Customizer is saved.\u003C\u002Fli>\n\u003Cli>When Menus are saved.\u003C\u002Fli>\n\u003Cli>When a fields in Advanced Custom Fields are saved.\u003C\u002Fli>\n\u003Cli>When a Contact Form 7 form is saved.\u003C\u002Fli>\n\u003Cli>When a Formidable Form form is saved.\u003C\u002Fli>\n\u003Cli>When WooThemes settings are saved.\u003C\u002Fli>\n\u003Cli>When NextGen Gallery albums and galleries are updated (beta – may not clear cache on all actions).\u003C\u002Fli>\n\u003Cli>When Qode options are saved this plugin forces browsers to reload the custom css and custom js.\u003C\u002Fli>\n\u003Cli>When a WP Forms forms or settings are saved.\u003C\u002Fli>\n\u003Cli>When WooCommerce settings are saved. (Cache should already be clearing when products are saved.)\u003C\u002Fli>\n\u003Cli>When settings from the Insert Headers and Footers plugin by WPBeginner are saved.  \u003C\u002Fli>\n\u003Cli>When Settings from a settings page is saved.  This includes settings from WordPress core, Yoast SEO, and most other plugins using the Settings API.\u003C\u002Fli>\n\u003Cli>When WordPress is updated.\u003C\u002Fli>\n\u003Cli>When plugins are updated, activated, and deactivated.\u003C\u002Fli>\n\u003Cli>When WordPress, plugins, and themes are automaticallly updated.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwebheadcoder.com\u002Fclear-cache-for-me\u002F\" rel=\"nofollow ugc\">See the plugin’s homepage for more details\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Note:  Since some caching systems run in the \u003Ccode>shutdown\u003C\u002Fcode> hook, this plugin also runs in that hook.  This means if PHP does not have enough time, some code including any hooks within the \u003Ccode>ccfm_clear_cache_for_all()\u003C\u002Fcode> function are not guaranteed to run.  If you need code to run, consider using the \u003Ccode>ccfm_clear_cache_for_me_setup\u003C\u002Fcode> hook.\u003C\u002Fp>\n\u003Ch3>Developer Options\u003C\u002Fh3>\n\u003Ch4>ccfm_supported_caching_exists\u003C\u002Fh4>\n\u003Cp>Use this filter to determine if this plugin should do anything including showing the button on the dashboard.  Return true if a caching system is supported.\u003Cbr \u002F>\nDefault: True if any of the supported caching systems is active.\u003Cbr \u002F>\nSee Example 1 below.\u003C\u002Fp>\n\u003Ch4>ccfm_admin_init or ccfm_init_actions\u003C\u002Fh4>\n\u003Cp>Use this action to add hooks when cache is to be cleared.  Or do any other setup activity.\u003C\u002Fp>\n\u003Ch4>ccfm_clear_cache_for_me_before\u003C\u002Fh4>\n\u003Cp>Use this action to clear cache from an unsupported caching system before the default caching systems clear their cache.\u003C\u002Fp>\n\u003Ch4>ccfm_clear_cache_for_me\u003C\u002Fh4>\n\u003Cp>Use this action to clear cache from an unsupported caching system after the default caching systems clear their cache.\u003C\u002Fp>\n\u003Ch4>Example\u003C\u002Fh4>\n\u003Cp>If you were using an unsupported caching system you’ll need to identify the caching plugin’s class or function which clears the cache.  As an example, if the unsupported caching system called the \u003Ccode>MyOtherCache::clear_all()\u003C\u002Fcode> function, you would use the following code to get this plugin to clear the cache.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003C?php\nfunction my_other_cache_enable( $return = false ) {\n    if ( class_exists( 'MyOtherCache' ) )\n        return true;\n    return $return;\n}\nadd_filter('ccfm_supported_caching_exists', 'my_other_cache_enable');\n\nfunction my_other_cache_clear() {\n    if ( my_other_cache_enable() )\n        MyOtherCache::clear_all();\n}\nadd_action('ccfm_clear_cache_for_me', 'my_other_cache_clear');\n\u003C\u002Fcode>\u003C\u002Fpre>\n","Purges cache on WPEngine, W3TC, WP Super Cache, WP Fastest Cache when widgets, menus, settings update.  Forces browsers to reload CSS and JS files.",40000,728677,96,29,"2025-06-09T02:36:00.000Z","6.8.5","3.8",[55,56,57,58,59],"cache","clear","css","js","purge","https:\u002F\u002Fwebheadcoder.com\u002Fclear-cache-for-me\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fclear-cache-for-widgets.2.4.2.zip",null,{"slug":64,"name":65,"version":66,"author":5,"author_profile":6,"description":67,"short_description":68,"active_installs":69,"downloaded":70,"rating":71,"num_ratings":72,"last_updated":73,"tested_up_to":25,"requires_at_least":74,"requires_php":75,"tags":76,"homepage":82,"download_link":83,"security_score":9,"vuln_count":38,"unpatched_count":38,"last_vuln_date":62,"fetched_at":40},"wp-cron-status-checker","WP-Cron Status Checker","1.2.8","\u003Cp>\u003Cstrong>What happens if WP-Cron stops working?\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>WordPress, Themes, and Plugins would never know if a new version is out.  You could login to your website everyday for months, and never see any notices about updates. If you’re not careful you’ll soon have an out of date WordPress installation susceptible to hackers.  Scheduled posts would never get published, auto drafts never deleted… you get the picture.  Your website would crumble up and die.\u003C\u002Fp>\n\u003Cp>Use Woocommerce?  Subscriptions?  Customers would never get billed again!  Sessions would never be deleted.  Scheduled sales would never appear.  Your website would become bloated while giving away subscriptions for one time payments.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>WP-Cron is important.  So make sure it keeps working.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Think of this plugin as insurance, but free.  WordPress, plugins, themes, and servers are all moving parts that can be updated at anytime.  You can’t guarantee any of these changes won’t break your website in some way.  While it’s not likely WP-Cron will stop working, if it does, you better know about it.\u003C\u002Fp>\n\u003Cp>Every 24 hours this plugin automatically checks to see if WP-Cron is still able to run.  Obviously, it does not depend on WP-Cron.  Instead it sets its own transients that expire over 24 hours.  Whenever the transient expires it checks to make sure WordPress can run WP-Cron.  If an unexpected error occurs the you’ll get an email.\u003C\u002Fp>\n\u003Cp>In addition to checking if WP-Cron CAN run, this plugin now logs all hooks running with WP-Cron and if they fail or complete.  You’ll be able to see what ran, when it ran, how long it took, and if it completed.\u003C\u002Fp>\n\u003Cp>For your convenience The WP-Cron Status Checker is displayed on your WordPress admin dashboard.  The status page is accessible through the Tools -> WP Cron Status side menu.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Know when WP-Cron doesn’t complete\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>When a WP-Cron hook fails you’ll get notified soon after.  A hook “fails” when it takes longer than 5 minutes to complete.  You’ll get an email within 24 hours (or based on the plugin’s settings) to notify you of any failures.\u003C\u002Fp>\n\u003Cp>Sometimes a plugin runs some code that abruptly exits the process and there is no way of knowing when it stopped.  WP-Cron Status Checker does it’s best to detect this type of code.  If it’s caught, the elapsed time is not recorded and you’ll see “N\u002FA” with an “Incomplete” status.  Other times when it’s caught you’ll see an “Exit” status which is considered complete.  \u003Ca href=\"https:\u002F\u002Fwebheadcoder.com\u002Fwp-cron-status-checker\u002F\" rel=\"nofollow ugc\">Please see the plugin page for more on completion statuses.\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>PRO Version\u003C\u002Fstrong>\u003Cbr \u002F>\nThe PRO version removes the 3 log limit and lets you choose to keep logs longer and email more frequently.  Please see more on the plugin page:  \u003Ca href=\"https:\u002F\u002Fwebheadcoder.com\u002Fwp-cron-status-checker\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fwebheadcoder.com\u002Fwp-cron-status-checker\u002F\u003C\u002Fa>\u003C\u002Fp>\n","If WP-Cron runs important things for you, you better make sure WP-Cron always runs!",5000,118334,70,8,"2026-01-10T00:17:00.000Z","4.0","5.6",[77,78,79,80,81],"check","cron","logging","notify","scheduled","https:\u002F\u002Fwebheadcoder.com\u002Fwp-cron-status-checker","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-cron-status-checker.1.2.8.zip",{"slug":85,"name":86,"version":87,"author":5,"author_profile":6,"description":88,"short_description":89,"active_installs":9,"downloaded":90,"rating":9,"num_ratings":37,"last_updated":91,"tested_up_to":25,"requires_at_least":74,"requires_php":27,"tags":92,"homepage":98,"download_link":99,"security_score":36,"vuln_count":37,"unpatched_count":38,"last_vuln_date":100,"fetched_at":40},"wh-tweaks","WH Tweaks","1.0.3","\u003Cp>Often times, ideas from WordPress Ideas (https:\u002F\u002Fwordpress.org\u002Fideas\u002F) or bugs from WordPress Trac (https:\u002F\u002Fcore.trac.wordpress.org\u002F) take years to make it into WordPress Core.  Sometimes even if everyone agrees on the fix it still doesn’t get in.  This plugin is the temporary patch you’ve been waiting for.  Activate any feature you want and disable any you don’t want.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Allow excerpts to show links.\u003C\u002Fli>\n\u003Cli>Obscure login errors so an attacker will not know if a username exists.\u003C\u002Fli>\n\u003Cli>Hide WordPress version in both meta tags and script inclusions.\u003C\u002Fli>\n\u003Cli>Make category children highlighted with a subtle gray background.\u003C\u002Fli>\n\u003Cli>Some added shortcodes.\u003C\u002Fli>\n\u003Cli>Customize login.\u003C\u002Fli>\n\u003Cli>Remove emoji scripts and styles.\u003C\u002Fli>\n\u003Cli>Automatically set the Return-Path to the From address if it’s not already set (Trac #22837).\u003C\u002Fli>\n\u003Cli>Show private pages in parent dropdowns (Trac #8592).\u003C\u002Fli>\n\u003Cli>Allow commas in category terms (Trac #14691).\u003C\u002Fli>\n\u003Cli>Show sidebar from main site in Multisite (Trac #22370).\u003C\u002Fli>\n\u003Cli>Disable default WordPress REST API endpoints.\u003C\u002Fli>\n\u003Cli>Remove author pages from public viewing.\u003C\u002Fli>\n\u003Cli>Redirect user enumeration to 403 Forbidden page.\u003C\u002Fli>\n\u003Cli>Resolve PHP notices about “ob_end_flush()” (Trac #18525 and #22430).  \u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Each of these options can be turned on or off on the Settings -> WH Tweaks page.\u003C\u002Fp>\n","Common functionality WordPress core should have but maybe shouldn't.",4149,"2026-01-07T06:39:00.000Z",[93,94,95,96,97],"bugs","codex","fix","problems","trac","https:\u002F\u002Fwebheadcoder.com\u002Fwh-tweaks","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwh-tweaks.1.0.3.zip","2025-12-21 00:00:00",{"slug":102,"name":103,"version":104,"author":5,"author_profile":6,"description":105,"short_description":106,"active_installs":107,"downloaded":108,"rating":9,"num_ratings":37,"last_updated":109,"tested_up_to":52,"requires_at_least":110,"requires_php":27,"tags":111,"homepage":27,"download_link":117,"security_score":36,"vuln_count":37,"unpatched_count":38,"last_vuln_date":118,"fetched_at":40},"wp-log-action","WP Log Action","0.54","\u003Cp>This plugin uses hooks in the opposite way most plugins do.  You add \u003Ccode>do_action\u003C\u002Fcode> where you want to do some logging and this plugin will save it to the database only when active.\u003C\u002Fp>\n\u003Ch4>Log Activity\u003C\u002Fh4>\n\u003Cp>This plugin now logs plugin activity (when activated, deactivated, deleted, updated, installed), when wordpress is updated, and when functions are used wrong or deprecated.\u003C\u002Fp>\n\u003Cp>Example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>do_action( 'wp_log_info', 'So far ok', 'Details of what is ok.' );\nif ( $something_bad_happened ) {\n    do_action( 'wp_log_error', 'This Happened!', 'Details of what happened.' );\n    ...\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>See Tools->Logs to view, delete, and export the logs on the admin side.  Only users with the manage_options capability will have access.\u003C\u002Fp>\n\u003Cp>This plugin automatically logs deprecated and doing_it_wrong errors.  The rest is what you add to your code.\u003C\u002Fp>\n\u003Cp>You can log what functions will be run for a specific action or filter.  For example if you want to see what runs in the ‘init’ hook:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>function check_init_hook() {\n    do_action( 'wp_log_debug_hook', 'init' );\n}\nadd_filter( 'init', 'check_init_hook', 0 );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The following are the different levels of logging to add to your code.  You can use any level how you see fit, the descriptions of each level are just guidelines.\u003C\u002Fp>\n\u003Ch4>Emergency\u003C\u002Fh4>\n\u003Cp>System is unusable\u003Cbr \u002F>\n    do_action( ‘wp_log_emergency’, $label, $message );\u003C\u002Fp>\n\u003Ch4>Alert\u003C\u002Fh4>\n\u003Cp>Action must be taken immediately.\u003Cbr \u002F>\n    do_action( ‘wp_log_alert’, $label, $message );\u003C\u002Fp>\n\u003Ch4>Critical\u003C\u002Fh4>\n\u003Cp>Critical conditions.\u003Cbr \u002F>\n    do_action( ‘wp_log_critical’, $label, $message );\u003C\u002Fp>\n\u003Ch4>Error\u003C\u002Fh4>\n\u003Cp>Runtime errors that do not require immediate action but should typically be logged and monitored.\u003Cbr \u002F>\n    do_action( ‘wp_log_error’, $label, $message );\u003C\u002Fp>\n\u003Ch4>Warning\u003C\u002Fh4>\n\u003Cp>Exceptional occurrences that are not errors.\u003Cbr \u002F>\n    do_action( ‘wp_log_warning’, $label, $message );\u003C\u002Fp>\n\u003Ch4>Notice\u003C\u002Fh4>\n\u003Cp>Normal but significant events.\u003Cbr \u002F>\n    do_action( ‘wp_log_notice’, $label, $message );\u003C\u002Fp>\n\u003Ch4>Info\u003C\u002Fh4>\n\u003Cp>Interesting events.\u003Cbr \u002F>\n    do_action( ‘wp_log_info’, $label, $message );\u003C\u002Fp>\n\u003Ch4>Debug\u003C\u002Fh4>\n\u003Cp>Detailed debug information.\u003Cbr \u002F>\n    do_action( ‘wp_log_debug’, $label, $message );\u003C\u002Fp>\n","Add error or debug logging in your code and leave it there.  Logs will only be recorded with this plugin, otherwise will be ignored.",40,4580,"2025-05-06T21:22:00.000Z","5.3",[112,113,114,115,116],"activity","debug","developer-tool","log","warning","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-log-action.0.54.zip","2024-12-10 00:00:00",{"slug":120,"name":121,"version":122,"author":5,"author_profile":6,"description":123,"short_description":124,"active_installs":125,"downloaded":126,"rating":9,"num_ratings":37,"last_updated":127,"tested_up_to":52,"requires_at_least":128,"requires_php":129,"tags":130,"homepage":27,"download_link":136,"security_score":9,"vuln_count":38,"unpatched_count":38,"last_vuln_date":62,"fetched_at":40},"no-js-social-sharing","No JS Social Sharing","1.2","\u003Cp>No tracking, no logins, no extracurricular scripts.   This plugin provides social media icons to share your post without the BS.\u003C\u002Fp>\n\u003Cp>This plugin is designed for the pure purpose of having social media icons above and\u002For below your posts with Google’s Page Speed score in mind.  Other plugins load scripts that lead to “Remove unused Javascript”, “Eliminate render-blocking resources”, or “Reduce JavaScript execution time” flags.  This plugin will not load any javascript on the front-end and will only load the social media icons and a short string of styles to your page – unless you don’t want it to.\u003C\u002Fp>\n\u003Cp>You can also choose to not automatically show the icons anywhere (choose “None” for placement in the settings) and instead use a shortcode:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[njss text=\"Share this post on:\" networks=\"facebook,twitter,pinterest,email\" icon_size=\"32\"]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>This plugin currently only has Facebook, Twitter, Pinterest, and email built in.\u003C\u002Fp>\n","No tracking, no logins, no extracurricular scripts.   This plugin provides social media icons to share your post without the BS.",10,1209,"2025-05-14T21:13:00.000Z","5.0","7.0",[131,132,133,134,135],"optimized","pagespeed","seo","share","simple","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fno-js-social-sharing.1.2.zip"]