im having a big issue here. everytime i upload picture. that messge came up on the top of the page..you can see this error at my site (http://www.postbuddies.com/

also when i tried to put url image on moviedb.it doesnt show anything.i think its something to do with image file or somthing.

here is the full error messge im getting on the front page of my site

warning: Parameter 1 to image_display() expected to be a reference, value given in C:\server\xampp\htdocs\includes\module.inc on line 462.

even though i checked that error is on that line and i got that on 462 line

return call_user_func_array($function, $args);

i dont know wat im doing wrong and wat i missed. any help?

CommentFileSizeAuthor
#3 image.display-reference.3.patch648 bytessun
error msge.jpg68.57 KBmusicster
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

joachim’s picture

joachim CreditAttribution: joachim commented
Status: Active » Postponed (maintainer needs more info)

Line 462 seems to be within module_invoke.

Which is pretty weird, as image_display() is not a hook.

Are you using any modules which depend on image? Are any of those trying to call image_display() as a hook?

Tauntuan1980’s picture

Tauntuan1980 CreditAttribution: Tauntuan1980 commented

I am having the same issue. The only thing I am using that depends on Image is Image Upload. I get the follow errors when I initially attach the image as well:

* warning: Parameter 2 to og_form_alter() expected to be a reference, value given in /usr/share/drupal6/includes/common.inc on line 2839.
* warning: Parameter 2 to taxonomy_batch_operations_form_alter() expected to be a reference, value given in /usr/share/drupal6/includes/common.inc on line 2839.
* warning: Parameter 2 to upload_image_form_alter() expected to be a reference, value given in /usr/share/drupal6/includes/common.inc on line 2839.
* warning: Parameter 2 to user_relationship_mailer_form_alter() expected to be a reference, value given in /usr/share/drupal6/includes/common.inc on line 2839.
* warning: Parameter 2 to og_access_form_alter() expected to be a reference, value given in /usr/share/drupal6/includes/common.inc on line 2839.
* warning: Parameter 2 to notifications_content_form_alter() expected to be a reference, value given in /usr/share/drupal6/includes/common.inc on line 2839.

Then I get the Parameter 1 to image_display error once I publish, and my attached photo is gone.

Any help would be great.

sun’s picture

sun
Primary language German
Location Karlsruhe
CreditAttribution: sun commented
Component: views support » image.module
Category: support » bug
Status: Postponed (maintainer needs more info) » Needs review
FileSize
image.display-reference.3.patch648 bytes

Anyway, I don't see a reason why $node should be taken by reference in the first place here.

tax15’s picture

tax15 CreditAttribution: tax15 commented

I am using Drupal 6.20 and the patch mentioned by 'sun' already exists in the image module.
I am still getting the following error:

warning: Parameter 1 to image_display() expected to be a reference, value given in C:\xampp\htdocs\drupal620\includes\module.inc on line 462.

Any suggestion?

joachim’s picture

joachim CreditAttribution: joachim commented

> I am using Drupal 6.20 and the patch mentioned by 'sun' already exists in the image module.

It doesn't. It currently passes by reference.

ossama.selim’s picture

ossama.selim CreditAttribution: ossama.selim commented

doesn't work for me!!

ossama.selim’s picture

ossama.selim CreditAttribution: ossama.selim commented

Try to remove & from image.modules at in this code:"

function image_display(&$node, $label = IMAGE_PREVIEW, $attributes = array()) {
  if (empty($node->images[$label])) {
    return;
  }

"
it works for me!

joachim’s picture

joachim CreditAttribution: joachim commented
Issue summary: View changes
Status: Needs review » Fixed

Fixed.

  • joachim committed 74eed6c on 6.x-1.x authored by sun 
    Issue #921412 by sun: Removed referenced $node parameter to...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.