[⚠️ URGENT] SL Wiki: syntax highlight is broken *and* in-world access via viewer is down...
tracked
Gwyneth Llewelyn
I'm aware that you guys have been tinkering with the SL Wiki recently, and so this might be a consequence of those changes — or not.
I was reviewing some information on the SL Wiki, and suddenly realised that one of my templates was broken (
Template:Code
): it spewed out the <syntaxhighlighting...>
pseudo-tags, as expected, but these weren't recognised by the MediaWiki parsing mechanism. I thought that the problem was somehow on that template, but I quickly noticed that it's widespread: none
of the pages using syntax highlighting work. Even those still using <source...>
stopped working, and I suspect the same applies to a lot
of other 'automatic' tags (regular templates seem to be fine... so long as they don't rely on the built-in tags).I wondered how nobody had noticed this — even considering that the SL Wiki might not be that much used in general — but at least the built-in LSL editor, which uses as 'help' a link to the LSL Portal section, should have been immediately tagged by someone wondering why none of the code was showing up as before.
Well, the reason is simple to understand: all built-in functions give the following error:
Access Denied
You don't have permission to access "http://wiki.secondlife.com/wiki/llHTTPRequest" on this server.
Reference #18.4c671702.1748621307.5b5badf
https://errors.edgesuite.net/18.4c671702.1748621307.5b5badf
(see attachment)
Note that the URL for the error reference doesn't work, either, but that's not
your
problem. 😂My first impression was that the culprit was your Akamai/Edgesuite and/or AWS configuration — it wasn't properly redirecting
http://
to https://
. Thus, the issue. However, all the browsers I could grab will automagically replace http://
with https://
, so I couldn't tell exactly what was wrong.curl
to the rescue...HTTP/1.1 301 Moved Permanently
Content-Type: text/html
Content-Length: 134
Expires: Fri, 30 May 2025 17:36:50 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Fri, 30 May 2025 17:36:50 GMT
Connection: keep-alive
<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
</body>
</html>
`
Ok, so far so good, configured exactly as expected!
`
HTTP/2 403
mime-version: 1.0
content-type: text/html
content-length: 395
expires: Fri, 30 May 2025 17:40:25 GMT
cache-control: max-age=0, no-cache, no-store
pragma: no-cache
date: Fri, 30 May 2025 17:40:25 GMT
<HTML><HEAD>
<TITLE>Access Denied</TITLE>
</HEAD><BODY>
<H1>Access Denied</H1>
You don't have permission to access "http://wiki.secondlife.com/wiki/LlHTTPRequest" on this server.<P>
Reference #18.cd7d1302.1748626825.bfdba40a
<P>https://errors.edgesuite.net/18.cd7d1302.1748626825.bfdba40a</P>
</BODY>
</HTML>
`
Hmm. That doesn't look so good. It will really require some Linden love to get it working again!
Well, good luck; hopefully, fixing one issue will also fix the other; or else you just have
two
issues to fix!## Possible related issues:
P.S.: Note that I've also tried to use different user-agent headers, just in case that was the reason for the failed permission (found on a forum discussing the specific error given by Akamai/Edgesite).
Log In
Skullphern Resident
It has been nearly a month since this was reported.
There are full sections and examples for scripting, completely missing from the wiki, for a problem that is a plugin no longer being enabled... from what I am understanding must be a matter of either finding a replacement or turning it back on again.
example: (look at the examples section)
normally this examples section would be 10 examples long, with many different pointers showing how to use the function.
having been scripting in SL for 10 years, I would go to this page often to figure out this function I only used sporadically.
this is unacceptable, and incredibly unprofessional.
Does this mean scripting in SL is not important to Linden labs?
imagine if this was the marketplace?
the social forums?
primfeed?
Please, this is getting more frustrating as i keep finding whole pages unusable.
How am I supposed to teach people how to script if I can't point to the official source in confidence?
bubblecharm7 Resident
Skullphern Resident Ikr? i picked the worst time to learn LSL. Please fix the wiki
Maestro Linden
Merged in a post:
The LSL wiki appears to be truncating longer code blocks
Arrehn Oberlander
- Visit https://wiki.secondlife.com/wiki/LlTeleportAgent (or many other pages with longer code examples).
- Scroll down almost to the end, to just above the the "See Also" section.
- Notice that the code block is truncated. See attached picture.
--
The code block is fully there in the page source, this seems to be some presentation error. I had this result in multiple browsers, all javascript enabled. Seems to be a recent change.
Peter Stindberg
Nexii Malthus
Dropped a warning notice on the LSL Portal page, which can be removed once the issue is resolved
Gwyneth Llewelyn
Nexii Malthus I just saw that! Thanks a lot! I was wondering... "is there any way of having a template that puts a banner on
all
pages?" but then I forgot to look it up...Soon, if this persists, I'll shamelessly copy your banner and put it on the LSL Navigation Bar!
Lettie Linden
Merged in a post:
LSL Wiki Issues
Love Zhaoying
Some Wiki pages now have issues, apparently due to a Wiki software update.
Example LSL Wiki page which now has issues: https://wiki.secondlife.com/wiki/LlJsonValueType
This example page is now showing "template issues" which is also causing it to drop out of its category ("JSON" in this case).
Comment from Frionil Fang: "[it is] the syntax highlighter in general that has broken down. On some pages it results in a complete, catastrophic template failure and the pages drop out of their categories, on other pages it just breaks the code examples. Probably sounds like something to contact support over to see if anyone cares/can figure it out."
Discussion of issue started here: https://community.secondlife.com/forums/topic/523728-lsl-scripting-wiki-issues/#findComment-2914416
Lettie Linden
tracked
Thank you for letting us know! I have forwarded this information on to the developers for investigation.
Gwyneth Llewelyn
Lettie Linden you're welcome! Although you'd want a system administrator to get this fixed — not a developer ;-)
Frionil Fang
According to the Special:Version page on the wiki, the <syntaxhighlight> tag is not registered as a parser extension tag and as a result the code examples inside them get parsed as raw MediaWiki/HTML markup and cause varying levels of breakdown. Has some kind of an update broken compatibility with the SyntaxHighlight extension, or just is it not being loaded?
Gwyneth Llewelyn
Frionil Fang very very very likely that's the root of all troubles. Who knows, perhaps
this
time, once someone reviews what broke this, they might fix this old issue wih SVG as well. And who knows what else...Thunder Rahja
Make sure you're accessing the wiki via HTTPS (secure) and not HTTP (unsecure). When you try HTTP, the website redirects your browser to use HTTPS. I don't know if this means that redirection (the HTTP "location" header) is broken in some or all viewers.
AWalphaomega Resident
Thunder Rahja same issue whether http or https
Gwyneth Llewelyn
Thunder Rahja if you read my error report carefully, you can see that the automatic redirect from
http://
to https://
is
working fine — that's why I included the output from curl
. That's on Akamai/EdgeSuite's side — they have it configured accordingly to send back a 301 Moved Permanently
response with the correct Location
header — feel free to test it out with whatever tool you have (some online tools will work, some won't; apparently Akamai/Edgesuite is blocking popular online header check sites to reach LL's servers...).The counter-argument is, of course, experimenting with the viewer in-world to access a website which does that 301 redirect server-wise and see what happens. They look good to me on the sites I tested. At least on the macOS version of SL....
AWalphaomega Resident
This is definitely a problem. This is currently what you get when you try to read an extensive list like vehicle params: https://gyazo.com/7437f7f2dd8934b278ac0e43bb21d562
Gwyneth Llewelyn
Indeed. As a reference, here is what the Wayback Machine captured for that page around April 27, 2025 — the last time it managed to grab an almost-complete snapshot of the SL Wiki:
Note: Wayback Machine snapshots refer to
changed
pages on a certain date; this particular one had not been changed since March 10, so that's the last captured date.What can be seen there is that after May 9 the Wayback Machine was unable to crawl any further pages:
DimplesApplePie Spicy
Gwyneth Llewelyn
Gwyneth Llewelyn
DimplesApplePie Spicy you're absolutely correct — the code loading the syntax highlighting is totally and absolutely broken.
BTW, I tried to figure out how Fandom does it (Fandom is Wikia — Wikipedia's
other
company — someone has to pay for the bills 😅). They do a much simpler trick, they just load something like the popular highlight.js
script or something basic like that, and wrap a basic template around <pre>
tags. It's easy, simple, straightforward, works all the time, even if it's not so, uh, 'integrated' into the Wiki...