• 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
    • Max versus Current Revision

    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: Max versus Current Revision

    • Issue Tools
      • View Changes
    1. issueid=281 October 12, 2008 3:32 PM
      pegasus pegasus is offline
      VaultWiki Team
      Max versus Current Revision
      Contradiction thanks to moderated edits

      Here's the situation. The current revision is defined as the most recent revision that has been approved. The "Next Revision" links when comparing or viewing revisions use the current revision value to determine when NOT to create a link.

      Since a revision needing approval occurs after the current revision it would not be possible to reach that revision using the "Next revision" link.

      In addition, if the revision ID is known, we could view the revision needing approval in these contexts. However, because it is not the current revision, a "Next revision" link would be present, even though no later revision exists.

      To solve these issues, a distinction needs to be made between the MAX revision and the CURRENT revision. Also, the "Next revision" link would have to consider moderation/editor permissions when the MAX revision requires approval. Rather than pulling just a single record containing MIN and MAX values, we probably have to pull the whole table, and cycle through to get the MIN, MAX, and CURRENT values.
    Issue Details
    Issue Number 281
    Issue Type Bug
    Project VaultWiki 3.x Series
    Category History / Revisions
    Status Fixed
    Priority 3 - Loss of Functionality
    Affected Version 2.1.1
    Fixed Version 2.1.2
    Milestone (none)
    Software DependencyAny
    Users able to reproduce bug 0
    Users unable to reproduce bug 0
    Attachments 0
    Assigned Users (none)
    Tags (none)




    1. October 16, 2008 1:08 PM
      pegasus pegasus is offline
      VaultWiki Team
      Okay, I think everything has been adjusted so I'm marking this as Fixed.
      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 5:56 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
  • 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.