Report - Awesome Support 6.0.6

Does Awesome Support work with WordPress 5.8.2 and PHP 7.4.8? A smoke test was performed on 2021-11-11 08:47:23 UTC.

Summary

Errors

90	PHP notices
2	PHP deprecation warnings
1	JavaScript exceptions
1	Page failed to load 1 404 Not Found
	No resource errors

Performance

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

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

Environment

WordPress version	5.8.2
PHP version	7.4.8
MySQL version	8.0.21
PHP memory limit	256M

Plugin Info

Last updated	2025-03-27T08:55:00+00:00
Active installs	8,000+
WordPress.org page	https://wordpress.org/plugins/awesome-support/
Badges	Get badge code

Pages 29

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=8649d4e9cf
Aspect	after-activation
HTTP status	200
Load time	2.771 s
Memory usage	5.81 MiB
JS errors	None
Resource errors	None

Dashboard →

URL	/wp-admin/as-setup
Aspect	menu-item
HTTP status	404
Load time	0.358 s
Memory usage	4.64 MiB
JS errors	None
Resource errors	None

Tickets

URL	/wp-admin/edit.php?post_type=ticket
Aspect	menu-item
HTTP status	200
Load time	0.549 s
Memory usage	5.75 MiB
JS errors	None
Resource errors	None

Tickets → Add New

URL	/wp-admin/post-new.php?post_type=ticket
Aspect	menu-item
HTTP status	200
Load time	1.378 s
Memory usage	5.91 MiB
JS errors	None
Resource errors	None

Tickets → Tags

URL	/wp-admin/edit-tags.php?taxonomy=ticket-tag&post_type=ticket
Aspect	menu-item
HTTP status	200
Load time	0.301 s
Memory usage	5.65 MiB
JS errors	None
Resource errors	None

Tickets → Channels

URL	/wp-admin/edit-tags.php?taxonomy=ticket_channel&post_type=ticket
Aspect	menu-item
HTTP status	200
Load time	0.391 s
Memory usage	5.7 MiB
JS errors	None
Resource errors	None

Tickets → Settings

URL	/wp-admin/edit.php?post_type=ticket&page=wpas-settings
Aspect	menu-item
HTTP status	200
Load time	0.832 s
Memory usage	5.73 MiB
JS errors	None
Resource errors	None

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	1.005 s
Memory usage	5.74 MiB
JS errors	None
Resource errors	None

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	1.179 s
Memory usage	5.76 MiB
JS errors	None
Resource errors	None

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.706 s
Memory usage	5.73 MiB
JS errors	None
Resource errors	None

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.389 s
Memory usage	5.72 MiB
JS errors	None
Resource errors	None

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.525 s
Memory usage	5.72 MiB
JS errors	None
Resource errors	None

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.422 s
Memory usage	5.72 MiB
JS errors	None
Resource errors	None

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.446 s
Memory usage	5.77 MiB
JS errors	None
Resource errors	None

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.575 s
Memory usage	5.72 MiB
JS errors	None
Resource errors	None

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.378 s
Memory usage	5.72 MiB
JS errors	None
Resource errors	None

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.419 s
Memory usage	5.72 MiB
JS errors	None
Resource errors	None

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.422 s
Memory usage	5.72 MiB
JS errors	None
Resource errors	None

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.525 s
Memory usage	5.72 MiB
JS errors	None
Resource errors	None

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.634 s
Memory usage	5.69 MiB
JS errors	None
Resource errors	None

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.395 s
Memory usage	5.72 MiB
JS errors	None
Resource errors	None

Tickets → Tools

URL	/wp-admin/edit.php?post_type=ticket&page=wpas-status
Aspect	menu-item
HTTP status	200
Load time	0.356 s
Memory usage	5.71 MiB
JS errors	None
Resource errors	None

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.337 s
Memory usage	5.64 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:642:29)\n at e (/wp-admin/load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,regenerator-runtime,wp-polyfill,wp-hooks&ver=5.8.2:2:30038)\n at t (/wp-admin/load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,regenerator-runtime,wp-polyfill,wp-hooks&ver=5.8.2:2:30340)", "trace": null, "code": null } ]`
Resource errors	None

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.323 s
Memory usage	5.71 MiB
JS errors	None
Resource errors	None

Tickets → Addons

URL	/wp-admin/edit.php?post_type=ticket&page=wpas-addons
Aspect	menu-item
HTTP status	200
Load time	5.566 s
Memory usage	5.66 MiB
JS errors	None
Resource errors	None

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.357 s
Memory usage	5.63 MiB
JS errors	None
Resource errors	None

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.336 s
Memory usage	5.63 MiB
JS errors	None
Resource errors	None

Tickets → About

URL	/wp-admin/edit.php?post_type=ticket&page=wpas-about
Aspect	menu-item
HTTP status	200
Load time	0.593 s
Memory usage	5.69 MiB
JS errors	None
Resource errors	None

Test site – Just another WordPress site

URL	/
Aspect	front-page
HTTP status	200
Load time	0.291 s
Memory usage	4.67 MiB
JS errors	None
Resource errors	None

Benchmark

