Compatibility with Display Suite [#1616426]

Problem/Motivation

An error occurs when this module is used in combination with Display Suite's core fields (like node Post Date). It's down to the fact that these DS fields are not fully conformant to Field API. For a detailed analysis see the related issues in Display Suite.

Proposed resolution

#1875634: Remove Field Formatter Class settings in uninstall
Cleaning up this module's settings on uninstall would at least allow recovery from the situation described in Comment #5.
The rest is best fixed in Display Suite project. Track the related issues for Display Suite.
Potentially affects all modules using Field Formatter Settings API in combination with Display Suite.
If no satisfactory resolution in Display Suite, consider adding some workaround code for DS core fields.
For a possible approach, see the workaround (hacky) in Field Formatter Conditions

#1875634: Remove Field Formatter Class settings in uninstall
#1875750: Allow DS core fields to have alterable settings, include them in field_info_instance_settings()
#1900014: Field formatter settings summary alter implementations choke on DS Pseudo fields

Original report by marcorai

I install your module and it works for my objectives, but i had these error messages:

Notice: Undefined index: title in field_formatter_class_formatter_info() (linea 68 di /sites/all/modules/field_formatter_class/field_formatter_class.module).
Notice: Undefined index: post_date in field_formatter_class_formatter_info() (linea 68 di /sites/all/modules/field_formatter_class/field_formatter_class.module).

How can I fix it?

Comment	File	Size	Author
#13	My_field formatter class issue.png	73 KB	Gyver06

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

andrewmacpherson CreditAttribution: andrewmacpherson commented 28 June 2012 at 21:53

Thanks for the error report Marco. Sorry I haven't looked at it in detail yet.

Comment #2

fraweg CreditAttribution: fraweg commented 25 July 2012 at 23:08

Hello,

I have the same issue.. Have anyone solve this ?

Best regards
Frank

Comment #3

thoka CreditAttribution: thoka commented 3 October 2012 at 16:25

Same issue here. Has anybody got a grip on the issue?

Comment #4

marcorai CreditAttribution: marcorai commented 8 November 2012 at 09:57

Just some more details.

By the module, I assigned a custom class at the title field and i have the error.
So i have removed that class, ma the error is still there.

Comment #5

Mark LaCroix CreditAttribution: Mark LaCroix commented 19 December 2012 at 16:38

I have the same problem.

The problem first started when I moved a field which had a custom class on it into a Display Suite block region. The sad irony is that I only moved that particular field into that region as a quick test of DS's "Region to Block" functionality. I never meant to keep it there... :'-(

Worse even is the fact that I can't uninstall the module. I can disable it, but when I try to uninstall it, while it is removed from the uninstall list, it remains in the module list. If I reactivate it, my previous data returns (along with the error), so whatever borked it up hasn't been cleared from the database. My next step is to manually remove the module from both the server and the database, I suppose, but I'd rather not have to do that.

Interestingly, whatever the problem is, it hasn't impacted functionality, and it only shows up the second time a browser loads a page on the site. Clearing the browser's cache give you one error free page load. :-)

I'm sure there's a simple solution, but it's driving me crazy right now. This is a great module, I can't wait to get it working again. Thank you for any help you can provide.

Comment #6

markhalliwell

English

CreditAttribution: markhalliwell commented 28 December 2012 at 18:30

This seems to be an issue only when core Display Suite fields are involved, referencing #1875750: Allow DS core fields to have alterable settings, include them in field_info_instance_settings().

Comment #7

Gyver06 CreditAttribution: Gyver06 commented 23 January 2013 at 18:22

I am having the same behaviour. Any patch ?

Comment #8

fraweg CreditAttribution: fraweg commented 23 January 2013 at 20:05

Hi,

no for me there is no solution to solve this.. :-(

Best regards
Frank

Comment #9

Gyver06 CreditAttribution: Gyver06 commented 23 January 2013 at 22:13

OK, Thanks for the info.
I have de installed Field Formatter Class. Maybe someone find a solution in a near future.

Best regards
Eric.

Comment #10

wooody CreditAttribution: wooody commented 1 February 2013 at 09:40

Any help to fix the problem... I made views as block and I use the block with display suite.. and the problem from that field..

Comment #11

wooody CreditAttribution: wooody commented 1 February 2013 at 09:59

I fixed it.. I just change the field Entities to Taxonomy Term and its work fine now..
BR,

Comment #12

wooody CreditAttribution: wooody commented 7 February 2013 at 12:12

a lot of problems... I think better to use CSS Class with Display Suite
CSS classes for regions
CSS classes for fields

Comment #13

Gyver06 CreditAttribution: Gyver06 commented 11 February 2013 at 20:43

File	Size
My_field formatter class issue.png	73 KB

If that can help to fix the issue, here enclosed is a screen capture with more infos.
Please, any help is welcome.

Comment #14

andrewmacpherson CreditAttribution: andrewmacpherson commented 15 February 2013 at 11:39

Title:	Undefined index	» Better integration with Display Suite
Priority:	Normal	» Major
Status:	Active	» Postponed

I've updated the issue summary to reference the Display Suite problems. Thanks to everyone who has provided additional information about this problem.

I'll also add a note on the main project page to highlight this issue.

Marking as postponed, because the solution is being explored in Display Suite project.

Comment #15

andrewmacpherson CreditAttribution: andrewmacpherson commented 15 February 2013 at 11:45

Title:

Better integration with Display Suite

» Compatibility with Display Suite

Comment #16

andrewmacpherson CreditAttribution: andrewmacpherson commented 15 February 2013 at 15:28

#1875634: Remove Field Formatter Class settings in uninstall - Fixed in 7..x-1.x-dev

The settings for this module are now removed when uninstalling the module.

Comment #16.0

andrewmacpherson CreditAttribution: andrewmacpherson commented 15 February 2013 at 15:28

Issue summary:

View changes

Major update to issue summary, using issue template.

Comment #17

mansspams CreditAttribution: mansspams commented 12 May 2013 at 12:41

Please see #1992948: Make DS leaner by outsourcing field formatting features as it could be related and could serve as higher level initiative for good changes.

Comment #18

fraweg CreditAttribution: fraweg commented 16 April 2014 at 14:45

Hello,

does the #16 patch also get in the stable version?

Best regards
Frank

Comment #19

andrewmacpherson CreditAttribution: andrewmacpherson commented 28 April 2014 at 18:38

@fraweg: Hi Frank. Yes, kind of. There isn't actually a patch on comment #16. It's a link to an improvement which partially helps with this problem. It was included in the 7.x-1.1 stable release.