Reintroduce word wrapping to the custom login message

[efelon]

The <pre> tag breaks the well formed output of the login messages by introducing scrollbars and wrong background color. Later is most noticeable in the dark theme.

before	after

Just by using div instead of pre fixes the output.

DO NOT DELETE THE UNDERLYING TEXT

Please note

Please read this information carefully. You can run ./lnms dev:check to check your code before submitting.

• Have you followed our code guidelines?
• If my Pull Request does some changes/fixes/enhancements in the WebUI, I have inserted a screenshot of it.

Testers

If you would like to test this pull request then please run: ./scripts/github-apply <pr_id>, i.e ./scripts/github-apply 5926
After you are done testing, you can remove the changes with ./scripts/github-remove. If there are schema changes, you can ask on discord how to revert.

[SourceDoctor]

LGTM

[murrant]

@efelon this breaks line returns in the message

[efelon]

@murrant Can you give me more details how you entered the new lines?

What I have done is to check the "General Authentication Settings" input field for "Logon Message". There you don't have the possibility to enter new lines. After your comment I tried also:

Which will print "\n" and <br> just as characters. I also tried: &#13;&#10;

[murrant]

@efelon Like this:

line one
line two

That is why it was changed to a pre tag a couple of releases ago ;)

If you want both, you will need to have use nl2br and html purifier to allow only br (and maybe a few select other) tags.

[efelon]

@murrant I see, my bad. I haven't checked the option in the configuration config.php:

$config['login_message']    = "Unauthorised access or use 
shall render the user liable to 
criminal and/or civil prosecution.";

Let me see if I can find a solution otherwise I will make a new PR reverting the change.

[efelon]

I found a solution using <div> and white-space: pre-wrap; working on firefox and chrome. I create another PR later.

[librenms-bot]

This pull request has been mentioned on LibreNMS Community. There might be relevant details there:

https://community.librenms.org/t/21-1-0-changelog/14698/1