Created attachment 1612 [details] Example of page enteries problem DNS forward configuration usability Entries are unreadable white on white text.
DNS forward configuration - color of entries there: In /srv/web/ipfire/cgi-bin/ approximately in line 328 replace ‚white‘ with ‚black‘. That should be all.
DNS forward configuration - here readability Approximately in line 328 replace 'black' with 'white: - $col="bgcolor='${Header::colourred}' style='color: black'"; } + $col="bgcolor='${Header::colourred}' style='color: white'"; } That should do the job. :-)
It is the text colour that needs to be changed, not the background colour.
You're right, Adolf! style='color: ...' sets the color of the text.
(In reply to Waynie from comment #4) > You're right, Adolf! > > style='color: ...' sets the color of the text. Sorry, my mistake. You are right. I saw the bgcolor word and didn't look through the whole line closely enough. However this also shows the need for clearing up and standardising of the code as other cgi pages don't specify the text colour in the same way and so each page needs to be looked at individually to fix things so if an update is required it can't be done to any central code and then apply to all pages as it should do. Feel free to submit a patch to the dev mailing list with the change. https://www.ipfire.org/docs/devel/submit-patches
IPFire-2.x component should always be --. A named component is only used for IPFire-3.x
The patch has been merged into next and will be in CU191 https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=de8ed87d05887907740bef72180b6e8f63d01416
https://www.ipfire.org/blog/ipfire-2-29-core-update-191-is-available-for-testing
The testing install of CU191 on my vm testbed shows the problem as fixed. Would be good if the original bug poster can also confirm that they consider it solved.
https://www.ipfire.org/blog/ipfire-2-29-core-update-191-released