Project

General

Profile

Actions

Bug #47372

closed

Problem with enforcing an image in a news record.

Added by Kay Strobach about 11 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
FormEngine aka TCEforms
Target version:
-
Start date:
2013-04-19
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.3
Tags:
Complexity:
medium
Is Regression:
No
Sprint Focus:

Description

Setting:

TCEFORM.tt_news.image.config.minitems = 1
In the Pagets in TYPO3 4.7.10 enforces an image to be selected. Sadly this can't be uploaded like it was possible in TYPO3 4.5 LTS.

I get an alert with the following text (having an image selected in the upload field ...):

The fields marked with a yellow exclamation mark are not yet correctly filled in. Please complete them properly.
But it's possible to select an image via the filepicker wizard beside the image selector.

This problem can be a problem in TYPO3 or in tt_news, as i found it using tt_news i reported it here - but i assume it's core related :(


Files

Bildschirmfoto 2015-06-15 um 15.41.42.png (15.5 KB) Bildschirmfoto 2015-06-15 um 15.41.42.png Screenshot of error DACHCOM.DIGITAL AG, 2015-06-15 15:42

Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #18429: required fields in Flexform are not correct marked with Exclamation SignClosed2008-03-12

Actions
Related to TYPO3 Core - Bug #68795: The fields marked with a yellow exclamation mark are not yet correctly filled in. Please complete them properly.Closed2015-08-06

Actions
Actions #1

Updated by Mathias Schreiber over 9 years ago

  • Status changed from New to Needs Feedback
  • Assignee set to Mathias Schreiber
  • Is Regression set to No

Does this still apply to FAL?

Actions #2

Updated by Kay Strobach over 9 years ago

not to fal afaik, but if you use non FAL file fields, which is still possible ...

Actions #3

Updated by Wouter Wolters about 9 years ago

  • Status changed from Needs Feedback to Accepted
  • Assignee deleted (Mathias Schreiber)
  • Target version deleted (4.7.11)
  • TYPO3 Version changed from 4.7 to 6.2
  • Complexity changed from no-brainer to medium
Actions #4

Updated by Wouter Wolters about 9 years ago

Problem still applies to non FAL fields.

Actions #5

Updated by Gerrit Code Review about 9 years ago

  • Status changed from Accepted to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/37523

Actions #6

Updated by Gerrit Code Review about 9 years ago

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/37523

Actions #7

Updated by Gerrit Code Review about 9 years ago

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/37523

Actions #8

Updated by Gerrit Code Review about 9 years ago

Patch set 1 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/37732

Actions #9

Updated by Wouter Wolters about 9 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
Actions #10

Updated by DACHCOM.DIGITAL AG almost 9 years ago

Hi. This commit breaks the upload field, when you try to upload a new file, when "minitems" is set to at least "1". When you choose a file from the filelist, it works.

Actions #11

Updated by Bernhard Kraft over 8 years ago

This bug also still occurs here.

Using the file wizard to select a file from fileadmin works but when uploading a file directly the exclamation mark still remains and one can't save. This occurs wiht TYPO3 6.2.14 and "media" element (field "image") of EXT:news version 3.2.2. Overriding the "minitems" field to "0" solved the problem.

I do not know if this still occurs in 7.x. A related issue #18429 has been closed because it is solved in 7.x and as this is no security issue I do not know whether it should just get closed again with a won't fix.

Actions #12

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF