Closed (fixed)
Project:
Drupal core
Version:
5.7
Component:
node system
Priority:
Critical
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
11 Apr 2008 at 15:32 UTC
Updated:
26 Dec 2008 at 15:42 UTC
warning: call_user_func_array(): First argumented is expected to be a valid callback, 'flexinode-1_node_form' was given in /var/www/html/kb/includes/form.inc on line 218.
Comments
Comment #1
adkatrit commentedComment #2
miurahr commentedSame here.
I hava caught same situation.
Version: 6.3
warning: call_user_func_array(): First argumented is expected to be a valid callback, 'flexinode-1_node_form' was given in /var/www/drupal/includes/form.inc on line 359.
I have updated from 4.7 + flexinode and privacy_by_role module.
As first step, I update database with 5.9 version using update.php, then goto 6.3 version.
after that, I access admin/content/node-settings and order 'rebuild role access'.
After rebuilding, above message is displayed when trying to edit.
Also, almost all access restriction is broken.
Comment #3
miurahr commentedIt is likely occured by 'the node which is unexisted content type'.
I have 2 site and both make similar error.
One is the node which is user defined type but after migrating, its type may be removed automatically.
Other is the node which is a calendar data, third party module on 4.7 version.
Farmer is like a bug for migration logic. Because user defined type is a core feature of Drupal.
Comment #4
yareckon commentedI believe that the reason that a lot of access control is broken in your new site is that many of the access control names have changed and your permissions based on these names may not be checked. I would log in as the uid=1 user and add back in your checkboxes.
However, I do see the same errors on a 4.6 / civicspace site that I am currently upgrading when I click on edit on the events content type. Currently am looking for a good way to fix this.
Comment #5
yareckon commentedended up using flexiconvert to migrate my content after the upgrade, may or may not work for other types of errors.
Comment #6
ainigma32 commentedJudging from the age of the original post and the fact that the other problems seem to be solved this issue seems resolved.
Setting to fixed.
Feel free to reopen if you think that is wrong.
- Arie