Bug #65618
closed
Working with list module and page content
0%
Description
Hi,
I think this module will not work correctly. If I chose Caption in "set field" - nothing is shown in the table. But captions still there from FAL metadata. If I now edit the field for all content elements with images I can set a value in this field - a caption.
But in the content element itself nothing changed. The caption from FAL metadata is shown, if I edit the content element and even in Frontend.
But if the editor is working with list module, he sees the cation which was added in the list module.
And - if there is more than one image in the content element - which caption should be edited here?
IMHO fields which you can not edit should not be shown. For me this module is very buggy. In 6.2 and in 7.
Files
Updated by Mathias Schreiber over 9 years ago
- Status changed from New to Needs Feedback
- Assignee set to Mathias Schreiber
Can you supply a screenshot of the view you are refering to?
Keep in mind:
The field tt_content.caption is only available for backwards compatibility and should not be used by an editor since... 6.0?
Updated by Andrea Herzog-Kienast over 9 years ago
- File caption.PNG caption.PNG added
Hi Mathias,
I think no screenshot is needed. But I will attach one.
But as you said - only for backwards compatibility - should not be visible for an editor by default - if field is not useable.
Updated by Alexander Opitz over 9 years ago
- Category set to Backend User Interface
- Status changed from Needs Feedback to New
- Assignee deleted (
Mathias Schreiber)
Updated by Riccardo De Contardi about 9 years ago
- Status changed from New to Needs Feedback
in version 7.5-dev (latest master) that field is not present (you have to install the compatibility6 system extension to enable it again)
Do you think this is sufficient to consider this closed?
Updated by Daniel Goerz over 8 years ago
- Status changed from Needs Feedback to Closed
I close this because as Riccardo stated the field is no longer present in tt_content.
For 6.2 it is very unlikely to be an issue thats going to be tackled since only critical bugs and security patches are going into 6.2 at this point.
If you still think this is a bug that needs to be adressed in 7.6 or the master branch, please open an updated ticket or reopen this one with further information.