Does Aplazame work with WordPress 6.2.2 and PHP 8.1.12? A smoke test was performed on .
| 2 | PHP fatal errors |
| No JavaScript exceptions | |
| All test pages loaded successfully | |
| No resource errors |
Memory usage: 13.95 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 | 6.2.2 |
|---|---|
| PHP version | 8.1.12 |
| MySQL version | 10.6.10 |
| PHP memory limit | 512M |
| Last updated | |
|---|---|
| Active installs | 500+ |
| WordPress.org page | https://wordpress.org/plugins/aplazame/ |
| Badges |
|
| URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
|---|---|
| Requested URL | /wp-admin/plugins.php?action=activate&plugin=aplazame%2Faplazame.php&plugin_status=all&paged=1&s&_wpnonce=09d48cbdff |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.478 s |
| Memory usage | 3.04 MiB |
| JS errors | None |
| Resource errors | None |
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.138 s |
| Memory usage | N/A |
| JS errors | None |
| Resource errors | None |
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.260 s | 0.254 s | -0.006 s | 3.07 MiB | 3.09 MiB | + 22.25 KiB |
| /wp-admin/edit.php | 0.174 s | 0.187 s | +0.013 s | 3.1 MiB | 3.12 MiB | + 22.25 KiB |
| /wp-admin/post-new.php | 0.708 s | 0.888 s | +0.180 s | 5.02 MiB | 5.05 MiB | + 26.62 KiB |
| /wp-admin/upload.php | 0.542 s | 0.309 s | -0.233 s | 3.02 MiB | 3.02 MiB | + 4.84 KiB |
| /wp-admin/options-writing.php | 0.185 s | 0.140 s | -0.045 s | 3.01 MiB | 3 MiB | - 8.4 KiB |
| /wp-admin/media-new.php | 0.285 s | 0.209 s | -0.076 s | 2.99 MiB | 3.01 MiB | + 17.03 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.237 s | 0.168 s | -0.069 s | 3.01 MiB | 3.03 MiB | + 22.2 KiB |
| /wp-admin/post-new.php?post_type=page | 0.597 s | 0.719 s | +0.122 s | 5.01 MiB | 5.04 MiB | + 22.2 KiB |
| /wp-admin/options-discussion.php | 0.210 s | 0.221 s | +0.011 s | 3 MiB | 3 MiB | + 5.65 KiB |
| /wp-admin/edit-comments.php | 0.203 s | 0.195 s | -0.008 s | 3.03 MiB | 3.03 MiB | + 4.84 KiB |
| / | 0.285 s | 0.136 s | -0.149 s | 2.97 MiB | ||
| Average | 0.335 s | 0.311 s | -0.024 s | 3.38 MiB | 3.44 MiB | + 13.95 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 | 91.5% | 2,030 | 701 | 46 | |
| PO File | 8.5% | 189 | 84 | 1 | |
| Total | 2,219 | 785 | 47 | ||
| Lines of code | 1,741 |
|---|---|
| Total complexity | 261 |
| Median class complexity | 5.0 |
| Median method complexity | 1.0 |
| Most complex class | WC_Aplazame |
| Most complex function | WC_Aplazame_Gateway::init_form_fields() |
| Classes | 33 |
|---|---|
| Methods | 122 |
| Functions | 1 |
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 2[26-Jul-2023 09:56:55 UTC] PHP Fatal error: Uncaught Error: Call to undefined function WC() in /wp-content/plugins/aplazame/classes/lib/Helpers.php:10
Stack trace:
#0 /wp-content/plugins/aplazame/aplazame.php(266): Aplazame_Helpers::render_to_template()
#1 /wp-includes/class-wp-hook.php(308): WC_Aplazame->aplazameJs()
#2 /wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters()
#3 /wp-includes/plugin.php(517): WP_Hook->do_action()
#4 /wp-includes/general-template.php(3049): do_action()
#5 /wp-content/themes/twentyseventeen/header.php(22): wp_head()
#6 /wp-includes/template.php(783): require_once('...')
#7 /wp-includes/template.php(718): load_template()
#8 /wp-includes/general-template.php(48): locate_template()
#9 /wp-content/themes/twentyseventeen/index.php(18): get_header()
#10 /wp-includes/template-loader.php(106): include('...')
#11 /wp-blog-header.php(19): require_once('...')
#12 /index.php(17): require('...')
#13 {main}
thrown in /wp-content/plugins/aplazame/classes/lib/Helpers.php on line 10
[26-Jul-2023 09:57:03 UTC] PHP Fatal error: Uncaught Error: Call to undefined function WC() in /wp-content/plugins/aplazame/classes/lib/Helpers.php:10
Stack trace:
#0 /wp-content/plugins/aplazame/aplazame.php(266): Aplazame_Helpers::render_to_template()
#1 /wp-includes/class-wp-hook.php(308): WC_Aplazame->aplazameJs()
#2 /wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters()
#3 /wp-includes/plugin.php(517): WP_Hook->do_action()
#4 /wp-includes/general-template.php(3049): do_action()
#5 /wp-content/themes/twentyseventeen/header.php(22): wp_head()
#6 /wp-includes/template.php(783): require_once('...')
#7 /wp-includes/template.php(718): load_template()
#8 /wp-includes/general-template.php(48): locate_template()
#9 /wp-content/themes/twentyseventeen/index.php(18): get_header()
#10 /wp-includes/template-loader.php(106): include('...')
#11 /wp-blog-header.php(19): require_once('...')
#12 /index.php(17): require('...')
#13 {main}
thrown in /wp-content/plugins/aplazame/classes/lib/Helpers.php on line 10