Bug #16215
closed
HMENU.special = browse fails on unavailable translations in it's way...
0%
Description
If you have a HMENU with special=browse in a multi-language site, this generally works fine.
If a page that would be the next or previous page has no translation and you are not browsing with the default language, the menu mails and acts as if there was no next page, even if there would be one "behind" the page without translation.
The attached patch fixes this for the situtation I am currently looking at. It would be nice if others could test this, to make sure the fix doesn't cause any bad side-effects.
I'd be also interested in opinions about the handling of pages without translation when using the different paradigms for the display of non-translated pages. That is something the patch doesn't actively deal with at all...
The patch was created against CVS, branch TYPO3_3_8, but applies to current CVS as well.
(issue imported from #M3628)
Files
Updated by Karsten Dambekalns almost 17 years ago
The bug is still present in 4.0.6 (and probably other versions), could someone double check this? Thanks!
Updated by Chris topher about 14 years ago
Same code still present in current trunk.
Updated by Alexander Opitz about 11 years ago
- Category deleted (
Communication) - Status changed from New to Needs Feedback
- Target version deleted (
0)
The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?
Updated by Alexander Opitz over 10 years ago
- Status changed from Needs Feedback to Closed
No feedback for over 90 days.