When updating to the newest version of Common Functionality (cf) (7.x-1.x-dev, 2012-May-05), upon running update.php I encountered this nasty error:

Fatal error: Call to undefined function cf_error_append_history() in /home/account/public_html/drupal/sites/all/modules/cck_accessibility/cck_accessibility.module on line 84

Comments

thekevinday’s picture

I suppose I enjoy shooting myself in the foot...

What version were you using prior to updating the cf module?

While I investigate this, could you try out the 7.x-1.x-dev of the cck module?
I just made the development snapshot for cck_accessibility available for download.

thekevinday’s picture

Status: Active » Closed (won't fix)

Okay, I think I identified the problem.

It seems that drupals development/versioning/snapshot system seems to be making a mistake.
It is creating the 7.x-1.x-dev snapshot from master instead of the 7.x-1.x branch.
As a result, it is pulling in the 7.x-2.x version.

So in reality, 7.x-1.x-dev is in fact 7.x-2.x-dev.

You should be using the 7.x-1.5 version of cf as it should work fine.
If using the stable 7.x-1.5 produces the same problem, let me know.

You should be able to use the git commands to get the proper 7.x-1.x-dev branch as describe here: http://drupal.org/node/990562/git-instructions/7.x-1.x .

I really want to close this as "can't fix". but there is no such state.

thekevinday’s picture

Project: CCK Accessibility » Common Functionality
Version: 7.x-1.0 » 7.x-1.5
Assigned: Unassigned » thekevinday
Status: Closed (won't fix) » Active

Okay.
Its not just specific to the 7.x-1.x-dev branch, when the 7.x-1.5 was created, somehow the drupal package system pulled from master and completely ignore the 7.x-1.5 tag.

I am going to first assume I did something weird in the git repository and try to figure out what I did and find a way to fix it.

Pending that, I will report a bug on the drupal website packaging system (as soon as I find the correct terminology/name to search for and report for).

thekevinday’s picture

Status: Active » Fixed

As far as I can tell, moving 7.x-1.x onto master and making a new release 7.x-1.6 against the master branch seems to have solved the problem.

Re-open this issue if the 7.x-1.6 version has the same problem as 7.x-1.5.

Status: Fixed » Closed (fixed)

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