[TYPO3-templavoila] lost of CE header and system warning!!!

Alessandro Canè canet at canet.it
Tue Jan 13 17:54:10 CET 2009


hi list,

every time a NOT ADMIN user tries to insert any kind of content on a page,
he gets this error on the backend and desired new content SEEMS not to be
created:

Warning: array_merge() [function.array-merge]: Argument #1 is not an array
in /.../public_html/typo3conf/ext/templavoila/class.tx_templavoila_api.php
on line 223
Warning: Cannot modify header information - headers already sent by (output
started at /.../typo3conf/ext/templavoila/class.tx_templavoila_api.php:223)
in /.../public_html/typo3conf/ext/templavoila/mod1/index.php on line 1773
Warning: Cannot modify header information - headers already sent by (output
started at
/.../public_html/typo3conf/ext/templavoila/class.tx_templavoila_api.php:223)
in /.../public_html/typo3conf/ext/tm_shared_lib/class.ux_template_4_2.php on
line 430

He needs to reload the page (just clickin on that page on the site tree) to
see the new content appear (and disappear the warnings)...
BUT AT THIS POINT WHEN HE GETS INTO THE ELEMENT HEADER IS NOT PRESENT...

This happens using T3 version 4.2.2 AND ext. tm_shared_lib version 1.0.9




MY SECOND ATTEMPT:

if I try after having tm_sahred_lib REMOVED, the behaviour stays the same,
just the error changes to this:

Warning: array_merge() [function.array-merge]: Argument #1 is not an array
in /.../public_html/typo3conf/ext/templavoila/class.tx_templavoila_api.php
on line 223
Warning: Cannot modify header information - headers already sent by (output
started at
/.../public_html/typo3conf/ext/templavoila/class.tx_templavoila_api.php:223)
in /.../public_html/typo3conf/ext/templavoila/mod1/index.php on line 1773
Warning: Cannot modify header information - headers already sent by (output
started at
/.../public_html/typo3conf/ext/templavoila/class.tx_templavoila_api.php:223)
in /.../typo3_src-4.2.2/typo3/template.php on line 632

One thing I cannot understand is why it does not happen to an admin...
I've cleaned al the user-configs I thought could be "dangerous" too!
It doesn't seem to me this could be a coding issue...


Any idea on why does it acts like this?
Please help!

----------------------------------------
Canè Alessandro


More information about the TYPO3-project-templavoila mailing list