We found one participant being confused by the fact that you can upload only one image by default. Although that's obviously not a significant data point, we felt it was just a weird default anyway.

Although this was a limit we set initially for the Bartik theme, and standard profile in Drupal 7 - there seems no good reason to do this. Users expect to be able to add more images, and requiring them to go deep into Drupal's configuration just to add a few images to an Article

I propose we set it to unlimited.

Files: 
CommentFileSizeAuthor
#3 1562802-default-image-field-cardinality-3.patch500 bytesNiklas Fiekas
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] Unable to apply patch 1562802-default-image-field-cardinality-3.patch. Unable to apply patch. See the log in the details link for more information. View

Comments

aspilicious’s picture

Well most articles are based on one picture a title and some text. More images are mostly added inside a new field?
Can be wrong...

ry5n’s picture

Is there a downside to removing this limitation? Would it be somehow more confusing to site builders/content creators if the limit was not there?

Niklas Fiekas’s picture

Status: Active » Needs review
FileSize
500 bytes
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] Unable to apply patch 1562802-default-image-field-cardinality-3.patch. Unable to apply patch. See the log in the details link for more information. View

So ... the basic change would be this. Would we also want to change the

  • label (Image)
  • helptext (Upload an image to go with this article.)
  • machine name (field_image)

?

yoroy’s picture

I'm in favor for allowing multiples. The one ugly-fying thing is that currently, you'd also get multiple images shown in the teaser version. That's what #1234624: Limit the number of fields to display is for.

Status: Needs review » Needs work

The last submitted patch, 3: 1562802-default-image-field-cardinality-3.patch, failed testing.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.