404 solution page is blank

Hey Bruno, Thanks for letting me know about this and thanks for including the video. I’ve released version 4.1.2 that should give us more information about what’s happening in the debug log. If you could 1. update to version 4.1.2, 2. go to the blank page, and then 3. go to the Settings (Options) tab via the Plugins link that works, then 4. Then scroll down to the logging and privacy section and at the bottom there there’s a debug log and if you click on “View” then you can see the debug log. If you could paste the debug log for me on https://pastebin.com/ , then that would be really helpful. At least the last five pages, the bottom five pages of the debug log. After you paste it on to paste bin, then you have to click the “create new paste” button at the bottom and then you’ll be able to copy the URL and send it to me here. We can’t post the debug log here because it’s too long for the WordPress forums. The new version should give us more information about what’s going on and what the issue is. Thanks.

Sure, here it is: https://pastebin.com/RQ53seNn

Hey Bruno, Thanks for the log file. It looks like your installation is corrupted. There are some missing files and the plugin crashes before being able to load the (blank) page. The best thing is to uninstall the plugin and reinstall it to see what happens. If the page is still blank after reinstalling: —– do you know how to check your PHP error log? It might have a line that starts with ‘404 Solution’ (for example) that would give us more information in that case. If you have cPanel you can usually that in cPanel > Error Log, or in wp-content/debug.log if you have WP_DEBUG_LOG enabled in your wp-config.php. If you find a line like that in the PHP error log please paste that here. If you want you could also add these to your wp-config.php temporarily. define('WP_DEBUG', true); define('WP_DEBUG_LOG', true); and then retest. The the php log or the file wp-content/debug.log should show some ‘404 Solution’ errors. —– I released version 4.1.3 which should log a bit more and also fixes some other bugs from your log.

I’ve installed the update, but still get a blank page. So, I’ve removed the plugin, then reinstalled again. Got a black page also. Any suggestions?

Thank you for your patience. I’ve tried to improve the logging in version 4.1.4. Hopefully if you update to that latest version that I just released you’ll be able to see an error message instead of a blank page and let me know what it says.

Thank you, but it seems it made no difference. This page is still blank: https://www.showmetech.com.br/wp-admin/options-general.php?page=abj404_solution Here’s a video showing it: https://www.loom.com/share/c509aee3fa8041e487d79dd23db4b3f0

Bruno, Thank you very much for the video. It’s very helpful. It looks like the page is taking too long to load. I’ll try to get the fixes to you today in the next version.

Hey Bruno, I understand you’ve uninstalled the plugin and that’s fine.If you want to try version 4.1.5 which should be a bit different, just let me know how it goes. If not thanks for the heads up about the bug anway. Aaron

Thanks, pages are now showing, so that’s an advance! But I still have the redirection errors now. Please take a look: https://www.loom.com/share/cf742d5a8f4b4025be8d8c6dedf4896b

Hey Bruno, So glad it started working for you. Again your video is helpful. I had some computer issues today so I couldn’t get to this. I’ll try to fix the last issues you’re seeing tomorrow. Aaron

Hey Bruno, 4.1.6 was just released. It should solve the specific issue you saw where /redes/ was not redirecting to /redes-social. Let me know how it goes. thanks

Thank you for the latest update! It seems to have corrected the redirections from Rank Math, that the plugin was messing up. But now I’m getting this new error: https://www.loom.com/share/eb9a2bbd22284101b63e629e412c6890 Can you take a look, please?

Hey Bruno, Thanks for your latest video. Please try version 4.1.7. Hopefully that issue will be fixed for you. Please let me know. Thanks

Guys, the plugin broke again. It is failing to load the configuration page and breaking redirects: https://nimb.ws/SC1xiFZ

Hey Bruno, Sorry about that. I’m working on it now.

Thanks! I’ve noticed there’s an update to your plugin, so I’ve updated and tried again. Unfortunately, it still did not work: https://nimb.ws/iO5Y0B9

Thanks again for your feedback. Again, I’m working on it right now.

Still working on getting all new test cases to pass. It will be ready today or tomorrow. It may not fix the issue and may only show a more detailed error message.

Version 4.1.10 was released but after further investigation it will not fix the Captured 404’s tab not loading for some people. So I’m currently working on the next version which will definitively fix the issue. Hopefully it will be done today or tomorrow.

Hey Bruno, I hope that all of the problems have been solved with version 4.1.11. Just let me know how it goes.

Hey Bruno, I haven’t heard from you in a while. Hopefully that means you’ve discovered version 4.1.13 and everything is working great for you with that. If not then thanks for your continued feedback up until now. It’s really useful to have direct feedback from someone. Most people just click ‘uninstall’ and go away (which isn’t helpful to me). Also, hopefully you don’t find any more serious issues in the next 4 days or so because my computer has to be repaired from tomorrow and I’m not sure when I’ll get it back so doing an update will be fairly inconvenient during that time. If you don’t respond then I’ll just assume everything is fine and close this thread after some time goes by and if you have any other issues just let me know by starting a new thread. Aaron

