Actions
Bug #68172
closedUnknown column 'storage_pid' in 'field list'
Status:
Closed
Priority:
Must have
Assignee:
Category:
Backend User Interface
Target version:
Start date:
2015-07-15
Due date:
% Done:
100%
Estimated time:
TYPO3 Version:
7
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:
Description
I did a fresh checkout of the current master branch and get the following error, as soon as the page module is opened. It seems, that the formerly removed column "storage_pid" is still used somewhere in TYPO3 7.4-dev.
Please note, that the error does not apprear, if you had installed compatibility6 extension and did'nt remove unused fields in the install tool, as the field "storage_pid" remains in the "pages" table.
array(4 items) caller => "TYPO3\CMS\Core\Database\DatabaseConnection::exec_SELECTquery" (60 chars) ERROR => "Unknown column 'storage_pid' in 'field list'" (44 chars) lastBuiltQuery => "SELECT pid,uid,title,doktype,TSconfig,is_siteroot,storage_pid,t3ver_oid,t3ve r_wsid,t3ver_state,t3ver_stage,backend_layout_next_level FROM pages WHERE ui d=1 AND pages.deleted=0 AND 1=1" (184 chars) debug_backtrace => "call_user_func#25 // TYPO3\CMS\Backend\{closure}# // TYPO3\CMS\Backend\Http\ Application->run#24 // TYPO3\CMS\Core\Core\Bootstrap->handleRequest#90 // TY PO3\CMS\Backend\Http\BackendModuleRequestHandler->handleRequest#286 // TYPO3 \CMS\Backend\Http\BackendModuleRequestHandler->callTraditionalModule#87 // r equire(po3/sysext/backend/Modules/Layout/index.php),po3/sysext/backend/Class es/Http/BackendModuleRequestHandler.php#184 // TYPO3\CMS\Backend\Controller\ PageLayoutController->init#16 // TYPO3\CMS\Backend\Utility\BackendUtility::r eadPageAccess#325 // TYPO3\CMS\Backend\Utility\BackendUtility::getRecordPath #722 // TYPO3\CMS\Backend\Utility\BackendUtility::BEgetRootLine#461 // TYPO3 \CMS\Backend\Utility\BackendUtility::getPageForRootline#332 // TYPO3\CMS\Cor e\Database\DatabaseConnection->exec_SELECTquery#384 // TYPO3\CMS\Core\Databa se\DatabaseConnection->debug#307" (868 chars)
After installing the "compatibility6" extension, the error message is not shown any more.
Actions