When the trace files directory is accessible though your web server you may be able to use your browser to view the trace files and daily trace summary files. If you can’t use the browser, then you will have to view them from the back end.
Viewing files with the browser
Viewing trace files in the browser
- Open your browser
You may want to open a new tab or window, or use a different browser.
- Navigate to the trace files directory
e.g.
https://s.b/wordpress/bwtraceIf you see the WordPress Not Found ( 404 ) page then this implies the folder’s permissions do not allow access.
If
.htaccessauthentication has been implemented you will need to enter your username and password before you see the directory listing. - Choose the file to view
Select a file to view and click on it. If you don’t know which file to view pick the daily trace summary file.
- Browse the Daily Trace Summary file
View the daily trace summary file to see which transactions have been run and find the trace file name for the transaction you’re interested in.
- Browse the trace file
Use your browser’s find function to help locate the trace record’s you’re interested in.
Notes
- The web server will need to be configured to allow directory listings.
- If the folder is protected with the appropriate
.htaccessand.htpasswdfiles then only valid users will be able to see the files.
See also
Viewing files in the back end
When the trace files directory is not accessible from the browser then you have to view the trace files from the backend.
In a local development environment you can use your file manager. e.g. Explorer.
If they’re on a Linux server then you will either need to ftp the files or ssh to the server and browse them there.
Summary of viable access methods
Protecting your trace files directory
On a staging or live server the trace files directory can be protected using Htaccess Authorisation.
