Flutterwave Payments 1.0.6

Does Flutterwave Payments work with WordPress 6.3.1 and PHP 8.1.12? A smoke test was performed on .

Summary

Errors
No PHP errors, warnings or notices
No JavaScript exceptions
All test pages loaded successfully
No resource errors
Looks good! No problems were detected.
Performance

Memory usage: 40.55 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.

Environment
WordPress version6.3.1
PHP version8.1.12
MySQL version10.6.10
PHP memory limit512M
Plugin Info
Last updated
Active installs 1,000+
WordPress.org page https://wordpress.org/plugins/rave-payment-forms/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 4

Plugins ‹ Test site — WordPress

Page screenshot: Plugins ‹ Test site — WordPress
URL /wp-admin/plugins.php?plugin_status=all&paged=1&s
Requested URL /wp-admin/plugins.php?action=activate&plugin=rave-payment-forms%2Frave-payment-forms.php&plugin_status=all&paged=1&s&_wpnonce=352fcd0741
Aspect after-activation
HTTP status 200
Load time 0.309 s
Memory usage 2.81 MiB
JS errors None
Resource errors None

Flutterwave

Page screenshot: Flutterwave
URL /wp-admin/admin.php?page=flutterwave-payments
Aspect menu-item
HTTP status 200
Load time 0.165 s
Memory usage 2.86 MiB
JS errors None
Resource errors None

Flutterwave → Transactions

Page screenshot: Flutterwave → Transactions
URL /wp-admin/admin.php?page=flutterwave-payments-transactions
Aspect menu-item
HTTP status 200
Load time 0.154 s
Memory usage 2.79 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.178 s
Memory usage 3.16 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.385 s0.339 s-0.046 s2.82 MiB2.87 MiB+ 46.36 KiB
/wp-admin/edit.php0.220 s0.220 s+0.000 s2.85 MiB2.89 MiB+ 46.36 KiB
/wp-admin/post-new.php0.826 s0.600 s-0.226 s5.21 MiB5.27 MiB+ 61.83 KiB
/wp-admin/upload.php0.860 s0.448 s-0.412 s2.77 MiB2.8 MiB+ 28.98 KiB
/wp-admin/options-writing.php0.250 s0.188 s-0.062 s2.76 MiB2.78 MiB+ 20.95 KiB
/wp-admin/media-new.php0.286 s0.244 s-0.042 s2.74 MiB2.78 MiB+ 41.18 KiB
/wp-admin/edit-tags.php?taxonomy=category0.204 s0.208 s+0.004 s2.76 MiB2.8 MiB+ 46.35 KiB
/wp-admin/post-new.php?post_type=page0.676 s0.629 s-0.047 s5.21 MiB5.26 MiB+ 57.41 KiB
/wp-admin/options-discussion.php0.240 s0.208 s-0.032 s2.75 MiB2.78 MiB+ 29.48 KiB
/wp-admin/edit-comments.php0.430 s0.190 s-0.240 s2.78 MiB2.81 MiB+ 29.02 KiB
/0.288 s0.180 s-0.108 s3.13 MiB3.17 MiB+ 38.17 KiB
Average 0.424 s0.314 s-0.110 s3.25 MiB3.29 MiB+ 40.55 KiB

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.

PHP
CSS
JavaScript
Language % Lines of code Comment lines Files
PHP70.7%2,3501,32426
CSS16.1%53593
JavaScript8.9%296405
Markdown3.8%12601
SVG0.4%1304
Sass0.2%501
Total 3,325 1,373 40

PHP Code Analysis | More results »

Lines of code 1,915
Total complexity 353
Median class complexity 11.0
Median method complexity 1.0
Most complex class FLW_Shortcode_Payment_Form
Most complex function Flutterwave_Payments::get_payment_url()
Classes 20
Methods 150
Functions 0

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 1

Custom Post Types 1

ID Name
payment_listPayment Lists

PHP Error Log

The log file is empty.

See also: All tests for this plugin, How to Hide Flutterwave Payments Admin Menus