New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conto Manager Error "Parse error on line 1: Deprecated: Not prov ^ Expected one of: 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE'" #2525 #612
Comments
Looks like your composer.json or composer.lock file has been changed and is not valid anymore. |
I copied one from my other installations which does not have this error and copy pasted the extensions....same error This is my composer.json
|
We've had the same issue recently in Slack. It looks like deprecation warnings are shown, which is likely a (wrong) configuration of the server. |
Ich hatte das Problem heute auch. |
I have several installations at the same hosting. Just two of them show this error. In this case live and dev site of one domain . I will try the advice with cookies |
Delete all cookies of this domain did help...thx |
Hello, i have the same issue. (Contao 4.9.3) it also shows following errors in front and backend. (just visible for me when logged in and debug modus is/was active) Deprecated: Not providing the current time is deprecated. Please pass an instance of DateTimeInterface. in /xxx/public/vendor/lcobucci/jwt/src/Token.php on line 296 Deprecated: Implicit conversion of keys from strings is deprecated. Please use InMemory or LocalFileReference classes. in /xxx/public/vendor/lcobucci/jwt/src/Signer/BaseSigner.php on line 57 |
Can you tell me which configuration exactly? |
I ran into the same issue. After deleting the cookies and in debug mode, I get the following error message:
DomainFactory, PHP 7.3.10, Contao 4.9.9 |
Seems to pop up more frequently in the community now: https://community.contao.org/de/showthread.php?79657-Runtime-Notice-date()-We-selected-Europe-Berlin-for-CET-1-0-no-DST-instead |
I did notice that some server environments do allow |
We are using the default settings on the Hostingwerk servers: ; error_reporting
; Default Value: E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED
; Development Value: E_ALL
; Production Value: E_ALL & ~E_DEPRECATED & ~E_STRICT
error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT |
Yep, and so do most hosters, presumably. And it does not exclude The gist from there is that productive environments should (at least) use |
If I understand you correct in contao/contao#1941 (review) @fritzmg this issue has to and has/will be fixed in Contao core? |
I have also implemented a fix in 4e7e200 that should generally ignore such CLI messages in the Contao Manager. |
That still needs to be discussed. The issue occurs due to the "recommended" PHP error_reporting setting for production environments, which do not exclude E_USER_DEPRECATED. This is not a problem in the front or back end, because Contao sets its own error_reporting setting there. However, the CLI does not adjust this. I have not created an issue or PR about this yet, as I still need to actually test it. |
Disabling error_reporting in my php configuration didnt help. I guess, the problem is the third line in the contao-manager.phar.
I tried to remove the line, but after that the contao manager didnt work anymore. |
Ok, wenn I run the script with shell_exec the PHP settings in the control panel have no effect. So I cant change these settings at my provider. I downloaded the contao-manager.phar.php from https://contao.org/de/download.html but still get the error. Is the file already updated somewhere? |
There is no new release yet. Once released, the Contao Manager will update itself automatically. |
Affected version(s)
Contao 4.10.4
Ionos Hosting
PHP 7.4.12
Description
When i open Contao manager i get an error overlay without having done any changes. 2 days ago there was no error.
When i try to navigate to Maintanance i see the row from debug mode refreshing and when its done the error overlay appears. In the background i can see this strange message.
Errorlog
[26-Nov-2020 11:25:16 Europe/Berlin] [2020-11-26 11:25:16] app.CRITICAL: Uncaught PHP Exception Seld\JsonLint\ParsingException: "Parse error on line 1: Deprecated: Not prov ^ Expected one of: 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '['" at phar:///homepages/46/d346729057/htdocs/meinedomain-dev/web/contao-manager.phar.php/vendor/seld/jsonlint/src/Seld/JsonLint/JsonParser.php line 339 {"exception":"[object] (Seld\\JsonLint\\ParsingException(code: 0): Parse error on line 1:\nDeprecated: Not prov\n^\nExpected one of: 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[' at phar:///homepages/46/d346729057/htdocs/meinedomain-dev/web/contao-manager.phar.php/vendor/seld/jsonlint/src/Seld/JsonLint/JsonParser.php:339)"} []
What i tried since yet
I don´t know how to describe this behaviour better.
The text was updated successfully, but these errors were encountered: