Feature #17638
closed
Integrate possibility to show content elements depending on a given rule
Added by Oliver Hader over 16 years ago.
Updated about 7 years ago.
Description
Perhaps we should start with an example before an abstract:
Imagine, that you're running a TYPO3 site with several domains (mysite.com, shop.mysite.com, partner.mysite.com) that are all using the same page tree. Now, a content element shall only be visible if the website user hits your site using a special domain (e.g. partner.mysite.com). That content element show some additional information and isn't visible on the other pages.
What you can do currently, is to use some TypoScript conditions or a redirect using the domain record of TYPO3. But there isn't yet a possibility to assign such conditions to single content elements.
Assigning a domain was just an example, this could be anything, e.g. GET-parameter, systemtime, server-environment-variable. I tend to call this a "rule" or "front-end rules" (fe_rules).
(issue imported from #M6419)
Files
The applied patch adds a new database table 'fe_rules' (integrate it using your install tool > database analyzer > compare). Currently only the types 'domain' and 'group' are defined.
- A domain looks for the HTTP_HOST, enter the domain record in the expression field, you can also use wildcards, e.g. "*.typo3.org".
- A group can contain again other rules (similar to fe_groups)
- The field "allow/deny" inverts the evaluation of an expression
A new field 'fe_rules' is added to tt_content records which allows one to define rules for each content record.
Still alpha/experimental.
Added a new version:
- added 'fe_users' to getHash in TSFE
- started iconWorks for fe_rules with the file flag 'r', e.g. tt_content__r.gif
- added comments & some cleaning
TODO:
- possibly add pages (cave: caching!)
- improve caching, also concerning bug #17630 ("gr_list concept needs to be improved")
could a good idea to have not only Typoscript rules, but also a php callback, and add optional sections to test conditions return values for show/hide.
Updated patch to work again with TYPO3 4.2-beta3:
0006419_alpha_v2_4.patch
- Category deleted (
Communication)
- Target version changed from 4.6.0 to 4.6.0-beta1
- Target version deleted (
4.6.0-beta1)
- Status changed from Accepted to Needs Feedback
Hi Oliver,
what's the state of this issue?
Nowadays one would call that feature as "context based content delivery". Thus, in general this still makes sense, but obviously not with the implementation I've created 7 years ago :)
So closing this issue and creating a blueprint?
- Target version set to 8 LTS
- Status changed from Needs Feedback to Closed
- Assignee deleted (
Oliver Hader)
As there has been no feedback since a long time, I am closing this one.
If you think that this is the wrong decision or that there is still work to be done, please reopen it or open a new issue with a reference to this one. Thank you.
- Target version deleted (
8 LTS)
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by