WP Customer Area 8.1.2

Does WP Customer Area work with WordPress 6.1.1 and PHP 7.4.8? A smoke test was performed on .

Summary

Errors
30PHP notices
No JavaScript exceptions
All test pages loaded successfully
No resource errors
Performance

Memory usage: 1.45 MiB
The average PHP memory usage increased by this amount after activating by the plugin.

Page speed impact: 0.033 seconds
The average page load time increased by this amount after activating the plugin.

Environment
WordPress version6.1.1
PHP version7.4.8
MySQL version8.0.21
PHP memory limit256M
Plugin Info
Last updated
Active installs 10,000+
WordPress.org page https://wordpress.org/plugins/customer-area/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 16

Install WP Customer Area ‹ Test site — WordPress

Page screenshot: Install WP Customer Area ‹ Test site — WordPress
URL /wp-admin/admin.php?page=wpca-setup
Requested URL /wp-admin/plugins.php?action=activate&plugin=customer-area%2Fcustomer-area.php&plugin_status=all&paged=1&s&_wpnonce=dd8c70360a
Aspect after-activation
HTTP status 200
Load time 0.645 s
Memory usage 4.95 MiB
JS errors None
Resource errors None

Settings → WP Customer Area

Page screenshot: Settings → WP Customer Area
URL /wp-admin/options-general.php?page=wpca-settings
Aspect menu-item
HTTP status 200
Load time 0.211 s
Memory usage 4.87 MiB
JS errors None
Resource errors None

Settings → WP Customer Area → Frontend

Page screenshot: Settings → WP Customer Area → Frontend
URL /wp-admin/options-general.php?page=wpca-settings&tab=cuar_frontend
Aspect menu-item-tab
HTTP status 200
Load time 0.157 s
Memory usage 4.85 MiB
JS errors None
Resource errors None

Settings → WP Customer Area → Site Pages

Page screenshot: Settings → WP Customer Area → Site Pages
URL /wp-admin/options-general.php?page=wpca-settings&tab=cuar_customer_pages
Aspect menu-item-tab
HTTP status 200
Load time 0.246 s
Memory usage 4.97 MiB
JS errors None
Resource errors None

Settings → WP Customer Area → Capabilities

Page screenshot: Settings → WP Customer Area → Capabilities
URL /wp-admin/options-general.php?page=wpca-settings&tab=cuar_capabilities
Aspect menu-item-tab
HTTP status 200
Load time 0.226 s
Memory usage 4.89 MiB
JS errors None
Resource errors None

Settings → WP Customer Area → Private Pages

Page screenshot: Settings → WP Customer Area → Private Pages
URL /wp-admin/options-general.php?page=wpca-settings&tab=cuar_private_pages
Aspect menu-item-tab
HTTP status 200
Load time 0.160 s
Memory usage 4.85 MiB
JS errors None
Resource errors None

Settings → WP Customer Area → Private Files

Page screenshot: Settings → WP Customer Area → Private Files
URL /wp-admin/options-general.php?page=wpca-settings&tab=cuar_private_files
Aspect menu-item-tab
HTTP status 200
Load time 0.394 s
Memory usage 5.15 MiB
JS errors None
Resource errors None

Private area

Page screenshot: Private area
URL /wp-admin/admin.php?page=wpca-logs
Aspect menu-item
HTTP status 200
Load time 0.149 s
Memory usage 4.98 MiB
JS errors None
Resource errors None

Private area → Status

Page screenshot: Private area → Status
URL /wp-admin/admin.php?page=wpca-status
Aspect menu-item
HTTP status 200
Load time 0.153 s
Memory usage 4.88 MiB
JS errors None
Resource errors None

Private area → Status → Installed add-ons

Page screenshot: Private area → Status → Installed add-ons
URL /wp-admin/admin.php?page=wpca-status&tab=installed-addons
Aspect menu-item-tab
HTTP status 200
Load time 0.141 s
Memory usage 5.03 MiB
JS errors None
Resource errors None

Private area → Status → Pages

Page screenshot: Private area → Status → Pages
URL /wp-admin/admin.php?page=wpca-status&tab=customer-pages
Aspect menu-item-tab
HTTP status 200
Load time 0.135 s
Memory usage 4.9 MiB
JS errors None
Resource errors None

Private area → Status → Actions and filters

Page screenshot: Private area → Status → Actions and filters
URL /wp-admin/admin.php?page=wpca-status&tab=hooks
Aspect menu-item-tab
HTTP status 200
Load time 0.328 s
Memory usage 6.34 MiB
JS errors None
Resource errors None

Private area → Status → Templates

