-
-
Notifications
You must be signed in to change notification settings - Fork 214
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
[Bug]: Messages are messed when using e107 debug codes #5251
Comments
Yes, it works this way - not a big problem, just remove ?[debug=basic+] from URL and refresh page (debug mode is still on) - related to a problem with URL parameters and SEF URL (regex). |
@Jimmi08 Ok, i understand it works this way, but i have a big problem if i want to show error messages for my plugin in the frontend. For instance, with my code, if i got the debug activated, it always has messages, and the script simply exits, but it shouldn't exit, because messages are not from the script... If i set debugging off, it works like it should, no exit.... But of course, if i have a message in my plugin, it stops and exits.... What i'm doing wrong here? P.S.: Just a remark, the simple removal of the ?[debug=basic+] from URL doesn't work, if i remove it, debug is still on, even without that in the URL. I have to put ?[debug=off!] on the URL to force debug off.... How i miss the Firefox plugin.... |
All debug settings were moved to the admin area, I suppose you have still browser extension like me, so setting debug on frontend causes this.
|
@Jimmi08 I don't have the debug extension As far i see it, it's because i'm using the I'll give it a shot and try it... |
Not Needed:
Simplify:
|
@Vodhin That will work, but if i have more conditions to set warning messages, it will be little bit redundant with the code.... |
Well, i think i catch the bug..... For instance, if i do
my plugin works like a charm even under debugging.... But if i do
my script simply stops without any warning under debugging.... Anyone has this same issue??? |
The LAN files need to be loaded before HEADERF By the way, You can use HTML in the message
this will render a bullet list. Use whatever HTML you like. |
@Vodhin Not quite....
On this code, if all ifs are true, the philcat admin lan is correctly loaded.... and the error messages are correctly rendered... But if you do like my example before, it doesn't work. Furthermore, if i move the Real weird bug... |
What e107 version are you using?
v2.3.3, Latest Github version (just updated)
Bug description
If i try to use messages in my plugin, like this:
and if i try to debug the page with the e107 debug codes in the url, my page is not displayed, as per my code, it has messages and exits....
If i disable the e107 debug codes, it all goes right....
How can i use warning and error messages in my plugin without having this issue?
How to reproduce
Try to use my above code (with some changes) inside a plugin, and test with and without the e107 debug codes in the page url....
Expected behavior
I expected the e107 debug messages no mix with plugins messages....
What browser(s) are you seeing the problem on?
Firefox
PHP Version
PHP 7.4
The text was updated successfully, but these errors were encountered: