Issue: [noparse]

Issue Tools
- View Changes

October 14, 2011 2:28 PM

Lord Doys

Junior Member

[noparse]

The conversion script converted the <nowiki> into [noparse]
but when viewing the templates containing the noparse it does parses the spacial characters:

it makes things kinda unreadable.. any way to avoid this?

{{Tnavbar|{{subst:PAGENAM E}}|mini=1}}
<tt>{{Tnavbar|{{subst:PAG ENAME}}|plain=1}}
{{Tnavbar|{{subst:PAGENAM E}}|mini=1|nodiv=1&#12 5;} {{Tnavbar|{{subst:PAGENAM E}}|plain=1|nodiv=1&#1 25;}
{{Tnavbar|{{subst:PAGENAM E}}|miniv=1}} {{Tnavbar|{{subst:PAGENAM E}}|viewplain=1}}
{{Tnavbar|{{subst:PAGENAM E}}|miniv=1|nodiv=1&#1 25;} {{Tnavbar|{{subst:PAGENAM E}}|viewplain=1|nodiv= 1}}
{{Tnavbar|{{subst:PAGENAM E}}|fontcolor=green}&#12 5;

Issue Details

Issue Number 2505

Issue Type Bug

Project VaultWiki 3.x Series

Category Templates

Status Fixed

Priority 4 - Warnings / Script Errors

Affected Version 3.0.14

Fixed Version 4.0.0 Alpha 1

Milestone (none)

Software DependencyAny

Users able to reproduce bug 0

Users unable to reproduce bug 0

Attachments 0

Assigned Users (none)

Tags (none)

October 17, 2011 3:57 AM

pegasus

VaultWiki Team

I would need to see the raw editor text of the template in question to debug this issue.

Reply

October 17, 2011 8:29 AM

Lord Doys

Junior Member

Code:

[h="2"]Usage[/h]
Copyable examples when inside a given [wiki]template[/wiki] adds Tnavbar navigational functionality:
[noparse]{{Tnavbar|{{subst:PAGENAME}}|mini=1}}[/noparse] 
[noparse]{{Tnavbar|{{subst:PAGENAME}}|plain=1}}[/noparse] 
[noparse]{{Tnavbar|{{subst:PAGENAME}}|mini=1|nodiv=1}}[/noparse]
[noparse]{{Tnavbar|{{subst:PAGENAME}}|plain=1|nodiv=1}}[/noparse] 
[noparse]{{Tnavbar|{{subst:PAGENAME}}|miniv=1}}[/noparse] 
[noparse]{{Tnavbar|{{subst:PAGENAME}}|viewplain=1}}[/noparse] 
[noparse]{{Tnavbar|{{subst:PAGENAME}}|miniv=1|nodiv=1}}[/noparse] 
[noparse]{{Tnavbar|{{subst:PAGENAME}}|viewplain=1|nodiv=1}}[/noparse] 
[noparse]{{Tnavbar|{{subst:PAGENAME}}|fontcolor=green}}[/noparse]

its in the doc description of a template..
actually looking at it, it should have been converted to [template]Tnavbar|[var]PAGENAME[/var]|mini=1[/template

October 17, 2011 3:36 PM

pegasus

VaultWiki Team

It wasn't converted because it was inside <nowiki>, so it gets treated literally.

{{subst: is not handled anyway, because AFAIK, this should have already been replaced by MediaWiki when you first saved it. From Wikipedia:

Originally Posted by http://en.wikipedia.org/wiki/Help:Substitution

Substitution is a function whereby, when an editor saves a page, an item in the wikicode is permanently replaced with its current value.

But MediaWiki doesn't perform substitutions on <nowiki> code, so it's still there.

However, I should be able to duplicate the gibberish output using this code, and will get back to you on the code change to clean it up.

Reply
October 18, 2011 3:04 AM

Lord Doys

Junior Member

yeah dont worry about the substutition, it comes in handy when using boilerplates.. but people tend to copy the format more from similat pages instead of using boilerplates.

but my bigger concerns are still the REDIRECT pages.. none of them have been converted (written lowercase AND uppercase)
.. how to use swtich
I have been trying to look for things on the website, wiki and manual.. but some things are outdated or missing

Reply
October 18, 2011 4:35 AM

pegasus

VaultWiki Team

Check your AdminCP > VaultWiki > Wiki Code Manager, and edit the Redirect row. Make sure it is setup to parse in wiki pages. If not, this was likely the problem and I apologize, as I know how long your pages take to convert.

Reply
October 18, 2011 10:15 AM

Lord Doys

Junior Member

the setting for redirect was set to parse, so that is not the cause of it.
only 1 exists in the redirect list, one that i have fixed myself.

List redirects
Namespace:

Showing 1 results of 1 starting with #1.

View (previous 50) (next 50) (20 | 50 | 100 | 250 | 500).

Obscuring mist → D20:Obscuring Mist (Spell)

Reply
October 24, 2011 5:58 AM

pegasus

VaultWiki Team

Re: opening post

This requires a custom parser when pulling template parts in order to solve properly. Using regular expressions ignores noparse items, and using noparse functions garbles the output as above. Instead, a custom parser needs to be made to use noparse outside meta items, but still show it for meta text, and to encode only the items that are not wrapped in meta tags.

This is solved, but the fix has been applied only to 4.0.0 Alpha 1, since VaultWiki 3 doesn't support extending the parser in any of the ways I have mentioned.

Reply

+ Reply

All times are GMT -4. The time now is 12:28 AM.

This site uses cookies to help personalize content, to tailor your experience, and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.

Learn more… Accept Remind me later

Welcome to VaultWiki.org, home of the wiki add-on for vBulletin and XenForo!

Issue: [noparse]

Issue Tools