FANDOM


This Forum has been archived

Visit the new Forums
Forums: Index Community Central Forum Adding links to top bar
FANDOM's forums are a place for the community to help other members.
To contact staff directly or to report bugs, please use Special:Contact.

50px-Replacement filing cabinet.svg

Note: This topic has been unedited for 3470 days. It is considered archived - the discussion is over. Do not add to unless it really needs a response.


Wikia: WBVDKT

I've always been against Oasis as it makes features more... distinct (for lack of a better word) and therefore hard to find. I want to remove the slide-down menu (with options to delete, edit etc.), the facebook like button and the talk link then readd them next to the slidedown menu which ends in a link to history, then I want to add a history button too incase the menu for whatever reason doesn't work (like on an iPad). Is any of this possible (which I imagine it is), and could anyone provide me with the code or resources I need to execute this plan? I'de imagine it comes in the form of me adding stuff to the javascript or cascading style sheet...

Thanks,

--User:Kris159 (Talk) 21:03, April 1, 2011 (UTC)

Most of it is but cannot be done wiki wide. It would be for personal use only. None of this has been done before as far as I know and so would take someone very good with css and js to work it out. Talk with User:Monchoman45.--GodPray  21:20,4/1/2011 

I feel totally special right now. I'm not sure I completely understand what you're asking, though: you said you want to remove the edit button dropdown, but then you said you want to add things next to the dropdown menu? Moving stuff around is easy and can definitely be done, but not wiki-wide as far as I know.  Monchoman45  Talk  Contribs  Skystone  21:55,4/1/2011 
I don't mind if it's not wikia-wide, since my community is small. I want to remove the edit dropdown menu, and place it next ot the history drop down menu. I also want a history button next to that, and to move the facebook like and talk page buttons next to those, so it's all in line with the history drop down menu. --User:Kris159 (Talk) 23:03, April 1, 2011 (UTC)
Aha - that's easy. Add this to your JS file:
function MoveEditButton() {
	var button = $('#WikiaPageHeader .wikia-menu-button').clone();
	$('#WikiaPageHeader .wikia-menu-button').remove();
	button.appendTo('#WikiaPageHeader details');
	$('#WikiaPageHeader').append('<a href="/index.php?title=' + wgPageName + '&action=history" class="wikia-button" style="margin-left:10px;">History</a>');
}

addOnloadHook(MoveEditButton);
That should do it. Let me know if there are overlapping problems or anything like that.  Monchoman45  Talk  Contribs  Skystone  23:29,4/1/2011 
Where do you get this stuff? P.S. no overlapping occured, what about a history button and moving the talk page button? P.S. 2: Overlapping did occur, found the history button a few pixles down the page. I have a code anyway that moves the page slightly up, you should take a look at this. --User:Kris159 (Talk) 23:50, April 1, 2011 (UTC)
Whoops, forgot about the talk page button. Replace the above code with this:
function MoveEditButton() {
	$('.commentslikes').prependTo('#WikiaPageHeader details');
	$('#WikiaPageHeader details').prepend('<a href="/index.php?title=' + wgPageName + '&action=history" class="wikia-button" style="margin-left:10px;">History</a>');
	$('#WikiaPageHeader .wikia-menu-button').prependTo('#WikiaPageHeader details');
}

addOnloadHook(MoveEditButton);
I'd also suggest adding #WikiaPageHeader details {width:980px;right:320px;} and #WikiaPageHeader .categories {display:none;} to your CSS to make the details bar wide enough to fit everything.  Monchoman45  Talk  Contribs  Skystone  00:42,4/2/2011 
Thanks for all the help. Does it violate anything if I make it wikia-wide? User:Kris159 (Talk) 11:52, April 2, 2011 (UTC)
It is likely that it does violate the ToU. Most changes to the interface do.    ǝsʞpɐןǝ  (message wall)  12:28, 2/04/2011
Hmm... well I reread the terms of use and it doesn't "lock, remove, or otherwise obstruct the proper functioning and view of advertisements, and/or user interface and functionality by other users", it only moves some features in to a place I would argue is more seeable (and therefore is not obstructive) and adds one (although I can't say the same about some other features I've edited...). I'de just rather not copy and paste CSS and JS several times to the regular users' scripts... Kris159 TalkLegacyWBVDKT 15:24, 2011/04/02

Wikia are quite strict about this sort of thing though. These sort of personalisations cannot go wikiwide, as they differ from the 'standard issue' interface.

As for copy/pasting into other user's scripts - you shouldn't be doing that anyway without permission from said users. Put the code on a talk page/forum with instructions so that they can do it themselves.

EDIT: Your entire wiki seems to violate the ToU - I would be very careful if I were you and remove some of your modifications. See Monchoman45's guide to CSS and JS for examples of what is and isn't allowed site-wide.    ǝsʞpɐןǝ  (message wall)  15:35, 2/04/2011

Whoops... I didn't know, but I'll remove the feature-tweaking wikia-wide CSS and JS now. The regulars I was talking about (about 5 of them) do not really care about the setup of the Wikia and agree as my version of infoboxes are quite wide (they leave about 20px for the text with a standard thumb next to an infobox) and are close cyber friends of mine. Kris159 TalkLegacyWBVDKT 15:51, 2011/04/02
Would things like making section headings bold and changing color of fonts be allowed? 'Darn the ambiguity of ToU Kris159 TalkLegacyWBVDKT 15:54, 2011/04/02
That should be allowed. It doesn't effect the actual interface, aside from maybe the odd bit of text.    ǝsʞpɐןǝ  (message wall)  15:57, 2/04/2011
I don't know whether it is the wiki's code or the above modification of the buttons, but I'm getting two hide sidebar buttons on your site.    ǝsʞpɐןǝ  (message wall)  16:00, 2/04/2011
I did't even know there was a hide sidebar button... where is it? Kris159 TalkLegacyWBVDKT 16:04, 2011/04/02
Go to Monchoman45's guide to CSS and JS for the code, but essentially it is personal css gives you a button that allows you to hide and show the sidebar. The problem on your site though is that as the edit button has been essentially duplicated to produce the history button, the 'Hide Sidbar' button shows twice. I'm sure there's a fix, but I'm an amateur CSSer.    ǝsʞpɐןǝ  (message wall)  16:09, 2/04/2011
As am I. I'll just move the script for the button movement in to personal scripts so it doesn't effect anyone that doesn't want it. Kris159 TalkLegacyWBVDKT 16:10, 2011/04/02
That's probably because the jQuery found two matches, and thus added it to both of them. Not really sure why it would do that, though.  Monchoman45  Talk  Contribs  Skystone  16:18,4/2/2011 
Why isn't the personal common.js working? Does it take time to load or something? Kris159 TalkLegacyWBVDKT 16:20, 2011/04/02

(unindent) I don't think you can define personal common.js. Or rather, I don't think the page loads a personal common.js.  Monchoman45  Talk  Contribs  Skystone  16:23,4/2/2011 

...So is there anything I can do? Or any code I can put on to prevent the duplicate buttons from happening? Kris159 TalkLegacyWBVDKT 16:26, 2011/04/02
I wrote the code for that button when I was just getting started with JS - in fact, most of the stuff on that blog could use a tune up. There's not much you can do, but I should probably rewrite some of my functions.  Monchoman45  Talk  Contribs  Skystone  16:27,4/2/2011 
Well it's only a duplicate, and I'm assuming it doesn't obstruct anything when I say I'll leave it be. Thanks for all the help, everyone. Kris159 TalkLegacyWBVDKT 16:34, 2011/04/02
Community content is available under CC-BY-SA unless otherwise noted.