Actions
Bug #67350
closedPHP Warning: preg_match(): Compilation failed: internal error: previously-checked referenced subpattern not found at offset 1963
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Fluid
Target version:
-
Start date:
2015-06-08
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.5
Tags:
Complexity:
Is Regression:
No
Sprint Focus:
Description
With TYPO3 6.12 (not with the versions before) I allways get a PHP warning in some backend modules (e.g. Extension Manager, Install Tool...) and in the frontend:
#1: PHP Warning: preg_match(): Compilation failed: internal error: previously-checked referenced subpattern not found at offset 1963 in /pathto/typo3_src-6.2.12/typo3/sysext/fluid/Classes/Core/Parser/TemplateParser.php line 813
That is this line:
if (preg_match(self::$SCAN_PATTERN_SHORTHANDSYNTAX_OBJECTACCESSORS, $section, $matchedVariables) > 0) {
When I set SYS['displayErrors'] = 0, I get this Message:
Oops, an error occurred! This exception should never be thrown, there is most likely some error in the regular expressions. Please post your template to the bugtracker at forge.typo3.org.
When I set FE['debug'] = FALSE, I get this error:
#1237900529: The argument "triggers" was registered with type "array", but is of type "string" in view helper "TYPO3\CMS\Extensionmanager\ViewHelpers\Be\TriggerViewHelper"
Or here antoher example:
Oops, an error occurred! The argument "arguments" was registered with type "array", but is of type "string" in view helper "TYPO3\CMS\Fluid\ViewHelpers\RenderViewHelper"
Updated by Markus Klein over 9 years ago
- Status changed from New to Needs Feedback
- Complexity deleted (
medium)
Which PHP version exactly and which server OS?
Updated by Kurt Gusbeth over 9 years ago
I guess it is not an error of TYPO3 6.12. I downgraded and the error is still there.
It must be a problem of the server. You can close this bug therefore.
Updated by Kurt Gusbeth over 9 years ago
PHP Version 5.5.25-1~dotdeb+7.1 (Debian server).
Updated by Markus Klein over 9 years ago
- Status changed from Needs Feedback to Closed
Yep, duplicate of #67048
Updated by Kurt Gusbeth over 9 years ago
Better you reopen the bug.
I think the reason for the problem is a PHP update from PHP 5.5.x to 5.5.25.
Updated by Markus Klein over 9 years ago
Please comment on the original issue. This is a duplicate.
Actions