Need to support separate trace files for WordPress MultiSite sites

bobbingwide / oik-bwtrace

debug trace for WordPress

https://www.oik-plugins.com/oik-plugins/oik-bwtrace-debug-trace-for-wordpress/

GNU General Public License v2.0

6 stars 1 forks source link

Need to support separate trace files for WordPress MultiSite sites #27

Open bobbingwide opened 8 years ago

bobbingwide commented 8 years ago

The current solution does not take into account the fact that the installation may be WordPress MultiSite. There are times where it's OK for all the trace output to be written to one file and other times where it's not.

We should allow for using different files for MultiSite

[ ] when tracing at startup
[x] and in the daily trace summary report.

bobbingwide commented 8 years ago

It would be nice if the site_id were included in the trace output in a WPMS installation. Also, when tracing batch processing, the selection of the trace file should depend on the site that's selected through the url= parameter.

bobbingwide commented 8 years ago

For a multisite site which is not the primary site ( blog_id not 1 ) then the daily trace summary file will be bwtrace.vt.mmdd.blog_id.

There may be a lot of files but each will only record the activity for the given blog id.

bobbingwide commented 4 years ago

Just to confirm that this is now documented. For Daily Trace Summary reports the date format is now ccyymmdd. Since the file is not written until shutdown the blog_id will be known.

For other trace files there could still be some confusion as to which file to use. This has to be taken into consideration in the solution for #82