All In One WP Security 5.3.4

Does All In One WP Security work with WordPress 6.7.1 and PHP 8.1.12? A smoke test was performed on .

Summary

Errors
94PHP notices
1Unrecognized messages in the PHP error log
No JavaScript exceptions
All test pages loaded successfully
No resource errors
Performance

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

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

Environment
WordPress version6.7.1
PHP version8.1.12
MySQL version10.6.10
PHP memory limit512M
Plugin Info
Last updated
Active installs 1,000,000+
WordPress.org page https://wordpress.org/plugins/all-in-one-wp-security-and-firewall/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 54

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=all-in-one-wp-security-and-firewall%2Fwp-security.php&plugin_status=all&paged=1&s&_wpnonce=4eccac0c22
Aspect after-activation
HTTP status 200
Load time 0.397 s
Memory usage 3.8 MiB
JS errors None
Resource errors None

WP Security

Page screenshot: WP Security
URL /wp-admin/admin.php?page=aiowpsec
Aspect menu-item
HTTP status 200
Load time 0.537 s
Memory usage 3.96 MiB
JS errors None
Resource errors None

WP Security → Locked IP addresses

Page screenshot: WP Security → Locked IP addresses
URL /wp-admin/admin.php?page=aiowpsec&tab=locked-ip
Aspect menu-item-tab
HTTP status 200
Load time 0.212 s
Memory usage 3.9 MiB
JS errors None
Resource errors None

WP Security → Permanent block list

Page screenshot: WP Security → Permanent block list
URL /wp-admin/admin.php?page=aiowpsec&tab=permanent-block
Aspect menu-item-tab
HTTP status 200
Load time 0.254 s
Memory usage 3.82 MiB
JS errors None
Resource errors None

WP Security → Audit logs

Page screenshot: WP Security → Audit logs
URL /wp-admin/admin.php?page=aiowpsec&tab=audit-logs
Aspect menu-item-tab
HTTP status 200
Load time 0.206 s
Memory usage 4.01 MiB
JS errors None
Resource errors None

WP Security → Debug logs

Page screenshot: WP Security → Debug logs
URL /wp-admin/admin.php?page=aiowpsec&tab=debug-logs
Aspect menu-item-tab
HTTP status 200
Load time 0.221 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP Security → Settings

Page screenshot: WP Security → Settings
URL /wp-admin/admin.php?page=aiowpsec_settings
Aspect menu-item
HTTP status 200
Load time 0.215 s
Memory usage 3.82 MiB
JS errors None
Resource errors None

WP Security → Settings → .htaccess file

Page screenshot: WP Security → Settings → .htaccess file
URL /wp-admin/admin.php?page=aiowpsec_settings&tab=htaccess-file-operations
Aspect menu-item-tab
HTTP status 200
Load time 0.192 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP Security → Settings → wp-config.php file

Page screenshot: WP Security → Settings → wp-config.php file
URL /wp-admin/admin.php?page=aiowpsec_settings&tab=wp-config-file-operations
Aspect menu-item-tab
HTTP status 200
Load time 0.219 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP Security → Settings → Delete plugin settings

Page screenshot: WP Security → Settings → Delete plugin settings
URL /wp-admin/admin.php?page=aiowpsec_settings&tab=delete-plugin-settings
Aspect menu-item-tab
HTTP status 200
Load time 0.215 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP Security → Settings → WP version info

Page screenshot: WP Security → Settings → WP version info
URL /wp-admin/admin.php?page=aiowpsec_settings&tab=wp-version-info
Aspect menu-item-tab
HTTP status 200
Load time 0.206 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP Security → Settings → Import/Export

Page screenshot: WP Security → Settings → Import/Export
URL /wp-admin/admin.php?page=aiowpsec_settings&tab=settings-file-operations
Aspect menu-item-tab
HTTP status 200
Load time 0.207 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP Security → Settings → Advanced settings

