Jump to content

Troubleshooting: Difference between revisions

From Logistack
No edit summary
No edit summary
Line 5: Line 5:
== Reporting Errors ==
== Reporting Errors ==


'''Do not under any circumstance,''' post these errors at our GitHub support, doing this can lead to the hijacking of your website!
'''Do not under any circumstance,''' post PHP errors at our GitHub support, doing this can lead to the hijacking of your website!


For PHP errors, always contact me by email at [http://mailto:lee@venture-logistics.co.uk lee@venture-logistics.co.uk].
== How to Report an Issue ==
 
Logistack includes a detailed error reporting mechanism, that uses the 500 error page.
 
Whenever there's a significant error, or in some circumstances a warning, an error log is created, and the error is shown on that page.


== How to Report an Issue ==
You'll need to be logged as an admin to see this page, all non-admins are redirected to a page asking them to report the incident.


Please include the details below so we can reproduce and fix problems quickly.
In the first instance, copy this message, create a new issue at the GitHub Community, and paste the message.


* '''URL & Page:'''
Remove the path, just leaving the file name.  
* '''Logged-in role/user:''' (e.g., Admin / Manager)
* '''Screenshots'''
* '''Console errors (if any):'''
* '''Network request details (if any):'''
* '''Server/PHP error snippet (if any):'''
* '''Browser & version / device OS:'''


== Using Developer Tools ==
== Using Developer Tools ==

Revision as of 11:31, 13 October 2025

Logistack is stable software with many months of development and testing. I've installed on several environments, both locally and externally, and it should under most circumstances perform perfectly without error. That said, the software, being mostly a back-end platform, includes error reporting code that will create a a snippet of code at the top of the page, giving the reason why the error occurred.

Do not attempt to edit any core (back-end) .php files, it is a fragile language that will, cause an error, and the inability to view the affected page.

Reporting Errors

Do not under any circumstance, post PHP errors at our GitHub support, doing this can lead to the hijacking of your website!

How to Report an Issue

Logistack includes a detailed error reporting mechanism, that uses the 500 error page.

Whenever there's a significant error, or in some circumstances a warning, an error log is created, and the error is shown on that page.

You'll need to be logged as an admin to see this page, all non-admins are redirected to a page asking them to report the incident.

In the first instance, copy this message, create a new issue at the GitHub Community, and paste the message.

Remove the path, just leaving the file name.

Using Developer Tools

Amazing tool that makes debugging a lot easier.

For a video guide on how to use developer tools, see Developer Tools Guide

Privacy & Security

  • Never share API keys, cookies, Authorization headers, or a full JSON Web Token - not even with me!
  • Mask secrets like: sk-****last4.
  • Remove personal data unless it is essential to reproduce the issue.