Project

General

Profile

Actions

Bug #19017

closed

The HTML code is being eaten by HTML parser after migration from TYPO3 4.2

Added by Anton over 14 years ago. Updated over 14 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Communication
Target version:
-
Start date:
2010-06-01
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.4
PHP Version:
4.3
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

I have had a site at TYPO3 4.2.

After I migrated to 4.3 my frontend content screwed up. Details:
1) The template (being parsed by automaketemplate) looses parts of html-code, there is a lot of extra HTML code. Fore example if i have a form and it ends correctly with </form> in template, it looks like </form</form> after TYPO3 parses it.

2) in tt_news records I get many tags visible like <br />, <strong>, & etc
The HTML code is correct, it worked OK with previous TYPO3 version. I tried to change the code many ways, but the code is always eaten somewhere.

Now I upgraded to beta3 of TYPO3 4.4 and it stays precisely the same. Eaten in the same places the same way.

(issue imported from #M14573)

Actions #1

Updated by Chris topher over 14 years ago

I don't think that this is a bug in TYPO3, but a configuration issue.

Please use the mailing lists to find a solution - you will get answers there more quickly than here.

Actions #2

Updated by Anton over 14 years ago

There's just one reason I do not suppose it is a configuration issue. Just to test that out I installed a fresh TYPO-3 4.3 before asking this question. There I installed TemplaVoila template engine. And I took the very same html template from my old site and gave it tp TV to map for me. When It showed me the mapping layout... I saw the very same parts of eaten code...

Actions #3

Updated by Chris topher over 14 years ago

Version 4.2 (where this "bug" would have to be introduced) was released more than 2 years ago. Don't you think that somebody would have found such a devastating bug already a long time ago? Especially, when it breaks the whole website directly after updating? But noone has. I therefore still don't think that there is a parsing bug in TYPO3.

Instead I am convinced you also will make it work; just using a modified template only.

Please use the official mailing lists located at http://lists.typo3.org or a forum of your choice to get further help on that.

Actions

Also available in: Atom PDF