1. Home
2. 404 Solution
3. 2.35.24

404 Solution 2.35.24

Does 404 Solution work with WordPress 6.7.1 and PHP 8.1.12? A smoke test was performed on 2024-11-22 10:06:25 UTC.

Summary

Pages 3

Plugins ‹ Test site — WordPress

Settings → 404 Solution

Test site – Just another WordPress site

Benchmark

URL	Load time			Memory usage
	Inactive	Active	Change	Inactive	Active	Change
/wp-admin/index.php	0.324 s	0.335 s	+0.011 s	3.48 MiB	3.53 MiB	+ 51.8 KiB
/wp-admin/edit.php	0.197 s	0.187 s	-0.010 s	3.54 MiB	3.59 MiB	+ 52.91 KiB
/wp-admin/post-new.php	0.773 s	0.672 s	-0.101 s	5.92 MiB	5.98 MiB	+ 56.02 KiB
/wp-admin/upload.php	0.564 s	0.334 s	-0.230 s	3.5 MiB	3.53 MiB	+ 35.49 KiB
/wp-admin/options-writing.php	0.199 s	0.210 s	+0.011 s	3.47 MiB	3.51 MiB	+ 39.51 KiB
/wp-admin/media-new.php	0.317 s	0.478 s	+0.161 s	3.46 MiB	3.51 MiB	+ 47.68 KiB
/wp-admin/edit-tags.php?taxonomy=category	0.194 s	0.212 s	+0.018 s	3.48 MiB	3.53 MiB	+ 58.63 KiB
/wp-admin/post-new.php?post_type=page	0.577 s	0.648 s	+0.071 s	5.92 MiB	5.97 MiB	+ 51.81 KiB
/wp-admin/options-discussion.php	0.280 s	0.285 s	+0.005 s	3.47 MiB	3.51 MiB	+ 36.8 KiB
/wp-admin/edit-comments.php	0.199 s	0.225 s	+0.026 s	3.49 MiB	3.53 MiB	+ 35.51 KiB
/	0.305 s	0.227 s	-0.078 s	3.41 MiB	3.43 MiB	+ 22.66 KiB
Average	0.357 s	0.347 s	-0.011 s	3.92 MiB	3.97 MiB	+ 44.44 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.

Language		%	Lines of code	Comment lines	Files
	PHP	72.3%	8,761	1,919	29
	Markdown	11.1%	1,343	0	2
	JavaScript	5.4%	649	170	8
	HTML	5.3%	642	20	22
	SQL	4.1%	495	125	33
	CSS	1.4%	175	16	1
	JSON	0.4%	45	0	1
Total			12,110	2,250	96

PHP Code Analysis | More results »

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 5

• wp_abj404_logsv2
• wp_abj404_lookup
• wp_abj404_permalink_cache
• wp_abj404_redirects
• wp_abj404_spelling_cache

Options wp_options 1

• abj404_settings

PHP Error Log 36 lines

[22-Nov-2024 10:06:42 UTC] WordPress database error Table 'wordpress.wp_abj404_lookup' doesn't exist for query 
/* ------------------ /wp-content/plugins/404-solution/includes/sql/correctLookupTableIssue.sql BEGIN ----- */ 

delete from wp_abj404_lookup
where lkup_value in (
    select * from (
	    SELECT DISTINCT lkup_value 
	    FROM wp_abj404_lookup 
	    group by lkup_value 
	    having count(lkup_value) > 1
    ) a
)

/* ------------------ /wp-content/plugins/404-solution/includes/sql/correctLookupTableIssue.sql END ----- */ 
 made by activate_plugin, plugin_sandbox_scrape, include_once('/plugins/404-solution/404-solution.php'), require_once('/plugins/404-solution/includes/Loader.php'), ABJ_404_Solution_SpellChecker::init, ABJ_404_Solution_SpellChecker::getInstance, ABJ_404_Solution_PluginLogic->getOptions, ABJ_404_Solution_PluginLogic->updateToNewVersion, ABJ_404_Solution_PluginLogic->updateToNewVersionAction, ABJ_404_Solution_DatabaseUpgradesEtc->createDatabaseTables, ABJ_404_Solution_DatabaseUpgradesEtc->reallyCreateDatabaseTables, ABJ_404_Solution_DatabaseUpgradesEtc->correctIssuesBefore, ABJ_404_Solution_DataAccess->correctDuplicateLookupValues, ABJ_404_Solution_DataAccess->queryAndGetResults
[22-Nov-2024 10:06:42 UTC] WordPress database error Table 'wordpress.wp_abj404_spelling_cache' doesn't exist for query delete from wp_abj404_spelling_cache where matchdata is null or matchdata = '' made by activate_plugin, plugin_sandbox_scrape, include_once('/plugins/404-solution/404-solution.php'), require_once('/plugins/404-solution/includes/Loader.php'), ABJ_404_Solution_SpellChecker::init, ABJ_404_Solution_SpellChecker::getInstance, ABJ_404_Solution_PluginLogic->getOptions, ABJ_404_Solution_PluginLogic->updateToNewVersion, ABJ_404_Solution_PluginLogic->updateToNewVersionAction, ABJ_404_Solution_DatabaseUpgradesEtc->createDatabaseTables, ABJ_404_Solution_DatabaseUpgradesEtc->reallyCreateDatabaseTables, ABJ_404_Solution_DatabaseUpgradesEtc->correctIssuesBefore, ABJ_404_Solution_DatabaseUpgradesEtc->correctMatchData, ABJ_404_Solution_DataAccess->queryAndGetResults
[22-Nov-2024 10:06:43 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>404-solution</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
[22-Nov-2024 10:06:44 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>404-solution</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
[22-Nov-2024 10:06:44 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>404-solution</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
[22-Nov-2024 10:06:46 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>404-solution</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
[22-Nov-2024 10:06:46 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>404-solution</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
[22-Nov-2024 10:06:47 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>404-solution</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
[22-Nov-2024 10:06:47 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>404-solution</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
[22-Nov-2024 10:06:49 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>404-solution</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
[22-Nov-2024 10:06:49 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>404-solution</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
[22-Nov-2024 10:06:49 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>404-solution</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
[22-Nov-2024 10:06:49 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>404-solution</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
[22-Nov-2024 10:06:50 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>404-solution</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
[22-Nov-2024 10:06:50 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>404-solution</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
[22-Nov-2024 10:06:50 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>404-solution</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
[22-Nov-2024 10:06:53 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>404-solution</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
[22-Nov-2024 10:06:53 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>404-solution</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
[22-Nov-2024 10:06:53 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>404-solution</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
[22-Nov-2024 10:06:53 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>404-solution</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
[22-Nov-2024 10:06:54 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>404-solution</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
[22-Nov-2024 10:06:54 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>404-solution</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

---