[TYPO3-templavoila] 1.3.7 -> 1.4.1: Template Object could not be unserialized successfully.

Thomas Russel blueworm01 at gmx.net
Thu Dec 3 14:53:39 CET 2009

Yeh, all mapping are gone :-/
Thank god that it's only on a test box.

QUESTION -> Would this help (BEFORE the TV update):

In the 'Install'-tool, enable the checkbox in [UTF8filesystem].

Then edit all TO (template objects) ->click-> modify TO/DO. As all 
mappings are still there (because it's still 1.3.7), I would just save 
the template object again. Would Typo3 then save it correctly as UTF-8 ?

Xavier Perseguers schrieb:
> Hi,
>> I just updated from 1.3.7 to 1.4.1 and all I get at the FE now is:
>> TemplaVoila ERROR:
>> Template Object could not be unserialized successfully.
>> Are you sure you saved mapping information into Template Object with 
>> UID "1"?
>> Since there is no updated documentation on what to consider/update 
>> during an update, I would appreciate any help here.
> I guess this is due to the templatemapping field having been changed 
> from mediumtext to blob in table tx_templavoila_tmplobj. If you had 
> accentuated characters in your template and not a UTF8 configured 
> backend, I guess this is the error you get.
> This problem is typically due to a character set transformation problem.

More information about the TYPO3-project-templavoila mailing list