Skip to content

Style errors more conspicuously and consistently #82

@waldyrious

Description

@waldyrious

Currently some errors are explicitly marked as errors:

Examples of messages explicitly marked as errors

$error = _('OAuth token was lost, please log in again.');

$error = 'Failed to create a changeset: '.$response->getBody();

$error = _('Could not aquire changeset id for a new changeset.');

...and these are styled in red:

Level0/www/page.php

Lines 13 to 15 in 390c810

<?php if( $error ): ?>
<p style="color: red;"><?=htmlspecialchars($error) ?></p>
<?php endif ?>

However, other error messages are merely assigned to $messages:

Examples of error messages that are not marked as such

$messages[] = _('Failed to open XML stream');

$messages[] = sprintf(_('Download is incomplete, maximum of %d objects has been reached'), MAX_REQUEST_OBJECTS);

...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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions