This project is not covered by Drupal’s security advisory policy.
*** Warning ***
Please only use this if you can read code. I'm not completely ready to release this yet.
Taxonomy and Node truncate deletes data by bundles. Entity truncating will delete everything in that table. Also if you export and check 'export ids' then add new content to the Taxonomy, Node or Entity it will not import the data. You will get duplicate id error.
Quickly export and import Content Types, Entities and Taxonomy terms from one site to another.
*** Supports these Entity Reference Fields ***
Users - uid
Taxonomies - tid
Content - nid
Will be adding bundles to entities soon. Working on the refresh of the Page Layouts module and I'm pretty sure I will be using entity bundles for new blocks so unique fields can be applied.
When exporting data if you export with the entity id, nid or tid you will have to truncate the database for the entity, content type or taxonomy. Added exception handling there so no errors if you forget to check the truncate checkbox.
Allows the user to import and export entities, content types or taxonomy terms.
It creates the temp folder and also a folder called easy_content in public://easy_content in sites/default/files.
Each content type is built as a separate plugin with one function named content that return the array of RowResults.
Comes with an example custom module called ct_backups.
ct_backups
Put the example module in the modules/custom folder.
Change the file named 'ct_backups.info.yml.example' to 'ct_backups.info.yml'.
When you export the content the plugins will be saved to the sites/default/files/easy_content folder.
Copy the classes it makes into the src/Plugin/EasyContent folder in the custom module.
Clear the cache and visit the Configuration->Development->Easy Import page.
You can create any name you like for the custom module as long as the Plugin folder structure remains the same.
Project information
- Project categories: Developer tools, Import and export, Integrations
- Created by trigve hagen on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
