Closed (fixed)
Project:
Drupal core
Version:
7.17
Component:
field system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Feb 2011 at 04:34 UTC
Updated:
30 Nov 2012 at 14:43 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
bfroehle commentedAre you using any contributed modules which provide additional field types?
Can you provide the steps needed to reproduce this?
Comment #2
htalwala commentedI am using the Links module and the Scheduler module. I think this error started happening after I installed the Field Permissions module, but I removed it, and I am still getting this error.
This error happens when I create a new field for a content type, and then go to the field display section and try to move that new field into the hidden section.
Comment #3
andrebonfanti commentedI am getting the same error too, but it happens when I try to click the field gear icon in the "manage display" form of my custom content type. I'm trying to configure an image field to be a "thumbnail" in teaser display, while the default is "original". The error is the same:
An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: /?q=system/ajax
StatusText: OK
ResponseText:
Fatal error: Function name must be a string in /home/(my domain)/public_html/modules/field_ui/field_ui.admin.inc on line 143
The error happens even if I try to drag field to hidden section, as for htalwala.
My content type has only the default "body" field and an "image" field.
I have installed other modules which provide fields ("term reference", "node reference"), but the error was there before. I changed the admin theme from Seven to Bartik but the error remains.
In my logs I find these two errors:
Error 1:
Error 2:
Thank you for any suggestion.
Comment #4
yched commentedsubscribe for now
Comment #5
andrebonfanti commentedupdate: my error has gone for the moment in the content type "manage display" page.
I do not remember the steps I took. I managed to move fields by toggling the "show/hide row weight" option at the top and moving by editing weights (the toggle hides the drag-n-drop handles, so I think the page disable ajax, but I'm not sure).
I disabled the Dhtml menu module, too, which I used to avoid page reload. I'm not sure this caused the issue because a similar error appears when I try to fill the autocomplete field of the state/province Location module.
(UPDATE: the error does not show any more in autocomplete Location module)
I'll let you know if I remember other steps I took.
Comment #6
jibberish commentedSubscribe.
I'm getting the same error.
I try to change a content type and manage the display and I get this:
Error:
An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: /drupal7/system/ajax
StatusText: OK
ResponseText:
Fatal error: Function name must be a string in c:\wamp\www\drupal7\modules\field_ui\field_ui.admin.inc on line 143
I'm really not sure what I've changed, but everything had been working perfectly for some time.
Cheers
Jibb
Comment #7
htalwala commentedIt seems to be the fields permissions module itself that is creating the error. If you install it, you will no longer be able to hide fields using the original fields interface, you will have to do it through the field permissions module. Even if you uninstall the module, you will still get the error.
Comment #8
adriansky commentedI solved disabling the modele: Drupal for Firebug.
Comment #9
gerhardbaumeister commentedsubscribe
Comment #10
jibberish commentedThere seem to be lots of references to this problem, but I can't find a solution anywhere.
Comment #11
yched commentedI have no clue what might happen here. It is probabaly caused by malformed "rows" in the form array describing the "Manage display" table. Off hand, I don't see how this could be related to the field_permissions module.
The attached debug patch should provide additional info to help us have a clearer notion about which module is at fault. To anyone facing the bug : please apply the patch and post the debug info here (might be reasonably large, please post in an attached .txt file).
Note : the patch will "hide" the bug but won't fix it. I don't recommend saving actual changes to your "Manage fields" forms with the patch applied.
Comment #12
jibberish commentedHi yched
First off - thanks very much for the reply.
I'm running on WAMP and don't have access to Linux / UNIX at the moment. You wouldn't happen to have a pre-patched version of the file you could share for Windows would you? I know what CYGWIN is, but I've never used it.
Also - how do you invoke the debug mode?
Thanks in advance.
Cheers
Jibb
Comment #13
yched commented@jibberish: you can easily apply the patch manually. Edit the modules/field_ui/field_ui.admin.inc file, and within the field_ui_table_pre_render() function, delete the lines marked with a '-', add the lines marked with '+'.
Comment #14
jibberish commented@yched: I can manipulate image settings again now! Where do I find the log files? Is this in reports > Recent log messages
Comment #15
jibberish commented@yched: I'm going to assume that this is the location of the logs and there are 3 logs written each time I try to update an image:
Log 1
Log 2
Log 3
Comment #16
yched commentedOk, so in your case this is caused by the captcha module. I'll investigate.
For others : please post the debug messages in an attached txt file ;-)
Comment #17
jibberish commented@yched
Thanks very much for the time you've put into this. You are absolutely right.
Test 1
Restore original field_ui.admin.inc and disable captcha
Result
All working
Test 2
Upgrage to captcha 7.x-1.0-alpha2 and enable captcha
Result
Fail
So - I had a little look around the Captcha options and found another test to try:
Test 3
Disabled "Add CAPTCHA administration links to forms" checkbox from withing configuration > captcha
Result
All working
I now have a fully working site. You are my hero!!!! Thanks very much!!!!
As a side note - I have a backup of the site with all the same modules but a with slightly older content types and content with that captcha option still on and everything works in there. If that hadn't been the case, I would've tried disabling captcha - but it worked on an old backup.
Thanks once again for helping me (and hopefully others) here....I really was starting to go a bit insane and lose all motivation.
Jibb
Comment #18
yched commentedCreated #1121264: Breaks Field UI's "Manage display" page. in the Captcha issue queue.
Closing this thread as a duplicate.
If other people encouter the bug without having the captcha module enabled, please reopen and provide the debug info described in comment #11 above.
Comment #19
ericxb commentedI can confirm a similar problem fixed by disabling "Drupal for Firebug."
In my case, I was trying to reveal hidden fields for the teaser display and received a fatal ajax error.
Comment #20
andrebonfanti commented#17 worked for me
Disabled "Add CAPTCHA administration links to forms" checkbox from withing configuration > people > captcha > general settings.
thanks
Comment #21
jghyde commentedThis error also occurs with the module http://drupal.org/project/memcache installed on Drupal 7 (I am using Drupal 7.3-dev and memcache 7.x-).
It appears that memcache is not storing the form, or the forms token (?) and the $_POST data is empty, firing off the
watchdog('ajax', 'Invalid form POST data.', array(), WATCHDOG_WARNING);.The returned error is that ^^ above in watchdog. I opened an issue is the memcache module queue #1214536: Drupal 7 content-type fields_ui module ajax forms not getting cached
Comment #22
Anonymous (not verified) commentedI have the same issue and I don't use the CAPTCHA module...
This error message only appears when Link module or Address Field module are enabled (both or separately).
Someone can help me to fix that?
Thank you in advance.
Comment #23
nebel54Hi laurent, i am having the same issues (same debug output) on drupal 7.17 since yesterday. Your directory structure suggests that you are using barracuda/octopus, is that right?
Comment #24
nebel54@laurent, if you are using barracuda/octopus: I just found out that there seem to be some cache related issues: Could you try to disable caching, through creating the file sites/all/modules/cache/NO.txt in your platform and check if the problem still appears? That did help in my case.
Comment #25
Anonymous (not verified) commentedTotally right, I'm using BOA-2.0.4 stable.
Comment #26
Anonymous (not verified) commentedIssue solved! You saved my life :)
But, I guess cache is now disabled... Did you found a real fix?
Comment #27
swentel commentedSo since this is related to barracuda/octopus, not core's fault then, I'd suggest opening an issue in that project.
Comment #28
muschpusch commentedFor reference: #1854926: field_ui error: Function name must be a string
Comment #29
omega8cc commentedIn the BOA context it is a duplicate of #1839122: Disabling Redis on known AJAX calls breaks AJAX based UI elements