Feature #17638

Integrate possibility to show content elements depending on a given rule

Added by Oliver Hader about 12 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2007-09-29
Due date:
% Done:

0%

PHP Version:
5.0
Tags:
Complexity:
Sprint Focus:

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)

0006419_alpha.patch View (14.8 KB) Administrator Admin, 2007-09-29 15:36

0006419_alpha_v2.patch View (19.8 KB) Administrator Admin, 2007-09-30 11:47

0006419_alpha_v2_4.patch View (19.7 KB) Administrator Admin, 2008-03-22 10:41


Related issues

Related to TYPO3 Core - Feature #17630: gr_list concept needs to be improved New 2007-09-27
Related to TYPO3 Core - Feature #71694: Personalized Content Closed 2015-11-19

History

#1 Updated by Oliver Hader about 12 years ago

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.

#2 Updated by Oliver Hader about 12 years ago

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")

#3 Updated by emds-itsupport almost 12 years ago

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.

#4 Updated by Oliver Hader over 11 years ago

Updated patch to work again with TYPO3 4.2-beta3:
0006419_alpha_v2_4.patch

#5 Updated by Xavier Perseguers over 8 years ago

  • Category deleted (Communication)
  • Target version changed from 4.6.0 to 4.6.0-beta1

#6 Updated by Xavier Perseguers over 8 years ago

  • Target version deleted (4.6.0-beta1)

#7 Updated by Alexander Opitz about 5 years ago

  • Status changed from Accepted to Needs Feedback

Hi Oliver,

what's the state of this issue?

#8 Updated by Oliver Hader almost 5 years ago

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 :)

#9 Updated by Alexander Opitz over 4 years ago

So closing this issue and creating a blueprint?

#10 Updated by Alexander Opitz about 4 years ago

  • Target version set to 8 LTS

#11 Updated by Riccardo De Contardi over 3 years ago

What's the status of this issue? It seems like the extension https://typo3.org/extensions/repository/view/contexts?

#12 Updated by Riccardo De Contardi almost 3 years ago

  • 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.

#13 Updated by Alexander Opitz almost 3 years ago

  • Target version deleted (8 LTS)

Also available in: Atom PDF