A whole bunch of errors...

[Jaxel]

For a short while, I even got this error on a category page, which is really problematic. On many of my pages, I am getting the following error:

The page cannot be displayed because the requested offset is too high.

Clicking on a SECTION EDIT link on this page, brings up a BLANK text box. (in both the ajax and non-ajax version) If I type anything in the text box and click submit, it adds whatever I typed to the TOP of the page. As well, if I click undo on this new edit, I get an error saying the edit doesn't exist.

http://www.8wayrun.com/wiki2/Algol_-_Frame_Data_-_Soulcalibur_IV

The powered by link is WAY too intrusive. How can I edit it to make it fit into my skin better? Right now it breaks the footer on many of my skins. As well, the powered by link for VaultWiki should NOT show up on every page... it should only show up on Wiki pages. The fact that it shows up on EVERY page makes me wonder how much extra processing time this mod will add to my forums.

Posting an article/category/anything on a Wiki forum will return a FATAL ERROR if you have ANY plugin based bb codes. Many mods use these plugin based bb codes. For some reason Vault Wiki is polling the "bbcode_fetch_tags" plugin more than once... this is a bug that I'm amazed hasn't been discovered yet. If you disable all plugin based bb codes on your forum (and I mean ALL), the wiki will work... however that reduces the functionality of MANY other mods.

Can't use smilies in articles/categories/templates. I figured this was a built in feature!

There are no real MAIN PAGES with this wiki

I am using a parser function that can have both numbers and words. With MediaWiki, I have different cases for >0, <0 ==0 and then false for all, which is what words should be. However, in VaultWiki, all words are considered >0, instead of being read as not a number. There needs to be a way to handle less than 0, greater than 0, equal to 0, and not a number.

can't decrease the size of tab links in the css

[pegasus]

The offset error should be fixed in the next build of Categories, which will be posted tomorrow.
The parser word > 0 is fixed in the next build of Parser Extensions, which will also be posted tomorrow.

I have discussed your smilies and fatal error issues in the other threads you posted. I also explained how to redirect your users to a main, main page in your other thread.

Because different browsers will break the layout if the CSS isn't exactly a certain way, we have not added any easy way to modify the dimensions of the tab itself. You should still be able to modify the font-size of p-text.

Your section edit issue is discussed here: http://www.vaultwiki.org/issues/813/
Your CSS saving issue is discussed here: http://www.vaultwiki.org/issues/812/

[Jaxel]

New issues with the parser functions...

In addition to the words being taken as > 0...

If I have "hit=0", instead of "hit = 0" (notice the lack of spaces), it will return a FALSE, instead of the character 0. So when I use {{{hit}}} it returns a null, instead of returning the character "0"

As well, both >0 and <0 become true if the value is not 0.

[pegasus]

Please post the entire code you are attempting to do this in.

[Jaxel]

Callup from an article...

[template]framesROW|atk=Chertan Aladlar|cmd=:A:|lvl=:H:|dmg=0|imp=14|grd=-4|hit=0|cnt=4|scr=(?)|nts=[/template]

Contents of Template:framesROW

[table]
|-
| class="alt2" style="white-space:nowrap" | <small>{{{atk}}}</small>
| class="alt2" style="white-space:nowrap" | <small>{{{cmd}}}</small>
| class="alt2" style="white-space:nowrap" | <small>{{{lvl}}}</small>
| class="alt2" style="white-space:nowrap" | <small>{{{imp}}}</small>
| class="alt2" style="white-space:nowrap" | <small>{{{dmg}}}</small>
| style="color:#000000; background-color:#[if={{{grd}}}==0]CCFFCC[else /][if={{{grd}}}>0]CCCCFF[else /][if={{{grd}}}<0]FFCCCC[else /]FFFFCC[/if]" | <small>{{{grd}}}</small>
| style="color:#000000; background-color:#[if={{{hit}}}==0]CCFFCC[else /][if={{{hit}}}>0]CCCCFF[else /][if={{{hit}}}<0]FFCCCC[else /]FFFFCC[/if]" | <small>{{{hit}}}</small>
| style="color:#000000; background-color:#[if={{{cnt}}}==0]CCFFCC[else /][if={{{cnt}}}>0]CCCCFF[else /][if={{{cnt}}}<0]FFCCCC[else /]FFFFCC[/if]" | <small>{{{cnt}}}</small>
| class="alt2" | <small>{{{scr}}}</small>
| class="alt2" align="right" | <small>[if="{{{nts}}}"]{{{nts}}}[else /]-[/if]</small>
[/table]

You can see several errors if you run this template...

1. dmg=0 - the 0 won't show up, it will just return an empty table cell.

2. grd=-4 - instead of it returning "FFCCCC", it will instead return "[if=-4==0]CCFFCC[else /][if=-4&amp;gt". This same error will come up in with both the hit and cnt fields.

3. change hit=0 to hit=KND - it will assume KND is > 0, instead of it running to the final else.