Drupal.org Excerpt:
Change the content type of your posts while editing them. [More...]
Details:
| Maintainer: | kkaefer |
| Links: | |
| Categories: | Administration, Developer, Utility |
Ratings
| Attribute | Average |
|---|---|
| Features | 3.5 / 5 |
| Reliability | 4.5 / 5 |
| Ease Of Use | 4.5 / 5 |
| Documentation | 3 / 5 |
| Vote Count | 2 |
Module Overview
Downloads
| Version | Date | Files | Release notes |
|---|---|---|---|
| 6.x-1.0 | 2008-Mar-23 | Download | Recommended for 6.x |
| 5.x-1.0 | 2008-Mar-23 | Download | Recommended for 5.x |
Total Downloads: 68 "Development" releases should be considered in beta.
Options: Add a review
One Caveat
I had a forum that I wanted to remove, but I wanted to save the threads as nodes of another type. So I used nodetype.module to change the type, and it worked great... BUT...
When I went to delete the forum, I got a warning (from the forum module) that said, "Deleting a forum ... will delete all ... associated posts as well."
No problem, I thought, as I had changed the type of all the posts and the forum now appeared empty. So I clicked "Delete" and was horrified to see that all the posts were deleted even though I had changed their type!
The cause of the problem: the forum module doesn't check the node type when deleting nodes associated with a deleted forum -- it only looks at the nodes' taxonomy. (Each forum uses a specific taxonomy term.) The forum module "believed" the nodes were still forum nodes, even though I changed the type, because I didn't think to change the taxonomy.
Oops!
Nodetype is really handy...
I had two content types that, over time, became nearly indistinguishable (much like story and page have in Drupal) - in fact, it was becoming a nuisance to have both.
But what to do - re-entering all that data to get rid of one type isn't realistic... Nodetype to the rescue!
This module is really simple - it adds a "Change Node Type" select widget to the node-edit form. Edit the node, select a new type, save. That's it.
My two node types had an identical structure, but they were complex CCK types with image, node reference, and other fields. Nodetype moved all the data over perfectly.
The module installed easily, has no configuration (other than permissions), and worked exactly as advertised without requiring a shred of documentation. However, I don't know what it would do with fields that did not match across the source and destination types - so a little documentation would be useful for other use-cases. Also, I wouldn't recommend allowing end-users to access this module - I imagine you could create a world of hurt if you didn't know what you were doing.
I have ranked the features rather low because I think there is potential here to add a bunch more useful stuff. It would be nice to be able to do bulk operations through the content admin panel, or to be able to change all nodes of one type to another. Dialing through every node-edit screen beats the heck out of re-entering data, but still sucks. That said, it does the job it was built for very nicely - saved me a bunch of time... which I've now squandered writing this review ;-)
Module Tools
Search Modules
User login
Most Downloaded
Sponsored By
Latest Reviews
Node Blocks
"Very simple. After installing the module: 1) Create a new Content Type called "Node Block" with nodeblock..."
FCKeditor - WYSIWYG HTML editor
"I have tried TinyMCE and now FCKeditor and I must say that this one is better. Some bugs but quick response..."
Node Radioactivity
"Radioactivity might be a bit hard to configure due a variety of settings and options but there's a pot..."