Page screenshot: Private area → Status → Templates
URL /wp-admin/admin.php?page=wpca-status&tab=templates
Aspect menu-item-tab
HTTP status 200
Load time 0.221 s
Memory usage 4.96 MiB
JS errors None
Resource errors None

Private area → Status → Settings

Page screenshot: Private area → Status → Settings
URL /wp-admin/admin.php?page=wpca-status&tab=reset
Aspect menu-item-tab
HTTP status 200
Load time 0.159 s
Memory usage 4.89 MiB
JS errors None
Resource errors None

Test site – Just another WordPress site

Page screenshot: Test site – Just another WordPress site
URL /
Aspect front-page
HTTP status 200
Load time 0.605 s
Memory usage 4.68 MiB
JS errors None
Resource errors None

Widgets ‹ Test site — WordPress

Page screenshot: Widgets ‹ Test site — WordPress
URL /wp-admin/widgets.php
Aspect new-sidebar-widgets
HTTP status 200
Load time 2.823 s
Memory usage 6.91 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.304 s0.370 s+0.066 s3.54 MiB5.01 MiB+ 1.47 MiB
/wp-admin/edit.php0.167 s0.192 s+0.025 s3.57 MiB5.04 MiB+ 1.47 MiB
/wp-admin/post-new.php0.741 s1.058 s+0.317 s5.46 MiB6.94 MiB+ 1.48 MiB
/wp-admin/upload.php0.451 s0.384 s-0.067 s3.41 MiB4.87 MiB+ 1.46 MiB
/wp-admin/options-writing.php0.135 s0.167 s+0.032 s3.4 MiB4.87 MiB+ 1.47 MiB
/wp-admin/media-new.php0.230 s0.225 s-0.005 s3.38 MiB4.85 MiB+ 1.46 MiB
/wp-admin/edit-tags.php?taxonomy=category0.155 s0.187 s+0.032 s3.48 MiB4.96 MiB+ 1.48 MiB
/wp-admin/post-new.php?post_type=page0.651 s0.616 s-0.035 s5.46 MiB6.93 MiB+ 1.48 MiB
/wp-admin/options-discussion.php0.195 s0.197 s+0.002 s3.38 MiB4.87 MiB+ 1.48 MiB
/wp-admin/edit-comments.php0.183 s0.216 s+0.033 s3.48 MiB4.96 MiB+ 1.48 MiB
/0.295 s0.256 s-0.039 s3.46 MiB4.68 MiB+ 1.21 MiB
Average 0.319 s0.352 s+0.033 s3.82 MiB5.27 MiB+ 1.45 MiB

Code Statistics

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.

PO File
PHP
Language % Lines of code Comment lines Files
PO File69.6%96,72951,91129
PHP20.8%28,9519,547284
JavaScript4.5%6,2951,73124
SVG1.9%2,70703
LESS1.6%2,25113039
JSON1.1%1,55705
CSS0.2%33174
Markdown0.1%12404
Total 138,945 63,326 392

PHP Code Analysis | More results »

Lines of code 23,220
Total complexity 4,252
Median class complexity 15.0
Median method complexity 1.0
Most complex class CUAR_Settings
Most complex function CUAR_CountryHelper::getStates()
Classes 127
Methods 1,524
Functions 63

Additions

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.

Options wp_options 11

User Metadata wp_usermeta 2

Custom Post Types 3

ID Name
cuar_log_eventLog events
cuar_private_pagePrivate Pages
cuar_private_filePrivate Files

Sidebar Widgets 8

ID Name
cuar_private_file_categoriesWPCA - File Categories
cuar_private_file_archivesWPCA - File Archives
cuar_private_filesWPCA - Recent Files
cuar_private_file_authorsWPCA - File Authors
cuar_private_page_categoriesWPCA - Page Categories
cuar_private_page_archivesWPCA - Page Archives
cuar_private_pagesWPCA - Recent Pages
cuar_private_page_authorsWPCA - Page Authors

Capabilities 26

PHP Error Log 30 lines

[16-Nov-2022 10:15:18 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:18 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:19 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:19 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:20 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:21 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:22 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:23 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:24 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:25 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:26 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:27 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:28 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:29 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:33 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:35 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:37 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:37 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:38 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:40 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:41 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:41 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:41 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:41 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:43 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:43 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:44 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:44 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:50 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
[16-Nov-2022 10:15:50 UTC] PHP Notice:  Function add_menu_page was called <strong>incorrectly</strong>. The seventh parameter passed to <code>add_menu_page()</code> should be numeric representing menu position. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.0.0.) in /wp-includes/functions.php on line 5835
See also: All tests for this plugin, How to Hide WP Customer Area Admin Menus