b8150e5d9b
Bump WooCommerce version. https://developer.woocommerce.com/2021/07/23/woocommerce-5-5-2-fix-release/ |
||
|---|---|---|
| Advanced Custom Fields | ||
| Advanced Database Cleaner | ||
| All in One SEO | ||
| Antispam Bee | ||
| Async JavaScript | ||
| Autoptimize | ||
| Beaver Builder | ||
| Cache Enabler | ||
| Classic Editor | ||
| Comet Cache | ||
| Coming Soon Page | ||
| Disable Comments | ||
| Disable Email Notifications | ||
| Disable Gutenberg | ||
| Disable Plugin Deactivation | ||
| Disable WooCommerce Bloat | ||
| Elementor | ||
| General WordPress Keys | ||
| Genesis | ||
| Gutenberg Ramp | ||
| Heartbeat Control | ||
| Hummingbird | ||
| Hyper Cache | ||
| Inactive Logout | ||
| Lazy Load by WP Rocket | ||
| Limit Login Attempts Reloaded | ||
| Machete | ||
| MainWP Child Reports | ||
| NItroPack | ||
| Rank Math SEO | ||
| REST API Toolbox | ||
| Simple Cache | ||
| Site Health Manager | ||
| Site Health Tool Manager | ||
| SmartCrawl | ||
| Speed Booster Pack | ||
| Stop Spammers | ||
| Swift Performance | ||
| W3 Total Cache | ||
| Widget Disable | ||
| WooCommerce | ||
| WordPress Zero Spam | ||
| WP Compress | ||
| WP Fastest Cache | ||
| WP Maintenance Mode | ||
| WP Optimize | ||
| WP Search Insights | ||
| WP Security Audit Log | ||
| WP Super Cache | ||
| WP Widget Disable | ||
| WP-DBManager | ||
| WPS Limit Login | ||
| Yoast Duplicate Post | ||
| Yoast SEO | ||
| README.md | ||
Bulk Setting Manager Keys
This repository contains "Keys" for use with the MainWP Bulk Settings Extension.
The Bulk Settings Extension is a custom plugin built to allow the MainWP Dashboard to control almost any WordPress plugin installed on a MainWP Child site.
How it Works
MainWP Bulk Settings Manager Extension works together with the MainWP Key Maker plugin. The Key Maker plugin grabs necessary data from your WordPress site (where you have set you preferences), next, the Extension converts the data to a key that you can submit to the rest of your child sites and apply your preferences.
Does Bulk Settings Manager work with XYZ plugin or theme?
While we have not tested every plugin or theme Bulk Settings Manager should technically work with any plugin or theme that uses standard forms.
If you want to check if the information you want to work with will be recorded:
- Install the free MainWP Key Maker plugin
- Submit the form you want to be able to use in Bulk Settings Manager.
- Once you have submitted the form press the MainWP Key Maker button that will be in your WP Admin Top Menu.
- You will now see at least 2 “Keys” that will pop up for you “Post-submission Request” and “Pre-submission Request” (you almost always want to use Post-submission since that is the information gathered after you submitted the form).
- Now click on “Verify Form Fields and Values” this will show you in a human readable way what information was gathered.
If everything looks right and all your information was gathered correctly then you can be 99% sure that it will work with Bulk Settings Manager to change all your Child sites.
An example of where Bulk Settings Manager would not work is during the initial setup of JetPack where you are required to leave your Child site to verify login credentials. However, you would be able to set up keys for JetPack after the verify credential step.
Important Notes:
Pre-submission requests often don’t have all fields and values detected. Using the Pre-submission requests may lead to incomplete Keys. We strongly recommend using Post-submission requests!
In order to see the Post-submission request, you need to submit the form that you are trying to grab and make the Key. Once you get to the page where the form is located, make sure that the wanted values are correctly set, submit the form and after that, you will be able to see the Post-submission request.
Some forms are divided in multiple mini-forms. MainWP Key Maker plugin detects all mini-forms and displays Post-submission requests for all of them.
If you get multiple Post-Submission requests, be sure to use the Verify Form Fields and Values button and find the “biggest” one. The request that is showing all form fields will probably be the one.
