I just upgraded from rc7 to rc10, and it is looking grim.

If I click manage fields for, say, page, it takes me to
/admin/content/node-type/page/fields, but it shows me the same edit page that I see at
http://cse.localhost/admin/content/node-type/page
I don't see the new "add field" or "add group" controls.
I still have an "Add Group" tab at the top of the page, but going there generates an error:
Call to undefined function _content_admin_display_contexts() in ...\fieldgroup.module on line 160

I will try the dev and see if it is an better.

Comments

starbow’s picture

starbow commented
Title: Unsuccessful upgrade to rc10 » Unsuccessful upgrade to rc10 (finger pointing at fieldgroup)

Upgrade to dev, ran update.php

Going to /admin/content/node-type/page/fields

Fatal error: Call to undefined function fieldgroup_types() in C:\Program Files\xampp\htdocs\citris6\sites\all\modules\contrib\cck\includes\content.admin.inc on line 140

Turned off fieldgroups module
Yay, I see the mange fields page.

So maybe it is all a fieldgroup issue?

karens’s picture

karens commented
Status: Active » Postponed (maintainer needs more info)

I can't replicate the problem, but update to the latest -dev code and try the update again. I've been doing some more tweaking of the upgrade process since rc10.

karens’s picture

karens commented

Also you should definitely not see the Add Group tab after the update, the tab is gone. Maybe we need to add a menu_rebuild() to the update. Let me know if you see that in the latest code.

karens’s picture

karens commented

Looking at your error messages, 'Call to undefined function _content_admin_display_contexts() in ...\fieldgroup.module on line 160' makes no sense in either -dev or rc10, there is no such thing at that line in the fieldgroup module. In fact, I cannot find any place that _content_admin_display_contexts() is used at all in the fieldgroup module in either -dev or rc10.

And your other error message 'Fatal error: Call to undefined function fieldgroup_types() in C:\Program Files\xampp\htdocs\citris6\sites\all\modules\contrib\cck\includes\content.admin.inc on line 140' -- that function definitely does exist in the fieldgroup module, and that line has if (module_exists('fieldgroup')) right before it, so there is no way you should see an error like that.

It sounds like you don't have the right code or that you have old versions somewhere else that you system is trying to use.

starbow’s picture

starbow commented

Very mysterious.
I downloaded the 10/14 dev, and you are right about the if(module_exists), and the "fieldgroup_groups" call does not trigger an error. But "fieldgroup_types" still does. I can see the function in the fieldgroup.module.

Ah, ok. I deleted the entire cck directory, then installed the dev tarball. Now it is working. I guess just installing the tarball over the older version left some cruft behind.

karens’s picture

karens commented
Status: Postponed (maintainer needs more info) » Fixed

There were no changes in files or file positions between rc7 and rc10. Files *were* moved around between rc6 and rc7, and then there were a number of changes to the fieldgroup module after rc7, so maybe you still had the old files in the wrong places in rc7, but things didn't start acting up until we made changes to the fieldgroup module after that.

Anyway, it sounds like this is fixed.

berenErchamion’s picture

berenErchamion commented

I get the same error using the latest dev code:

Fatal error: Call to undefined function fieldgroup_types() in C:\apache\htdocs\drupal\modules\cck\includes\content.admin.inc on line 140

I'm running D6.5 with everything up to date.

beren

yched’s picture

yched commented

Give a closer look at the end of comment #5 above :
You probably have some leftover files from a previous CCK version. Delete your cck folder and replace it with the content of the downloaded tarball.

berenErchamion’s picture

berenErchamion commented

hey thanks alot! That definitely worked. I missed that comment.

beren

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.