HyperPay Payments 2.1.0
Does HyperPay Payments work with WordPress 6.1.1 and PHP 8.1.12? A smoke test was performed on .
Summary
Errors
| 1 | PHP fatal errors |
| 2 | PHP notices |
| No JavaScript exceptions | |
| 1 | Page failed to load
|
| No resource errors |
Performance
No data available.
Environment
| WordPress version | 6.1.1 |
|---|---|
| PHP version | 8.1.12 |
| MySQL version | 10.6.10 |
| PHP memory limit | 512M |
Plugin Info
| Last updated | |
|---|---|
| Active installs | 500+ |
| WordPress.org page | https://wordpress.org/plugins/hyperpay-gateways/ |
| Badges |
|
Pages 1
WordPress › Error
| URL | /wp-admin/plugins.php?activate=true&plugin_status=all&paged=1&s= |
|---|---|
| Requested URL | /wp-admin/plugins.php?action=activate&plugin=hyperpay-gateways%2Fhyperpay-payments.php&plugin_status=all&paged=1&s&_wpnonce=2f6d643605 |
| Aspect | after-activation |
| HTTP status | 500 |
| Load time | 0.200 s |
| Memory usage | N/A |
| JS errors | None |
| Resource errors | None |
Benchmark
No benchmark data available.
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.
| Language | % | Lines of code | Comment lines | Files | |
|---|---|---|---|---|---|
| PHP | 76.4% | 1,076 | 588 | 11 | |
| CSS | 10.3% | 145 | 13 | 3 | |
| PO File | 7.9% | 111 | 73 | 1 | |
| JavaScript | 5.4% | 76 | 23 | 3 | |
| Total | 1,408 | 697 | 18 | ||
PHP Code Analysis | More results »
| Lines of code | 977 |
|---|---|
| Total complexity | 138 |
| Median class complexity | 2.5 |
| Median method complexity | 2.0 |
| Most complex class | Hyperpay_main_class |
| Most complex function | Hyperpay_main_class::process_payment() |
| Classes | 8 |
|---|---|
| Methods | 42 |
| Functions | 6 |
Additions
No data available.
PHP Error Log 16 lines
[15-Jan-2023 12:19:15 UTC] PHP Fatal error: Uncaught Error: Class "WC_Payment_Gateway" not found in /wp-content/plugins/hyperpay-gateways/includes/Hyperpay_main_class.php:8
Stack trace:
#0 /wp-content/plugins/hyperpay-gateways/gateways/WC_Hyperpay_Tabby_Gateway.php(3): require_once()
#1 /wp-content/plugins/hyperpay-gateways/includes/class-install.php(28): include_once('...')
#2 /wp-includes/class-wp-hook.php(308): hyperpay_main::load()
#3 /wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters()
#4 /wp-includes/plugin.php(517): WP_Hook->do_action()
#5 /wp-settings.php(480): do_action()
#6 /wp-config.php(191): require_once('...')
#7 /wp-load.php(50): require_once('...')
#8 /wp-admin/admin.php(34): require_once('...')
#9 /wp-admin/plugins.php(10): require_once('...')
#10 {main}
thrown in /wp-content/plugins/hyperpay-gateways/includes/Hyperpay_main_class.php on line 8
[15-Jan-2023 12:19:15 UTC] PHP Notice: Function is_embed was called <strong>incorrectly</strong>. Conditional query tags do not work before the query is run. Before then, they always return false. 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 3.1.0.) in /wp-includes/functions.php on line 5835
[15-Jan-2023 12:19:15 UTC] PHP Notice: Function is_search was called <strong>incorrectly</strong>. Conditional query tags do not work before the query is run. Before then, they always return false. 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 3.1.0.) in /wp-includes/functions.php on line 5835
See also: All tests for this plugin