Project

General

Profile

Actions
Copy link

Bug #16215

closed

HMENU.special = browse fails on unavailable translations in it's way...

Added by Karsten Dambekalns over 18 years ago. Updated about 11 years ago.

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

0%

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

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

browse-mutlilang.patch (979 Bytes) browse-mutlilang.patch Administrator Admin, 2006-06-05 19:12
Actions
Copy link

Also available in: Atom PDF