Plugin Contributor
dvkob
(@dvkob)
vincentweb: Yep, post type selection has been moved to the csv file from the interface. Still have to update that screenshot…
Last time I checked WordPress did not support tags for pages.
Is possible create one to support page tag?
Last issue, about the page, could import to subpage?
For example, domain.com/main-page/sub-page.
Plugin Contributor
dvkob
(@dvkob)
vincentweb: If you think you need tags for pages, you’re probably doing something wrong.
As of the current version, it’s not possible to import a sub-page.
Hi,
Thank you anyways! : )
I think you could made it better!
Especially for the basis, like parent, update existing and token…
Thank once again!
This plugin does exactly what I need, except for being able to set the parent page for importing Pages (rather than posts). I have 600 pages I need to import, all with different parents. I don’t want to have to set the parent pages on all of those by hand… 🙁
Guys, should donate to dvkob if you found it is useful. : )
Plugin Contributor
dvkob
(@dvkob)
mike62: A similar request/question comes up from time to time on the forums, but nobody has explained to me yet the rationale behind importing 600 pages. Pages are for static content, such “About” or “Contact” pages. Why do you think you need to import 600 pages?
I’m actually building a custom directory of store names and addresses. All the directory plugins I’ve seen do not have any import at all, and no one wants to copy/paste 600 addresses. So I’m going to use custom fields, etc, to display posts and sort them by country/province/city. In thinking of it more I’ll likely use categories for these locations, and parent them accordingly, and let users drill down.
Unless anyone knows of a better way to do this…! :S
Plugin Contributor
dvkob
(@dvkob)
mike62: Based on what you describe, I agree that it’s probably a better idea to create the directory using categories and posts (or custom taxonomies and custom post types) instead of creating a tree of pages.
