TYPO3 Core

That would mean that the ID of the static template has changed. Can you check this, please?

I'm sorry, let's pretend I'm a noob - what's the quickest way to check this?

You could have compared the IDs with those from your backup, but never mind, I misread your posting. Apparently your problem ist still existing since re-adding did not help.

Can you reproduce the whole thing on a different site?

Sorry again, I only have this one installation. I can give you access if needed.

If you want to help, then please set up a 2nd installation. I will not test this further before.

We got the same problem, but with no static template. Other updates went fine...

If you clear the cache, the first site is redered correctly. If you click on another site you get "No Template Found". If you clear the cache one again, you can see the other site.

We use "Page Template Selector" if this helps...

Hi!

Is this the same as 0005088?

Hello.

I'm also getting this issue using templavoila.

Any update?

Hi!
We (ess-erfurt.de) have exactly the same problem.
The page is visible as long as it is not cached. After the first page entry (which often shows only page type 0 (other pagetypes don't work) you only get "No template found".

If you are logged in as an admin and have FE panel enabled and activated you might have a chance to look at the page..

EDIT: It doesn't matter if your install tool update wizzard is in compatible mode to <=3.8 Even then the error occurs..

Typo 4.1.1 is installed. Site completely in utf-8 (DB, forceCharset etc.)

When "subtitle" field in template contains Russian symbols "No template found!" is generated after page is cached.

To view the page it is necessary to clear the cache but on second page opening error will be displayed again. cache_hash.content is mediumblob in DB so the problem does not relate to 0005088

For me the problem has gone away after updating to 4.1.1. Site is completely in utf-8, languages english, spanish and japanese.

Change type of `content` field to longtext in`cache_hash` table, it helps.

Andreys hint works fine for me. The problem occurred while moving from server to another.
The database was exported (mysqldump) and imported (mysql) with --default-character-set=utf8
TYPO3 4.2.6, MySQL 5.0.75-0ubuntu10.2, PHP Version 5.2.6-3ubuntu4.1

resolved with #21569