When creating a action page as Staff role, uploaded jpg via the Attachments dialogue on /node/add/take-action. (Cursor in Plea field)
Went to "add another" to attach a text file and upon hitting the button got this error:

* warning: Parameter 2 to date_form_alter() expected to be a reference, value given in /var/lib/hudson/jobs/watershednow/workspace/drupal/includes/common.inc on line 2883.
* warning: Parameter 2 to date_timezone_form_alter() expected to be a reference, value given in /var/lib/hudson/jobs/watershednow/workspace/drupal/includes/common.inc on line 2883.
* warning: Parameter 2 to signup_form_alter() expected to be a reference, value given in /var/lib/hudson/jobs/watershednow/workspace/drupal/includes/common.inc on line 2883.
* warning: Parameter 2 to taxonomy_image_form_alter() expected to be a reference, value given in /var/lib/hudson/jobs/watershednow/workspace/drupal/includes/common.inc on line 2883.
* warning: Parameter 2 to wysiwyg_form_alter() expected to be a reference, value given in /var/lib/hudson/jobs/watershednow/workspace/drupal/includes/common.inc on line 2883.
* warning: Parameter 2 to wysiwyg_imagefield_form_alter() expected to be a reference, value given in /var/lib/hudson/jobs/watershednow/workspace/drupal/includes/common.inc on line 2883.
* warning: Parameter 2 to wn_map_form_alter() expected to be a reference, value given in /var/lib/hudson/jobs/watershednow/workspace/drupal/includes/common.inc on line 2883.
* warning: Parameter 2 to comment_notify_form_alter() expected to be a reference, value given in /var/lib/hudson/jobs/watershednow/workspace/drupal/includes/common.inc on line 2883.

CommentFileSizeAuthor
#14 fileuploaderror.png134.51 KBskjalf
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

seanberto’s picture

Huh. I can't replicate this. It's possible that it is/was a caching issue. Could you try again? Could you also try to replicate with a different content type?

Oh, and what browser are you using? Might be applicable since it's an AJAX callback.

skjalf’s picture

Also got this same error as Staff adding an image to node/add/event.

skjalf’s picture

This happened in FF-- my Chrome is slow today for some reason

skjalf’s picture

Update: Did NOT get this error in Chrome (on Event and Take Action creation), only FF (3.6.7)

seanberto’s picture

Huh. I'm not getting it in FF 3.6 for Mac. Could you try a few more browser combinations? Thanks for helping me track this down. And just to double check, this is only when you try to add more than one attachment at a time? If you add one attachment, save the node, and then try again, I wonder what happens.

skjalf’s picture

OK, was able to replicate again upon node creation in FF, Chrome, and Safari. However, you're right--I can edit an existing node and happily upload as many files as I want with no problem. Error seems to occur on node creation (doesn't seem to matter what content type).

Steps: Create a new node. Upload a file in Attachments. Once the first file is uploaded, hit "add another" for the error.

seanberto’s picture

Assigned: Unassigned » robbieferrero

Still can't replicate this. I'm passing over to Robbie for testing on a PC.

seanberto’s picture

Robbie. please close if you can't replicate.

seanberto’s picture

Just tested in IE as well. I can't replicate this.

robbieferrero’s picture

Tested on windows 7 in both IE8 and Firefox and Chrome, when I click Add Another Item I get:

warning: array_merge_recursive() [function.array-merge-recursive]: recursion detected in D:\dev\watershednow\drupal\sites\all\modules\contrib\cck\includes\content.node_form.inc on line 364.

This occurs before I attempt to browse/upload the new item. This also occurs after I've submitted the node and gone back to edit it.

seanberto’s picture

Assigned: robbieferrero » seanberto

Yeah. I just saw this. This has got to be filefield sources fault. I'll take this one on.

seanberto’s picture

Component: Code » QA
Assigned: seanberto » skjalf
Priority: Normal » Major

More info on this. Now that I've removed FF sources, on a clean install I'm not getting this. I'm passing this over to Sarah for more complete testing.

seanberto’s picture

Title: Reference error when trying to "add another" attachment in /node/add/take-action » Test field attachments on all content types
skjalf’s picture

Assigned: skjalf » seanberto
FileSize
134.51 KB

I got this again. It happens reliably when I take the following steps:

1) Create content of some kind. In content creation page,
2) Upload one file under attachments
3) Hit "add another" and the error immediately appears

It doesn't seem to happen if a node with an existing attachment is being edited and another attachment added.

I'm gonna run updates to see if it's anything weird on my end... screenshot attached

seanberto’s picture

Status: Active » Closed (won't fix)

As much as I hate to admit it, I'm going to mark this issue as wontfix. It's not affecting the actual saving of data. If I turn off errors on the screen, it just racks up silent errors in the logs. Blah.

TheDoctor’s picture

What OS & PHP version is being used? I'm getting the same error msg on Ubuntu Server 10.04LTS w/ PHP 5.3.2-1ubuntu4.5. gateway69 reports similar issue & yosisays states downgrading to PHP 5.2 solved it, although their issue was due to different modules. See http://drupal.org/node/892676 . http://drupal.org/node/705512 might be related. What little I understand seems to indicate PHP 5.3 is interpreting certain modules differently than 5.2, but I've yet to personally test this.

(Forgive me if I'm way off mark; still learning)

Kev’s picture

Status: Closed (won't fix) » Active

Hi folks,

I could reproduce this warning message with Drupal 6.19 after an upgrade of PHP from 5.2 to 5.3 on gentoo. (Chromium & Firefox on client)

After adding an attachment on an article, I get:

warning: Parameter 2 to wysiwyg_form_alter() expected to be a reference, value given in /var/www/[...]/includes/common.inc on line 2883.

The only installed modules are Content Access, Mass Contact and Wysiwig.

I re-opened this ticket because:

1st: php-5.3 will be more common in these days as more and more distributions are releasing it as stable to replace 5.2. More and more users will get this warning and will be confused about it. This should be fixed.

2nd: as far as I can the devs/people who failed to reproduce it did not take an 5.3 issue into consideration.

Kind regards,

Kev

seanberto’s picture

Status: Active » Closed (won't fix)

Hi Kev and TheDoctor, these errors are against contrib modules (WYSIWYG Imagefield being the most likely culprit) that are used in this Drupal distro, not the distro itself. It'd be great if you could move this issue to that queue.

Cheers,
Sean

mvc’s picture

seanberto’s picture

There was no date field on this content type, so I don't think that this last comment is applicable.

If you are not testing against the Watershed Now distribution and it's combination of modules and content types, please do not comment on tickets in this queue. Sorry, but it muddies the water.