Page screenshot: WP Security → Settings → Advanced settings
URL /wp-admin/admin.php?page=aiowpsec_settings&tab=advanced-settings
Aspect menu-item-tab
HTTP status 200
Load time 0.216 s
Memory usage 3.83 MiB
JS errors None
Resource errors None

WP Security → Settings → Two factor authentication

Page screenshot: WP Security → Settings → Two factor authentication
URL /wp-admin/admin.php?page=aiowpsec_settings&tab=two-factor-authentication
Aspect menu-item-tab
HTTP status 200
Load time 0.222 s
Memory usage 3.85 MiB
JS errors None
Resource errors None

WP Security → User Security

Page screenshot: WP Security → User Security
URL /wp-admin/admin.php?page=aiowpsec_usersec
Aspect menu-item
HTTP status 200
Load time 0.208 s
Memory usage 3.83 MiB
JS errors None
Resource errors None

WP Security → User Security → Login lockout

Page screenshot: WP Security → User Security → Login lockout
URL /wp-admin/admin.php?page=aiowpsec_usersec&tab=login-lockout
Aspect menu-item-tab
HTTP status 200
Load time 0.222 s
Memory usage 3.86 MiB
JS errors None
Resource errors None

WP Security → User Security → Force logout

Page screenshot: WP Security → User Security → Force logout
URL /wp-admin/admin.php?page=aiowpsec_usersec&tab=force-logout
Aspect menu-item-tab
HTTP status 200
Load time 0.233 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP Security → User Security → Logged in users

Page screenshot: WP Security → User Security → Logged in users
URL /wp-admin/admin.php?page=aiowpsec_usersec&tab=logged-in-users
Aspect menu-item-tab
HTTP status 200
Load time 0.231 s
Memory usage 3.82 MiB
JS errors None
Resource errors None

WP Security → User Security → Manual approval

Page screenshot: WP Security → User Security → Manual approval
URL /wp-admin/admin.php?page=aiowpsec_usersec&tab=manual-approval
Aspect menu-item-tab
HTTP status 200
Load time 0.304 s
Memory usage 3.9 MiB
JS errors None
Resource errors None

WP Security → User Security → Salt

Page screenshot: WP Security → User Security → Salt
URL /wp-admin/admin.php?page=aiowpsec_usersec&tab=salt
Aspect menu-item-tab
HTTP status 200
Load time 0.321 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP Security → User Security → HTTP authentication

Page screenshot: WP Security → User Security → HTTP authentication
URL /wp-admin/admin.php?page=aiowpsec_usersec&tab=http-authentication
Aspect menu-item-tab
HTTP status 200
Load time 0.491 s
Memory usage 3.82 MiB
JS errors None
Resource errors None

WP Security → User Security → Additional settings

Page screenshot: WP Security → User Security → Additional settings
URL /wp-admin/admin.php?page=aiowpsec_usersec&tab=additional
Aspect menu-item-tab
HTTP status 200
Load time 0.221 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP Security → Database Security

Page screenshot: WP Security → Database Security
URL /wp-admin/admin.php?page=aiowpsec_database
Aspect menu-item
HTTP status 200
Load time 0.226 s
Memory usage 4 MiB
JS errors None
Resource errors None

WP Security → Database Security → Database backup

Page screenshot: WP Security → Database Security → Database backup
URL /wp-admin/admin.php?page=aiowpsec_database&tab=database-backup
Aspect menu-item-tab
HTTP status 200
Load time 0.204 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP Security → File Security

Page screenshot: WP Security → File Security
URL /wp-admin/admin.php?page=aiowpsec_filesystem
Aspect menu-item
HTTP status 200
Load time 0.225 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP Security → File Security → File protection

Page screenshot: WP Security → File Security → File protection
URL /wp-admin/admin.php?page=aiowpsec_filesystem&tab=file-protection
Aspect menu-item-tab
HTTP status 200
Load time 0.208 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP Security → File Security → Host system logs

