Imported from the Apple Support Forums via the Wayback Machine 🔗
I use the English Wikipedia site a lot. I've made no technical changes to my Mac or connection or settings at the site, but since this afternoon, every time I open a page there, a small message box comes up with the safari icon:
"http://en.wikipedia.org"
"Replaced by addportletLink()"
I have to hit the "OK" button exactly three times, and only then is the page displayed. This problem doesn't occur on any other Wikimedia site (Commons, foreign-language Wikipedias, etc). I've cleared the cache, re-installed Safari 3.1.
Imported from the Apple Support Forums via the Wayback Machine 🔗
I'm seeing the same message box popup for every page I navigate to on Wikipedia. It seems something about Safari has changed in the last week to make it behave strangely on a number of websites.
0
::jeff::·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I'm having the same issue on Windows with IE. I haven't fired up my mac (10.5.2) to see if it has the same issue.
0
moboyle79·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I'm using Firefox 3 beta 5. I have to click OK once. It just started today. No idea how to solve it, but I'd say it's a bug introduced by someone editing Wikipedia's javascript. I'm betting it'll be solved in a few days.
As a temporary fix, you can just log out, if you're only browsing. Or, you can change your skin (in "My Preferences", click "Skin" and change to Modern, or something).
Message was edited by: moboyle79
0
spacecadet2016·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I've posted an alert at the English-language Wikipedia's "Village pump (technical)", but am unsure how effective this will be. http://en.wikipedia.org/wiki/Wikipedia:Villagepump_%28technical%29#URGENT_action_required.2C_please:_browser_issues_with_eng.W Palone
Tony
0
spacecadet2016·
Imported from the Apple Support Forums via the Wayback Machine 🔗
All fixed, thanks guys. Someone at Wikipedia had messed with their code, and the issue has been resolved. Now at least we know what to do next time.