Troubleshooting: Difference between revisions
Lee Miller (talk | contribs) |
Lee Miller (talk | contribs) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
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. | 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. | ||
<span class="fw-bold text-danger">Do not attempt to edit any core (back-end) .php files,</span> it is a fragile language that will, cause an error, and the inability to view the affected page. | |||
== Reporting Errors == | == Reporting Errors == | ||
| Line 18: | Line 18: | ||
<span class="fw-bold text-danger">Remove the path</span>, just leaving the file name. | <span class="fw-bold text-danger">Remove the path</span>, just leaving the file name. | ||
Visit support @ https://github.com/venture-logistics/logistack/issues | |||
== Using Developer Tools == | == Using Developer Tools == | ||
| Line 27: | Line 29: | ||
== Privacy & Security == | == Privacy & Security == | ||
* | * <span class="fw-bold text-danger">Never share API keys, cookies, Authorization headers, or a full JSON Web Token</span> - not even with me! | ||
* Mask secrets like: <code>sk-****last4</code>. | * Mask secrets like: <code>sk-****last4</code>. | ||
* Remove personal data unless it is essential to reproduce the issue. | * Remove personal data unless it is essential to reproduce the issue. | ||
Latest revision as of 03:14, 14 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.
Visit support @ https://github.com/venture-logistics/logistack/issues
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.