No terms when upgrading from 6.x-1.0-beta1 to beta2

oh, I think I forgot to clear the cache in the update 6001...

no, cache has been cleared (automatically when update.php is executed).

has the update 6001 from content_taxonomy been executed?

Can you provide further information?
Or can someone confirm an upgrade without problems?

Hi,

I got the same issue, before running update.php, and ... and update.php didn't solve the issue.

My findings : In Global Settings,

1) Vocabulary is kept OK
2) Parent Term is lost (--- instead) if existed previously, and if it didn't existed it doesn' work as well.

Thank you

EDIT : I tried to upload beta1 (after update.php), but it still doesn't work [and I do not want to lose my data]

EDIT : I tried to upload beta1 (after update.php), but it still doesn't work [and I do not want to lose my data]

beta1 definitely doesn't work after running updates from beta2.
I think you can temporarily fix the problem by re-saving the fields on the cck admin pages.
I'm still working on this issue to find the problem, on my drupal installation the update was successful.

I found the problems, update 6000 and 6001 were incompatible with each other.
On my private drupal installation I executed the 6000 update first, made code changes and executed 6001 afterwards, so the problem wasn't occurring.

The fix has been committed and I will tag it as beta3 immediately.

For people who have already executed both updates:
Because of the problems, the parent setting has been destroyed. Beta3 will fix that, but if you have selected a parent term in the settings, this configuration is lost! You have to re-set this setting again manually. Sorry for causing this problem.. :(

Hi,

I tried this : update.php 6002 only from beta1 to beta3 (without 6000 and 6001).

I still lose my Parent Term in my field configuration, but views are ok. ... oh oh ??

Could you explain what we must do in order to go from from beta1 to beta3 ?

Thank you

update 6000: port from 5.x to 6.x -> not necessary for you and was causing the problems (but fixed)
update 6001: necessary to update the parent settings for beta2 and higher -> needs to be executed
update 6002: fixes problems introduced by beta2

I recommend you executing 6001 and 6002. In case you are running 6000, it shouldn't cause any problems now.
Remember that the parent setting might have been lost with beta2 and is set to 0. In case of a direct upgrade from beta1 to beta3 everything should work fine with the updates.

I hope this information is clear for you and you get for fields working again. Otherwise just ask :)

Fine, Thanks.

I did update.php 6001 from beta1 to beta3, and it run also and 6002.

I get all Parent Terms in my field configuration and in my views.

I just lost one among tens of my display setting (back to Above instead of inline). Strange :-) Had anyone the same behaviour ?

Thank you for this great module.

EDIT : I tried this on another server and i have the same problem with only one display [ I just lost one among tens of my display setting (back to Above instead of inline). Strange :-) Had anyone the same behaviour ? ]

Hi,
In my case, with drupal 6.4 and cck 6.x-2.0-rc6, upgrading from Content Taxonomy 6.x-1.0-beta1 to 6.x-1.0-beta3 broke edition of all my taxonomy (not content_taxonomy) fields (multiple select). After upgrade, all the select widget to choose my terms aren't displayed when editing nodes.

upgrade 6000 throws a lot of :
array_merge() [function.array-merge]: Argument #2 is not an array in /path2mydrupal/sites/all/modules/cck/content.install on line 29.
and my cck/content.install contains :
$db_result = db_query("SELECT * FROM {". content_instance_tablename() ."} nfi ".
" LEFT JOIN {". content_field_tablename() ."} nf ON nf.field_name = nfi.field_name");
while ($row = db_fetch_array($db_result)) {
$field = array_merge($row, unserialize($row['global_settings'])); // line 29

If I skip upgrade 6000 (just 6001 & 6002), all seems OK.

(FYI, I never used drupal 5 but I started this mysql database with a drupal 6.1 install and early cck-6.x-2 & early content_taxonomy-6.x-1.x-dev, around april/may)

[edit sept 13th 2008] : the pb of hidden taxo edition was caused by, after upgrade, in advanced settings of my content_taxonomy field, "Hide default taxonomy fields on the node form" was checked (I don't understand how).

I mark this issue as fixed, because no one is going to update from beta1 to beta2 any more and updates from beta1 to beta3 or beta4 are working.