Web/Marketplace Bugs

Marketplace and SL websites
  • Search existing bugs before submitting
  • Use support.secondlife.com for customer support issues
  • Keep posts on-topic
[⚠️ URGENT] SL Wiki: syntax highlight is broken *and* in-world access via viewer is down...
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... `# curl -i http://wiki.secondlife.com/wiki/LlHTTPRequest HTTP/1.1 301 Moved Permanently Content-Type: text/html Content-Length: 134 Location: https://wiki.secondlife.com:443/wiki/LlHTTPRequest 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! ` curl -i https://wiki.secondlife.com:443/wiki/LlHTTPRequest 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&#58;&#47;&#47;wiki&#46;secondlife&#46;com&#47;wiki&#47;LlHTTPRequest" on this server.<P> Reference&#32;&#35;18&#46;cd7d1302&#46;1748626825&#46;bfdba40a <P>https&#58;&#47;&#47;errors&#46;edgesuite&#46;net&#47;18&#46;cd7d1302&#46;1748626825&#46;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: * https://feedback.secondlife.com/web-bugs/p/https-wikisecondlifecom-wiki * https://feedback.secondlife.com/web-features/p/second-life-wiki-timing-out-with-http-504-errors 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).
20
·

tracked

Addressing the premium membership cancellation trap
As most of you already know. SL premium and premium+ memberships can be booked for a month or a whole year. Im gonna use the term premium for both memberships to keep it easy to read. The monthly or yearly amount has to be paid the moment one chooses to upgrade their account from basic and is going to extend automatically until the user downgrades or payment issues arise. The issue: As soon as the user downgrades from Premium to basic manually, all premium perks (Lindenhome, mainland parcel, reduced upload fees, linden stipend, etc) are going to be taken the same moment of the cancellation, no matter if there is one day or 11 months of premium time left. Is there any money refunded you may ask? No, not a single cent. Why should the current practice be changed? Because giving the customer what they paid for in advance should be something that we dont even need to talk about. We pay up to 250 bucks for up to 12 months - thats a lot of money to still be asked from Linden employes to "just setup a phone alarm for ringing in 11 months" Not going to refer to all the continents and countries, where that kind of business practices would already be sued into oblivion, as LL is located in the US and only has to stick to US law - nevertheless is doesnt shed a good light on how premium customers are treated, customers who send their money directly to LL. Personally I didnt learn my lesson - im even premium plus since two years, but for the love of SL, not the company behind.
10
·

tracked

Load More