Project

General

Profile

Actions

Feature #16466

closed

HMENU.special = language

Added by Martin K¤stner almost 18 years ago. Updated over 10 years ago.

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

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

If I use the language menu with:

lib.langMenu = HMENU
lib.langMenu.addQueryString = 1
lib.langMenu.addQueryString.exclude = cHash
lib.langMenu.normalWhenNoLanguage = 1
lib.langMenu.special = language
lib.langMenu.special.value = 0,1,2

the correct links would be shown with no cHash (because the cHash is unique for each language). There is no option to generate that cHash for the URL with the correct value.

IMHO the cHash value should always be removed and set to the correct value in the function for the language menu if addQueryString is set. You then get always the correct URL with parameters and the corresponding value for the cHash.

Using RealURL with option enableCHashCache=TRUE (if this is associated with the Problem)

when not excluding cHash than I get always the actual URL not the links to the page in other languages.
(issue imported from #M4038)

Actions #1

Updated by Xavier Perseguers over 12 years ago

  • Category deleted (Communication)
  • Status changed from New to Needs Feedback
  • Target version deleted (0)
  • PHP Version deleted (4)

Still valid?

Actions #2

Updated by Alexander Opitz about 11 years ago

  • Status changed from Needs Feedback to Closed

No response over 1 year => closed

Actions #3

Updated by Martin Kutschker about 11 years ago

  • Status changed from Closed to New

Indeed the bug is still unresolved. The point is that you have two options:

a) use addQueryString.exclude = cHash

But that will make TYPO3 response with the wrong content from the cache. This is a no go as the client will get the wrong page.

b) don't use addQueryString.exclude = cHash

But that will break the cHash. TYPO3 will render the page without cache (incl. configuration cache) and prohibit client side caching. This is a big performance loss, but at least the right content is delivered to the client.

For typolink there is a remedy which can be used as a workaround: typolink.useCashHash = 1. The point is that the cHash is not only used but recalculated. This is what is missing for HMENU. Anyway here comes a snippet for a HMENU with correct cHashes.

NO {
doNotLinkIt = 1
stdWrap {
typolink {
parameter.data = TSFE : id
addQueryString.exclude = L,cHash
useCacheHash = 1
}
}
}
Actions #4

Updated by Alexander Opitz about 11 years ago

  • Status changed from New to Needs Feedback

With which version did you try it?

Actions #5

Updated by Alexander Opitz over 10 years ago

  • Status changed from Needs Feedback to Closed

No feedback for over 90 days.

Actions

Also available in: Atom PDF