Feature #18294
closed
Layer to override content
0%
Description
On the same principle as for translations, an idea would be to have a page or a content element overriden by another version of it depending on some conditions. And that recursively to a certain number fo levels.
For example, I have a text written in generic terms.
Then I want it to be decelined for 10 sectors. The wording will be different, the examples, etc.
Then for each sector I would like the text to be declined for different types of audiences: specialists, experts, newbies, etc.
etc. etc. to n-levels
And then each of those contents should be translatable as it is the case now.
(issue imported from #M7650)
Updated by emds-itsupport over 16 years ago
Although I will be almost done with the specifications of this module, if someone is interested, I will submit the specs, but this pretty much like the language layers.
Updated by Oliver Hader over 16 years ago
The most interesting part of this feature would be how to define these conditions and how to setup a chain of responsibility.
I started to work on a similar task - currently it supports only displaying single content elements depending on domain names - the conditions are called rules there which shall of course be extended by other stuff.
see feature #17638
Updated by emds-itsupport over 16 years ago
This is a very useful feature which is quite handy as well. What I have in mind actually is for eg.:
- a drop down menu where one chooses its layer and sublayer and then the middle part of TYPO3 refreshes with the adapted content, and this layered content is also ready for translation.
- some TS configuration or whatever else, where one defines the layers and sub-layers which are to be shown in the above mentioned drop down list
The in the front end, the user, depending on his profile, is assigned to a content.
I see conditional CE for simple cases. For this case, I would need something very user friendly.
I am looking forward anyway to conditional rendering, it makes things clearer than using templates.
Updated by Oliver Hader over 16 years ago
I see - this also requests some more work on the general hierarchy of records and leads to introduce a "meta layer" which can be extended then by translation, workspaces, IRRE, conditional layers, etc.
Updated by emds-itsupport over 16 years ago
I think you've got it... I'll post the specs in about two weeks... hectic times for me lately.
Updated by Mr. Hudson about 13 years ago
Patch set 1 of change Ib80e1bd6176841088712cbf40e3d2c9e8ac87973 has been pushed to the review server.
It is available at http://review.typo3.org/5672
Updated by Alexander Opitz over 11 years ago
- Status changed from New to Needs Feedback
- Target version deleted (
0)
As this report is very old, is the handling in newer TYPO3 CMS Versions (like 6.0/6.1) more like you expect it?
Updated by Alexander Opitz about 11 years ago
- Status changed from Needs Feedback to Closed
No feedback for over 90 days.