Skip to content

v3.0.0 - Improved control over tracing and GDPR considerations

  
0

To Do

0

In progress

14

Done

This project doesn’t have any columns or cards.

Menu

v3.0.0 - Improved control over tracing and GDPR considerations #1

  
Updated Dec 13, 2019
With the increased use of the REST API we need to improve our control of what gets traced and where it gets traced to. There are 4 main ways that WordPress logic is invoked to satisfy a request.

With the increased use of the REST API we need to improve our control of what gets traced and where it gets traced to. There are 4 main ways that WordPress logic is invoked to satisfy a request.

  1. Normal browser - front-end and admin and HTTP requests from other servers
  2. AJAX requests
  3. REST requests
  4. Command line interface

Most WordPress specific debugging tools don't help developers to follow what's going on in 2., 3. and 4. oik-bwtrace v3.0.0 will do!

Some of the code will be refactored from procedural to object oriented.

For GDPR we need to ensure that trace files are not publicly accessible. All trace files will now be stored in a Trace files directory. Tracing will not be supported if this is not set or is an invalid directory.

The changes are enough for the semantic versioning to be changed to v3.0.0. We're skipping over v2.2.0 - which was used in an alpha version in April 2018

Activity

    Loading activity

Archived cards

Loading archived cards…

You can’t perform that action at this time.