Thanks! Just to let you know, I’ve installed version 4.1.13 . Unfortunately, it still fails to load the redirections page. Here’s a video showing it: https://www.loom.com/share/7114b8e5a089426da6cdb5685814e9a4 Error screens: https://nimb.ws/VpKQbrF https://nimb.ws/jygxl47 https://nimb.ws/1eBRuIg Alerts: Could not finish refreshing data (stage 1, getCapturedURLSPageTable() -> getRedirectsForView() / getRedirectsForView.sql) 404 Solution: AJAX error while updating the table.What was happening: Rendering bottom pagination links Query: getPaginationLinks(bottom) -> getRedirectsForViewCount() / getRedirectsForView.sql HTTP status: textStatus: timeout errorThrown: timeout action: ajaxUpdatePaginationLinks subpage: abj404_logs Elapsed: 45006ms Timeout budget: 45000ms Inflight stage: paginationLinksBottom

Thanks! Just to let you know, I’ve installed version 4.1.13 . Unfortunately, it still fails to load the redirections page. Here’s a video showing it: https://www.loom.com/share/7114b8e5a089426da6cdb5685814e9a4 Error screens: https://nimb.ws/VpKQbrF https://nimb.ws/jygxl47 https://nimb.ws/1eBRuIg Alerts: Could not finish refreshing data (stage 1, getCapturedURLSPageTable() -> getRedirectsForView() / getRedirectsForView.sql) 404 Solution: AJAX error while updating the table.What was happening: Rendering bottom pagination links Query: getPaginationLinks(bottom) -> getRedirectsForViewCount() / getRedirectsForView.sql HTTP status: textStatus: timeout errorThrown: timeout action: ajaxUpdatePaginationLinks subpage: abj404_logs Elapsed: 45006ms Timeout budget: 45000ms Inflight stage: paginationLinksBottom

Hey Bruno, thanks for reinstalling the plugin and trying it again. Sorry that there were still issues. I did make another attempt to fix the issue. So before, the ‘page redirects’ and the ‘captured 404s’ tabs were all working off of just one big query which was timing out for you I guess. So I split that into 11 smaller substeps that each individually should happen really quickly even on a resource restricted machine. And the results are cached so that once it’s done building for the first time, the page should load almost immediately. And every time the page loads the cache is updated in the background. So hopefully that should work for you now. If you feel like it and you get a chance to retest version 4.1.15, that would be great. If not, that’s fine too. But I am interested to know whether it works or not, of course. While the steps are executing the first time, you should see updates on the screen that says what the current step is and how it’s progressing. And after that I should just work.

Hello Aaron and thank you for the update. Unfortunately, it still did not work. 🙁 Here are the latest error messages after I’ve updated the plugin: https://www.loom.com/share/66c6d3c7e6234f5ea40de189e3c3bcd8 This reply was modified 3 weeks, 5 days ago by Bruno Martinez .

Hey Bruno, Thank you for your continued feedback. I’m pretty sure that version 4.1.16 will fix the issue, but I thought the previous version would fix it too so who knows. Anyway if it still doesn’t work with 4.1.16 please send me the debug logs via email or using https://pastebin.com/ . Debug logs are at Options > Advanced > Logging and Privacy > View. It’s too long to paste here and gets deleted so that’s why it has to be pasted to pastebin. thanks

Hello, I’m back to alert that the errors continue to exist, ok? After the latest update (today), I’ve noticed this cron alert: https://nimb.ws/FgSjd6b It doesn’t seem right, since I have a server cron configured: https://nimb.ws/FnIjG9H What do you recommend?

Hey Bruno, thanks for the feedback again. Based on your first screenshot, it looks like the plugin is actually working. There’s a message in the table that says that it’s working on stage two out of eleven and it’s working through the batches and so basically that should update every once in a while and it should go through all eleven stages and once it’s done then the page will load and it will load quickly from then on after that and update in the background. The error message is a false positive or a false alarm, I’m pretty sure. I’ll have to remove that in a later version. I circled the part of the screenshot that shows the progress that was being made in light green. https://i.ibb.co/bg7ZZZcT/screenshot-a.png So as long as it says it’s making progress, then it should continue until it’s done.I’m not sure how long it will take, but give it a few minutes, I think. This reply was modified 3 weeks, 2 days ago by Aaron .

I don’t think that’s the case. The process still didn’t conclude correctly: https://nimb.ws/Y6fC8zT

Hey again Bruno, Thanks for the screenshots. In this new version (4.1.18) there’s supposed to sometimes be a button to press if an error happens that will send me the log file directly. I do think that this version will just work for you, but I also thought that for the previous version, so we’ll see I guess. Please let me know when you have a chance. thanks Aaron

