TYPO3 Core

(The mapping is needed because of the 32 chars per field/name restriction of Oracle.)

This solution works!!!

But, in oracle databases varchar types are limited to 4000 chars. Then when i save my template mapping, if the result is upper than 4000 chars, none records are saved.

Have you a solution?

With more than 4000 chars the VARCHAR fields are called CLOB. You need to change them in ORACE Adminsystem (havent tried this yet but the problem is well-known.

Thank you Michael for your ansmer!

I havealeady tested this solution, but it doesn't seem to work. None record are saved in database.

Someone have tried this solution?

Thanks,

No sorry, no idea yet. At the moment we are working on a T3 <-> ORACLE testsystem where we hopefully can solve all problems with templavoila and other major extensions. I would inform you when we are ready (will take some time).

I added a fix for this to the SVN version, please give it a try. See #5481 for more info.

I checked the latest version from http://svn.t3.digitaldistrict.de/cgi-bin/trac.cgi/browser/typo3/TYPO3core/trunk/typo3/sysext/dbal/class.ux_t3lib_db.php?rev=12620 . Unfortunately it doesnt solve the problem for me. Maybe there is a newer version somewhere else?

TemplaVoilà is running properly with TYPO3 4.3 (beta3 at the moment)

the topic is about templavoila and ORACLE not only templavoila and TYPO3

Michael, I know the topic is about TV and Oracle. What I said is that with TYPO3 4.3 beta3 (now RC1), DBAL was updated and the version 1.0.0 of DBAL should not have this bug anymore when using Oracle.

Mapping of tx_templavoila_datastructure to tx_templavoila_ds still has to be done manually (I'll see whether something semi-automatic may be created for TYPO3 4.4) but the rest should be OK.

Bug with "Ungültiger Zeichnen" may be related to a bug I found today in TV (#12721)

Michael, can you confirm this bug still occurs? If so, could you please post an real example how to reproduce this bug? Because you wrote initially that you had to remap tx_templavoila_datastructure to tx_templavoila_ds (which is a must I admit) but then you want tx_templavoila_tmplobj to be remapped to tx_tv_tmplobj which you did not say you added to the mapping configuration. This mapping is not needed but if present, it should work of course.

As such, please update this bug with your mapping information and today's errors if it still doesn't work. TYPO3 4.3 will be out soon and unless you can show me that this bug still occurs, I'll close this bug as for me TV just works smoothly (unless bug #12721 which is located in TV itself).

Thanks for your patience.

I cannot confirm if its still occuring in 4.3, but i am quite sure because the problem is
a DBAL and not a TYPO3 core problem. Means: as long the bug exists in DBAL it exists in TYPO3 :).
The DBAL mapping is just not working correct.

These are my localconf settings

$TYPO3_CONF_VARS['EXTCONF']['dbal']['mapping'] = array (

// TemplaVoila
        'tx_templavoila_datastructure' => array (
            'mapTableName' => 'tx_tv_datastructure',
        ),
        'tx_templavoila_tmplobj' => array (
            'mapTableName' => 'tx_tv_tmplobj',
        ),
);

FYI, this bug will be closed around Christmas - that is in about 2 weeks - if nobody can confirm here that this bug can be reproduced with TYPO3 4.3 and its DBAL version (1.0.2).

A lot of work has been done in the last months on DBAL for the release of TYPO3 4.3.0 and I am running websites with Oracle and TemplaVoilà without having noticed this problem.

Thanks for your understanding.

As already said, lots of work have been done for the release of TYPO3 4.3 and this bug could not be reproduced anymore.