FANDOM

Haldarn

Bureaucrat Admin
  • I live in Kidderminster, UK
  • I was born on April 19
  • I am Male
A FANDOM user
  Loading editor
  • Good job on the reorganizing of the monster rearing pages.

      Loading editor
  •   Loading editor
    •   Loading editor
    •   Loading editor

    •   Loading editor
    •   Loading editor
    • A FANDOM user
        Loading editor
  • I did some digging and managed to fix the issues with tooltips showing up on mobile. Turns out there's a "hidden" class that hides elements on mobile, so we just need to use class="hidden" in addition to style="display:none;" whenever we want to hide anything. The class does nothing outside of mobile, so that display: none is still needed. Wikia is great at web design.

      Loading editor
    • Mobile view example
      I still maintain, even after my discussion with people over on Community Central, that by far and away the better solution to mobile use is to use the one-time Desktop Site link at the bottom, or ask your browser to "View Desktop Site".

      Tooltips work on my mobile fine under Chrome with longpress. The layout is actually better than Oasis on desktop because it moves the siderail underneath the page.

      And until Mercury becomes even slightly aesthetically pleasurable, I don't intend to spend any time developing pages for it (ie moving away from tables to structure design templates) as Wikia have requested. They did open channels to say they could provide assistance to anyone of our admins who wanted to do so, in case you felt the urge - I have also let Toast know - details are in that thread^^

        Loading editor
    • Oh, no, you're absolutely right. The mobile site is breaking all kinds of rules when it comes to good web design - I haven't seen much worse. I'm only interested in fixing things that are very broken on mobile, like the tooltips showing up all the time and the infoboxes being all kinds of broken. I'm not too concerned with making it look good on mobile, because they make that pretty much impossible (no stylesheets, stripping inline styling, etc.).

      I'm also moving away from using tables in templates, but that has more to do with the flexibility that styled divs provide; the mobile site functionality is just a bonus.

        Loading editor
    • A FANDOM user
        Loading editor
  • Forgive me if this has been addressed else where, but are the forums down for maintenance or permanently? i cant seem to log into them at all

      Loading editor
    • Wikia stopped supporting the forums on 30th April 2017, when they were taken offline permanently.

      Wikia do host the archive of the forums which is only available to download via Torrent, at about 2.5GB. I just checked and it's still available.

      It is a phpbb archive, so I believe in order to browse them in their original format, you'd have to upload the archive to a phpbb server, whether that is local or online. If you're just after information and don't mind crawling unformatted text, you may be able to do so just from the archive itself.

      If you'd like the torrent file, feel free to drop me a private message on our Discord server with your e-mail address and I'll send the .torrent file to you (I can't upload it here).

      If you have current queries, rather than being after old posts, our Discord server is your best place to ask! :)

        Loading editor
    • A FANDOM user
        Loading editor
  • So, I got carried away improving {{TrustNPC}} and noticed that Template:FFXIbox looks incredibly bad/broken on mobile. I couldn't leave that alone, so I ended up making a CSS replacement for the fancy border part: you can now use "ffxi-box" as a class to add an image border of File:FFXIbox.png. Here's an example:

    {|class="ffxi-box"
    | Look at me, I'm a bordered table
    |}
    
    Look at me, I'm a bordered table

    It should be a pretty simple matter to update Template:FFXIbox to use the class and styled divs (see Template:TrustNPC as an example), but I haven't taken the time to do that yet.

      Loading editor
    • View all 10 replies
    • Oh, and regarding the annoying space issue: add style="margin-bottom: 0.5em" to the table that you're using for a dialogue box. Margins are like padding, but they're outside of the element instead of inside and the "0.5em" means half a font size of space. If you want to avoid using a description list (the : list) to indent the dialogue boxes, you can also use margin-left to indent it manually.

        Loading editor
    • Ooh, thanks! :)

        Loading editor
    • A FANDOM user
        Loading editor
  • Chocobo Digging/Zones A-M Chocobo Digging/Zones N-Z Treasure Casket Rewards/N-Z Have errors on them which makes the zone pages look weird. I don't think it's the page itself. I can't figure out which template changed that created this issue. Maybe you'll have better luck tracking it down.

      Loading editor
    • Thanks for highlighting that. Changes to the {{Abundance}} template have meant that it requires zero values, whereas those you'd mentioned were left blank which generate the formatting error.

      I've corrected the messes you pointed out, but I'm going to ask User:Karuberu to take a look at the 'Divided by zero' default message on those Abundances that are 0|0.

        Loading editor
    • Thanks ^^

        Loading editor
    • A FANDOM user
        Loading editor
  • The other half of my plan to replace {{Item Header}} is now complete: I made a new script which wraps header sections and applies classes to the wrapper.

    It works in a similar way to the collapsible header sections script, but is slightly more complex, using the span's attributes to specify the target and classes. To make things simple, I created {{WrapHeaderSection}} for the generic functionality and {{Item Sections}} for a simple include on item pages. I also created {{Collapse Sections}} as an easy way to include the collapsible header sections tag.

    The script changes are still under review, so you might have to turn on test mode to see it, but I've added it to my sandbox: compare the new revision to the old revision (the difference is only apparent in Monobook, so I've specified that skin in those links).

    I should note that while this functionality could be useful from time to time, it's better to explicitly wrap sections when possible. The biggest use case I see is to avoid a specific issue of section editing. Consider the following page markup:

    <div>
    ==Header 1==
    Content
    </div>
    <div>
    ==Header 2==
    Other content
    </div>
    

    Using the section edit feature on "Header 1" will show the following:

    Content
    </div>
    <div>
    

    An editor that doesn't understand what's going on might remove those div tags, thinking they're a mistake. We saw this happen a lot with the old item page formatting: novice editors would often remove the |width="50%" valign="top"| at the bottom of a section and wreck the formatting.

      Loading editor
    • I was following until "I should note that while..." - I'm not sure your meaning on explicitly wrapping sections. I understand the example of section edit errors, having run into those every now and then.

      What I understood; Basically every Item page now needs to begin with: {{Item Sections}} and we'll have the pre {{Item Header}} appearance of section edits, plus the collapsibility.

      Quick question; would you prefer Section headers that aren't covered by {{Item Sections}} (eg How To Obtain, Notes) to be added to {{Item Sections}} as we come across them, or just to be added as additional {{WrapHeaderSection}} lines on an item's page? The former might help in standardisation.

      Quick question 2; do I need concern myself with {{WrapHeaderSection}} <wrapper-class> for standard usage, or is that reserved for advanced formatting that I haven't conceived yet?

      So based on that, and yup I can see it working well on your Sandbox, I don't follow the bit about the functionality only being useful from time to time and needing explicit wraps normally. Sorry for being dumb!

        Loading editor
    • Sorry, that's on me - I could have explained that a lot better. You got most of it, though. Replace the {{Item Header}} headers with regular headers, include {{Item Sections}} on the page, and you can get the fancy functionality of {{Item Header}} without losing section editing or experiencing any of the other quirks of {{Item Header}}.

      It was poorly explained, but by explicitly, I just meant manually wrapping the sections in a div like this:

      <div class="someclass">
      ==Header 1==
      Content
      </div>
      

      As opposed to using {{WrapHeaderSection}} like this:

      {{WrapHeaderSection|Header 1|someclass}}
      ==Header 1==
      Content
      

      Both will do pretty much the same thing, but the {{WrapHeaderSection}} method has worse performance (it might cause slowdowns if used too much on a single page) and the script won't run until after the page is fully loaded, so you might see some things shift after fully loading. It's probably not a big deal in most cases, but it's something to keep in mind.

      RE: #1: I think it's safe to leave out the other item sections, since they don't need any special formatting like the Statistics, Other Uses, and other sections do. {{Collapse Sections}}, which is included in {{Item Sections}}, ensures that all of the header sections will still be collapsible, without having to be specified by a {{WrapHeaderSection}} in {{Item Sections}} (or otherwise). I don't think we have any other reason to wrap them in a special class, but maybe I'm forgetting something?

      RE: #2: So, all {{WrapHeaderSection}} does is wrap a header and its following section in a div and add a class to the div. The wrapper class param is just the class that's being applied to the wrapper div. This can be really useful for styling purposes, but essentially all it does is turn this:

      {{WrapHeaderSection|Header 1|someclass}}
      ==Header 1==
      Content
      

      Into this:

      <div class="someclass">
      ==Header 1==
      Content
      </div>
      
        Loading editor
    • A FANDOM user
        Loading editor
  • I ran Karubot yesterday and added labeled sections around item images on every page that uses {{Item Image}}. I realized only after running it that you were using "ItemImage" and not "Item Image" as section names, so I ran it again to swap all of the "ItemImage" sections over to "Item Image". That may have broken some transclusion somewhere, so I wanted to let you know about it.

      Loading editor
    • Woop!

      Yeah that's probably broken a lot of things ;; lol I'll get on it. :)

        Loading editor
    • A FANDOM user
        Loading editor
  • I just wrote a script that generates collapsible header sections, much like the ones from {{Item Header}}, but without all the complications. All you have to do is include <span class="collapse-sections"></span> somewhere on the page (see my sandbox as an example). I'd like to move away from {{Item Header}}, since it has so many issues, and this is a first step.

      Loading editor
  • Hey, I just wanted to let you know that I've made two new templates that you'll probably want to know about: {{Map Overlay}} and {{Location Tooltip}}.

    I made {{Location Tooltip}} to enhance {{Location}} with tooltip maps that highlight the position on the map, since I find myself wasting a lot of time looking up where NPCs are on maps. I was originally going to use {{Tooltip-Map}} and {{Zone Map Coordinates}}, but I wanted more flexibility than those templates offered and there were a few odd design decisions, so I built a new template. I'm going to create labeled sections inside the map pages for the main cities and fix the issues with the tooltip script before adding the functionality to {{Location}}, though.

    After finishing {{Location Tooltip}}, I ended up breaking out some of the functionality to make {{Map Overlay}}, which is a more general-purpose template that can overlay just about anything over a standard-sized map (provided the map and the overlays are wrapped in a container with "position: relative" or "position: absolute"). I'm not sure how much use it will get outside of {{Location Tooltip}}, since maps with locations marked within the image itself are better in most scenarios, but it exists if you ever need something like that.

      Loading editor
    • View all 10 replies
    • It seems that using a div inside a caption causes the caption to terminate and tosses the div and everything after it out of the caption. The tooltips and overlays used hidden divs, so it was causing issues there. I changed them to spans and it seems to be fine now, but keep an eye out for any side effects of the change.

        Loading editor
    • Shall do, and thanks very much!

        Loading editor
    • A FANDOM user
        Loading editor
See archived talk page
Give Kudos to this message
You've given this message Kudos!
See who gave Kudos to this message