Part three turns the spreadsheet into published nodes, and shows how to send them into a content type you built yourself rather than the one the module ships.
The import screen, field by field
Enable pb_import_node and the form appears at /admin/content/paragraphs/pb-import-node. Four inputs, and only two of them are guesses:
- CSV File — required, the file built in part two.
- Image Folder Relative Path — optional, and left empty for a text-only run.
- Content Type — a text field pre-filled with
pb_import_node. - Vocabulary Name — also pre-filled with
pb_import_node, and it takes a machine name.
Press Import and rows become nodes, with terms created in that vocabulary as they are encountered.
Pointing it at your own content type
Both text fields exist so you can override them, and the form's own help says what the contract is: a different content type must carry the same field names as the one shipped here. That means three fields — pb_import_node_image for the picture, pb_import_node_body for formatted long text, and pb_import_node_tag for the taxonomy reference. Name them anything else and the importer has nowhere to write.
The simplest honest route is to install the module's content type first, look at how those three fields are configured, and mirror that on yours.
When a row does not land
Rows are processed with error tracking rather than one fatal stop, so a bad row is reported while the rest continue. The two usual causes are a picture that was never registered in part one, and a file name whose capitalisation differs from the CSV cell.
The importer needs the administer site configuration permission and is built for ^11.3 || ^12. Confirm that against your site on the Paragraphs Bundles Import module page, then carry on to part four for slideshows, accordions and tabs.
Need this built into your own site? See Drupal development services, or request a quote.
