BBloke
commented
3 years ago Hi Leonie,
I know we bounced this around but you fired something up and the answer in the mean time, without having a switch to turn them off, is to take any PHx placeholders out where possible and replace IF.
I also have a feeling that there are PHx placeholders in certain snippets, i.e. AjaxSearch, which will give the same issues.
I never figured out whether the errors where always generated because the was a DocLister call on a page/template containing PHx calls. I feel that DocLister, whilst being the reason for them (because of plugin version being v2.2.0) it's only because as a whole web page there are other PHx calls that Evo and trips a system event.
Seems to be the same as #1336:
Since upgrading some of my websites to Evo 3.x the system logs are being filled with hundreds of entries resulting from phx 2.2.0 which seems to be assets/snippets/DocLister/lib/DLphx.class.php.
These log entries show always the results of the phx parser. They are filling my database in days with some hundred MB. I could til now not find out why phx is logging every page call nor do I have any idea how to stop phx from logging.
On one website the installed phx plugin version is 2.2.2. In the system events log is written phx 2.2.0 as the origin of the log. 2.2.0 is the version which is delivered with DocLister. Deactivating "normal" plugin phx does not change the accumulation of log entries.
With 1.4.x everything worked without hassle. Since 3.x the log is cluttered. In regards of backwards compatibility this should not be. And because the log entries are informational and no warnings or errors there is also no necessity for them. I miss the switch to turn them off like it is in the configuration of the "normal" phx plugin.