Forum:Infobox In Sidebar Module

considering that I see no evidence that it's in operation, and sorry if it's been answered recently, but I recall hearing this somewhere:


 * "Wikia are looking at putting infoboxes and other page content into modules in the sidebar. More "modules" are being developed for it, [...]."

This sounds like a reasonable solution to getting the horrible Oasis skin on track to usefulness, or at least to begin making it bearable. Has there been any development on this feature (or, should I say, this necessity)? When is it expected? Is it expected? Was it abandoned? Thanks, --Dubiel 17:31, May 13, 2011 (UTC)


 * Never heard of such plans. However, there are plans to utilize the siderail in the Rich Text Editor. More details here. — Sovq 17:57, May 13, 2011 (UTC)


 * Yes, someone mentioned those plans and they are ongoing. Special:Chat is accessible as a sidebar module and is being tested on various wikis (see Chat). Unfortunately, Wikia doesn't seem to like to give us alot of prior notice all the time, but they are working on stuff. -- Fandyllic (talk &middot; contr) 13 May 2011 5:49 PM Pacific

Come back tommorrow and I'll have it ready for you to try out. I just have to cleanup my code and make it work with any infobox.


 * Thanks a lot. I can't wait for it to happen. Getting the infoboxes in on the far right would be a vast improvement, if not a remedy in itself. --Dubiel 16:12, May 14, 2011 (UTC)

Infobox Module
Okay, I'm a JS idiot, but I've been able to produce code that works. As it's non-TOU compliant, here are the instructions:


 * 1) Install the code here to MediaWiki:Infobox.js.
 * 2) Add  to the infobox template.
 * 3) Add the following import to your personal wikia.js, replacing WIKINAME with your wiki's name:
 * importScriptPage('MediaWiki:Infobox.js', 'WIKINAME');
 * 4) Add  to your personal wikia.css.

Please give feedback, and report any bugs. I know it could be done cleaner, but I think it's almost perfect. You may need to reformat your infobox to make it look better within the module.

Response

 * Thank you, although no matter what I can't get this javascript to work (not even when applying it to my profile at your Casualty wiki). To aid in troublshooting, where can I see it in action? --Dubiel 22:16, May 14, 2011 (UTC)


 * Clear your cache and such. It definitely works. When you create new .js or .css pages, they sometimes take a while before they're loaded properly.


 * Cache is definitely clean and clear. Just to be certain - shouldn't this be enough to view the Casualty modules? --Dubiel 23:01, May 14, 2011 (UTC)

Your code is correct. Have you tried looking at a page with an infobox on? This page for example. The code has worked for both me and moncho.


 * Thank you for your patience, it works fine on those pages and looks great - but only when I log out, oddly. --Dubiel 10:53, May 15, 2011 (UTC)
 * Odd... I'm sure it's cache related. It'll fix itself in time.

Have updated instructions to make the interface 'cleaner' (Basically, to reduce the amount of rearrangement you see when js deploys)


 * Sorry to sound like Steve Bovis here, but having tested on three browsers, ensured the .js and .css is operative and cleaned my cache numerous times, I still encounter weird problems on the Casualty wiki. With the new .css, the infobox disappears completely and no side module is visible. Tested on Firefox, IE and Chrome. I don't know, perhaps I'm making an idiotic mistake or there is some glitch with my preferences, but the code looks ok... --Dubiel 15:06, May 15, 2011 (UTC)
 * InfoboxModule.png, now I am worried. You have identical code to me (Including my awesome CustomOasis skin) and it doesn't appear to work...
 * The css forces the infobox to disappear, but the js is meant to bring it back (and does, for me). This is a js problem, as the module isn't being produced either, but I believe it is at your end. Tell me, does other js work for you, for example, collapsable tables?
 * If you want, come onto Casualty Wiki Chat, and we'll try to sort it there.


 * The problem was solved once I reinstalled the browser. I can't be sure of the exact cause, but seems it was due to conflicting plugins, so indeed it was from my end. Thanks a lot for your patience again, the feature is awesome! --Dubiel 15:56, May 15, 2011 (UTC)