IT works fine to upload files with ampersand in the file proper name to a node with a unmarried image field, but if there are multiple image fields on the node the file uploads and is stored properly, but doesn't brandish in preview or on the node and it throws the error "Discover : Undefined index: display_field in file_field_widget_value() (line 595 of /home/jglynn/public_html/canmorehousing.ca/modules/file/file.field.inc )." when saving the node.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Anonymous's picture

Annotate #i

Anonymous (not verified) Credit Attribution: Bearding commented

squeamish problems. i can get this to neglect with just a unmarried image with '&' in the filename. will play with another characters.

past the time nosotros get to image_style_deliver(), the menu system has messed with the args such that everything afterwards the '&' is gone, so nosotros get all sorts of brokenness from that betoken on.

  • Log in or annals to post comments

Anonymous's picture

Comment #2

Bearding (not verified) Credit Attribution: Anonymous commented

Title: When uploading image files to a node with multiple paradigm fields, file names with ampersand do not display » Uploading a file with '& in the proper name causes failures
Version: seven.9 » viii.x-dev
  • Log in or register to post comments

Anonymous's picture

Annotate #3

Bearding (not verified) Credit Attribution: Anonymous commented

Title: Uploading a file with '& in the name causes failures » Uploading a file with '&' in the name causes failures
  • Log in or register to post comments

Anonymous's picture

Comment #4

Anonymous (not verified) Credit Attribution: Bearding commented

given a path like "sites/default/files/styles/large/public/field/image/hope%26.png", with clean urls enabled, past the fourth dimension this hits php, apache has decoded '%26' to '&', and $_GET['q'] looks like this:

"sites/default/files/styles/large/public/field/epitome/hope"

and we take another $_GET key, '_png'.

which is what is causing this awesome. sooooo, we prolly need to disallow '&', or encode it differently, or something.

  • Log in or register to post comments

webchick's picture

Annotate #five

webchick

Primary language English language

Location Vancouver 🇨🇦

Credit Attribution: webchick commented

Looks like a legit problems, but I'yard not sure that it's a big plenty deal to cake D8 features. There's no data loss occurring.

  • Log in or register to post comments

swentel's picture

Weird, I've tried to reproduce this (single and multiple images), but tin can't.

Screen Shot 2012-01-31 at 15.33.32.png

  • Log in or register to post comments

Cottser's picture

Comment #8

Cottser

Primary language English

Credit Attribution: Cottser commented

@swentel - I wasn't able to reproduce, just I only tested a single image in a single image field (based on the study from the closed issue mentioned in #half-dozen).

  • Log in or register to mail service comments

webchick's picture

Comment #9

webchick

Primary language English

Location Vancouver 🇨🇦

Credit Attribution: webchick commented

Status: Agile » Postponed (maintainer needs more info)

Sounds like we need more info. It's possible this is an environs issue?

  • Log in or register to post comments

Cottser's picture

I had a take chances to test again, wasn't able to reproduce.

This is all on the article content blazon on a fresh install of 7.12.

  1. Single field with single ampersand epitome
  2. Two fields with ampersand images on both
  3. One field with multiple ampersand images

And several combinations of the in a higher place. More info indeed.

  • Log in or register to post comments

Anonymous's picture

Annotate #11

Anonymous (not verified) Credit Attribution: Anonymous commented

Status: Postponed (maintainer needs more than info) » Needs review
File Size
wtf-lol-d7.patch ane.87 KB

FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch wtf-lol-d7.patch. Unable to use patch. See the log in the details link for more than information. View
wtf-lol.patch 1.93 KB

PASSED: [[SimpleTest]]: [MySQL] 34,084 pass(es). View
lolz.png 160.42 KB

no. no. no. this is hands reproducible.

checkout this patch for drupal 7 and drupal 8, and the attached screenshots.

so, they should pass. for lolz, see how this is cleaved, just all green.

  • Log in or register to postal service comments

rooby's picture

Using D7.14:

I take a site that pull images in via feeds imagegrabber and information technology had pulled in an image with an ampersand in the file name, which on the staging server (Ubuntu, Apache ii, PHP 5.2) seemed to work fine.

When I pushed it up to the alive server today (Windows, IIS vii, PHP 5.ii) and prototype way images for the file weren't being generated as it was trying to hit an image style path that stopped where the ampersand was in the original file name.
- I can't access the site from where I am now so i can't give the exact watchdog messages.

  • Log in or register to mail comments
