Actions
Bug #55989
closedDebug "Column 'cookie' cannot be null"
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Indexed Search
Target version:
-
Start date:
2014-02-14
Due date:
% Done:
100%
Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.3
Tags:
Complexity:
easy
Is Regression:
Yes
Sprint Focus:
Description
Function writeSearchStat of SearchFormController.php triggers a debug message in FE, because $this->fe_user->id resolves to NULL and cookie is a non-null column.
(possibly the same will happen in SearchController.php)
$insertFields = array( 'searchstring' => $this->piVars['sword'], 'searchoptions' => serialize(array($this->piVars, $sWArr, $pt)), 'feuser_id' => (int)$this->fe_user->user['uid'], // fe_user id, integer 'cookie' => $this->fe_user->id, // cookie as set or retrieve. If people has cookies disabled this will vary all the time... 'IP' => GeneralUtility::getIndpEnv('REMOTE_ADDR'), // Remote IP address 'hits' => (int)$count, // Number of hits on the search. 'tstamp' => $GLOBALS['EXEC_TIME'] );
This seems to have started after 6.2.0beta3
Updated by Markus Klein almost 11 years ago
- Status changed from New to Accepted
This is due to the patch that allowed to insert NULL values into DB.
From time to time some place popup where the insert was not constructed properly, like here.
Can you push a patch?
Updated by Markus Klein almost 11 years ago
- Complexity set to easy
- Is Regression changed from No to Yes
Target versions are all 6.x
Updated by Gerrit Code Review over 10 years ago
- Status changed from Accepted 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/28281
Updated by Georg Ringer over 10 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 34fcdead654333f207ff479cf70fecb9d53e081b.
Actions