• Register
    • Help

    striker  0 Items
    Currently Supporting
    • Home
    • News
    • Forum
    • Wiki
    • Support
      • Manage Subscriptions
      • FAQ
      • Support For
        • VaultWiki 4.x Series
        • VaultWiki.org Site
    • What's New?
    • Buy Now
    • Manual
    • 
    • Support
    • VaultWiki 3.x Series
    • Bug
    • Legacy Headlines Cause Editor Mismatch

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

      VaultWiki allows your existing forum users to collaborate on creating and managing a site's content pages. VaultWiki is a fully-featured and fully-supported wiki solution for vBulletin and XenForo.

      The VaultWiki Team encourages you to join our community of forum administrators and check out VaultWiki for yourself.

    Issue: Legacy Headlines Cause Editor Mismatch

    • Issue Tools
      • View Changes
    1. issueid=2086 November 16, 2010 1:58 PM
      pegasus pegasus is offline
      VaultWiki Team
      Legacy Headlines Cause Editor Mismatch

      When an article contains headlines written using legacy code like:
      Code:
      === Headline ===
      [h3]Headline[/h]
      Then a conversion takes place before locating them which is likely to change the length of the article and cause the editor to display only parts of the text that it should.
    Issue Details
    Issue Number 2086
    Issue Type Bug
    Project VaultWiki 3.x Series
    Category Headlines / Sections
    Status Fixed
    Priority 4 - Warnings / Script Errors
    Affected Version 3.0.5
    Fixed Version 3.0.6
    Milestone (none)
    Software DependencyAny
    Users able to reproduce bug 0
    Users unable to reproduce bug 0
    Attachments 0
    Assigned Users (none)
    Tags (none)




    1. November 16, 2010 2:54 PM
      pegasus pegasus is offline
      VaultWiki Team
      Fixed for the next build. When in a Fake parse, headlines will not be converted. Every other legacy tag will not convert, but will run noparse on its contents. Since doing so would also make H=1 tags unable to re-nest on a fake parse, but still able to in a regular parse, regularly parsed legacy tags add noedit around their contents to prevent a mismatch in that way.
      Reply Reply  
    + Reply

    Assigned Users
    Loading Please Wait
    Tags
    Loading Please Wait
    • Contact Us
    • License Agreement
    • Privacy
    • Terms
    • Top
    All times are GMT -4. The time now is 7:59 PM.
    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
  • striker
    Powered by vBulletin® Version 4.2.5 Beta 2
    Copyright © 2023 vBulletin Solutions Inc. All rights reserved.
    Search Engine Optimisation provided by DragonByte SEO (Pro) - vBulletin Mods & Addons Copyright © 2023 DragonByte Technologies Ltd.
    Copyright © 2008 - 2013 VaultWiki Team, Cracked Egg Studios, LLC.