• 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
    • Task
    • Maintain Import IDs Beyond Import Completion

    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: Maintain Import IDs Beyond Import Completion

    • Issue Tools
      • View Changes
    1. issueid=3368 October 6, 2013 11:40 AM
      pegasus pegasus is offline
      VaultWiki Team
      Maintain Import IDs Beyond Import Completion

      Currently import IDs are cleared during the last step of an import in order to prevent collisions during future imports. However, it is useful to maintain import IDs in case the same database is imported again at a later time, or if some of the import data is needed for smooth operation of some features (e.g. imported namespaces might behave differently, or we might optimize the node stack handler if a page is known to be not imported, and therefore definitely not triple-stacked.

      Change names of the import fields from things like import_threadid or import_pageid, and put a consistently named importid on every table that might contain importable data during installation.

      Create a separate table for storing import IDs relative to database identifiers:
      Code:
      vw_import
      importid | INT | UNSIGNED | original source ID
      table | STR | target table name
      ident | STR | identifier that VaultWiki can use to uniquely identify different databases. It should not be possible to fully regenerate the database credentials from this identifier, but it should be possible to generate the same identifier whenever the same database is used.
    Issue Details
    Issue Number 3368
    Issue Type Task
    Project VaultWiki 4.x Series
    Category Importing
    Status Completed
    Priority 6 - Dev-Related Tasks
    Target Version 4.0.0 Beta 6
    Resolved Version 4.0.0 Gamma 1
    Milestone VaultWiki 4 Beta X
    Software DependencyAny
    License TypePaid
    Votes to perform 1
    Votes not to perform 0
    Attachments 0
    Assigned Users (none)
    Tags (none)




    1. November 1, 2013 6:15 PM
      Alfa1 Alfa1 is offline
      Distinguished Member
      Is this included in beta 7?
      Reply Reply  
    2. November 2, 2013 2:23 PM
      pegasus pegasus is offline
      VaultWiki Team
      No it's not. This requires a fairly major rework of the import system.
      Reply Reply  
    3. November 2, 2013 2:59 PM
      Alfa1 Alfa1 is offline
      Distinguished Member
      Is this slated for beta 8?
      If its a major rework of the import system then please consider a CLI script similar to this: http://xenforo.com/community/resourc...importer.1397/
      Reply Reply  
    4. November 4, 2013 11:23 AM
      pegasus pegasus is offline
      VaultWiki Team
      The import system as it is currently written should already support CLI with minimal changes to the system. We just haven't written a CLI script to access it yet.

      When I said it's a major rework I simply mean that it requires changes (only a few lines though) to most import classes, and there are quite a few classes.

      I can prioritize this for the next release since there were other issues with the importer that would require importing again.
      Reply Reply  
    5. November 4, 2013 5:57 PM
      Alfa1 Alfa1 is offline
      Distinguished Member
      That would be great. I don't mind bug searching and testing. But it's only possible if the import process can be repeated.
      Reply Reply  
    6. November 17, 2013 4:13 PM
      pegasus pegasus is offline
      VaultWiki Team
      Wanted to comment that as of today the basic system is completed, and that the VW4 importer has been updated to use it. I will probably finish updating the VW3 importer by end of day, and then this issue can be closed.
      Reply Reply  
    7. November 18, 2013 12:04 AM
      pegasus pegasus is offline
      VaultWiki Team
      Completed for the next release.
      Reply Reply  
    8. November 18, 2013 7:45 AM
      Alfa1 Alfa1 is offline
      Distinguished Member
      Great. Please advise how to remove the current data in order to get a clean import. Do I need to uninstall VW? Will that remove all tables?
      Reply Reply  
    9. November 18, 2013 1:13 PM
      pegasus pegasus is offline
      VaultWiki Team
      Uninstall/reinstall is one way. In Beta 7, you can also call the following from a PHP script (usually from inside controller/cp/impex, because it's a protected method):
      Code:
      vw_Hard_Core::controller('CP/Impex')->clear()
      That will delete everything in the wiki except for the default data.
      Once IDs are maintained, we can make a less destructive clear() method.
      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 9:00 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.