Hello People,







I have some troubles with creating an fork of tt_products.







I have renamed all classes, php files, variables, sql database tables, and
the (main) folder with my new name ( tt_freiraum ). I have changed some
things in the language files. But when I now add the Shop Plugin as an
Content Element. I get at the FrontEnd only the Header. I have included the
static Typoscript from extensions.







I have changed in ext_tables.php the id of the Plugin (from 5 to 7)







1.

t3lib_extMgm::addPlugin(Array('LLL:EXT:'.TT_FREIRA UM_EXTkey.'/locallang_db.x

ml:tt_content.list_type_pi1','7'),'list_type');

2.

$TCA['tt_content']['types']['list']['subtypes_excludelist']['7']='layout,sel

ect_key';

3.

$TCA['tt_content']['types']['list']['subtypes_addlist']['7']='pi_flexform';

4. t3lib_extMgm::addPiFlexFormValue('7',

'FILE:EXT:'.TT_FREIRAUM_EXTkey.'/flexform_ds_pi1.xml');



I have figure out that pi/class.tx_ttfreiraum_pi1.php is loaded but the main

- function is never called.







I hope someone can help me. But I have to say thanks for creating this great

Typo3 Ext.



_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

on Sat, 16 Aug 2008 14:07:51 +0200, Tobias Hochgürtel wrote:

> I have renamed all classes, php files, variables, sql database tables,
> and the (main) folder with my new name ( tt_freiraum ). I have changed
> some things in the language files. But when I now add the Shop Plugin as
> an Content Element. I get at the FrontEnd only the Header. I have
> included the static Typoscript from extensions.

that might give a mix of old and new names, where half the references is
not available any more.
Doing something like this I would replace EVERY occurence of the original
extkey with the new one.

the other problem might be the new extension key itself:
tt_freiraum is not in the regular namespace
either use user_... for local extensions or tx_... for public.

keep attention to the special behavior of tt_...-extensions as they are
remains of the first versions of TYPO3. I don't know exactly wether this
happens in the newest TYPO3-versions, but I remember some mentions about
special handling of these extensions in core.
I don't think your extension is known to the core.
You might change the behaviour of your extension to that of 'normal'
extensions (like created with kickstarter)

bernd
--
http://www.pi-phi.de/t3v4/cheatsheet.html
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

> that might give a mix of old and new names, where half the references is
> not available any more.
> Doing something like this I would replace EVERY occurence of the original
> extkey with the new one.

okay, i have replaced every occurence of the orginal extkey ( tt_products || TT_PRODUCTS ) to ( tt_freiraum || TT_FREIRAUM ).

> the other problem might be the new extension key itself:
> tt_freiraum is not in the regular namespace
> either use user_... for local extensions or tx_... for public.

but what is with the tt_products self? It's working with the tt_ namespace...
I have only renamed all occurence of the orginal extkey...

> keep attention to the special behavior of tt_...-extensions as they are
> remains of the first versions of TYPO3. I don't know exactly wether this
> happens in the newest TYPO3-versions, but I remember some mentions about
> special handling of these extensions in core.
> I don't think your extension is known to the core.
> You might change the behaviour of your extension to that of 'normal'
> extensions (like created with kickstarter)

Is there any paper about this handling? I will search, but If you know some place where I can read about this, please send it to me.

I think I will try the renaming the ext again.. to get clear..



-----Original Message-----
From: typo3-english-bounces (AT) lists (DOT) netfielders.de [mailto:typo3-english-bounces (AT) lists (DOT) netfielders.de] On Behalf Of bernd wilke
Sent: Samstag, 16. August 2008 15:10
To: typo3-english (AT) lists (DOT) netfielders.de
Subject: Re: [TYPO3] create a fork of an extension and having troubles with Frontend output

on Sat, 16 Aug 2008 14:07:51 +0200, Tobias Hochgürtel wrote:

> I have renamed all classes, php files, variables, sql database tables,
> and the (main) folder with my new name ( tt_freiraum ). I have changed
> some things in the language files. But when I now add the Shop Plugin as
> an Content Element. I get at the FrontEnd only the Header. I have
> included the static Typoscript from extensions.

that might give a mix of old and new names, where half the references is
not available any more.
Doing something like this I would replace EVERY occurence of the original
extkey with the new one.

the other problem might be the new extension key itself:
tt_freiraum is not in the regular namespace
either use user_... for local extensions or tx_... for public.

keep attention to the special behavior of tt_...-extensions as they are
remains of the first versions of TYPO3. I don't know exactly wether this
happens in the newest TYPO3-versions, but I remember some mentions about
special handling of these extensions in core.
I don't think your extension is known to the core.
You might change the behaviour of your extension to that of 'normal'
extensions (like created with kickstarter)

bernd
--
http://www.pi-phi.de/t3v4/cheatsheet.html
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

on Sat, 16 Aug 2008 16:18:03 +0200, Tobias Hochgürtel wrote:

>> that might give a mix of old and new names, where half the references
>> is not available any more.
>> Doing something like this I would replace EVERY occurence of the
>> original extkey with the new one.
>
> okay, i have replaced every occurence of the orginal extkey (
> tt_products || TT_PRODUCTS ) to ( tt_freiraum || TT_FREIRAUM ).
>
>> the other problem might be the new extension key itself: tt_freiraum is
>> not in the regular namespace either use user_... for local extensions
>> or tx_... for public.
>
> but what is with the tt_products self? It's working with the tt_
> namespace... I have only renamed all occurence of the orginal extkey...
>
>> keep attention to the special behavior of tt_...-extensions as they are
>> remains of the first versions of TYPO3. I don't know exactly wether
>> this happens in the newest TYPO3-versions, but I remember some mentions
>> about special handling of these extensions in core. I don't think your
>> extension is known to the core. You might change the behaviour of your
>> extension to that of 'normal' extensions (like created with
>> kickstarter)
>
> Is there any paper about this handling? I will search, but If you know
> some place where I can read about this, please send it to me.

I have looked - and found nothing
maybe some core-member can give us a hint?

> I think I will try the renaming the ext again.. to get clear..

try to register your/an extension key:

- login to typo3.org (you may need to register)

- go to tab 'Extensions'

- in left menu select 'Extension Keys'

- if you are logged-in you can select the tab 'Register keys'

here you find:
'The key must not being with one of the following prefixes:
tx,u,user_,pages,tt_,sys_,ts_language_,csh_', but no reason.
(hm, there is a typo: 'being' instead of 'begin', who will correct it?)

with this key you are able to release your extension-variant with an own
valid extension key.



bernd
--
http://www.pi-phi.de/t3v4/cheatsheet.html
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

yeah thanks the prefixed helps me..

Currently I creating again a the fork..

I think this time it it should run better

I have figure out that the static Includede Typoscript loads the PI script.

I think the misstake was in the Typoscript and the extenion key / Typoscript Array..

... I write again when all things run

Greets Tobi


-----Original Message-----
From: typo3-english-bounces (AT) lists (DOT) netfielders.de [mailto:typo3-english-bounces (AT) lists (DOT) netfielders.de] On Behalf Of bernd wilke
Sent: Samstag, 16. August 2008 22:02
To: typo3-english (AT) lists (DOT) netfielders.de
Subject: Re: [TYPO3] create a fork of an extension and having troubles with Frontend output

on Sat, 16 Aug 2008 16:18:03 +0200, Tobias Hochgürtel wrote:

>> that might give a mix of old and new names, where half the references
>> is not available any more.
>> Doing something like this I would replace EVERY occurence of the
>> original extkey with the new one.
>
> okay, i have replaced every occurence of the orginal extkey (
> tt_products || TT_PRODUCTS ) to ( tt_freiraum || TT_FREIRAUM ).
>
>> the other problem might be the new extension key itself: tt_freiraum is
>> not in the regular namespace either use user_... for local extensions
>> or tx_... for public.
>
> but what is with the tt_products self? It's working with the tt_
> namespace... I have only renamed all occurence of the orginal extkey...
>
>> keep attention to the special behavior of tt_...-extensions as they are
>> remains of the first versions of TYPO3. I don't know exactly wether
>> this happens in the newest TYPO3-versions, but I remember some mentions
>> about special handling of these extensions in core. I don't think your
>> extension is known to the core. You might change the behaviour of your
>> extension to that of 'normal' extensions (like created with
>> kickstarter)
>
> Is there any paper about this handling? I will search, but If you know
> some place where I can read about this, please send it to me.

I have looked - and found nothing
maybe some core-member can give us a hint?

> I think I will try the renaming the ext again.. to get clear..

try to register your/an extension key:

- login to typo3.org (you may need to register)

- go to tab 'Extensions'

- in left menu select 'Extension Keys'

- if you are logged-in you can select the tab 'Register keys'

here you find:
'The key must not being with one of the following prefixes:
tx,u,user_,pages,tt_,sys_,ts_language_,csh_', but no reason.
(hm, there is a typo: 'being' instead of 'begin', who will correct it?)

with this key you are able to release your extension-variant with an own
valid extension key.



bernd
--
http://www.pi-phi.de/t3v4/cheatsheet.html
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english