Project

General

Profile

Actions

Bug #16676

closed

default setting for imageorient does not work

Added by Sascha Egerer about 18 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
-
Target version:
-
Start date:
2006-10-30
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
4.4
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Setting a default Value for imageorient in tt_content does not work!
I've tried this in User, Group and Site TSconfig

TCAdefaults.tt_content.imageorient = 2

(issue imported from #M4448)


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #22712: userTSconfig: TCAdefaults.tt_content.imagecols = 1 does not workClosed2010-05-25

Actions
Related to TYPO3 Core - Bug #30864: userTSconfig: TCAdefaults.tt_content.imagecols = 1 does not workClosed2011-10-12

Actions
Actions #1

Updated by Chris topher over 14 years ago

Still present in 4.4beta2.

Actions #2

Updated by taywa gmbh about 14 years ago

still dosent work in 4.4.4! tested in userconfig

TCAdefaults.tt_content.imageorient = 26

For me as an Workaround in pageTS, remove all imageorient exept the 26.

TCEFORM.tt_content.imageorient.removeItems = 0, 1, 2, 8, 9, 10, 17, 18, 25, --div--

Actions #3

Updated by Josef F. Glatz (Old User) over 13 years ago

TCA "doesn't cares" about default values... it's in the wizard

  1. classic page module
    mod.wizards.newContentElement.wizardItems.common.elements.textpic.tt_content_defValues.imageorient = 18
  1. templavoila
    templavoila.wizards.newContentElement.wizardItems.common.elements.textpic.tt_content_defValues.imageorient = 18
Actions #4

Updated by Christian Knuth over 12 years ago

  • Target version changed from 0 to 4.7.5

still present in 4.7.1

i think this is a common expected behaviour that

TCEFORM.tt_content.imageorient.default = 18

or

TCAdefaults.tt_content.imageorient = 18

is changing the default for creating new elements. But unfurtunately it does still not work this way.

Actions #5

Updated by Frank Nägler over 10 years ago

this bug is still present in 6.2.3, I think after seven years, this should be fixed ;)

Actions #6

Updated by Stefan Neufeind about 10 years ago

  • Description updated (diff)
  • Is Regression set to No

Just stumbled across this as well, current master (post-6.2). And of course that installation I had also still used TemplaVoila. How counter-intuitive is that :-(

Actions #7

Updated by Markus Klein about 10 years ago

  • Status changed from New to Accepted
  • Target version changed from 4.7.5 to next-patchlevel
Actions #8

Updated by Mathias Schreiber about 9 years ago

  • Target version deleted (next-patchlevel)
Actions #9

Updated by René Fritz about 9 years ago

Still not working in 7.6:

TCEFORM.tt_content.imageorient.default = 2
TCAdefaults.tt_content.imageorient = 2

This works:

mod.wizards.newContentElement.wizardItems.common.elements.image.tt_content_defValues.imageorient = 2
mod.wizards.newContentElement.wizardItems.common.elements.textpic.tt_content_defValues.imageorient = 2

I didn't dive very deep, but in DatabaseRowDefaultValues imageorient is already set (to 17) so a default value will not applied by the code afterwards.

Actions #10

Updated by Frank Nägler over 8 years ago

  • Status changed from Accepted to In Progress
  • Assignee set to Frank Nägler
Actions #11

Updated by Gerrit Code Review over 8 years ago

  • Status changed from In Progress 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 https://review.typo3.org/47266

Actions #12

Updated by Gerrit Code Review over 8 years ago

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

Actions #13

Updated by Gerrit Code Review over 8 years ago

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

Actions #14

Updated by Frank Nägler over 8 years ago

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

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF