Feed The Beast Wiki

Follow the Feed The Beast Wiki on Discord or Mastodon!

READ MORE

Feed The Beast Wiki
Register
Advertisement

Common.js[]

I noticed an unused function called "ModifySidebar" in the common.js, apparently unused anywhere and wondered if it was worth keeping? Cblair91 (talk) 13:03, 26 January 2015 (UTC)

Resolved in my JS cleanup Cblair91 (talk) 09:11, 27 May 2015 (UTC)

Problems accessing wiki pages like /dev/null[]

The problem arises from how the wiki does its links: it doesn't check for restricted characters, leading it to try to send anyone trying to get to the /dev/null page to the literal web address "/dev/null" because it tries to link to //dev/null. To actually access the /dev/null page you have to directly access the url "http://ftb.gamepedia.com/%2Fdev%2Fnull", which has the '/'s replaced with the URL encoding for '/': %2F. -- Preceding unsigned comment was added by 68.164.105.40 (talkcontribs)

We are well aware of this issue. This problem is something that can't be avoided as it a limitation of the website itself; however there was a quick fix made to circumvent this issue when the article was made which gives a fully operating link in the Navbox for the OpenBlocks mod. For quick reference the link in the Navbox targets /dev/null rather than the conventional location. --Wolfman_123_ · FTB Wiki Staff 01:31, 13 March 2015 (UTC)
Still suggest you create a page like dev/null for users using the search box. -- 16:27, 26 May 2015 (UTC)
Damn that's a mind screw. dev/null created. PaladinAHOne Staff (talk) 08:12, 27 May 2015 (UTC)

Ftb.css[]

Just checking through your CSS and stuff, I notice you have a FTB.css, yet it's never directly imported/called/used? Cblair91 (talk) 07:49, 26 January 2015 (UTC)

That is the old theme from before we moved to Gamepedia. 🐇Retep998🐇🐰Bunny Overlord🐰 07:53, 26 January 2015 (UTC)
So it's technically safe to remove? :) Cblair91 (talk) 13:03, 26 January 2015 (UTC)
Should be -- SatanicSantaFTB Wiki Admin 14:56, 26 January 2015 (UTC)
Needs deleting then :P Cblair91 (talk) 09:13, 27 May 2015 (UTC)

PLZ PATCH[]

Patch from commit df529ac. It's so annoying.

    Fix positioning of the ime selector.

diff --git a/lib/jquery.ime/jquery.ime.js b/lib/jquery.ime/jquery.ime.js
index eb99ebe..5b317b2 100644
--- a/lib/jquery.ime/jquery.ime.js
+++ b/lib/jquery.ime/jquery.ime.js
@@ -1037,7 +1037,7 @@
 
 			this.focus(); // shows the trigger in case it is hidden
 
-			elementPosition = this.$element.offset();
+			elementPosition = this.$element.offset() - $(document.body).offset().top;
 			top = elementPosition.top + this.$element.outerHeight();
 			left = elementPosition.left;

If you don't mind breaking the slide up and fade out animation, just add this to MediaWiki:Common.css:

.imeselector {
    margin-top: -29px !important;
}

Now the scrollbars in those syntax highlighting boxes are bothering me lol. --

16:15, 26 May 2015 (UTC)

.mw-code pre {
    overflow-x: visible;
}

Yeah. --

16:23, 26 May 2015 (UTC)

--- MediaWiki:Common.css	Tue Apr 21 06:09:00 2015
+++ MediaWiki:Common.css	Wed May 27 06:46:56 2015
@@ -14,18 +14,32 @@
 /** Fun stuff **/
 
 /** Rainbows **/
