[NSFW] Links are shown as fixed but in reality they are not corrected
-
I fixed the link e.g. here under
ise à jour de la méthode suisse de saturation écologique (Umweltbelastungspunkte 2006).
It is now shown as correct, but in real in still does not work
The page I need help with: [log in to see the link]
-
Hi @jungbluth
I ho9pe you’re well today!
Are you using “Local (old)” or “Cloud (new)” version of Broken Link Checker?
Is the site cached in any way (caching plugin and/or cache on server level and/or CloudFlare or similar proxy/CDN) and if so, did you purge all cache entirely?
Kind regards,
AdamHello Adam and thanks for answering so quickly.
I am using the old version (not online).
I tried to check with the cache. I did not find any active cache and I reloaded the pages in the browser. How can I check and modify the cache?
On Friday I solved about 50 broken links. But, today they are identified again by the Broken Link Checker as broken (what I see also when I open the page via Web or edit the page in WordPress.
I use WordPress 6.5.2. Can this be the cause of the problem?
BR Niels
Hi @jungbluth
Thank you for response and additional information!
I visited the page that you mentioned in your initial post (the “https://esu-services.ch/fr/projects/” one) and all the links in content there seem to be working fine, including “https://esu-services.ch/fr/projects/ubp06/”.
I understand that Broken Link Checker, however, is still reporting some links as broken there. Sticking to that specific page as an example, would you, please
1. go to “Link Checker -> Local (old) -> Broken Links” page in site’s back-end
2. select 2-3 example URLs that are present on that page and are still reported as broken
3. and thena) share those URLs with us in response
b) and for each of them click on “Details” link (that shows up once you hover over text in “Status” column for the link), copy information in right column there (that should start with “Log: “; but do copy entire code in that column) and paste it in response here?Thank you in advance!
Best regards,
AdamI would like to start with this page
https://esu-services.ch/de/publications/foodcase/
LInk under … dissertation.de
I choose “unlink” and then it is removed from the list on Link Checker but still available on my webpage
Next example https://esu-services.ch/publications/waste/
https://www.energieforschung.ch
Details…
- Link last checked: 29/04/2024
- HTTP code: 0
- Response time: 0.003 seconds
- Final URL: https://www.energieforschung.ch/
- Redirect count: 0
- Instance count: 2
This link has failed 3 times.
This link has been broken for 4 days.
- Log: [Warning] Could’t follow the redirect URL (if any) because safemode or open base dir enabled
Failed to connect to https://www.energieforschung.ch port 443 after 2 ms: Couldn’t connect to server [Error #7]
=== (No response) ===
Response headers
================
Link is broken.
Page https://esu-services.ch/fr/news/media/
Campanha contra água mineral chega à Suí?
- Link last checked: 29/04/2024
- HTTP code: 404
- Response time: 0.662 seconds
- Final URL: https://www.swissinfo.ch/por/noticias/economia/Campanha_contra_agua_mineral_chega_a_Suica.html?siteSect=161&sid=9330133&cKey=1216049373000&ty=st
- Redirect count: 0
- Instance count: 1
This link has failed 4 times.
This link has been broken for 3 days.
- Log: [Warning] Could’t follow the redirect URL (if any) because safemode or open base dir enabled
=== Code HTTP?: 404 ===
Response headers
================
HTTP/2 404
server: nginx
date: Mon, 29 Apr 2024 08:10:37 GMT
content-type: text/html; charset=UTF-8
x-hacker: If you’re reading this, you should visit wpvip.com/careers and apply to join the fun, mention this header.
x-powered-by: WordPress VIP <https://wpvip.com>
host-header: a9130478a60e5f9135f765b23f26593b
link: <https://www.swissinfo.ch/por/wp-json/>; rel=”https://api.w.org/”
x-rq: mxp2 111 253 443
age: 0
x-cache: miss
vary: Accept-Encoding
Request headers
================
GET /por/noticias/economia/Campanha_contra_agua_mineral_chega_a_Suica.html?siteSect=161&sid=9330133&cKey=1216049373000&ty=st HTTP/2
Host: https://www.swissinfo.ch
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.5112.34 Safari/537.36
Accept: */*
Referer: https://esu-services.ch
Connection: close
Range: bytes=0-2048
Response HTML
================
<!doctype html>
<html lang=”pt-PT”>
<head>
<meta charset=”UTF-8″>
<meta name=”viewport” content=”width=device-width, initial-scale=1″>
<link rel=’preload’ href=’//app.usercentrics.eu/browser-ui/latest/loader.js’ as=’script’ />
<link rel=’preload’ href=’//privacy-proxy.usercentrics.eu/latest/uc-block.bundle.js’ as=’script’ />
<meta name=’robots’ content=’noindex, follow’ />
<!– This site is optimized with the Yoast SEO Premium plugin v21.6 (Yoast SEO v21.7) – https://yoast.com/wordpress/plugins/seo/ –>
<title>Página n?o encontrada – SWI swissinfo.ch</title>
<meta property=”og:locale” content=”pt_PT” />
<meta property=”og:title” content=”Página n?o encontrada – SWI swissinfo.ch” />
<meta property=”og:site_name” content=”SWI swissinfo.ch” />
<meta property=”fb:pages” content=”1548905495412661″ />
<meta property=”fb:admins” content=”100001790948545″ />
<meta property=”fb:app_id” content=”135593233180345″ />
<meta property=”article:publisher” content=”https://facebook.com/swissinfochemportugues/” />
<meta property=”og:image” content=”https://www.swissinfo.ch/por/wp-content/uploads/swissinfo-theme/swi-fallback-featured-image.jpg” />
<meta property=”og:image:width” content=”1200″ />
<meta property=”og:image:height” content=”630″ />
<meta name=”twitter:image” content=”https://www.swissinfo.ch/por/wp-content/uploads/swissinfo-theme/swi-fallback-featured-image.jpg” />
<meta name=”twitter:title” content=”Página n?o encontrada – SWI swissinfo.ch” />
<link rel=”image_src” href=”https://www.swissinfo.ch/por/wp-content/uploads/swissinfo-theme/swi-fallback-featured-image.jpg” />
<!– / Yoast SEO Premium plugin. –>
<link rel=’dns-prefetch’ href=’//sibforms.com’ />
<link rel=’dns-prefetch’ href=’//app.usercentrics.eu’ />
<link rel=’dns-prefetch’ href=’//privacy-proxy.usercentrics.eu’ />
<link href=’//app.usercentrics.eu’ rel=’preconnect’ />
<link href=’//api.usercentrics.eu’ rel=’preconnect’ />
<link href=’//privacy-proxy.usercentrics.eu’ rel=’preconnect’ />
<link rel=’style
Le lien est cassé.
Hi @jungbluth
Thanks for response!
These examples explain it.
The links are indeed broken – for various reasons but they are correctly detected as broken. They either don’t respond, or lead to 404 page or, for example, are incorrect like this one
https://www.swissinfo.ch/por/wp-json/>
which has broken formatting – the last part, the
>
is breaking it.—–
Sot hat part is correct. If it comes to unlinking the reason for it is how the content is built on the site. You are using SiteOrigin bulder which uses its own custom blocks. So far so good but the way those blocks store data in the DB is different than “standard”. You can easily see it by e.g. disabling SiteOrigin builder on site and you’ll see that most of text widgets are rendered in block editor with an error rather than editable content.
That’s because the way the data of these blocks (at least if it comes to “text widget”) is saved in a “custom way” that requires SiteOrigin to properly parse and display it.
Broken Link Chekcer is not able to parse that and handle on its own becuase of that and it does not have any specific integration built-in with Site Origin. For the very same reason it also doesn’t know that the unlinking action failed.
I’m afraid there’s no solution for that and the “Local (old)” engine (which is a legacy one) will not receive such integration in future. In this case, I’m afraid, it can be used to check/detect those links but then they would need to be edited manually on site to get them fixed or unlinked.
Kind regards,
AdamThanks for checking this and the answer. BR Niels
Hi @jungbluth,
Since we haven’t heard from you for a while. I’ll mark this thread as resolved for now. Please feel free to open a new thread if you have new queries.
Kind Regards
Nithin
- The topic ‘[NSFW] Links are shown as fixed but in reality they are not corrected’ is closed to new replies.