URL	Load time			Memory usage
URL	Inactive	Active	Change	Inactive	Active	Change
/wp-admin/index.php	0.354 s	0.611 s	+0.257 s	3.08 MiB	5.64 MiB	+ 2.56 MiB
/wp-admin/edit.php	0.226 s	0.292 s	+0.066 s	3.11 MiB	5.71 MiB	+ 2.6 MiB
/wp-admin/post-new.php	1.128 s	1.031 s	-0.097 s	5.27 MiB	7.8 MiB	+ 2.53 MiB
/wp-admin/upload.php	0.408 s	0.469 s	+0.061 s	3.03 MiB	5.59 MiB	+ 2.56 MiB
/wp-admin/options-writing.php	0.270 s	0.201 s	-0.069 s	3.02 MiB	5.58 MiB	+ 2.55 MiB
/wp-admin/media-new.php	0.340 s	0.197 s	-0.143 s	3.01 MiB	5.58 MiB	+ 2.58 MiB
/wp-admin/edit-tags.php?taxonomy=category	0.202 s	0.228 s	+0.026 s	3.04 MiB	5.61 MiB	+ 2.58 MiB
/wp-admin/post-new.php?post_type=page	0.946 s	0.806 s	-0.140 s	5.26 MiB	7.79 MiB	+ 2.53 MiB
/wp-admin/options-discussion.php	0.268 s	0.654 s	+0.386 s	3 MiB	5.57 MiB	+ 2.57 MiB
/wp-admin/edit-comments.php	0.256 s	0.402 s	+0.146 s	3.04 MiB	5.61 MiB	+ 2.57 MiB
/	0.412 s	0.261 s	-0.151 s	2.96 MiB	4.67 MiB	+ 1.71 MiB
Average	0.437 s	0.468 s	+0.031 s	3.44 MiB	5.92 MiB	+ 2.49 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 File	75.7%	137,631	93,923	41
	PHP	14.8%	26,990	14,096	178
	CSS	4.7%	8,458	1,807	27
	HTML	2.0%	3,692	0	48
	LESS	1.5%	2,678	1,199	27
	JavaScript	1.2%	2,183	589	32
	SVG	0.1%	180	2	4
	JSON	0.0%	34	0	2
Total			181,846	111,616	359

PHP Code Analysis | More results »

Lines of code	24,406
Total complexity	4,761
Median class complexity	20.0
Median method complexity	2.0
Most complex class	WPAS_Tickets_List
Most complex function	wpas_register_core_fields()

Classes	66
Methods	713
Functions	490

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

wp_sm_sessions

Options `wp_options` 8

sm_session_db_version
ticket_channel_children
wisdom_notification_times
wpas_db_version
wpas_default_channels_added
wpas_options
wpas_setup_email_templates
wpas_version

Custom Post Types 4

ID	Name
ticket	Tickets
ticket_reply	Ticket Replies
ticket_history	Ticket History
ticket_log	Ticket 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_manager	Support Supervisor
wpas_support_manager	Support Manager
wpas_agent	Support Agent
wpas_user	Support User

Capabilities 41

view_ticket
view_private_ticket
edit_ticket
edit_other_ticket
edit_private_ticket
delete_ticket
delete_reply
delete_private_ticket
delete_other_ticket
assign_ticket
assign_ticket_creator
close_ticket
reply_ticket
settings_tickets
ticket_taxonomy
create_ticket
attach_files
view_unassigned_tickets
manage_licenses_for_awesome_support
administer_awesome_support
ticket_manage_tags
ticket_edit_tags
ticket_delete_tags
ticket_manage_products
ticket_edit_products
ticket_delete_products
ticket_manage_departments
ticket_edit_departments
ticket_delete_departments
ticket_manage_priorities
ticket_edit_priorities
ticket_delete_priorities
ticket_manage_channels
ticket_edit_channels
ticket_delete_channels
ticket_manage_privacy
ticket_manage_ticket_type
ticket_edit_ticket_type
ticket_delete_ticket_type
ticket_manage_ticket_templates
view_all_tickets

PHP Error Log 92 lines

[11-Nov-2021 08:47:47 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:48 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:50 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:50 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:51 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:51 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:52 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:54 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:54 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:55 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:56 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:47:58 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:00 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:01 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:02 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:03 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:04 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:06 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:07 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:08 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:09 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:09 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:11 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:11 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:12 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:13 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:14 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:15 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:20 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:21 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:22 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:23 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:23 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:24 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:24 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:24 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:25 UTC] PHP Deprecated:  allowed_block_types is <strong>deprecated</strong> since version 5.8.0! Use allowed_block_types_all instead. in /wp-includes/functions.php on line 5586
[11-Nov-2021 08:48:26 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:26 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:26 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:26 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:26 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:27 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:27 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:27 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:27 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:27 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:28 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:28 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:28 UTC] PHP Deprecated:  allowed_block_types is <strong>deprecated</strong> since version 5.8.0! Use allowed_block_types_all instead. in /wp-includes/functions.php on line 5586
[11-Nov-2021 08:48:29 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:29 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:29 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:29 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:29 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:30 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:30 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:30 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:31 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:31 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:31 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663
[11-Nov-2021 08:48:32 UTC] PHP Notice:  WP_Session::get_instance was called <strong>incorrectly</strong>. Please use native Session functionality. 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.0.) in /wp-includes/functions.php on line 5663

Awesome Support 6.0.6