Page screenshot: WP Security → File Security → Host system logs
URL /wp-admin/admin.php?page=aiowpsec_filesystem&tab=host-system-logs
Aspect menu-item-tab
HTTP status 200
Load time 0.215 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP Security → File Security → Copy protection

Page screenshot: WP Security → File Security → Copy protection
URL /wp-admin/admin.php?page=aiowpsec_filesystem&tab=copy-protection
Aspect menu-item-tab
HTTP status 200
Load time 0.212 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP Security → File Security → Frames

Page screenshot: WP Security → File Security → Frames
URL /wp-admin/admin.php?page=aiowpsec_filesystem&tab=frames
Aspect menu-item-tab
HTTP status 200
Load time 0.332 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP Security → Firewall

Page screenshot: WP Security → Firewall
URL /wp-admin/admin.php?page=aiowpsec_firewall
Aspect menu-item
HTTP status 200
Load time 0.204 s
Memory usage 3.82 MiB
JS errors None
Resource errors None

WP Security → Firewall → .htaccess rules

Page screenshot: WP Security → Firewall → .htaccess rules
URL /wp-admin/admin.php?page=aiowpsec_firewall&tab=htaccess-rules
Aspect menu-item-tab
HTTP status 200
Load time 0.212 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP Security → Firewall → 6G firewall rules

Page screenshot: WP Security → Firewall → 6G firewall rules
URL /wp-admin/admin.php?page=aiowpsec_firewall&tab=6g-firewall
Aspect menu-item-tab
HTTP status 200
Load time 0.215 s
Memory usage 3.82 MiB
JS errors None
Resource errors None

WP Security → Firewall → Internet bots

Page screenshot: WP Security → Firewall → Internet bots
URL /wp-admin/admin.php?page=aiowpsec_firewall&tab=internet-bots
Aspect menu-item-tab
HTTP status 200
Load time 0.209 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP Security → Firewall → Blacklist

Page screenshot: WP Security → Firewall → Blacklist
URL /wp-admin/admin.php?page=aiowpsec_firewall&tab=blacklist
Aspect menu-item-tab
HTTP status 200
Load time 0.205 s
Memory usage 3.82 MiB
JS errors None
Resource errors None

WP Security → Firewall → WP REST API

Page screenshot: WP Security → Firewall → WP REST API
URL /wp-admin/admin.php?page=aiowpsec_firewall&tab=wp-rest-api
Aspect menu-item-tab
HTTP status 200
Load time 0.204 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP Security → Firewall → Advanced settings

Page screenshot: WP Security → Firewall → Advanced settings
URL /wp-admin/admin.php?page=aiowpsec_firewall&tab=advanced-settings
Aspect menu-item-tab
HTTP status 200
Load time 0.221 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP Security → Brute Force

Page screenshot: WP Security → Brute Force
URL /wp-admin/admin.php?page=aiowpsec_brute_force
Aspect menu-item
HTTP status 200
Load time 0.209 s
Memory usage 4.03 MiB
JS errors None
Resource errors None

WP Security → Brute Force → Cookie based brute force prevention

Page screenshot: WP Security → Brute Force → Cookie based brute force prevention
URL /wp-admin/admin.php?page=aiowpsec_brute_force&tab=cookie-based-brute-force-prevention
Aspect menu-item-tab
HTTP status 200
Load time 0.208 s
Memory usage 3.85 MiB
JS errors None
Resource errors None

WP Security → Brute Force → CAPTCHA settings

Page screenshot: WP Security → Brute Force → CAPTCHA settings
URL /wp-admin/admin.php?page=aiowpsec_brute_force&tab=captcha-settings
Aspect menu-item-tab
HTTP status 200
Load time 0.308 s
Memory usage 3.95 MiB
JS errors None
Resource errors None

WP Security → Brute Force → Login whitelist

