Yes, if both sites are on the same server. Choose \"Another WordPress install on this server\" and enter the path to that site's WordPress folder (the one containing wp-config.php<\/code>). The migrator reads that site's database connection details from wp-config.php<\/code>, connects to its database to read packages only, and copies the files. The connection details are used only during the request and are never stored, logged or sent to the browser.<\/p><\/dd>\nSome files were skipped. Why?<\/h3><\/dt>\nThe dry run gives a reason for every skipped file: usually the file is missing from disk, or its type is not allowed in DocVault. Files that DocVault Pro could accept are listed separately.<\/p><\/dd>\n
My site has very large files. Will the migration time out?<\/h3><\/dt>\nThe migrator works in small batches and ends each batch early once it has run for 20 seconds (less if your server's PHP time limit is lower), then continues in the next request. A single file still has to be copied in one request, so a very large file on a server with a very short time limit can still time out; in that case, ask your host to raise the PHP time limit for the migration.<\/p><\/dd>\n
Can I try it on a few items first?<\/h3><\/dt>\nYes. On the Configure step, enter a number under Test run<\/strong> to migrate only the first files that are ready to migrate (oldest first; files that cannot be migrated are skipped and do not count). Check the result, then roll the test back before migrating everything, otherwise those files are migrated twice.<\/p><\/dd>\nCan I undo a migration?<\/h3><\/dt>\nYes. The final step has a rollback button that deletes the documents and files the migration created. Once no migrated documents of a source plugin are left, it also deletes the empty categories the migration created and the information DocVault used to keep that plugin's old links working. Categories that already existed are kept. Rollback uses the migration log, so keep the migrator installed until you are happy with the result.<\/p><\/dd>\n
What happens if I run the migration twice?<\/h3><\/dt>\nEach run creates new documents, so running it twice creates duplicates. Roll back the first run before running it again.<\/p><\/dd>\n
Are access restrictions kept?<\/h3><\/dt>\nYes. Public and logged-in-only settings are kept. Role restrictions are kept and enforced by free DocVault; viewing or changing the roles in the document editor needs DocVault Pro.<\/p><\/dd>\n
Can I delete the migrator afterwards?<\/h3><\/dt>\nYes. Deleting it removes its own settings and log. The documents stay, and so does the source information DocVault uses to keep old links working.<\/p><\/dd>\n
Who can run a migration?<\/h3><\/dt>\nAdministrators only (the manage_options<\/code> capability).<\/p><\/dd>\n\n<\/dl>\n\n\n1.11.2<\/h4>\n\n\n- Change: the notices shown when Trilobita DocVault is missing or too old now appear only on the Plugins screen, and the one-time access-repair notice can be dismissed.<\/li>\n<\/ul>\n\n
1.11.1<\/h4>\n\n\n- Change: \"Tested up to\" is declared in the readme only, as WordPress.org requires.<\/li>\n<\/ul>\n\n
1.11.0<\/h4>\n\n\n- New: a notice on the migrator page when Trilobita DocVault is older than 1.6.0, explaining that old links start working once DocVault is updated.<\/li>\n
- Security: source file paths can no longer point outside the WordPress Download Manager upload folder.<\/li>\n
- Security: the table prefix read from another site's wp-config.php is validated before use.<\/li>\n
- Fix: malformed data in the source database can no longer stop a preview or migration.<\/li>\n
- New: records the rules Trilobita DocVault 1.6.0 needs to keep old WordPress Download Manager shortcodes and URLs working. Sites migrated with 1.10.0 to 1.10.2 get them automatically on update.<\/li>\n
- New: asks for confirmation before migrating from a second site of the same plugin, because old links from two sites can collide.<\/li>\n
- New: WordPress Download Manager tags are migrated, and old tag shortcodes and tag pages keep working.<\/li>\n
- New: test run. Migrate only the first few files that are ready to migrate, check the result, roll it back, then migrate everything.<\/li>\n
- New: rollback also removes the categories the migration created (if empty) and the information DocVault used to keep the old links working, so the site is back to how it was before the migration.<\/li>\n
- Change: batches end early when a package has very large files, so a migration no longer risks a PHP timeout on shared hosting.<\/li>\n
- Change: documents are no longer added to an existing category that holds other content, such as blog posts. A separate \"(documents)\" category is created instead, and the preview tells you which.<\/li>\n
- Change: requires WordPress 6.5 or later.<\/li>\n
- Removed: WP Filebase support and the Filebase References page. WP Filebase has not been maintained for years.<\/li>\n
- Change: code tidy-ups for WordPress.org.<\/li>\n
- Fix: all admin messages can now be translated.<\/li>\n<\/ul>\n\n
1.10.2<\/h4>\n\n\n- Security: package data read from the source database can no longer create PHP objects.<\/li>\n<\/ul>\n\n
1.10.1<\/h4>\n\n\n- New: categories record their original slug, so DocVault can redirect old category URLs.<\/li>\n<\/ul>\n\n
1.10.0<\/h4>\n\n\n- New: every migrated document and category records its source, so Trilobita DocVault can keep old links, shortcodes and URLs working.<\/li>\n
- Fix: categories were not migrated on sites where DocVault uses the standard post categories.<\/li>\n
- Fix: \"first file only\" migrations recorded incomplete log entries.<\/li>\n
- Fix: Filebase References could match documents migrated from WordPress Download Manager.<\/li>\n
- Change: DocVault Pro is no longer required. The dry run shows which skipped file types Pro can add.<\/li>\n<\/ul>\n\n
1.9.11<\/h4>\n\n\n- Fix: role restrictions from WordPress Download Manager are now saved correctly. Documents migrated with earlier versions are repaired automatically.<\/li>\n<\/ul>","raw_excerpt":"Import documents from WordPress Download Manager into Trilobita DocVault and keep old links working. Preview everything in a dry run first.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/391957","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=391957"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/trilobita"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=391957"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=391957"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=391957"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=391957"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=391957"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=391957"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}