Awesome Support 6.2.1

Does Awesome Support work with WordPress 6.6.1 and PHP 8.1.12? A smoke test was performed on .

Summary

Errors
16PHP notices
1JavaScript exceptions
1Page failed to load
  • 1 404 Not Found
No resource errors
Performance

Memory usage: 1.59 MiB
The average PHP memory usage increased by this amount after activating by the plugin.

Page speed impact: 0.056 seconds
The average page load time increased by this amount after activating the plugin.

Environment
WordPress version6.6.1
PHP version8.1.12
MySQL version10.6.10
PHP memory limit512M
Plugin Info
Last updated
Active installs 8,000+
WordPress.org page https://wordpress.org/plugins/awesome-support/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 29

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=awesome-support%2Fawesome-support.php&plugin_status=all&paged=1&s&_wpnonce=05feff2160
Aspect after-activation
HTTP status 200
Load time 1.272 s
Memory usage 5.36 MiB
JS errors None
Resource errors None

Dashboard →

Page screenshot: Dashboard →
URL /wp-admin/as-setup
Aspect menu-item
HTTP status 404
Load time 0.213 s
Memory usage 4.17 MiB
JS errors None
Resource errors None

Tickets

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

Tickets → Add New

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

Tickets → Tags

Page screenshot: Tickets → Tags
URL /wp-admin/edit-tags.php?taxonomy=ticket-tag&post_type=ticket
Aspect menu-item
HTTP status 200
Load time 0.353 s
Memory usage 5.16 MiB
JS errors None
Resource errors None

Tickets → Channels

Page screenshot: Tickets → Channels
URL /wp-admin/edit-tags.php?taxonomy=ticket_channel&post_type=ticket
Aspect menu-item
HTTP status 200
Load time 0.431 s
Memory usage 5.2 MiB
JS errors None
Resource errors None

Tickets → Settings

Page screenshot: Tickets → Settings
URL /wp-admin/edit.php?post_type=ticket&page=wpas-settings
Aspect menu-item
HTTP status 200
Load time 0.630 s
Memory usage 5.21 MiB
JS errors None
Resource errors None

Tickets → Settings → Registration

Page screenshot: Tickets → Settings → Registration
URL /wp-admin/edit.php?post_type=ticket&page=wpas-settings&tab=registration
Aspect menu-item-tab
HTTP status 200
Load time 0.945 s
Memory usage 5.23 MiB
JS errors None
Resource errors None

Tickets → Settings → Moderated Registration

Page screenshot: Tickets → Settings → Moderated Registration
URL /wp-admin/edit.php?post_type=ticket&page=wpas-settings&tab=modregistration
Aspect menu-item-tab
HTTP status 200
Load time 0.823 s
Memory usage 5.23 MiB
JS errors None
Resource errors None

Tickets → Settings → Privacy

Page screenshot: Tickets → Settings → Privacy
URL /wp-admin/edit.php?post_type=ticket&page=wpas-settings&tab=privacy
Aspect menu-item-tab
HTTP status 200
Load time 0.610 s
Memory usage 5.21 MiB
JS errors None
Resource errors None

Tickets → Settings → Fields

Page screenshot: Tickets → Settings → Fields
URL /wp-admin/edit.php?post_type=ticket&page=wpas-settings&tab=Fields
Aspect menu-item-tab
HTTP status 200
Load time 0.356 s
Memory usage 5.2 MiB
JS errors None
Resource errors None

Tickets → Settings → Permissions

Page screenshot: Tickets → Settings → Permissions
URL /wp-admin/edit.php?post_type=ticket&page=wpas-settings&tab=permissions
Aspect menu-item-tab
HTTP status 200
Load time 0.331 s
Memory usage 5.19 MiB
JS errors None
Resource errors None

Tickets → Settings → Style

Page screenshot: Tickets → Settings → Style
URL /wp-admin/edit.php?post_type=ticket&page=wpas-settings&tab=style
Aspect menu-item-tab
HTTP status 200
Load time 0.296 s
Memory usage 5.19 MiB
JS errors None
Resource errors None

Tickets → Settings → E-Mails

Page screenshot: Tickets → Settings → E-Mails
URL /wp-admin/edit.php?post_type=ticket&page=wpas-settings&tab=email
Aspect menu-item-tab
HTTP status 200
Load time 1.009 s
Memory usage 5.25 MiB
JS errors None
Resource errors None

Tickets → Settings → Products Management

Page screenshot: Tickets → Settings → Products Management
URL /wp-admin/edit.php?post_type=ticket&page=wpas-settings&tab=products-management
Aspect menu-item-tab
HTTP status 200
Load time 0.400 s
Memory usage 5.2 MiB
JS errors None
Resource errors None

