Closed qzminski closed 6 years ago
We should also try to find the root cause here.
The active record is set in line 997 if the article ID is valid. So the problem seems to be that $intId
is not pointing to a valid database record in your case.
Do you have the corresponding request URL?
Yep, here is the curl:
curl \
--compressed \
-H "Accept: application/json" \
-H "Accept-Encoding: gzip, deflate, br" \
-H "Accept-Language: de-DE,de;q=0.9,en-US;q=0.8,en;q=0.7" \
-H "Connection: close" \
-H "Host: domain.tld" \
-H "Referer: https://domain.tld/" \
-H "User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36" \
-H "X-Accel-Internal: /internal-nginx-static-location" \
-H "X-Real-Ip: 212.90.203.26" \
-H "X-Request: JSON" \
-H "X-Requested-With: XMLHttpRequest" \
"https://domain.tld/contao?do=article&rt=R2yszlX-uqfrmn7HHq8bco931Pp-S2XC9ynJCUqsZuQ&ref=KesWCDcD&tid=1504&state=1&rt=R2yszlX-uqfrmn7HHq8bco931Pp-S2XC9ynJCUqsZuQ"
We logged only 2 events in total though and the issue hasn't been seen for 2 months now.
I couldn't reproduce this one. It's an ajax request that toggles the eye icon in the article tree view (according to the request details) but it's also strange why rt
is added twice to the URL so no idea how that could happen. Let's close that one and see if we find a reproducible case somewhen.
Agreed.
We have the below exception logged in the Sentry. Although I am not sure what exactly causes the problem, it should still be prevented.