Project

General

Profile

Actions

Feature #18913

closed

getText slide: register uid and level after slide hits

Added by Ralf Hettinger almost 16 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Frontend
Target version:
-
Start date:
2008-06-06
Due date:
% Done:

0%

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

Description

This feature refers to the getText attribute 'slide', which may be used for leveltitle, leveluid, levelmedia by default or to any field of pages by levelfield, if configured properly. Quite useful thing; not to be mixed up with the property 'slide' for CONTENT cObjects, which I'm not referring to hereby.

I think it would be even more useful, if one could refer to the menu's (pagetree's) level and a page's uid where the levelfield was fetched from after a slide hit during the walk back to the rootline.

The attached patch suggests two new register values

UID_FROM_LAST_PAGESLIDE_FOR_FIELD_[name of slided field]
LEVEL_FROM_LAST_PAGESLIDE_FOR_FIELD_[name of slided field]

which will be filled after each successful slide (i.e. there has been a slide hit) with the page uid and the menu level of the page that had some value for the requested field if it that was achieved by a slide to rootline.

(issue imported from #M8626)


Files

8626.patch (907 Bytes) 8626.patch Administrator Admin, 2008-06-06 15:03
8626_4.3.patch (972 Bytes) 8626_4.3.patch Administrator Admin, 2009-08-08 17:02
8626_wiki.txt (596 Bytes) 8626_wiki.txt Administrator Admin, 2009-08-08 17:02
Actions #1

Updated by Xavier Perseguers almost 13 years ago

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

Updated by Xavier Perseguers almost 13 years ago

  • Target version deleted (4.6.0-beta1)
Actions #3

Updated by Alexander Opitz almost 11 years ago

As this report is very old, is the handling in newer TYPO3 CMS Versions (like 6.0/6.1) more like you expect it?

Actions #4

Updated by Alexander Opitz almost 11 years ago

  • Status changed from New to Needs Feedback
Actions #5

Updated by Ralf Hettinger almost 11 years ago

The initial description of the issue is still valid for 6.1, although the patch would (of course) no longer apply.

Actions #6

Updated by Alexander Opitz almost 11 years ago

Can you provide a new patch?

Actions #7

Updated by Alexander Opitz over 10 years ago

  • Status changed from Needs Feedback to New
Actions #8

Updated by Mathias Schreiber over 9 years ago

  • Category set to Frontend
  • Target version set to 7.2 (Frontend)
Actions #9

Updated by Benni Mack almost 9 years ago

  • Target version changed from 7.2 (Frontend) to 7.4 (Backend)
Actions #10

Updated by Susanne Moog over 8 years ago

  • Target version changed from 7.4 (Backend) to 7.5
Actions #11

Updated by Benni Mack over 8 years ago

  • Target version deleted (7.5)
Actions #12

Updated by Susanne Moog over 4 years ago

  • Status changed from New to Closed

Due to low demand / low priority I'm going to close this issue now. If anyone takes time to implement it, simply open a new issue please. Thanks.

Actions

Also available in: Atom PDF