Does MainWP Child work with WordPress 7.1 and PHP 8.1.12? A smoke test was performed on .
| 1 | PHP notices |
| No JavaScript exceptions | |
| All test pages loaded successfully | |
| No resource errors |
Memory usage: 251.67 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
insignificant.
The plugin didn't make the site noticeably slower.
| WordPress version | 7.1 |
|---|---|
| PHP version | 8.1.12 |
| MySQL version | 10.6.10 |
| PHP memory limit | 512M |
| Last updated | |
|---|---|
| Active installs | 700,000+ |
| WordPress.org page | https://wordpress.org/plugins/mainwp-child/ |
| Badges |
|
| URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
|---|---|
| Requested URL | /wp-admin/plugins.php?action=activate&plugin=mainwp-child%2Fmainwp-child.php&plugin_status=all&paged=1&s&_wpnonce=04bfa2d167 |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.819 s |
| Memory usage | 5.86 MiB |
| JS errors | None |
| Resource errors | None |
| URL | /wp-admin/options-general.php?page=mainwp_child_tab |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 1.094 s |
| Memory usage | 4.53 MiB |
| JS errors | None |
| Resource errors | None |
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.225 s |
| Memory usage | 4.83 MiB |
| JS errors | None |
| Resource errors | None |
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.944 s | 0.773 s | -0.171 s | 4.23 MiB | 4.49 MiB | + 273.58 KiB |
| /wp-admin/edit.php | 0.543 s | 0.574 s | +0.031 s | 4.28 MiB | 4.53 MiB | + 255.66 KiB |
| /wp-admin/post-new.php | 2.220 s | 1.973 s | -0.247 s | 6.78 MiB | 7.05 MiB | + 278.66 KiB |
| /wp-admin/upload.php | 1.057 s | 1.063 s | +0.006 s | 4.25 MiB | 4.48 MiB | + 238.24 KiB |
| /wp-admin/options-writing.php | 0.556 s | 0.528 s | -0.028 s | 4.22 MiB | 4.46 MiB | + 242.24 KiB |
| /wp-admin/media-new.php | 0.772 s | 0.932 s | +0.160 s | 4.21 MiB | 4.46 MiB | + 250.44 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.557 s | 0.542 s | -0.015 s | 4.22 MiB | 4.47 MiB | + 255.61 KiB |
| /wp-admin/post-new.php?post_type=page | 2.082 s | 1.536 s | -0.546 s | 6.76 MiB | 7.02 MiB | + 271.48 KiB |
| /wp-admin/options-discussion.php | 0.880 s | 0.873 s | -0.007 s | 4.23 MiB | 4.46 MiB | + 234.74 KiB |
| /wp-admin/edit-comments.php | 0.557 s | 1.129 s | +0.572 s | 4.24 MiB | 4.48 MiB | + 238.25 KiB |
| / | 0.306 s | 0.222 s | -0.084 s | 4.6 MiB | 4.83 MiB | + 229.48 KiB |
| Average | 0.952 s | 0.922 s | -0.030 s | 4.73 MiB | 4.97 MiB | + 251.67 KiB |
Note: Third-party libraries and minified JS/CSS files are excluded from these statistics where possible, so the numbers you see here may be lower than those reported by other tools.
| Language | % | Lines of code | Comment lines | Files | |
|---|---|---|---|---|---|
| PHP | 83.4% | 45,227 | 20,433 | 97 | |
| PO File | 16.6% | 9,023 | 4,470 | 4 | |
| JSON | 0.0% | 11 | 0 | 1 | |
| Total | 54,261 | 24,903 | 102 | ||
| Lines of code | 44,608 |
|---|---|
| Total complexity | 12,072 |
| Median class complexity | 75.0 |
| Median method complexity | 3.0 |
| Most complex class | MainWP_Child_Updraft_Plus_Backups |
| Most complex function | MainWP_Child_Wordfence::get_diagnostics() |
| Classes | 97 |
|---|---|
| Methods | 1,906 |
| Functions | 17 |
Things that the plugin adds to the site. This section is not intended to be comprehensive. The test tool only looks for a few specific types of added content.
wp_options 14wp_usermeta 1[25-Aug-2026 16:44:38 UTC] PHP Notice: Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>mainwp-child</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.7.0.) in /wp-includes/functions.php on line 6260