Status: Needs review » Needs piece of work

The final submitted patch, wtf-lol-d7.patch, failed testing.

  • Log in or register to postal service comments

RaulMuroc's picture

Version: 8.x-dev » seven.x-dev
Status: Needs work » Active
  • Log in or register to post comments

marcingy's picture

Version: vii.x-dev » 8.x-dev
Condition: Active » Needs piece of work

Reseting version issues are fixed in head first.

  • Log in or register to post comments

j0rd's picture

I have a trouble with ampersand in the image proper noun and derivative cosmos via image styles.

Image is uploaded fine, merely unable to create image style.

Here's the filename:

                LLpidgeon&Handstandsplit.jpg

Here's the prototype style path from the browser

                /sites/default/files/styles/gallery_thumbnail/public/LLpidgeon%26Handstandsplit.jpg?itok=s4mfd5tX

Get this mistake

                Unable to generate the derived image located at public://styles/gallery_thumbnail/public/LLpidgeon.
  • Log in or register to mail service comments
Version: viii.i.x-dev » eight.2.x-dev

Drupal viii.1.9 was released on September 7 and is the last bugfix release for the Drupal 8.1.x serial. Drupal eight.one.x will not receive any further evolution aside from security fixes. Drupal 8.ii.0-rc1 is now available and sites should ready to upgrade to eight.2.0.

Issues reports should be targeted against the eight.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the viii.three.x-dev branch. For more than data see the Drupal 8 small version schedule and the Allowed changes during the Drupal eight release cycle.

  • Log in or register to post comments
Version: 8.two.x-dev » 8.three.x-dev

Drupal 8.ii.6 was released on Feb 1, 2017 and is the terminal full bugfix release for the Drupal 8.2.x series. Drupal 8.two.10 will not receive any farther development aside from disquisitional and security fixes. Sites should prepare to update to 8.three.0 on April v, 2017. (Drupal 8.three.0-alpha1 is bachelor for testing.)

Issues reports should be targeted confronting the 8.three.x-dev co-operative from now on, and new development or disruptive changes should be targeted confronting the 8.four.x-dev branch. For more data meet the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

  • Log in or register to post comments
Version: 8.three.x-dev » 8.four.x-dev

Drupal 8.3.6 was released on August two, 2017 and is the final full bugfix release for the Drupal eight.3.ten series. Drupal 8.3.10 volition not receive any further evolution aside from critical and security fixes. Sites should prepare to update to 8.4.0 on Oct four, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Problems reports should exist targeted against the viii.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.five.x-dev co-operative. For more information run into the Drupal 8 minor version schedule and the Allowed changes during the Drupal eight release cycle.

  • Log in or annals to post comments
Version: 8.4.x-dev » 8.5.x-dev

Drupal viii.4.four was released on January 3, 2018 and is the final full bugfix release for the Drupal viii.iv.10 series. Drupal 8.4.x will not receive whatever farther development bated from critical and security fixes. Sites should set up to update to 8.5.0 on March 7, 2018. (Drupal eight.5.0-alpha1 is bachelor for testing.)

Bug reports should be targeted against the 8.v.x-dev co-operative from at present on, and new evolution or disruptive changes should be targeted confronting the eight.6.x-dev branch. For more information see the Drupal 8 pocket-size version schedule and the Immune changes during the Drupal viii release cycle.

  • Log in or register to post comments
Version: viii.5.x-dev » 8.6.x-dev

Drupal 8.5.half-dozen was released on Baronial one, 2018 and is the final bugfix release for the Drupal viii.5.10 series. Drupal 8.5.10 will not receive any further evolution aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal viii.half-dozen.0-rc1 is available for testing.)

Issues reports should be targeted confronting the 8.half-dozen.x-dev branch from now on, and new development or confusing changes should be targeted against the viii.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Immune changes during the Drupal 8 release cycle.

  • Log in or register to mail service comments

kim.pepper's picture

Outcome summary: View changes
Status: Needs piece of work » Closed (outdated)

Closing every bit outdated. Please re-open if this is still relevant.

  • Log in or register to mail comments

minnur's picture

Annotate #24

minnur Credit Attribution: minnur as a volunteer commented

This is still happening in the latest D8 and D9. The site is on Pantheon.

  • Log in or register to mail comments