I wish I could find a way to replicate this issue (I can't replicate it on a clean install), however, it only started happening on a recent update from 7.7 to 7.8

When navigating to admin/config/people/accounts/display/full

Fatal error: Unsupported operand types in /modules/field_ui/field_ui.admin.inc on line 985

If anyone has a moment to give any thoughts on the issue that would be great.

EDIT: Playing around with this a bit more to source/replicate the issue, I am finding an addition error in dblog:

Notice: Undefined index: token in field_ui_display_overview_form() (line 909 of /modules/field_ui/field_ui.admin.inc). Making me think this is a token issue?

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

catch’s picture

Status: Active » Postponed (maintainer needs more info)

Please list the contrib modules you have installed. Do you know how to use print_r() to debug variables?

pixelsweatshop’s picture

I did a little research on print_r but am still unsure of where/how to use it. however, because I have devel installed, I noticed that I can use kpr($variable)-still unsure of where/how to use it though.

Enabling Devel's Display $page array shows:

Notice: Undefined index: full in /modules/field_ui/field_ui.admin.inc on line 909

The enabled modules are listed below:

addressfield 7.x-1.0-beta2
Administration menu 7.x-3.0-rc1
Autocomplete Deluxe 7.x-1.0-beta5
Backup and Migrate 7.x-2.2
Calendar 7.x-3.x-dev (2011-Aug-06)
Chaos tool suite (ctools) 7.x-1.0-rc1
CKEditor - WYSIWYG HTML editor 7.x-1.3
Comment notify 7.x-1.0-beta2
Context 7.x-3.0-beta2
Date 7.x-2.x-dev (2011-Aug-15)
devel 7.x-1.2
Drupal Commerce 7.x-1.0
Entity API 7.x-1.0-beta10
Field Slideshow 7.x-1.2
Global Redirect 7.x-1.3
Google Analytics 7.x-1.2
Google Analytics Reports 7.x-1.0
Google chart API 7.x-1.1
IMCE 7.x-1.4
Libraries API 7.x-1.0
Link 7.x-1.0-alpha3
logintoboggan 7.x-1.2
oauth 7.x-3.0-alpha1
pathauto 7.x-1.0-rc2
redirect 7.x-1.0-beta3
rules 7.x-2.0-rc1
search_api 7.x-1.0-beta10
simplenews 7.x-1.x-dev (2011-Jun-11)
token 7.x-1.0-beta5
views 7.x-3.0-rc1
views_slideshow 7.x-3.x-dev (2011-Jun-27)
webform 7.x-3.13
xmlsitemap 7.x-2.0-beta3
omega 7.x-3.0

msbrar’s picture

I am getting the same error too by clicking on manage fields in content type. But i get the message only when multilingual support is set to "Enabled with Translation". If i select a different option for my content type, it starts working.

Krusnik02’s picture

Grate! I have the same!!!
When press Manage Fields and anamge field display message from AJAX - Fatal error: Function name must be a string in /home/host3419/public_html/modules/field_ui/field_ui.admin.inc on line 152

Is there is any solution?

DamienMcKenna’s picture

It has been almost year since this was last updated, are you still experiencing this bug?

dddave’s picture

Closing old, stale issues. Re-open if your problem persists.

dddave’s picture

Status: Postponed (maintainer needs more info) » Closed (fixed)
myrto’s picture

i had a similar problem,
i enabled field translation for a content type and then i was getting "Fatal error: Unsupported operand types in /modules/field_ui/field_ui.admin.inc on line 447"
for me the error disappeared after updating internationalization (18n) and Variable modules

thim’s picture

Hi DDave,

I'm also facing this issue again.
I upgraded the Entity API and since then I cannot some of the custom displays.

Fatal error: Unsupported operand types in /www/modules/field_ui/field_ui.admin.inc on line 1025

The function crashes after:
[25-Mar-2013 11:51:04] PHP 8. field_ui_display_overview_form() /www/includes/form.inc:0

What can I do to resolve this or debug this?

Regards,
Tim

dddave’s picture

Sorry thim,

I doubt there is much for us to help you with. This is most likely caused by some module doing something wrong. Make sure your modules are up to date and other than that you might have to go into deeper debugging.

JWSmith’s picture

Version: 7.8 » 7.23
Status: Closed (fixed) » Needs review
FileSize
545 bytes

Pretty sure this last reported error (Comment #10), is a bug in core. Line 1025 of modules/field_ui/field_ui.admin.inc uses an arithmetic operator (+=) when it should be using the string concatenation operator (.=). This is most likely related to PHP 5.4.x, as earlier versions would happily process the += operator with strings. Ran into this myself over the weekend, after moving some DB tables from another location, and trying to adopt the external tables, then clicking on the Manage Fields tab.

From the PHP documentation (http://php.net/manual/en/language.types.string.php):
About a third of the way down in the page, provides this advice:

Useful functions and operators

Strings may be concatenated using the '.' (dot) operator. Note that the '+' (addition) operator will not work for this. See String operators for more information.

Patch provided below.

Status: Needs review » Needs work

The last submitted patch, D7-field_ui-Invalid-Operator-1275900-12.patch, failed testing.

JWSmith’s picture

Ok, looks like my limited trace of the code execution didn't see that this is also sometimes a number and sometimes an array, which would necessitate wrapping it some sort of if {} else {}. I didn't update anything else on the site, but I guess something changed with the server move.

More digging is in order.

harings_rob’s picture

Replacing

$settings += field_info_formatter_settings($formatter_type);

With

$settings .= field_info_formatter_settings($formatter_type);

Removes the error.

Only hides the problem.

Check out commerce_tax module. This is where the issue remains for me

Summit’s picture

Hi,

Thanks for #9, for me the error disappeared after updating internationalization (18n) and Variable modules.
This was the same on my site!

Greetings, Martijn

Summit’s picture

Issue summary: View changes

Added more info.

mhmd’s picture

Issue summary: View changes
FileSize
71.74 KB

I have the same issue and asked in drupal.stackexchange.com

Besides no title and description fields links (edit/delete)

taxonomy errors

reswild’s picture

I had the same issue as #17, and the cause turned out to be a bug in the Commerce Services module. There is a working patch for this in the module issue queue: https://www.drupal.org/node/2024813#comment-7718289

Version: 7.23 » 7.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.