• 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 4.x Series
    • Feature
    • Node History

    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: Node History

    • Issue Tools
      • View Changes
    1. issueid=2408 July 18, 2011 12:29 AM
      pegasus pegasus is offline
      VaultWiki Team
      Node History

      Currently we only have history for page content and attachment association with pages.

      It would also be beneficial to have history for other non-page nodes:
      • In case we change their titles or prefixes before expanding them as pages
      • In the case of books, in case we reorder the chapters or add/remove some chapters. Since this particular case would have a two-way effect on many child nodes, perhaps its best not to allow automated reversion, but instead just show highlight the changes in a comparison.
      • In case we want to review other associations historically, like groups, books, or language
    Issue Details
    Issue Number 2408
    Issue Type Feature
    Project VaultWiki 4.x Series
    Category History / Revisions
    Status Closed (Merged)
    Priority 8 - Major Features / Enhancements
    Suggested Version 4.0.0 Alpha 1
    Implemented Version 4.0.0 Alpha 1
    Milestone VaultWiki 4 Alpha X
    Software DependencyAny
    License TypePaid
    Votes for this feature 0
    Votes against this feature 0
    Attachments 0
    Assigned Users (none)
    Tags (none)




    1. March 14, 2012 1:01 AM
      pegasus pegasus is offline
      VaultWiki Team
      Moved up to Alpha 1 because doing so any later would require us to create all content again. Instead of every node getting a page later, all nodes get a page automatically. Further, only pages and unpageable nodes get URLs, so we can avoid the node-page URL conflict false positive, as well as the easily mismatches with category/group/book membership. Further, this relationship would allow us to have Book-ness or Category-ness as combinable add-ons to a page, though I don't personally see the point.

      Not doing this and moving forward with the current Alpha 1 data management scheme would actually be a feature reversion since we already track title edits for Books and Categories, and leaving this until later would remove that ability.

      Unfortunately this will be a slight setback since most content nodes will have to be reworked around the page node rather than all being separate entities, and all the spots that utilize them may need to be updated. I can't see this rework taking more than a few days to a week, however.

      That said, I don't recommend starting on this until we have finished the other tests, templates, and plugins possible, since making this change will require a dev environment backup restore.
      Reply Reply  
    2. March 22, 2012 5:57 PM
      pegasus pegasus is offline
      VaultWiki Team
      Okay updated most of the DMs and other code. Still need to handle existing custom area paths (paths are now attached to the page node), creating the missing area page nodes on import, and the updates to the page creation UI.

      With respect to my earlier assumption about combining Book/Category, etc, I don't think this will be possible (at least outright), since the permissions for each type are separate for now and are probably better that way.

      On the same note, I think it would be best to have an error message if combining Island with Category or Template, since Category and Template wouldn't be able to do anything in an Island.
      Reply Reply  
    3. March 23, 2012 6:57 AM
      pegasus pegasus is offline
      VaultWiki Team
      Things got complicated:

      An Area requires a page node to be created, but likewise a page node requires an area to be created in.

      This added 3 more steps to the upgrade process now that pages are required for all routable nodes (we originally wrote VaultWiki 4 with them optional).
      Reply Reply  
    4. March 23, 2012 11:22 PM
      pegasus pegasus is offline
      VaultWiki Team
      Counter updates had to be almost completely rewritten to support the change. Needed to add a new node-type field to identify child node-types (Chapters to Books, Members to Categories, Group Pages to Groups).

      Also added the page DM as an internal DM to the attach and area DMs, since those nodes need to have IDs first. Other node types like books and categories are internal to the page DM since they don't really need anything extra at creation time.

      Still some other things to round out before closing this issue and re-installing: the interface changes, and external URL validation for old main pages.
      Reply Reply  
    5. March 24, 2012 6:28 AM
      pegasus pegasus is offline
      VaultWiki Team
      Closing this issue. Fix up the editor when we debug the Edit tab.
      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 8:14 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.