Tickets → Settings → Basic Time Tracking

Page screenshot: Tickets → Settings → Basic Time Tracking
URL /wp-admin/edit.php?post_type=ticket&page=wpas-settings&tab=basictimetracking
Aspect menu-item-tab
HTTP status 200
Load time 0.336 s
Memory usage 5.2 MiB
JS errors None
Resource errors None

Tickets → Settings → REST API

Page screenshot: Tickets → Settings → REST API
URL /wp-admin/edit.php?post_type=ticket&page=wpas-settings&tab=rest-api
Aspect menu-item-tab
HTTP status 200
Load time 0.610 s
Memory usage 5.19 MiB
JS errors None
Resource errors None

Tickets → Settings → File Upload

Page screenshot: Tickets → Settings → File Upload
URL /wp-admin/edit.php?post_type=ticket&page=wpas-settings&tab=file_upload
Aspect menu-item-tab
HTTP status 200
Load time 0.332 s
Memory usage 5.19 MiB
JS errors None
Resource errors None

Tickets → Settings → Advanced

Page screenshot: Tickets → Settings → Advanced
URL /wp-admin/edit.php?post_type=ticket&page=wpas-settings&tab=advanced
Aspect menu-item-tab
HTTP status 200
Load time 0.339 s
Memory usage 5.2 MiB
JS errors None
Resource errors None

Tickets → Settings → Language Options

Page screenshot: Tickets → Settings → Language Options
URL /wp-admin/edit.php?post_type=ticket&page=wpas-settings&tab=Language
Aspect menu-item-tab
HTTP status 200
Load time 0.314 s
Memory usage 5.17 MiB
JS errors None
Resource errors None

Tickets → Settings → Integrations

Page screenshot: Tickets → Settings → Integrations
URL /wp-admin/edit.php?post_type=ticket&page=wpas-settings&tab=integration
Aspect menu-item-tab
HTTP status 200
Load time 0.322 s
Memory usage 5.2 MiB
JS errors None
Resource errors None

Tickets → Tools

Page screenshot: Tickets → Tools
URL /wp-admin/edit.php?post_type=ticket&page=wpas-status
Aspect menu-item
HTTP status 200
Load time 0.344 s
Memory usage 5.29 MiB
JS errors None
Resource errors None

Tickets → Tools → Log Viewer

Page screenshot: Tickets → Tools → Log Viewer
URL /wp-admin/edit.php?post_type=ticket&page=wpas-status&tab=logs
Aspect menu-item-tab
HTTP status 200
Load time 0.332 s
Memory usage 5.16 MiB
JS errors
[
    {
        "message": "TypeError: $(...).accordion is not a function\n    at HTMLDocument.<anonymous> (/wp-admin/edit.php?post_type=ticket&page=wpas-status&tab=logs:2058:29)\n    at e (/wp-admin/load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-hooks&ver=6.6.1:2:27028)\n    at t (/wp-admin/load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-hooks&ver=6.6.1:2:27330)",
        "trace": null,
        "code": null
    }
]
Resource errors None

Tickets → Tools → Cleanup

Page screenshot: Tickets → Tools → Cleanup
URL /wp-admin/edit.php?post_type=ticket&page=wpas-status&tab=tools
Aspect menu-item-tab
HTTP status 200
Load time 0.330 s
Memory usage 5.22 MiB
JS errors None
Resource errors None

Tickets → Addons

Page screenshot: Tickets → Addons
URL /wp-admin/edit.php?post_type=ticket&page=wpas-addons
Aspect menu-item
HTTP status 200
Load time 5.343 s
Memory usage 5.17 MiB
JS errors None
Resource errors None

Tickets → Get a Free Addon!

Page screenshot: Tickets → Get a Free Addon!
URL /wp-admin/edit.php?post_type=ticket&page=wpas-optin
Aspect menu-item
HTTP status 200
Load time 0.352 s
Memory usage 5.15 MiB
JS errors None
Resource errors None

Tickets → Help & Support

Page screenshot: Tickets → Help & Support
URL /wp-admin/edit.php?post_type=ticket&page=wpas-help-and-support
Aspect menu-item
HTTP status 200
Load time 0.467 s
Memory usage 5.15 MiB
JS errors None
Resource errors None

Tickets → About

