Bug #65997
closedTyposcript causing TCA Error - but not under all circumstances
0%
Description
Hi
I am not sure if this is a bug. It cost me a lot of sweat today.
I received the Exception http://wiki.typo3.org/Exception/CMS/1283790586 when deploying a seemingly upgraded 6.2 (ex 4.5 site) to the live system.
There was extremely legacy TypoScript in this site,
temp.item =CONTENT [globalVar = LIT:1 = {$constant}] temp.item { } [global]
This will throw the above exception, if the constant isn't set to 1.
I think that's fine, as TS is incomplete.
The thing is that this wouldn't happen on the development server, so I only noticed after deploying.
Both systems are on PHP 5.4.
What could be the reason such incomplete TS doesn't trigger an error on one system, but on the other, it does?
Files
Updated by Mathias Schreiber over 9 years ago
- Status changed from New to Needs Feedback
- Assignee set to Mathias Schreiber
Yo Urs,
both systems run in the same context (Dev/Prod)?
Updated by Urs Braem over 9 years ago
Yes, I deployed all files and db 1:1
It wasn't set on production (see screenshot) but nearly.
A possible difference that comes to my mind: the dev system seems to be running an old MySQL Version
dev (where TCA error didnt appear) Ver 14.12 Distrib 5.0.45, for pc-linux-gnu (i686) using readline 6.0
live (where TCA error did appear) Ver 14.14 Distrib 5.5.40, for Linux (x86_64) using readline 5.1
Updated by Alexander Opitz over 9 years ago
- Assignee deleted (
Mathias Schreiber)
This shouldn't have to do with MySQL version, as the error is before requesting data from database.
Is temp.item used in TS before given occurrence?
Updated by Alexander Opitz over 9 years ago
What tablename do you have in your error message?
Updated by Urs Braem over 9 years ago
Hi Alexander
I'm sorry, I can't reproduce it anymore. Let's just close this one, ok?
Thanks for your response to the issue anyway
Urs
Updated by Alexander Opitz over 9 years ago
- Status changed from Needs Feedback to Closed
Ok, thanks for feedback.
You may edit the wiki page and remove your TS code if you can't reproduce the issue.