You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know why exactly this happens, but for almost every request to my Nextcloud instance, it seems that somehow Pico CMS is invoked, and the following appears in the logs:
{"reqId":"2DssyqSnEWAeV5NzMsrk","level":0,"time":"2022-12-14T09:43:49+00:00","remoteAddr":"xxx","user":"xxx","app":"cms_pico","method":"PROPFIND","url":"/remote.php/dav/files/[...]/","message":"/appinfo/app.php is deprecated, use \\OCP\\AppFramework\\Bootstrap\\IBootstrap on the application class instead.","userAgent":"Mozilla/5.0 (Android) Nextcloud-android/3.23.0","version":"25.0.2.3","data":{"app":"cms_pico"}}
This leads to significant log spam.
I think the right way would be to switch to IBoostrap, but it might be sufficient for now to make sure that Pico CMS is only invoked, when a request to a Pico site is done and not for every other.
The text was updated successfully, but these errors were encountered:
This is a debug log message and not supposed to show up in production. Lower your log level resp. disable debug mode. Keeping this open to track when we choose to switch to IBootstrap later.
Ah you are totally right.
In my case it was not the debug mode that was active, but instead i had the loglevel set to 0.
After switching it to 1, everything is fine.
joshtrichards
changed the title
Log spam: appinfo/app.php is deprecated
Eliminate deprecated appinfo/app.php
Jun 14, 2024
I don't know why exactly this happens, but for almost every request to my Nextcloud instance, it seems that somehow Pico CMS is invoked, and the following appears in the logs:
This leads to significant log spam.
I think the right way would be to switch to IBoostrap, but it might be sufficient for now to make sure that Pico CMS is only invoked, when a request to a Pico site is done and not for every other.
The text was updated successfully, but these errors were encountered: