Publisher does not support the Fluid field type. Please do not contact asking when support will be available.
If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.
Ticket: On/Off Toggle for Developer Logging
| Status | Resolved |
| Add-on / Version | Bloqs 4.11.0 |
| Severity | |
| EE Version | 5+ |
Paul Larson
Feb 09, 2022I’m doing some housekeeping on a few sites w/ Bloqs, and a few have bloated dev logs. It’d be nice to have a toggle for this; even with logs restricted to logged in users with CP access, the log volume can ramp up quickly, as shown below.
https://www.dropbox.com/s/692jbum7bfgb5wk/2022-02-09_10-33-52.png?dl=0
Paul Larson
Feb 09, 2022
I knew this felt like deja vu:
https://boldminded.com/support/ticket/2351
BoldMinded (Brian)
Feb 09, 2022
Try the build in the next comment. The same rules apply as that previous ticket, it’ll only write to the log if the current user can access the CP, but this build won’t add a new row to the dev log table for each occurrence, it’ll just update the same log item as unread, so it looks new.
BoldMinded (Brian)
Feb 09, 2022
Comment has been marked private.
Paul Larson
Feb 09, 2022
Will do! Realized these sites needed a Bloqs update _and_ their historical logs might be the problem, and weren’t reflecting how the recent build might reduce it.
Thanks!
BoldMinded (Brian)
Feb 24, 2022
Closing this out. The latest release only logs if the user has CP access and it will not add excessive rows to the logs. It uses EE’s feature to just update the original logged item with a new timestamp.