Hippoo Ticket 1.0.0

Does Hippoo Ticket work with WordPress 6.4.3 and PHP 8.1.12? A smoke test was performed on .

Summary

Errors
2PHP fatal errors
No JavaScript exceptions
All test pages loaded successfully
No resource errors
Performance

Memory usage: 84.27 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.4.3
PHP version8.1.12
MySQL version10.6.10
PHP memory limit512M
Plugin Info
Last updated
Active installs <10
WordPress.org page https://wordpress.org/plugins/hippoo-ticket/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 5

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=hippoo-ticket%2Fhippoo-ticket.php&plugin_status=all&paged=1&s&_wpnonce=8a381f5385
Aspect after-activation
HTTP status 200
Load time 0.260 s
Memory usage 3.41 MiB
JS errors None
Resource errors None

Hippoo Tickets

Page screenshot: Hippoo Tickets
URL /wp-admin/edit.php?post_type=hippoo_ticket
Aspect menu-item
HTTP status 200
Load time 0.179 s
Memory usage 3.43 MiB
JS errors None
Resource errors None

Hippoo Tickets → Add Ticket

Page screenshot: Hippoo Tickets → Add Ticket
URL /wp-admin/post-new.php?post_type=hippoo_ticket
Aspect menu-item
HTTP status 200
Load time 0.852 s
Memory usage 3.61 MiB
JS errors None
Resource errors None

Hippoo Tickets → Settings

Page screenshot: Hippoo Tickets → Settings
URL /wp-admin/edit.php?post_type=hippoo_ticket&page=hippoo_ticket_con_ticket
Aspect menu-item
HTTP status 200
Load time 1.450 s
Memory usage 3.47 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.191 s
Memory usage 3.38 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.381 s0.461 s+0.080 s3.38 MiB3.49 MiB+ 114.34 KiB
/wp-admin/edit.php0.211 s0.268 s+0.057 s3.41 MiB3.52 MiB+ 112.05 KiB
/wp-admin/upload.php0.545 s0.343 s-0.202 s3.32 MiB3.44 MiB+ 115.32 KiB
/wp-admin/options-writing.php0.207 s0.176 s-0.031 s3.32 MiB3.37 MiB+ 58.15 KiB
/wp-admin/media-new.php0.300 s0.205 s-0.095 s3.3 MiB3.37 MiB+ 77.75 KiB
/wp-admin/edit-tags.php?taxonomy=category0.198 s0.174 s-0.024 s3.31 MiB3.41 MiB+ 98.92 KiB
/wp-admin/options-discussion.php0.386 s0.198 s-0.188 s3.3 MiB3.38 MiB+ 82.05 KiB
/wp-admin/edit-comments.php0.323 s0.199 s-0.124 s3.34 MiB3.42 MiB+ 81.55 KiB
/0.255 s0.163 s-0.092 s3.36 MiB3.38 MiB+ 18.27 KiB
Average 0.312 s0.243 s-0.069 s3.34 MiB3.42 MiB+ 84.27 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
Language % Lines of code Comment lines Files
PHP83.5%1,0867010
CSS15.2%19831
JavaScript0.9%1211
SVG0.4%502
Total 1,301 74 14

PHP Code Analysis | More results »

Lines of code 803
Total complexity 123
Median class complexity 20.0
Median method complexity 1.5
Most complex class HippooTicketControllerWithAuth
Most complex function hippoo_short_ticket()
Classes 1
Methods 10
Functions 32

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.

Database Tables 1

Options wp_options 1

Custom Post Types 1

ID Name
hippoo_ticketHippoo Tickets

PHP Error Log 30 lines

[10-Feb-2024 02:01:24 UTC] PHP Fatal error:  Uncaught Error: Class "WC_REST_Customers_Controller" not found in /wp-content/plugins/hippoo-ticket/app/web_api_auth.php:2
Stack trace:
#0 /wp-content/plugins/hippoo-ticket/app/web_api.php(5): require_once()
#1 /wp-includes/class-wp-hook.php(324): {closure}()
#2 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#3 /wp-includes/plugin.php(517): WP_Hook->do_action()
#4 /wp-includes/rest-api.php(593): do_action()
#5 /wp-includes/rest-api.php(551): rest_get_server()
#6 /wp-includes/rest-api.php(2918): rest_do_request()
#7 [internal function]: rest_preload_api_request()
#8 /wp-includes/block-editor.php(753): array_reduce()
#9 /wp-admin/edit-form-blocks.php(77): block_editor_rest_api_preload()
#10 /wp-admin/post-new.php(72): require('...')
#11 {main}
  thrown in /wp-content/plugins/hippoo-ticket/app/web_api_auth.php on line 2
[10-Feb-2024 02:01:25 UTC] PHP Fatal error:  Uncaught Error: Class "WC_REST_Customers_Controller" not found in /wp-content/plugins/hippoo-ticket/app/web_api_auth.php:2
Stack trace:
#0 /wp-content/plugins/hippoo-ticket/app/web_api.php(5): require_once()
#1 /wp-includes/class-wp-hook.php(324): {closure}()
#2 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#3 /wp-includes/plugin.php(517): WP_Hook->do_action()
#4 /wp-includes/rest-api.php(593): do_action()
#5 /wp-includes/rest-api.php(551): rest_get_server()
#6 /wp-includes/rest-api.php(2918): rest_do_request()
#7 [internal function]: rest_preload_api_request()
#8 /wp-includes/block-editor.php(753): array_reduce()
#9 /wp-admin/edit-form-blocks.php(77): block_editor_rest_api_preload()
#10 /wp-admin/post-new.php(72): require('...')
#11 {main}
  thrown in /wp-content/plugins/hippoo-ticket/app/web_api_auth.php on line 2
See also: All tests for this plugin