Page screenshot: WP Security → Brute Force → Login whitelist
URL /wp-admin/admin.php?page=aiowpsec_brute_force&tab=login-whitelist
Aspect menu-item-tab
HTTP status 200
Load time 0.489 s
Memory usage 3.82 MiB
JS errors None
Resource errors None

WP Security → Brute Force → 404 detection

Page screenshot: WP Security → Brute Force → 404 detection
URL /wp-admin/admin.php?page=aiowpsec_brute_force&tab=404-detection
Aspect menu-item-tab
HTTP status 200
Load time 0.210 s
Memory usage 3.93 MiB
JS errors None
Resource errors None

WP Security → Brute Force → Honeypot

Page screenshot: WP Security → Brute Force → Honeypot
URL /wp-admin/admin.php?page=aiowpsec_brute_force&tab=honeypot
Aspect menu-item-tab
HTTP status 200
Load time 0.203 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP Security → Spam Prevention

Page screenshot: WP Security → Spam Prevention
URL /wp-admin/admin.php?page=aiowpsec_spam
Aspect menu-item
HTTP status 200
Load time 0.206 s
Memory usage 3.82 MiB
JS errors None
Resource errors None

WP Security → Spam Prevention → Comment spam IP monitoring

Page screenshot: WP Security → Spam Prevention → Comment spam IP monitoring
URL /wp-admin/admin.php?page=aiowpsec_spam&tab=comment-spam-ip-monitoring
Aspect menu-item-tab
HTTP status 200
Load time 0.206 s
Memory usage 3.83 MiB
JS errors None
Resource errors None

WP Security → Scanner

Page screenshot: WP Security → Scanner
URL /wp-admin/admin.php?page=aiowpsec_filescan
Aspect menu-item
HTTP status 200
Load time 0.253 s
Memory usage 3.84 MiB
JS errors None
Resource errors None

WP Security → Scanner → Malware scan

Page screenshot: WP Security → Scanner → Malware scan
URL /wp-admin/admin.php?page=aiowpsec_filescan&tab=malware-scan
Aspect menu-item-tab
HTTP status 200
Load time 0.208 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP Security → Tools

Page screenshot: WP Security → Tools
URL /wp-admin/admin.php?page=aiowpsec_tools
Aspect menu-item
HTTP status 200
Load time 0.217 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP Security → Tools → WHOIS lookup

Page screenshot: WP Security → Tools → WHOIS lookup
URL /wp-admin/admin.php?page=aiowpsec_tools&tab=whois-lookup
Aspect menu-item-tab
HTTP status 200
Load time 0.201 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP Security → Tools → Custom .htaccess rules

Page screenshot: WP Security → Tools → Custom .htaccess rules
URL /wp-admin/admin.php?page=aiowpsec_tools&tab=custom-rules
Aspect menu-item-tab
HTTP status 200
Load time 0.191 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP Security → Tools → Visitor lockout

Page screenshot: WP Security → Tools → Visitor lockout
URL /wp-admin/admin.php?page=aiowpsec_tools&tab=visitor-lockout
Aspect menu-item-tab
HTTP status 200
Load time 0.541 s
Memory usage 3.82 MiB
JS errors None
Resource errors None

WP Security → Two Factor Auth

Page screenshot: WP Security → Two Factor Auth
URL /wp-admin/admin.php?page=aiowpsec_two_factor_auth_user
Aspect menu-item
HTTP status 200
Load time 0.245 s
Memory usage 3.81 MiB
JS errors None
Resource errors None

WP Security → Premium Upgrade

Page screenshot: WP Security → Premium Upgrade
URL /wp-admin/admin.php?page=aiowpsec&tab=premium-upgrade
Aspect menu-item
HTTP status 200
Load time 0.336 s
Memory usage 3.98 MiB
JS errors None
Resource errors None

WP Security → Premium Upgrade → Dashboard

