Bug #70094
closedsave and preview of backend user section links to home page
100%
Description
steps to reproduce:
1) create a page under the home page, type: backend user section
2) edit page
3) click on save and preview
Result: preview of the home page, instead of the page, with this url:
http://typo3.7.master.it/index.php?id=1&no_cache=1
Note: using a page created or modified in a workspace, I obtained this error:
array(4 items) caller => "TYPO3\CMS\Core\Database\DatabaseConnection::exec_SELECTquery" (60 chars) ERROR => "You have an error in your SQL syntax; check the manual that corresponds to y our MySQL server version for the right syntax to use near 'FROM pages WHERE pid=-1 AND t3ver_oid=0 AND t3ver_wsid=1 AND pages.del' at line 1" (226 chars) lastBuiltQuery => "SELECT FROM pages WHERE pid=-1 AND t3ver_oid=0 AND t3ver_wsid=1 A ND pages.deleted=0 LIMIT 1" (102 chars) debug_backtrace => "call_user_func#34 // {closure}# // TYPO3\CMS\Frontend\Http\Application->run# 33 // TYPO3\CMS\Core\Core\Bootstrap->handleRequest#76 // TYPO3\CMS\Frontend\ Http\RequestHandler->handleRequest#288 // TYPO3\CMS\Frontend\Page\PageGenera tor::renderContent#214 // TYPO3\CMS\Frontend\ContentObject\ContentObjectRend erer->cObjGet#206 // TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer- >cObjGetSingle#795 // TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer ->render#848 // TYPO3\CMS\Frontend\ContentObject\ContentContentObject->rende r#930 // TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer->cObjGetSing le#96 // TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer->cObjGetSing le#830 // TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer->render#848 // TYPO3\CMS\Frontend\ContentObject\CaseContentObject->render#930 // TYPO3\ CMS\Frontend\ContentObject\ContentObjectRenderer->cObjGetSingle#43 // TYPO3\ CMS\Frontend\ContentObject\ContentObjectRenderer->render#848 // TYPO3\CMS\Fr ontend\ContentObject\ContentObjectArrayContentObject->render#930 // TYPO3\CM S\Frontend\ContentObject\ContentObjectRenderer->cObjGet#40 // TYPO3\CMS\Fron tend\ContentObject\ContentObjectRenderer->cObjGetSingle#795 // TYPO3\CMS\Fro ntend\ContentObject\ContentObjectRenderer->render#848 // TYPO3\CMS\Frontend\ ContentObject\CaseContentObject->render#930 // TYPO3\CMS\Frontend\ContentObj ect\ContentObjectRenderer->cObjGetSingle#43 // TYPO3\CMS\Frontend\ContentObj ect\ContentObjectRenderer->render#848 // TYPO3\CMS\Frontend\ContentObject\Hi erarchicalMenuContentObject->render#930 // TYPO3\CMS\Frontend\ContentObject\ Menu\AbstractMenuContentObject->makeMenu#48 // TYPO3\CMS\Frontend\ContentObj ect\Menu\AbstractMenuContentObject->prepareMenuItems#424 // TYPO3\CMS\Fronte nd\ContentObject\Menu\AbstractMenuContentObject->prepareMenuItemsForDirector yMenu#562 // TYPO3\CMS\Frontend\Page\PageRepository->versionOL#715 // TYPO3\ CMS\Frontend\Page\PageRepository->getWorkspaceVersionOfRecord#1367 // TYPO3\ CMS\Core\Database\Databa..." (2167 chars)
Updated by Andreas Schosser about 9 years ago
We encountered the same error on TYPO3 6.2.15.
After downgrading to 6.2.14 all worked well. So I assume that this error has been introduced with 6.2.15.
Andreas
Updated by stephen leger about 9 years ago
Hi,
Get same error here under 6.2.14 and 6.2.15
Edit any page under draft workspace lead to such error while previewing.
require(po3_src-6.2.15/typo3/sysext/cms/tslib/index_ts.php),po3_src-6.2.15/index.php#28 // TYPO3\CMS\Frontend\Page\PageGenerator::renderContent#212 // TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer->cObjGet#214 // TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer->cObjGetSingle#697 // TYPO3\CMS\Frontend\ContentObject\FluidTemplateContentObject->render#752 // TYPO3\CMS\Frontend\ContentObject\FluidTemplateContentObject->renderFluidView#76 // TYPO3\CMS\Fluid\View\AbstractTemplateView->render#267 // FluidCache_Standalone_layout_homepage_03e0c27f82fda2142a8954cf37faba846d8ebce0->render#182 // TYPO3\CMS\Fluid\Core\ViewHelper\AbstractViewHelper->initializeArgumentsAndRender#41 // TYPO3\CMS\Fluid\Core\ViewHelper\AbstractViewHelper->callRenderMethod#230 // call_user_func_array#248 // TYPO3\CMS\Fluid\ViewHelpers\RenderViewHelper->render# // TYPO3\CMS\Fluid\View\AbstractTemplateView->renderSection#90 // FluidCache_Standalone_template_file_homepage_1e1c102ccd772128b6f9246423b926fe5f18e44b->section_594fd1615a341c77829e83ed988f137e1ba96231#222 // TYPO3\CMS\Fluid\Core\ViewHelper\AbstractViewHelper->initializeArgumentsAndRender#43 // TYPO3\CMS\Fluid\Core\ViewHelper\AbstractViewHelper->callRenderMethod#230 // call_user_func_array#248 // TYPO3\CMS\Fluid\ViewHelpers\RenderViewHelper->render# // TYPO3\CMS\Fluid\View\AbstractTemplateView->renderPartial#88 // FluidCache_Standalone_partial_homepage_header_964bbbfc0e5e4f83ae64da0f9d8bc70af94ffdb4->render#279 // TYPO3\CMS\Fluid\Core\ViewHelper\AbstractViewHelper->initializeArgumentsAndRender#42 // TYPO3\CMS\Fluid\Core\ViewHelper\AbstractViewHelper->callRenderMethod#230 // call_user_func_array#248 // TYPO3\CMS\Fluid\ViewHelpers\CObjectViewHelper->render# // TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer->cObjGetSingle#117 // TYPO3\CMS\Frontend\ContentObject\ContentObjectArrayContentObject->render#752 // TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer->cObjGet#40 // TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer->cObjGetSingle#697 // TYPO3\CMS\Frontend\ContentObject\HierarchicalMenuContentObject->render#752 // TYPO3\CMS\Frontend\ContentObject\Menu\AbstractMenuContentObject->makeMenu#48 // TYPO3\CMS\Frontend\Page\PageRepository->versionOL#451 // TYPO3\CMS\Frontend\Page\PageRepository->getWorkspaceVersionOfRecord#1199 // TYPO3\CMS\Core\Database\DatabaseConnection->exec_SELECTgetSingleRow#1347 // TYPO3\CMS\Core\Database\DatabaseConnection->exec_SELECTquery#406 // TYPO3\CMS\Core\Database\DatabaseConnection->debug#305
Updated by Thomas Oliver Moll about 9 years ago
Same over here with 6.2.15.
It seems the error can be safly ignored but when debuging is on, the messages annoys the users
Updated by Gerrit Code Review over 8 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/48036
Updated by Riccardo De Contardi over 8 years ago
[UPDATE] As far as I can see there is no problem on 6.2.22; on 8.2-dev I am not able to reproduce the ugly workspace error (but the preview is still wrong) - I am testing the patch
Updated by Gerrit Code Review over 8 years ago
Patch set 1 for branch TYPO3_7-6 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/48039
Updated by Wouter Wolters over 8 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 8fe33996357569d32aa2c8c653616938a6ba7ed3.