Hippoo Ticket 1.0.7

Does Hippoo Ticket work with WordPress 6.7.2 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: 66.98 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.7.2
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=a3d84bb021
Aspect after-activation
HTTP status 200
Load time 0.274 s
Memory usage 3.56 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.171 s
Memory usage 3.59 MiB
JS errors None
Resource errors None

Hippoo Tickets → Add New Ticket

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

Hippoo Ticket

Page screenshot: Hippoo Ticket
URL /wp-admin/admin.php?page=hippoo_ticket
Aspect menu-item
HTTP status 200
Load time 1.349 s
Memory usage 3.73 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.239 s
Memory usage 3.48 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.320 s0.322 s+0.002 s3.48 MiB3.59 MiB+ 114.75 KiB
/wp-admin/edit.php0.200 s0.172 s-0.028 s3.54 MiB3.62 MiB+ 73.54 KiB
/wp-admin/upload.php0.538 s0.296 s-0.242 s3.5 MiB3.55 MiB+ 57.94 KiB
/wp-admin/options-writing.php0.196 s0.177 s-0.019 s3.47 MiB3.53 MiB+ 52.91 KiB
/wp-admin/media-new.php0.265 s0.167 s-0.098 s3.46 MiB3.52 MiB+ 61.11 KiB
/wp-admin/edit-tags.php?taxonomy=category0.223 s0.175 s-0.048 s3.48 MiB3.55 MiB+ 71.78 KiB
/wp-admin/options-discussion.php0.263 s0.182 s-0.081 s3.48 MiB3.52 MiB+ 49.41 KiB
/wp-admin/edit-comments.php0.193 s0.188 s-0.005 s3.5 MiB3.54 MiB+ 48.91 KiB
/0.292 s0.173 s-0.119 s3.41 MiB3.48 MiB+ 72.44 KiB
Average 0.277 s0.206 s-0.071 s3.48 MiB3.55 MiB+ 66.98 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
PHP71.2%1,19111211
CSS24.1%40432
JavaScript3.2%5322
SVG1.5%2505
Total 1,673 117 20

PHP Code Analysis | More results »

Lines of code 806
Total complexity 124
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 33

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

[02-Apr-2025 21:53:44 UTC] PHP Fatal error:  Uncaught Error: Class "WC_REST_Customers_Controller" not found in /wp-content/plugins/hippoo-ticket/app/web_api_auth.php:3
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(618): do_action()
#5 /wp-includes/rest-api.php(576): rest_get_server()
#6 /wp-includes/rest-api.php(2957): rest_do_request()
#7 [internal function]: rest_preload_api_request()
#8 /wp-includes/block-editor.php(756): 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 3
[02-Apr-2025 21:53:45 UTC] PHP Fatal error:  Uncaught Error: Class "WC_REST_Customers_Controller" not found in /wp-content/plugins/hippoo-ticket/app/web_api_auth.php:3
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(618): do_action()
#5 /wp-includes/rest-api.php(576): rest_get_server()
#6 /wp-includes/rest-api.php(2957): rest_do_request()
#7 [internal function]: rest_preload_api_request()
#8 /wp-includes/block-editor.php(756): 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 3
See also: All tests for this plugin