Posted by robby.smith on February 27, 2010 at 12:58am
12 followers
Jump to:
| Project: | Content Taxonomy |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Hello,
I was wondering if there will be a way to convert all Content Taxonomy fields to the Druapl 7 structure of taxonomy as fields when upgrading from Drupal 6 to Drupal 7. I am asking because on the project page it says this module will not be ported so I am not sure that means my site in Drupal 6 with many Content Taxonomy fields won't be able to upgrade to Drupal 7 =(
Thank you and I look forward to learning more.
Comments
#1
subscribing
#2
It should be pretty simple to port the fields to D7, because the data structure is very similar. We can check how core ports CCK to the new Field API to reuse the code, but as far as I know no upgrade path exists until now.
Nevertheless, if we directly upgrade to core Taxonomy Fields we loose the advanced options Content Taxonomy offered (like setting the parent, depth, autocomplete settings,...). So I think we need some kind of extension, which is going to be much more simpler than the existing Content Taxonomy, but I don't have any plans yet.
#3
Tracking.
#4
tracking 2...
#5
sub
#6
Subscribe
#7
Hmm it looks like somewhere between D7 beta 3 and the current Dev version, someone must have built in an upgrade path for content taxonomy.
My most recent upgrade attempt automatically converted my content taxonomy fields to term reference fields for all of my content types. While it did rename my fields' names to taxonomy_vocabulary_1, taxonomy_vocabulary_2, etc, it did keep the labels the same. Overall it seems to work though.
*Update* With further tests I have found out that only the content taxonomy that is checked with "Save values additionally to the core taxonomy system (into the 'term_node' table" are actually converted over in the upgrade. If the "Save values" is not checked, the content is not converted. Content migrate may be able to convert these but a upgrade path for those type of content taxonomy will probably be required.
#8
for a simple update procedure we could sync the field values with the term_node table first (for fields without "Save values...") and then re-use D7's upgrade path.
this would be easy to implement. on the downside we end up with different fields and lose all content taxonomy field options...
#9
subscribe
#10
subscribe
#11
#12
Subscribing
#13
KarenS has been putting together a great content migrate module with hooks for other cck modules here: #781088: Updating CCK Fields and Data from D6 to D7.
Maybe content taxonomy can take advantage of some of those hooks to build a faster upgrade path?
#14
Thanks for this hint. I used CCK's Content Migrate module for upgrading email fields and it did a good job. I hope this module helps here as well.
#15
a basic upgrade path from D6 to D7 taxonomy term reference fields has been implemented.
please download the d7 version of content taxonomy and read the upgrade instructions on the project page.
#16
Automatically closed -- issue fixed for 2 weeks with no activity.