Bug #17449
closed
Clearing cache renders content incorrectly/incompletely
Added by Peter Murray over 17 years ago.
Updated over 11 years ago.
Category:
Content Rendering
Description
Updating the template or clearing the cache breaks the rendering of the page. Some parts of the template are not substituted.
For example all content elements (from temp or styles.content.get) that should go into subparts of the template identified by DIV are not substituted in. Content elements that should go into subparts identified by TD do work.
In the template I have:
- Configuring the Auto-Parser for main template:
plugin.tx_automaketemplate_pi1 {
# Read the template file:
content = FILE
content.file = fileadmin/templates/maintemplate.htm
- Here we define which elements in the HTML that
- should be wrapped in subpart-comments:
elements {
HEAD.all = 1
HEAD.all.subpartMarker = DOCUMENT_HEADER
HEAD.rmTagSections = title
BODY.all = 1
BODY.all.subpartMarker = DOCUMENT_BODY
DIV.all = 1
TD.all = 1
}
- Prefix all relative paths with this value:
relPathPrefix = fileadmin/templates/
}
- Main TEMPLATE cObject for the BODY
temp.mainTemplate = TEMPLATE
temp.mainTemplate {
# Feeding the content from the Auto-parser to the TEMPLATE cObject:
template =< plugin.tx_automaketemplate_pi1
# Select only the content between the <body>-tags
workOnSubpart = DOCUMENT_BODY
#Top
subparts.title < temp.title
subparts.topmenu < temp.topmenu
#Left column
subparts.left < styles.content.getLeft
#Center column
subparts.normal < styles.content.get
subparts.teaser < temp.teaser
subparts.bottommenu < temp.bottommenu
#Right column
subparts.right < styles.content.getRight
#Footer
subparts.copyright < temp.copyright
subparts.languagechooser < temp.languagechooser
}
Only the subparts.copyright and subparts.languagechooser are displaying with content.
The site has been working OK, but broke when clearing the cache.
(issue imported from #M5917)
TYPO3 Version 4.1.1
automaketemplate Version 0.1.0 local
Sounds pretty strange, and it's quite difficult to make a golden guess.
I suggest that you disable all local extensions first to identify if this is really a problem of TYPO3core.
I have disabled all the local extensions and still the same problem.
This is happening again with another site after adding the CMW Linklist extension.
The template has:
- Configuring the Auto-Parser for main template:
plugin.tx_automaketemplate_pi1 {
# Read the template file:
content = FILE
content.file = fileadmin/templates/default.htm
- Here we define which elements in the HTML that
- should be wrapped in subpart-comments:
elements {
HEAD.all = 1
HEAD.all.subpartMarker = DOCUMENT_HEADER
HEAD.rmTagSections = title
BODY.all = 1
BODY.all.subpartMarker = DOCUMENT_BODY
TD.all = 1
DIV.all = 1
UL.all = 1
}
- Prefix all relative paths with this value:
relPathPrefix = fileadmin/templates/
}
Only the UL tags are being substituted with content. The DIV tags still have the HTML template content.
The automake template substitution was working perfectly before clearing the cache as part of installing the extension.
Steps to resolve the problem:
Clear caches = no difference.
Uninstall CMW Linklist extension = no difference.
Compare and update the database using the INSTALL tool database analyser = no difference.
Delete files from /typo3temp/ using the INSTALL tool = no difference.
Clean up database using the INSTALL tool = no difference.
Further steps to solve the problem:
Upgraded to TYPO3 version 4.1.2 = no difference.
The problem appears to be related to character sets and the conversion of data from lowercase to uppercase and back again.
I was using UTF-8 for everything except for rendering the page. My TypoScript was setting config.locale to Turkish for the default language. Removing the config.locale setting has solved the problem, but perhaps there are deeper issues that should be examined and addressed in this and other related TYPO3 code.
In Turkish there are dotted and undotted i characters. The capital of the undotted i is the same as the English capital I. The capital of the dotted i is a different character. This means that if TYPO3 converts the case of the DIV tags during the template substitution then the spelling may be affected and tags would not be recognized.
Hi Peter,
| I was using UTF-8 for everything except for rendering the page.
would it be an option to use it everywhere? Also make sure to check the MySQL settings according to my description in #6098.
- michael
This bug may be related to #0007901.
- Status changed from New to Needs Feedback
- Target version deleted (
0)
- TYPO3 Version set to 4.1
The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?
Using UTF-8 has solved this issue and it does not exist in current TYPO3 CMS versions.
- Status changed from Needs Feedback to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by