Page screenshot: WP Security → Premium Upgrade → Dashboard
URL /wp-admin/admin.php?page=aiowpsec&tab=dashboard
Aspect menu-item-tab
HTTP status 200
Load time 0.439 s
Memory usage 3.81 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.268 s
Memory usage 3.63 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.341 s0.413 s+0.072 s3.48 MiB3.79 MiB+ 316.88 KiB
/wp-admin/edit.php0.172 s0.175 s+0.003 s3.54 MiB3.86 MiB+ 325.76 KiB
/wp-admin/post-new.php0.689 s1.439 s+0.750 s5.92 MiB6.23 MiB+ 308.72 KiB
/wp-admin/upload.php0.501 s0.454 s-0.047 s3.5 MiB3.78 MiB+ 289.56 KiB
/wp-admin/options-writing.php0.188 s0.181 s-0.007 s3.47 MiB3.76 MiB+ 293.55 KiB
/wp-admin/media-new.php0.243 s0.228 s-0.015 s3.46 MiB3.76 MiB+ 301.75 KiB
/wp-admin/edit-tags.php?taxonomy=category0.182 s0.167 s-0.015 s3.48 MiB3.78 MiB+ 306.92 KiB
/wp-admin/post-new.php?post_type=page0.495 s0.688 s+0.193 s5.92 MiB6.21 MiB+ 300.25 KiB
/wp-admin/options-discussion.php0.428 s0.223 s-0.205 s3.47 MiB3.76 MiB+ 290.05 KiB
/wp-admin/edit-comments.php0.213 s0.416 s+0.203 s3.49 MiB3.78 MiB+ 289.55 KiB
/0.267 s0.187 s-0.080 s3.48 MiB3.63 MiB+ 156 KiB
Average 0.338 s0.416 s+0.077 s3.93 MiB4.21 MiB+ 289 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
PO File
JavaScript
Language % Lines of code Comment lines Files
PHP48.3%26,83110,438228
PO File35.8%19,89212,6127
JavaScript12.8%7,10391210
CSS3.0%1,66886
Markdown0.1%6103
Total 55,555 23,970 254

PHP Code Analysis | More results »

Lines of code 21,838
Total complexity 4,684
Median class complexity 17.0
Median method complexity 2.0
Most complex class Simba_Two_Factor_Authentication_1
Most complex function AIOWPSecurity_General_Init_Tasks::__construct()
Classes 109
Methods 1,174
Functions 18

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 8

Options wp_options 5

User Metadata wp_usermeta 2

PHP Error Log 95 lines

[21-Nov-2024 16:07:20 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:20 UTC] TFA: Beginning attempt to port private key encryption over to openssl
[21-Nov-2024 16:07:21 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:21 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:23 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:24 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:25 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:25 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:26 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:27 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:28 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:29 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:30 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:31 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:32 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:32 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:33 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:34 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:35 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:36 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:37 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:38 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:39 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:40 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:41 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:42 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:43 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:44 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:45 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:46 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:47 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:47 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:48 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:49 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:50 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:51 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:52 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:53 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:54 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:55 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:56 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:57 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:58 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:07:59 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:00 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:01 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:02 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:03 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:04 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:05 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:06 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:06 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:07 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:09 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:10 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:11 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:12 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:13 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:14 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:14 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:14 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:16 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:16 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:16 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:16 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:16 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:16 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:16 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:16 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:16 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:16 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:17 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:17 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:17 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:17 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:17 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:18 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:18 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:18 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:19 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:19 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:19 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:19 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:19 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:20 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:20 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:20 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:20 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:20 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:20 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:20 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:21 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:21 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:21 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
[21-Nov-2024 16:08:22 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>all-in-one-wp-security-and-firewall</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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 6.7.0.) in /wp-includes/functions.php on line 6114
See also: All tests for this plugin, How to Hide All-In-One Security (AIOS) Admin Menus