Welcome to the DFO World Wiki. With many major updates since the release of DFO, many items are missing. Visit Item Database Project to learn more.
Please remember to click "show preview" before saving the page.
Thanks for the updated logo snafuPop!

Just a few questions...

Jump to: navigation, search
Revision as of 22 February 2019 at 05:10.
The highlighted comment was created in this revision.

Hey Dfoplayer. If you don't mind, I have a few questions about a few things.

1) When creating the page Aspect: Trine Set I noticed that the second headers for the Priest(F) and Priest(M) skills did not appear in the 3 part set effect. Am I doing something incorrectly?

2) Recently, I've been attempting to post the Youtube videos, the Chronicles of Luke: Chapters 1-5, into the Lore Episode page's collapsible tabs, but to no avail. How would I go about posting a Youtube video in a collapsible tab? Would it just be easier to post the Youtube link?

    18:06, 15 January 2019

    1) I'm not familiar with the Template:Set information so I don't know how it gets the skill data.

    2) Use the extension embedVideo. {{#ev:youtube|xx7tna_xoHY|225}}

    However, you cannot put this in the <pre> section of the collapsible tabs. I tested this and would need to place outside the <small> as well.

    {{HiddenTextStart| |Title=Episode 1: The Way of Peace - Linus's Monologue |Width=600 |Show=none }} <!-- Source:http://df.nexon.com/df/guide/TO/634 --> <small><small><pre> Lore info here </pre></small></small> {{#ev:youtube|xx7tna_xoHY|225}} {{HiddenTextEnd}}

    The first parameter is the youtube ID and second parameter is the width in pixels.

      18:28, 15 January 2019

      Ok. Thanks for the reply. :)

        18:31, 15 January 2019

        Hey Dfoplayer. Would you happen to have access to the wiki's LocalSettings.php? There seems to be an issue arising with the 1000 character string limit error. It seems to occur most prominently with the Equipment Infobox description parameter. I believe the culprit may have something to do with the Parser Function $wgPFStringLenghtLimit variable. From what I've researched, it is usually defaulted to 1000 and may be causing certain pages to return an error if the string limit is exceeded. Would it be possible to increase the string limit?

          20:29, 21 February 2019

          No I don't have access to that file.

          The Last time something like this occurred, we had a "Pages with too many expensive parser function calls. " coming from Template:SkillNav calling Template:IconLink too many times. How it was fixed was beyond me.

          Can you give me an example of an equipment page? I looked a recent ones and didn't see 1000 character error.

            21:10, 21 February 2019