Steven
Forum Replies Created
-
Forum: Plugins
In reply to: [Broken Link Checker] 403 Forbidden results and changing the user agent helpUnfortunately not much has improved since the error originally began.
My local version was only checking links once per week, so I don’t think it was an issue of my IP getting blocked for exceeding crawl limits at dozens of different websites all at the same time. I appreciate that suggestion though, as it’s a good idea to always consider.
I spent a few hours going through many of the 403 Forbidden links and I discovered that a lot of them seem be having trouble with Cloudflare’s human challenge. (link example, log file). You can see at the end of the log file this text, wrapped in a “challenge-error-text” id.<span id="challenge-error-text">Enable JavaScript and cookies to continue</span>My suspicion is Cloudflare is detecting the automation aspect of BLC and flagging it as suspicious. Is there something BLC can do on their end to better work with Cloudflare’s challenges?
If the target URLs are known, you can share your server IPs with the BLC Local User Agent
WPMU DEV Broken Link Checker Local Engine, so they can whitelist them in their server firewall. This way, we can resolve the issue completely.I’m a bit confused by this suggestion. Could you please elaborate? I have whitelisted both my server IPs and BLC’s IPs on my self-hosted shortlink server, but that didn’t help. I’m happy to send my server IPs to the BLC Local User Agent, but I don’t know where to do that.
Forum: Plugins
In reply to: [Broken Link Checker] 403 Forbidden results and changing the user agent helpHi Amin,
Just wanted to give a follow-up after trying the code snippet. The updated code seems to have solved the Twitter issues. However, I’m still getting a ton of 403 Forbidden errors for links that didn’t use to have them.
Our self-hosted link shortening tool is particularly perplexing. It and BLC have “played nicely” together for years. However now almost all of them give a link broken rejection along with the note “Enable JavaScript and cookies to continue” (link example, log file, firewall log file)
I followed the steps in your documentation and whitelisted on Cloudflare’s WAF tool the three Broken Link Checker IP addresses. I also whitelisted our live site’s IP address for good measure.
I even went so far as to temporarily disabled Cloudflare via their “development mode” option and the end results still are 403 Forbidden in BLC. So I’m not certain the issue here is stemming from my Cloudflare configuration.
Thanks again for passing my findings along to your development team and please let me know if there’s any further testing I can do to help from my end.Forum: Plugins
In reply to: [Broken Link Checker] 403 Forbidden results and changing the user agent helpThank you so much for the response.
Yes, I am using the local version. I will attempt to use the custom code today in order to fix the links.
Here are some examples of links giving me 400 and 403 errors. I have included the log file from each example link.- All fave.co links (example link, log file) are returning 403 with a basic “You don’t have permission to access” message.
- Many affiliate links (example link, log file) are returning 403 error saying “You don’t have permission to access the requested URL on this server.”
- Our internal shortlinks on our custom domain (example link, log file) are also now returning 403. These have never returned as 403 before, but for some reason says “Link is broken” despite still working just fine in browsers.
- While not a 403 error, all Twitter.com & X.com links (example link, log file) began giving a 400 Bad Request error at the same time the 403 errors appeared. The log for all these links says “This browser is no longer supported. Please switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center.”
I came to report this as well. There is a clear CSS confliction with all the dashboard admin screens. I confirmed it’s Post SMTP that’s causing the confliction via Troubleshooting.
The CSS is overwriting the default grey background with a lighter, bluer color. You can see this confliction in action here, where the grey background is still present behind the Add Media row, but everywhere else it’s light blue.Forum: Plugins
In reply to: [AAA Option Optimizer] Sorting options vanish when Ahrefs SEO is activatedHey Joost, thank you very much for the reply and prompting Ahrefs to update their plugin. I’ll be on the lookout for an update from them and will message their site to voice my support.
Apologies for talking to myself, but I stumbled upon the answer here! I missed that link at the bottom of the previous post.
https://displayposts.com/2019/01/04/list-posts-in-the-current-category/
For anybody Googling this after me, here’s the code you want:[display-posts taxonomy="category" tax_term="current"]I forgot to mention that I found this Code Snippet on the site to “Display posts in current category,” however I’m not seeing any actual code on the page. I simply see this.
https://www.billerickson.net/code/display-posts-current-category/Forum: Plugins
In reply to: [Easy Table of Contents] Shortcode to initially show table?Hey Magazine3, thank you so much for the speedy implementation!
I hate to say that it doesn’t seem to be working for me at the moment, however. I updated up to version 2.0.66.1, cleared my cache, and then tried placing [ez-toc initial_view=”show”] on a few pages. I didn’t change any of the other settings with my plugin installation. But the TOC still initially appear as hidden, not shown.
Is there anything else I need to do in order to get the initial_view=”show” to work? Thanks!
Update: The new feature seems to work on my staging site, so perhaps there’s a conflict elsewhere on my live site. I’ll investigate further tonight.Forum: Plugins
In reply to: [Easy Table of Contents] Shortcode to initially show table?Thank you, I’ll be on the lookout for that upcoming update!
Forum: Plugins
In reply to: [Easy Table of Contents] Shortcode to initially show table?Thanks for the reply!
I have the setting “Initial View: Initially hide the table of contents” checked because I want to initially hide the view for most of my tables. This successfully overrides the default behavior throughout my site.
However, there are one or two tables where I’d like to initially show the table instead. Is there anything registered with the shortcode that would allow me to do this?
Or would I need to uncheck the “Initial View” setting and then manually add the initial_view=”hide” to all my shortcode where I want to hide the table?Just wanted to say thank you for adding breadcrumbs to TSF and also I eagerly look forward to a future option where I can switch from Home > Category SEO Title > Post to something like Home > Category Name > Post
Forum: Plugins
In reply to: [Easy Table of Contents] Fatal error with latest versionJust wanted to chime in and say 2.0.30 also crashed my site and was causing such a heavy load issue that my host contacted me. Reverting back to 2.0.29 fixed the issue.
This is still an issue with both 5.9.3 and 6.0
I just updated to WordPress version 5.9 and can confirm this bug still exists.
Just want to bump and reiterate this is still an issue a month later.