Page screenshot: Tickets → About
URL /wp-admin/edit.php?post_type=ticket&page=wpas-about
Aspect menu-item
HTTP status 200
Load time 0.517 s
Memory usage 5.23 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.242 s
Memory usage 4.26 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.302 s0.362 s+0.060 s3.47 MiB5.19 MiB+ 1.72 MiB
/wp-admin/edit.php0.189 s0.209 s+0.020 s3.54 MiB5.25 MiB+ 1.72 MiB
/wp-admin/post-new.php0.655 s0.803 s+0.148 s5.75 MiB7.43 MiB+ 1.68 MiB
/wp-admin/upload.php0.520 s0.468 s-0.052 s3.49 MiB5.1 MiB+ 1.62 MiB
/wp-admin/options-writing.php0.179 s0.212 s+0.033 s3.41 MiB5.09 MiB+ 1.68 MiB
/wp-admin/media-new.php0.209 s0.174 s-0.035 s3.4 MiB5.09 MiB+ 1.69 MiB
/wp-admin/edit-tags.php?taxonomy=category0.182 s0.192 s+0.010 s3.47 MiB5.1 MiB+ 1.63 MiB
/wp-admin/post-new.php?post_type=page0.528 s0.730 s+0.202 s5.75 MiB7.42 MiB+ 1.67 MiB
/wp-admin/options-discussion.php0.208 s0.329 s+0.121 s3.41 MiB5.09 MiB+ 1.68 MiB
/wp-admin/edit-comments.php0.218 s0.350 s+0.132 s3.49 MiB5.11 MiB+ 1.62 MiB
/0.269 s0.244 s-0.025 s3.45 MiB4.26 MiB+ 822.4 KiB
Average 0.314 s0.370 s+0.056 s3.88 MiB5.47 MiB+ 1.59 MiB

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.

PO File
PHP
Language % Lines of code Comment lines Files
PO File70.3%137,81493,96752
PHP19.8%38,83617,471233
CSS4.8%9,5091,89632
HTML1.9%3,692048
JavaScript1.5%2,860864110
LESS1.4%2,6781,19927
Markdown0.3%55602
SVG0.1%18024
JSON0.0%2801
Total 196,153 115,399 509

PHP Code Analysis | More results »

Lines of code 36,058
Total complexity 7,159
Median class complexity 11.0
Median method complexity 2.0
Most complex class gasscssc
Most complex function gasscss_parser::parseChunk()
Classes 142
Methods 1,234
Functions 542

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 8

Custom Post Types 4

ID Name
ticketTickets
ticket_replyTicket Replies
ticket_historyTicket History
ticket_logTicket Log

Meta Boxes

{
    "ticket": {
        "wpas-mb-details": {
            "title": "Ticket Details",
            "context": "side"
        },
        "wpas-mb-version": {
            "title": "Misc and Debug",
            "context": "side"
        },
        "wpas-mb-ticket-main-tabs": {
            "title": "Main Tabs",
            "context": "normal"
        }
    }
}

Roles 4

ID Name
wpas_managerSupport Supervisor
wpas_support_managerSupport Manager
wpas_agentSupport Agent
wpas_userSupport User

Capabilities 41

PHP Error Log 16 lines

[24-Jul-2024 08:30:48 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.9.0.) in /wp-includes/functions.php on line 6085
[24-Jul-2024 08:30:52 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.9.0.) in /wp-includes/functions.php on line 6085
[24-Jul-2024 08:30:53 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.9.0.) in /wp-includes/functions.php on line 6085
[24-Jul-2024 08:30:56 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.9.0.) in /wp-includes/functions.php on line 6085
[24-Jul-2024 08:30:57 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.9.0.) in /wp-includes/functions.php on line 6085
[24-Jul-2024 08:30:59 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.9.0.) in /wp-includes/functions.php on line 6085
[24-Jul-2024 08:31:00 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.9.0.) in /wp-includes/functions.php on line 6085
[24-Jul-2024 08:31:01 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.9.0.) in /wp-includes/functions.php on line 6085
[24-Jul-2024 08:31:02 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.9.0.) in /wp-includes/functions.php on line 6085
[24-Jul-2024 08:31:05 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.9.0.) in /wp-includes/functions.php on line 6085
[24-Jul-2024 08:31:06 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.9.0.) in /wp-includes/functions.php on line 6085
[24-Jul-2024 08:31:07 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.9.0.) in /wp-includes/functions.php on line 6085
[24-Jul-2024 08:31:08 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.9.0.) in /wp-includes/functions.php on line 6085
[24-Jul-2024 08:31:09 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.9.0.) in /wp-includes/functions.php on line 6085
[24-Jul-2024 08:31:10 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.9.0.) in /wp-includes/functions.php on line 6085
[24-Jul-2024 08:31:11 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.9.0.) in /wp-includes/functions.php on line 6085
See also: All tests for this plugin, How to Hide Awesome Support Admin Menus and Meta Boxes