Project

General

Profile

Actions

Bug #23479

closed

Sitemap of TYPO3 does not work with Templa-Voila referenced content-elements

Added by Gabriel Kaufmann almost 14 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2010-08-30
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.3
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

I figured out that the default TYPO3-sitemap with menu-type "section-index" (for the current page) does not work with content-elements refered using templa-voila.

What I did:

I have a source-page with content-elements (in my case simple text with headlines). The source page also has a sitemap with "section-index" in it, that works fine!

I want to use the same contents in another page in my page-tree using the templaVoila referencing feature for contents. So on the target-page I tried different options for this.

1) using Tab: Options -> "Show contents from this page instead" option
2) using Tab: Extended -> Content [showing my columns defined in TemplaVoila with element-browser]

I didn't figure out how to make it work. It makes no difference if the sitemap-content is local in my target page or also referenced using the features mentioned above. The Sitemap simply keeps empty just showing it's headline that I defined into the content-element "sitemap".

I cannot provide a patch yet. Does anyone have a clue / patch for this?
(issue imported from #M15592)

Actions #1

Updated by Alexander Opitz over 10 years ago

  • Status changed from New to Needs Feedback
  • Target version deleted (0)
  • TYPO3 Version set to 4.3
  • Is Regression set to No

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?

Actions #2

Updated by Alexander Opitz over 10 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this ticket.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF