Template talk:MultiPoleQuestInfo

Hi Kevin,

I tweaked this template:

• I tried removing the extra space between the listing of the first pole and the second pole. Not sure if that will adversely affect the template
• I reduced the requirement to list from poles 1-4 to just list poles 1-2 since it was asking that I fill in for pole3 and pole4.
• Is there a way to remove the extra lines (carriage returns) placed after the list of poles?

You can see Guardian Grabber Quests as example of two poles. Was trying to replace the pole1 AND pole2 listing

😸Miyuki (talk) 23:54, 6 January 2022 (UTC)

Yes I tried to do this as well. Part (if not the entire) of the reason it leaves extra space is for the empty field. This used to work in Fandom's heavily forked MediaWiki, that became hugely popular due to the many modifications of making it more UI friendly and easier to edit. However, Fandom going back to a more original MediaWiki version, and also trying to appeal to its paying advert customers. Getting off track. Anyway the real solution would be trying to work how it is supposed to work correctly in MediaWiki and learning how to edit it as it is supposed to work. Something I never really took the time to learn as the basics to begin with. I have learned some of it now, but just did not take the time with this instance. With the old code having an empty field seems to have left a space, but with the new code I put in, that seems to have left a double space when there is an empty field. Worse the new code I put in adversely effects the old pages that had the empty fields. So I reverted it back to the old code for the first 4 poles. For example look at Broken Standard Quests or Holy Liberator Quests where if it has empty field such as |pole3 = or |pole4 = then it displays Level [[]] for every empty field. This is specifically why I changed the first 4 poles back to the old code but with trade off of it creating extra spaces with intentions of possibly (which may or may not ever happen) learning how to do proper code that does not leave spaces (I know that is possible just not sure how and why). It might just be a simple matter of making those fields 'inline' like so {{#if: {{{pole2}}} |, Level {{{pole2_lev}}} [[{{{pole2}}}]] }} | {{#if: {{#pos:{{{pole3}}} | pole3 }} | |, Level {{{pole3_lev}}} [[{{{pole3}}}]] }} Just not sure w/out testing it out. As I said I know I have not implemented the most correct code which would be ideal, but a work around would be to edit all those old pages and simply remove all instances of empty fields. There should not be that many. And we could do this for all the multi-pole quests as some of them simply only have the 1 pole listed. Again there are only so many multi-pole quests so would require a lil bit of work but should not be that much.

Asking to fill in for pole3 and pole4 should be a simple matter of leaving it empty or clicking space button and moving to the next field. I am not having such issues so makes me wonder how you edit or what editor you are using? I am using the Source Editor and under my preferences I have the 'editing toolbar' (aka 2010 wikitext editor) enabled. I know there is also a Visual Editor and thought I had seen that early on after the move, but I have not even seen that lately or recall where it is selected. Never really used it that much before anyway so have not really taken the time to look for it either though.

As to your last, yes there is a way. But see my first paragraph, just am not sure exactly how that is done. As stated it might be simply coding it 'inline'. The con of making it all inline is more difficult to read, at least in the Source Editor since it would all be done on one line instead shown on a next line, but if that works it needs to be done that way. I will have a look at that later. Kevin "Hawk" Fisher (talk) 09:30, 8 January 2022 (UTC)

Ok, I fixed all the white space being created by simply putting it all inline. Thought we had to use a | but we do not. But my new code adding more then 4 poles (and now incorporating pole 3 & 4) is still not correct. It is still creating the Level [[]] for empty fields when it should not be. As you tried to do, there needs to be an else portion in there somewhere but do not have the time atm to look into it. Instead will simply remove those from the few pages they are on. I still am curious what editor you are using. Kevin "Hawk" Fisher (talk) 04:07, 9 January 2022 (UTC)

Thanks for updating the code. I'm not sure what editor I am using other than that it shows me the code and not the visual editor stuff as with Wikipedia. 😸Miyuki (talk) 22:26, 10 January 2022 (UTC)