Thread:Angelo Gabrini/@comment-28083312-20200620055548/@comment-28083312-20201002022525

Sorry about that, is this a bit better? problems never get fixed Ye, Fandom definitely moves at a glacial pace in this regard & I also wish it could focus on more speed for fixes. Might be a dumb question but is Fandom eventually going to get rid of wikitext in the wiki itself? Not a dumb question, but requires some explaining. Fandom doesn't make MediaWiki software, the Wikimedia Foundation does that (folks who do Wikipedia n such). They also make the updates for MediaWiki software, & Fandom just uses it. In the past when we've built our own things onto MediaWiki, future updates don't have them in mind, & so we have to rebuild our custom extensions over & over on each new version of MediaWiki, to the point where we get a behemoth like Forum that makes that process nigh on impossible to continue. To avoid this, it was necessary for us to rethink how we build software. If we tack things onto MediaWiki, as with Forum, then we get stuck on outdated versions forever. Instead, we now build external software that "talks" to MediaWiki via API, like Discussions, but that is wholly separate from MediaWiki. This allows us to only use what the Wikimedia Foundation releases (as far as MediaWiki is concerned), so we can constantly upgrade MediaWiki with ease. Once we reach this ideal end state, with MediaWiki separated from all our other features, we can keep MediaWiki forever & expend very little effort to keep it up to date. There's no longer any reason to do away with it, & since our other applications don't have to be rebuilt every few years, in theory we should be able to invest more time in actually improving them once we reach the finish line. Sure, but I'm also sure that fandom can put more effort into it rather than introducing stuff like the fandom store which I think is utterly pointless. Is fandom going to start streaming tv shows and anime next? The Fandom store is one way Fandom is trying to diversify revenue streams. If we aren't completely dependent on ads, then we don't have to, as you say, care quite so much about views. If we have diverse revenue streams then we will be more stable & free to focus on what matters, like bug fixes. There are no plans to produce our own anime or TV show, but we have produced our own video game already.I know the redirection isn't the primary issue, but its relation requires some explanation of the HTML of the image embeds. Normally, image embeds are wrapped in a link to the file page, but clicking it does nothing because there's JavaScript in place that keeps the link inactive (unless hard clicking it) & instead presents the lightbox. What I think is happening is that the JS is failing so that when logged in the link suddenly starts working again, directing you to the file page, whereas while you are logged out you still get sent to the file page, but being logged out you then get redirected back to the page where the file was used on. That redirection would look like a simple reload. To see if I can prove this theory I need a bit more information. On a page where this happens to you, can you try appending  to the end of the URL, & then hit enter? (this must be before any  symbols in the URL, e.g.  ).  Once you've done this please check to see if the error is still happening. If it isn't, try just with  & then with , then let me know which works & which doesn't. If the bug is still happening in each situation, then try   to see if that fixes it. If none of these fixes the issue for you, please let me know & paste the final URLs you used for each test. With these tests I can mostly determine if anything on Fandom's end is causing the issue. One last thing: If you know how, open Developer Tools & display the browser console in Chrome while testing, & let me know if you see any JavaScript errors show up. If you see any then we might be able to zero in on why the JS is failing, if that is indeed the case.