Feature #24878: Add first and last attribute in sitemap content type - TYPO3 Core - TYPO3 Forge

Custom queries

Accessibility
Easy tasks
Forge Triage
JavaScript issues
JavaScript Issues (w/o Epics/Stories)
My open issues
No feedback within 90 days
Open Bugs
Open issues of 10
Recently modified
Regressions
Stabilization Issues
Usability or UX

Actions

Copy link

Feature #24878

closed

Add first and last attribute in sitemap content type

Added by Simon Schaufelberger almost 14 years ago. Updated about 9 years ago.

Status:

Closed

Priority:

Should have

Assignee:

Category:

TypoScript

Target version:

Start date:

2011-01-28

Due date:

% Done:

Estimated time:

PHP Version:

Tags:

Complexity:

Sprint Focus:

Description

currently the sitemap just shows a unordered list with no default classes for first and last item. overwriting is quite complex so add classes by default.

(issue imported from #M17389)

History
Notes
Property changes

Actions

Copy link

Updated by Jo Hasenau almost 14 years ago

This is a feature request then?

Actions

Copy link

Updated by Simon Schaufelberger almost 14 years ago

yes, how can i mark it here as a change request?

Actions

Copy link

Updated by Jo Hasenau almost 14 years ago

After posting it, you can only change it, when you are a core developer.

But you can mark bugs as "feature" instead of "minor" in the report form before sending them.

Actions

Copy link

Updated by Georg Ringer over 13 years ago

Tracker changed from Bug to Feature
Target version deleted (0)
TYPO3 Version set to 4.5

Actions

Copy link

Updated by Georg Ringer over 13 years ago

Category set to TypoScript

Actions

Copy link

Updated by Mathias Schreiber almost 10 years ago

Status changed from New to Needs Feedback
Assignee set to Mathias Schreiber

Hi Simon,

do you have a proposed snipplet at hand?

Actions

Copy link

Updated by Alexander Opitz over 9 years ago

Status changed from Needs Feedback to Closed
Assignee deleted (~~Mathias Schreiber~~)

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

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

Copy link