[TYPO3-dev] naming scheme for markers with mm table relation to another table
Franz Holzinger
franz at fholzinger.com
Fri Sep 15 21:25:25 CEST 2006
Hello Oliver,
> Maybe I don't get it right, but why do you store the
> pid in that marker names? What if a record goes from one page to another
> one and there is somewhere a hardcoded marker...
>
I do not store the pid within the marker, but the index of the pid among
the list of pids for one product.
> To use underscore as delimiter is no good idea.
> I'd like something like this:
> ###PRODUCT::NOTE_UID::1|text### which is
> <table>, <field>, <uid> and if available the <content-type>.
>
> Just my opinion... ;)
For backwards compatibility reasons we must keep the ###PRODUCT_NOTE_UID
in the front. E.g. the notes field has the marker ###PRODUCT_NOTE###
We could make a
###PRODUCT_NOTE_UID_1_1|TEXT###
and a
###PRODUCT_NOTE_UID_3_2|IMAGE###
>
> Franz Holzinger wrote:
>
>>proposals:
>>
>>###PRODUCT_NOTE_UID_1_1###
>
> :) Is the table "product_note_uid" or "product" or "product_note_uid_1_1"?
>
It is the tt_products table connected to a page having tt_content
elements on it.
The field in the tt_products table is note_uid which refers to the
uid_local of the mm table to the pages table -> uid_foreign.
The tt_content elements have the pid to reference to the pages table.
To get the title field of the first page I could use
###PRODUCT_NOTE_UID_1_TITLE###
Greets,
Franz
More information about the TYPO3-dev
mailing list