Bug #24175
closedmySQL statement CONTENT object previewlink is wrong (with left join + alias )
0%
Description
When I use an alias in a CONTENT object with SQL debugging in de back-end, the previewpage always shows a mySQL error saying there's an Unknown column '[my defined alias]' in 'field list'. When I checkout the error message, it's plain to see that the mySQL statement is missing the 'left join' and the 'as' parameters.
Everything works fine in the front-end. A deliberate typo in the selectFields shows a correct SQL statement with 'left join' and 'as', like there should be.
hope anyone can help me:
my typoscript can be found here: http://pastebin.com/embed_iframe.php?i=78AXr3tt
preview page:
ERROR
Unknown column 'plo_title' in 'field list'
lastBuiltQuery
SELECT title,nav_title,plo_title,plo_nav_title FROM pages WHERE pid=-1 AND t3ver_oid=0 AND t3ver_wsid=6 AND pages.deleted=0
---------------------------------------------------------------------
front-end
ERROR
Unknown column 'deliberateTypo' in 'field list'
SELECT deliberateTypo, pages.title as title, pages.nav_title as nav_title, plo.title as plo_title, plo.nav_title as plo_nav_title FROM pages LEFT OUTER JOIN pages_language_overlay plo on (pages.uid = plo.pid) WHERE pages.pid IN (92) AND pages.uid =54 AND pages.deleted=0 AND pages.hidden=0 AND pages.starttime<=1290517380 AND (pages.endtime=0 OR pages.endtime>1290517380) AND NOT pages.t3ver_state>0 AND pages.doktype<200 AND (pages.fe_group='' OR pages.fe_group IS NULL OR pages.fe_group='0' OR (pages.fe_group LIKE '%,0,%' OR pages.fe_group LIKE '0,%' OR pages.fe_group LIKE '%,0' OR pages.fe_group='0') OR (pages.fe_group LIKE '%,-1,%' OR pages.fe_group LIKE '-1,%' OR pages.fe_group LIKE '%,-1' OR pages.fe_group='-1')) LIMIT 1
(issue imported from #M16529)
Updated by Rutger Rek about 14 years ago
btw, this only seems to occur in a draft workspace with versioning
Updated by Alexander Opitz about 11 years ago
- Status changed from New to Needs Feedback
- Target version deleted (
0) - Is Regression set to No
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?
Updated by Alexander Opitz over 10 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this ticket.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.