Hi, I am dealing with reviewing and communicating the issue, but I am not an engineer. So, unfortunately, I do not know the answer to your question: is it related to the recent Fallout problems, or just a general question about the extension's coding?
Yes, it's related to the Fallout problems. This extension is the reason why the Infobox template doesn't work anymore on at least 50% of the Fallout wiki's pages. The extension appears to be incompatible with mediaWiki 1.19 and what I posted there is my hypothesis as to why. Fixing / updating the extension would be the easiest and most convenient solution for all. Or so it seems to me...
We updated Wikia to 1.19 quite a while ago, so it likely wouldn't explain the problems only just starting recently. However, it is possible it is somehow all related - I will pass it along to the technical staff to aid their investigation.
Kirkburn wrote: We updated Wikia to 1.19 quite a while ago, so it likely wouldn't explain the problems only just starting recently.
I find that just as odd as you do. My guess is based mostly based on the extension page itself which clearly states that it doesn't work under mediaWiki 1.19+. But the real problem may very well be something else entirely...
Hi Kirkburn, when the new editor was introduced like 2 years ago, we reported that js was not displaying on preview like it should. It has never been fixed. Is it ever going to be? I reported this on a special:contact (Request #79253, April 07) and it was ignored.
Ah, I think we must have missed that bit of your report. It is something we would love to expand, but is quite complex to achieve - we've got JS for specific features running, but unfortunately other items have just taken priority so far.
Are there specific JS situations that you feel are more important to have running (specific features, wiki JS, user JS, etc.), or generally all of it?
Well my answer is what I was saying countless times between the new editor being introduced - all of it! A preview should, like in normal mediawiki installations, show you what would happen if you clicked "publish", but just not save it to the database. I really don't see how that is hard to achieve, but this pop-up preview thing that you're having to hand tweak is a real pain.
The general issue is that JS is designed to work with specific layout structures - the preview dialog does not always match what it expects. This was not something we were anticipating to be a major issue when creating the dialog, but certainly realise the problems with since.
I will pass your views along to the product development staff to inform our future work.
