No subject

Tue Nov 13 12:05:00 CET 2007

understand why it is done like this, it makes it very powerful ... but still
... for a newbie I am starting to feel like when you ring the bank to
complain ... handed from one department to another :)

So, off to typolink on p.33. Trying to remember why I am here again ... oh
yeah, to create skip links ... ok ...

extTarget: target /stdWrap - target used for external links ( _top)
target: target /stdWrap - target used for internal links

now, you might think this is intuitive, but when so much else is not, it
really did not occur to me that "target" was being used in the html sense.
Even with _top stated, I still needed to read TyposcriptByExample to really
get this...

no_cache: boolean /stdWrap - Adds a "&no_cache=1"-parameter to the link

Ok .. I understand it ... but I have no idea when I would use it or not. I
know that some things use it, like DR wiki, but no idea what the rationale

useCacheHash: boolean - If set, the additionalParams list is exploded and
calculated into a hashstring appended to the url, like "&cHash=ae83fd7s87".
When the  

 (about now my eyes have glazed over ...)

caching mechanism sees this value, it calculates the same value on the
server based on incoming values in HTTP_GET_VARS, excluding
id,type,no_cache,ftu,cHash,MP values. If the incoming cHash value
matches the calculated value, the page may be cached based on this.
The [SYS][encryptionKey] is included in the hash in order to make it
unique for the server and non-predictable.

Hmm .. hope that one is not on the test ....

additionalParams string /stdWrap This is parameters that are added to the
end of the url. This must be code ready to insert after the last parameter.

This is very useful when linking to pages from a searchresult. The
searchwords are stored in the register-key SWORD_PARAMS and can be
insert directly like this: = register:SWORD_PARAMS

NOTE: This is only active for internal links!

As I cut that paragraph up here, it starts to make a whole lot more sense,
but I have never bothered to read it before ... it was just a paragraph of

addQueryString: boolean - Add the QUERY_STRING to the start of the link.
Notice that this does not check for any duplicate parameters! This is not a
problem (only the last
parameter of the same name will be applied), but enable
"config.uniqueLinkVars" if you still don't like it.

Another one I hope is not on the test ...

Wrap: wrap - Wraps the links. Ok ... get that one, only because I was given
a snippet with some navigation ts I did way back ... so I know that I can
wrap it with html.

If you don't know, you wouldn't know... wrap with what???

ATagBeforeWrap: boolean - If set, the link is first wrapped with ".wrap" and
then the <A>-tag.

This I get, but have no idea why it is useful.

The problem with these snippets of coding type information thrown in is
that, literally, my eyes glaze over .... I begin to scan, because my brain
just doesn't process that information, so it becomes like a blocked sewer
(sorry, that was a disgusting example, but the one that came to mind :) )
... it just blocks, and nothing further actually gets processed. I have to
consciously keep reading over and over, and sometimes physically have to
hide the coding jargon, so my brain can read only information it actually

> > That is why I made my own blog at Will take a look :)
May be >you should put this address to your signature? Having extra resource
visible never >hurts.

:) it isn't really meant for anyone else, only me ... although it is indexed
well by google. There are no high class bits of information there, just
notes to help me remember.

So anyway ... maybe that helps you "read" my mind a little ...

Oh ... and my typolinks still aren't working!


More information about the TYPO3-english mailing list