TYPO3 Core

works great
thank you

resolved in svn rev. 6365

there are problems reported in dev list, therfore i reopened the entry

Problem: I get 'No TypoScript template found!' in FE with this patch.

This error occurs with all my WebSites (all with 4.3 latest trunk) on my dev-server (Debian lenny, Php5.3).

I always use a plugin, that hold my complete TypoScript and all Templates for a website. So I do it always the same:
Plugin's TS has always something like
lib.myWebsite.defaultPage = PAGE
lib.myWebsite.defaultPage {
typeNum = 0
...
And the only thing in the Root-Template that I insert, is:
page < lib.myWebsite.defaultPage

How to reproduces (on my Testsites):
1. Clear all cache
2. View in FE works: renedered o.k.
3. Reload in FE: allways error 'No TypoScript template found!'

Btw.:
Removing the call to $this->procesIncludes(); in line 513 fixes the problem for me.

Additional Note:
Setting
$TYPO3_CONF_VARS['SYS']['useCachingFramework'] = '1';
fixes this issue.

Nevertheless, it should also work with CachingFramework disabled.

You should check what character encoding the included files have, and if there are any umlauts in them.

If there are some, you could try to convert them to utf-8 to see if this resolves your problem.

Of course something has to be done about including iso-8859-1 files when the system is set to UTF-8. I'll try to find a solutin tomorrow.

OK, I finally found this:

all my (selfmade) plugins do contain a TS-Setup file
ext_typoscript_setup.txt
for the realy basic configurations.
(I know, static-templates are the preferred ones, but I love to have the needed_ basic settings in ext_typoscript_setup.txt ...)

One of these plugins realy had an Umlaut-character and was not saved as utf8.
Changing this file to utf8 resolves the problem.

So I move further discussion to Thread http://bugs.typo3.org/view.php?id=12549 and this one can be closed again.

Hello again,

I just uploaded a file "tstemplate_charset.diff". Try to apply this to the latest version (RC1). In your case it should show an error message (yellow box) telling you that there was an error caching the templates, and you should check the charset of included TypoScript files:

------------
Error while caching TypoScript template!
Check charset of included TypoScript files!
------------

What you can do then is to change the file to utf-8, or set an attribute charset="" in your <INCLUDE_TYPOSCRIPT ...> tag like:

<INCLUDE_TYPOSCRIPT:source="FILE:EXT:tvt_nightshots/typoscript/setup.txt" charset="iso-8859-1">

Right - I get the mentioned error-message.
But it would be nice to see the path/name of the TS-File (at least the first TS-file that has wrong charset) ...

Thank you for the patch. I tried it, and I have 2 remarks:

After applying the patch I get a fatal error in the backend:
"Fatal error: Call to a member function conv() on a non-object in t3lib/class.t3lib_tsparser.php on line 542"

A simple check if $GLOBALS['TSFE']->csConvObj is null before calling the conf() method solves this problem.

Another problem are the ext_typoscript_setup.txt files. I think for a normal user it can be very confusing when he installs an extension an then gets the charset error message without any more hints.

Find a patch for this behaviour in issue #21569 (0012613_v2.patch).
In the long term view it would be good to have automatic conversion of external files if they don't match the used character encoding.