[TYPO3-core] Enhance typolink.addQueryTsring and fix bug #2280

Martin Kutschker Martin.Kutschker at blackbox.net
Mon Feb 27 22:34:54 CET 2006


Martin Kutschker writes on 
Sun, 26 Feb 2006 23:07:39 +0100 (MET):

> Hi!
> 
> The attached patch allows typolink.addQueryString to use GET and POST
> instead of QUERY_STRING. And it addes this feature also to a HMENU of
> type "language".
> 
> # empty "method" is QUERY_STRING
> typolink.addQueryString.method = GET | POST
> typolink.addQueryString.exclude = <list of arguments to remove>
> 
> # as typolink.addQueryString
> HMENU.addQueryString


The attached patch adresses the problems Karsten noted (_GET vs QUERY_STRING: array and encoding).

addQueryString.method

If set to to GET or POST then then the parsed query arguments (GET or POST data) will be used. This settings are useful if you use URL processing extensions like Real URL, which translate part of the path into query arguments.

addQueryString.exclude

List of query arguments to exclude from the link (eg L or cHash).

---

For HMENU the above lines plus the original entry may be added to the description of HMENU. Note that addQueryStrings works *only* for special=language.

Masi 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/x-patch
Size: 3805 bytes
Desc: not available
Url : http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20060227/d2c8fbd4/attachment.bin 


More information about the TYPO3-team-core mailing list