|Priority:||Must have||Due date:|
|TYPO3 Version:||6.1||PHP Version:|
The resizing of images (auto scaling to comlun-width) seems to work only with "text with image", when using the "image only"-content element the picture has the original size (leeds to funny overlay effects).
(TYPO3 4.5.11, multicolumn 2.1.13)
PS: its a great extension!
|related to Multicolumn for the page module - Bug #47065: shrink image sizemay be fault: $colPosMaxImageWidth calcu...||New||2013-04-09|
Updated by Chris no-lastname-given over 1 year ago
Ok, I have to correct myself.
When you use a predefined layout and note a size of the container -> I works.
- When you use a layout and change the width of the columns (i.e. 50%/50% -> 75%/25%), the image size doesnt change.
- When you use a custom layout, the image get scaled, but in a wrong way. Example: Custom Layout (25%/75%) -> The image is scaled like the 50%/50% preconfigured layout.
Updated by Viktor Livakivskyi about 1 year ago
In my case it doesn't work at all...
Tried to debug the code and found, that $colPosMaxImageWidth is not filled at line 268 of class.tx_multicolumn_pi1.php, when using percentage as width and setting it, i.e., like this: 'columnWidth = 30 || 70'.
But even hardcoding it didn't help me, and I still can't find, what is the reason of it.
Funny thing, that 'maxW' is set in tt_content.image - I can see it in debugs and image is cropped, when uding CE outside of multicolumn container, but same tt_content.image inside of container doesn't respect maxW at all...
Seems, that there must be some mystic TYPO3 setting, which I don't know...
Updated by Ralf Hettinger 2 months ago
At the moment, multicolulmn relies on a proper setup of TS constants, namely
styles.content.imgtext.colPos0.maxW styles.content.imgtext.colPos1.maxW styles.content.imgtext.colPos2.maxW
This can be changed with the following TS, where these constants are used:
.... have a look with TYPO3's TS object browser... it's quite self-explanatory.
I feel that there is a bug though within the follow-up calculation, see #47065