We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently some errors are explicitly marked as errors:
Level0/www/osmapi.php
Line 66 in 390c810
Line 84 in 390c810
Line 90 in 390c810
...and these are styled in red:
Level0/www/page.php
Lines 13 to 15 in 390c810
However, other error messages are merely assigned to $messages:
$messages
Line 155 in 390c810
Line 253 in 390c810
...so they appear as regular text in the page rendering, which can mask the fact that there was a problem.
These error messages should also be assigned to $error, or somehow made to be shown in a similar style to make sure the problem is noticed.
$error
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently some errors are explicitly marked as errors:
Examples of messages explicitly marked as errors
Level0/www/osmapi.php
Line 66 in 390c810
Level0/www/osmapi.php
Line 84 in 390c810
Level0/www/osmapi.php
Line 90 in 390c810
...and these are styled in red:
Level0/www/page.php
Lines 13 to 15 in 390c810
However, other error messages are merely assigned to
$messages
:Examples of error messages that are not marked as such
Level0/www/osmapi.php
Line 155 in 390c810
Level0/www/osmapi.php
Line 253 in 390c810
...so they appear as regular text in the page rendering, which can mask the fact that there was a problem.
These error messages should also be assigned to
$error
, or somehow made to be shown in a similar style to make sure the problem is noticed.The text was updated successfully, but these errors were encountered: