-
Notifications
You must be signed in to change notification settings - Fork 38
DEBUG setting not honoured #113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hmm, thanks for raising the issue. This is a new feature with v1.4.0, I've not seen this happen before in testing though. Let me take a look tomorrow. |
Wondering if you could try deleting the contents of the cache directory? |
Also can you exec into the container and check if the DEBUG environment variable is definitely false? You shouldn't have to specify it at all as the app sets debug to false internally if the environment variable isn't set. |
I'll do these actions tomorrow. If they don't fix it, I'd put money on it being the classic bug where a value of "false" appears to be true because it is a non-empty string 😄 |
You know what it probably is! I've even written and used a method to parse booleans from the yaml... jump/jumpapp/classes/Config.php Line 142 in 465d9b9
But looks like I've forgotten to use it here... Line 47 in 465d9b9
|
I think you've found the smoking gun, but for the sake of completeness...
I also couldn't find a cache dir anywhere under |
I've added the proper boolean check mentioned above, I'll create a new release later for it. In terms of the cache, the default directory is... |
Yes I'm using the stock docker image. I found and deleted the application cache. It didn't fix the problem with debug mode, but it really upset the application until I restarted the container. Loads of errors about it trying to open files from the cache that I had deleted. |
I've just added a few changes to the cache directory to stop this from happening again, will add to new release with the patch to fix debug. |
I'll also update the readme to clarify what exactly the default values are, as it really wasn't very clear on reflection. |
You mean to tell me that it's an open source project with ambiguous or missing documentation?? That never happens! Seriously though, I appreciate your effort tracking down and fixing these bugs 🙂 |
I've seen worse with a lot of closed source applications! But honestly writing good documentation is difficult and probably the least enjoyable part of maintaining a software project for other people to use. I'm still over the moon knowing that anyone other than me uses Jump though it's truly awesome! 😁 |
I've created release v1.4.1, pushed to docker hub, if you pull the |
Can confirm this is fixed in v1.4.1 🏆 |
Amazing, thank you so much for reaching out. All the best 😁 |
I'm running Jump on Kubernetes and I noticed that debug mode remains enabled even when I set
DEBUG: false
. The debug bar remains in the corner. I tried different ways of quotingfalse
and I even tried setting it totrue
, but I couldn't get rid of the debug bar. Pretty sure I didn't have this on v1.3.x.This is my deployment: https://jump.gazeley.uk/ (it's a work in progress so I'm still using the default sites but I'm going to stop fiddling for tonight)
This is the config that's being passed to the container:
https://jump.gazeley.uk/
The text was updated successfully, but these errors were encountered: