Wikivoyage:Arrivals lounge/Archives/2024/January

Links between Articles - have I missed a step?

I have added to the Lead section for Adelaide Hills. The existing Article Adelaide links to it.

When in the Adelaide Article, I can click on the link and get to the correct place with my changes. But if I 'hover' the mouse over the link, the 'pop-up' shows me the old Lead section text. Do I need to do something more to update the 'pop-up'?

I have restarted my computer in case I had a local cache that was not being updated. Using Firefox on Linux Mint. Catterns (talk) 18:09, 23 December 2023 (UTC)[reply]

@Catterns, it's working for me. Maybe the Page Previews system just needed a while to notice the change? WhatamIdoing (talk) 18:53, 23 December 2023 (UTC)[reply]
I am still getting the old Lead section text when I hover over the link with my mouse (and with the new links I created in this question). It is 09:37 Sun 24/12/2023 here local time. Catterns (talk) 23:08, 23 December 2023 (UTC)[reply]
I'm seeing the new text too, so I think it's probably some kind of local caching. I've noticed caching sometimes behaves weirdly on Wikivoyage and its sister sites. You can try:
  • Clearing your cookies
  • Using private browsing mode
  • Changing your IP address (e.g. with a VPN, or by using a mobile hotspot instead of your house's wifi or vice versa)
Regardless I expect it will probably fix itself within a couple of days. —Granger (talk · contribs) 23:35, 23 December 2023 (UTC)[reply]
Granger - OK will look again next week. Catterns (talk) 23:38, 23 December 2023 (UTC)[reply]
After further reading: I am not Autoconfirmed yet. Although not being asked for a CAPTCHA with edits, is there some form of 'Pending' that may be in operation. But my page edits have gone through OK. Catterns (talk) 23:36, 23 December 2023 (UTC)[reply]
@Catterns: I think autoconfirmed status is unlikely to be a factor here. But try accessing the page from a different IP address if you can. When I encountered a similar caching issue that stopped me from seeing the results of this change a week or so ago, I found that (to my surprise) using a VPN got around the problem. —Granger (talk · contribs) 23:40, 23 December 2023 (UTC)[reply]
Have done a further edit in the body and Published. It is now working for me. Catterns (talk) 05:02, 24 December 2023 (UTC)[reply]
I'm glad to hear that it is working now. WhatamIdoing (talk) 07:09, 24 December 2023 (UTC)[reply]

A follow-up that might be helpful?

On wikipedia Teahouse much the same has been asked and got the answer "I have purged Coulomb's law. This fixed it. PrimeHunter (talk) 14:09, 8 January 2024 (UTC)" which links to their Help:Purge page.

Is it possible to do something similar on a periodic basis in wikivoyage automatically? Catterns (talk) 21:38, 8 January 2024 (UTC)[reply]

I don't think we have any tools to purge the cache automatically more often than already happens. Normally, if a page is not edited, the cached copy is valid for 30 days and then purged. However, because ISPs may cache their own copies, then having it right "here" doesn't mean that that the correct/current copy will immediately be seen by everyone. WhatamIdoing (talk) 01:34, 9 January 2024 (UTC)[reply]
In the dim and distant past I designed and implemented a filing cache. They are tricky beasts. Catterns (talk) 02:08, 9 January 2024 (UTC)[reply]
wikitech:Parser cache says my numbers are wrong; in 2021, they reduced it to every 21 days for the mainspace. See phab:T282761 for more details, if you're interested (or wish to think about how lucky we are not to be responsible for that system! :-D ). WhatamIdoing (talk) 03:08, 9 January 2024 (UTC)[reply]
Looked at run times on T282761. Duration seems unreasonably long. Deletion logic probably no good and/or location of cache on disk(s) poorly chosen. I was never satisfied with my implementation, they are not easy. Catterns (talk) 03:36, 9 January 2024 (UTC)[reply]
As Wikimedia forces https nowadays, your ISP shouldn't be able to cache anything, unless your machine is under their control (such as often if the ISP is your employer and you are using their device). Thus caching should be limited to different layers on your and WMF's machines. –LPfi (talk) 11:34, 9 January 2024 (UTC)[reply]