Project

General

Profile

Actions

Feature #20064

closed

"no columns" setting for Images

Added by Bernd Schuhmacher about 15 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Fluid Styled Content
Target version:
-
Start date:
2009-02-20
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Is it possible to allow a layout without a given number of images in one row when using CE "Images".
This would be nice for some sites

(issue imported from #M10506)

Actions #1

Updated by Ernesto Baschny almost 15 years ago

Could you explain the use-case a bit more? Give an example of what you are trying to acchieve.

Actions #2

Updated by Christian Kuhn almost 14 years ago

Resolved, no change required.

The issue is still hard to understand without further feedback. Closing it for now. Please re-open if you could provide more information on what is really wanted and how to reproduce.

Actions #3

Updated by Stefan Neufeind almost 10 years ago

  • Status changed from Resolved to New
  • Target version deleted (0)
  • TYPO3 Version set to 6.2

I've just come across a similar request and think this ticket might fit.

Currently a CE of type "images" allows to choose from 1 to 8 images in a row. It might be nice to be able to just insert images and not have them in a fixed number of columns - for example when working with a variable page-width.

Actions #4

Updated by Riccardo De Contardi over 8 years ago

  • Category set to Content Rendering
Actions #5

Updated by Riccardo De Contardi almost 8 years ago

My guess is that this could be somehow solved using Fluid Styled Content element, replacing the MediaGallery.html Partial, removing the <f:for each="{row.columns}" as="column"> cycle... the problem remains how to get the@{column.media.something}@ data... :S

Actions #6

Updated by Susanne Moog over 6 years ago

  • Category changed from Content Rendering to Fluid Styled Content
  • Assignee deleted (Christian Kuhn)
Actions #7

Updated by Georg Ringer about 4 years ago

  • Status changed from New to Closed

Closing this issue because the shipped content elements are rather basic and are not really optimized for reponsive frontends. you need to create those content elements yourself. instead of creating one element which does all you should build elements which solve one specific problem.

Actions

Also available in: Atom PDF