-/* Check browser support @ http://caniuse.com/background-img-opts */
+/* Check browser support @ http://caniuse.com/background-img-opts & http://caniuse.com/linear-gradient */
 .rainbow {
-    background-image: -webkit-gradient( linear, left top, right top, color-stop(0, #F22), color-stop(0.15, #F2F), color-stop(0.3, #22F), color-stop(0.45, #2FF), color-stop(0.6, #2F2),color-stop(0.75, #2F2), color-stop(0.9, #FF2), color-stop(1, #F22) );
-    background-image: gradient( linear, left top, right top, color-stop(0, #F22), color-stop(0.15, #F2F), color-stop(0.3, #22F), color-stop(0.45, #2FF), color-stop(0.6, #2F2),color-stop(0.75, #2F2), color-stop(0.9, #FF2), color-stop(1, #F22) );
-    color: transparent;
+    background: linear-gradient(to right, #F22, #F2F 20%, #22F 35%, #2FF 55%, #2F2 70%, #FF2 85%, #F22);
+    color: rgba(0, 0, 0, 0.4);
     -webkit-background-clip: text;
     background-clip: text;
 }
+
+.rainbow.rainbow-repeating-100 {
+    background: repeating-linear-gradient(to right, #F22, #F2F 20px, #22F 35px, #2FF 55px, #2F2 70px, #FF2 85px, #F22 100px);
+    color: rgba(0, 0, 0, 0.4);
+    -webkit-background-clip: text;
+    background-clip: text;
+}
+
+.rainbow.rainbow-repeating-200 {
+    background: repeating-linear-gradient(to right, #F22, #F2F 40px, #22F 70px, #2FF 110px, #2F2 140px, #FF2 170px, #F22 200px);
+    color: rgba(0, 0, 0, 0.4);
+    -webkit-background-clip: text;
+    background-clip: text;
+}
+
 .rainbow > :not(.rainbow-ignore),
 .rainbow div:not(.rainbow-ignore) *,
 .rainbow span:not(.rainbow-ignore) * {
-    color: #000 !important;
+    color: rgba(0, 0, 0, 0.4) !important;
 }
 
 /** Upside down stuff **/

Fix for rainbow text and two flavors of repeating rainbow text. Patched just for User:Retep998. --

06:53, 27 May 2015 (UTC)

Add a "show background" class for the crafting grids[]

Can the line .CraftingGrid .grid { from MediaWiki:Common.css be changed to .CraftingGrid :not(.gridShowBackground) .grid {? This would make {{cg}} cells with the class "gridShowBackground" show the background on {{G/Cell}} for the sake of covering things like default backgrounds, as most in game cases hide that image (eg, the armor slots). Otherwise I would have to upload an additional image for each empty slot and add extra code to make sure it will display when the parameter is unset. Existing grid templates will be unaffected, so it is basically an "opt in" type thing. KnightMiner t/c 16:35, 3 November 2015 (UTC)


<- it does already have the grey background? In fact you have to explicitly say for it to not to have a background -
Chocohead NagEditsStaff 17:01, 3 November 2015 (UTC)
It appears .craftingGridNoBg is currently ignored. It used to be that Cg templates had to specify that for each cell to disable that behavior, but it appears it was made to always hide the background by default. TheSatanicSanta, do you think we should reinstate the requirement for .craftingGridNoBg to hide the background? 🐇Retep998🐇🐰Bunny Overlord🐰 18:49, 3 November 2015 (UTC)
Not sure. How much would it break things and how quickly and easily could it be fixed? Does it actually cause a problem, because I haven't really noticed any? -- SatanicSantaFTB Wiki Admin 19:19, 3 November 2015 (UTC)
It just means that the background visible in a standalone {{Gc}} call would also be visible in any Cg that doesn't use .craftingGridNoBg. It would be pretty simple to fix any Cgs that don't use it but should. A lot of Cgs already use it anyway. 🐇Retep998🐇🐰Bunny Overlord🐰 19:37, 3 November 2015 (UTC)
Most of the templates I've seen have used it, along with me personally using it in the new templates I make when relevant. The main problem is you can no longer tell it to show the background, which causes the default cell background issue I mentioned above. KnightMiner t/c 21:02, 3 November 2015 (UTC)
So wait, the change will basically be having to define it in the Cg as a whole, and will effect every cell in the Cg, rather than having to define it in individual cells? -- SatanicSantaFTB Wiki Admin 00:09, 4 November 2015 (UTC)
Look at {{Cg/Distillery/GregTech}}. Notice the {{Cg|cell|{{{1|{{{I1|}}}}}}|62|28|class=craftingGridNoBg}}. That's all a Cg would have to do to hide the background from {{Gc}}. Whether that background should be hidden or not depends on the Cg. For example, with GregTech the {{Gc}} backgrounds should always be hidden since you can clearly see the images in the slots from Greg's GUI's even when there is an item in them. 🐇Retep998🐇🐰Bunny Overlord🐰 00:23, 4 November 2015 (UTC)
Advertisement