Sorry to pressure, but still no solution? It’s been 2 weeks 🙁 Here’s the latest error screen: https://nimb.ws/GZue8BN

Hey Bruno, Well I am still working on it. I did release version 4.1.19 today. So, you know, let me know how it goes. Also, I don’t think you told me about how 4.1.18 worked for you? Basically I’ve found that there are some structural issues with the code that mean that every time I try to fix something I end up introducing a new issue elsewhere. So it needs to be refactored (rewritten) in various places and that will take some time. So hopefully 4.1.19 works for you. I’m not sure when 4.2.0 will be released.

Hi, I’m reporting an issue we observed on a high-traffic WordPress site using 404 Solution . The site started showing repeated 507 Insufficient Storage errors in wp-admin and during normal WordPress operations. After investigation, the server did not appear to be out of disk space or inodes: – Disk: ~614 GB total / ~141 GB free – Disk usage: ~77% – Inodes: ~19% used – PHP: 8.3 / LiteSpeed / CloudLinux-style shared hosting environment The 507 errors appeared to be caused by server resource pressure, not actual storage exhaustion. Evidence found The WordPress error_log repeatedly showed 404 Solution / abj404 rebuild errors, including: text<br>WordPress database error Illegal mix of collations<br>(utf8mb4_general_ci,IMPLICIT) and (utf8mb4_unicode_520_ci,IMPLICIT)<br>for operation '='<br><br>query:<br>SET STATEMENT max_statement_time=60 FOR<br>/* abj404:src=DataAccessTrait_LogsHitsRebuild::hitsTableInsertChunked#phase2Aggregate */<br>INSERT INTO smt_abj404_logs_hits_temp<br>(requested_url, logsid, last_used, logshits, failed_hits)<br>SELECT a.requested_url, MIN(a.logsid), MAX(a.last_used), SUM(a.logshits), SUM(a.failed_hits)<br>FROM smt_abj404_logs_hits_preagg a<br>INNER JOIN smt_abj404_redirects r<br>ON a.requested_url = COALESCE(r.canonical_url, CONCAT('/', TRIM(BOTH '/' FROM r.url)))<br>GROUP BY a.requested_url<br> And also: text<br>WordPress database error Query execution was interrupted (max_statement_time exceeded)<br><br>query:<br>SET STATEMENT max_statement_time=10 FOR<br>/* abj404:src=DataAccessTrait_LogsHitsRebuild::hitsTableInsertChunked#phase1Chunk */<br>INSERT INTO smt_abj404_logs_hits_preagg<br>(requested_url, logsid, last_used, logshits, failed_hits)<br>SELECT canonical_url, MIN(id), MAX(timestamp), COUNT(*),<br>SUM(CASE WHEN dest_url = '' OR dest_url IS NULL THEN 1 ELSE 0 END)<br>FROM smt_abj404_logsv2<br>WHERE id >= 4961718 AND id < 5061718<br>GROUP BY canonical_url<br> We also found that the plugin had large internal tables: text<br>smt_abj404_redirects ~604 MB / ~630k rows<br>smt_abj404_view_done ~516 MB<br>smt_abj404_logsv2 ~181 MB<br>smt_abj404_logs_hits ~7 MB<br> The scheduled event abj404_rebuildViewDone appeared to be continuously re-created by: php<br>PluginLogicTrait_Lifecycle::scheduleViewDoneWarmup()<br> Specifically, the logic appears to schedule it again whenever there is no existing scheduled event: php<br>if (wp_next_scheduled('abj404_rebuildViewDone') !== false) {<br>return;<br>}<br>wp_schedule_single_event(time() + 5, 'abj404_rebuildViewDone');<br> In our case, the event was repeatedly scheduled near-immediately, and the rebuild process was hitting database limits / collation issues / long-running queries. This likely created enough resource pressure for the host to return intermittent 507 Insufficient Storage errors. Temporary mitigation applied To stabilize the site, we temporarily: 1. Cleared the stuck scheduled event: php<br>wp_clear_scheduled_hook('abj404_rebuildViewDone');<br> 2. Removed stale/inflight trans...

Thank you for the detailed report, Bruno. I will take this into account for the new version. Still working on it by the way. Maybe it’ll be done the day after tomorrow, but no promises.

Version 4.2.0 was released today. The larger rewriting project is not done yet and has a long way to go. This version was released now to possibly fix the ongoing issue for you.

Hello, just to let you know, 3 weeks have passed and the issue has not been fixed: https://nimb.ws/58YOpgH

Okay Bruno, I’ll keep trying to get it working for you.

A month has passed, and this has not been fixed. I’m beginning to think it won’t.

Hey Bruno. I’m still working on it.