Update to 6.x-2.10 caused links to ... disappear [#1924904]

Hi,

I just updated the Link module from 6.x-2.9 to 6.x-2.10 and now the link fields have disappeared from my Drupal (6.28) instance. In the Dev environment, content types that utilize the Link module cause the page to crash (i.e., 500 error). In the Test environment, the links just do not appear. (I hadn't realized the Link update was what was causing errors in my Dev env but now that I've updated Test, a pattern has emerged.)

There are no errors or warnings, just ... nothingness. I wish I could provide more detail but that's all I got. I'd appreciate any advice or guidance on how to proceed. In the meantime, I'll be reverting to a backup of 6.x-2.9.

Thanks!

Comments

Comment #1

markfullmer commented 1 April 2013 at 21:15

Had the exact same problem. But it only happened for some content types with link fields

The problem was caused by two factors working in combination. If...
1) The URL Display Cutoff: field was blank
and
2) The variable being called in our template file was $node->field_image_link_link[0]['display_url'] (instead of $item['url'] or $fields['field_xxx']->content; )

The links would be truncated into ellipses (...)

The fix:
Make sure the URL Display Cutoff: field is not blank.

Home › Administer › Content management › your content type

Comment #2

byronveale commented 3 April 2013 at 18:20

I'm having this problem, and I've got an entry in the URL Display Cutoff field already. See also this issue:

http://drupal.org/node/1920004

Comment #3

byronveale commented 3 April 2013 at 18:31

Tried the 6.x-2.x-dev version, problem seems to be fixed.

Perhaps patch from http://drupal.org/node/1920004#comment-7132968 was implemented?

Thanks to all involved!

Comment #4

byronveale commented 4 April 2013 at 14:45

One more note: checking another site, it was using the "fixed" dev version of link, but was still getting the php error "call_user_func_array() expects parameter 1 to be a valid callback..." and the link fields were not visible. At first, I thought the problem still remained; then I cleared all caches. No more problem...