Feature #20551
closedNew HMENU property
0%
Description
I'd like to have a new property added to HMENU, at the same position (within TSref) as entryLevel. I'd like this new property to be called "phantomPage" and I'd like it to have stdWrap properties. When this property was set the menu would be generated using the HMENU setup as defined, but it would be generated as if you were on the "phantomPage" no matter what page you were actually on. This would need to work properly with all the special versions (directory, list, rootline, etc) of HMENU.
The reason this comes about is that I have an extension that can be used in many places on the site and in many different situation (listing various records of events), but every instance of this plugin displays the individual event detail page on only one particular page. I would then make use of this property to override the current navigation for the top horizontal navigation, the left hand column navigation, the breadcrumb navigation, etc and the user would have the impression they were on a sub page of there previous page (using a get variable, or other setting available in normal page generation)
So the possible page structure might be:
-home
|- help us
|-overseas events
| |-running events
|
|- fundraising for us
| |-running events
|
|- event details
So the events might be listed on both of the running events pages, but I want the top navigation, left hand navigation and breadcrumb to be different for the event details depending upon which listing page you've come from. (This is not the first time we've encountered this problem).
Then using conditions, stdWrap and other already core functions such as if, override, etc this property could be very powerful and useful.
If anyone is interested in this we would very very much like to see it in version 4.3 and we might be willing to sponsor part or all of it, depending upon the costs to do this. Please feel free to email me if you have any questions
tyler.kraft(at)netefficiency.co.uk
(issue imported from #M11248)
Updated by Alexander Opitz over 11 years ago
- Tracker changed from Bug to Feature
- 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.