After just doing an upgrade to the newest 5.0 GPL version this morning - and then switching to the new theme - I'm noticing some very odd text showing up inside any textarea text box that is normally pre-populated with data for editing - i.e., Apache directives or the manually editable php.ini file (attached screengrab).
Versions affected... Webmin: 1.782 - Authentic theme: 17.62
If I click into the text box as if to do an edit, it adds another of these unicode type characters at the cursor location. I can't select it/them to edit or remove them, and from looking at the underlying config files, I absolutely know they aren't in the originals. I can edit any of them either directly on the server, or ftp in and do it that way, so there are ways to get around the issue for me, but I won't presume everyone else can do the same. I haven't actually tried to edit anything in the textareas as-is, so I have no idea if they'll corrupt anything or not.
It appears to be either some type of EOL or BOL character being inserted on any blank line between paragraphs, or at the beginning of single blank lines. The accented "A" only shows within the rendered web page, but is NOT part of the same textarea's text shown by 'view frame source'. I presume that means the theme itself is adding these, and not the underlying code or them being in the actual config files themselves.
It also doesn't matter what browser I use. I've tried it with FF, Chrome and Opera, and they all behave the same. I'm accessing a CentOS 6.4 dev server locally, on which I also did a full OS update today as well, and I'm assuming none of that contributed - but - it's certainly possible I guess.
Comments
Hi,
Please take a look at Troubleshoot: https://github.com/qooob/authentic-theme#troubleshoot
This is encoding issue.
Submitted by RandyL on Thu, 02/04/2016 - 03:43 Comment #2
Thanks for the quick help. I had to take an additional step to get Chrome to display correctly.
My Chrome encoding was already set correctly, and after modifying all the global and user settings for theme use in Webmin/Usermin configs... the odd 'A' still showed. I toggled to auto-detect encoding, which didn't work - it reported the page as Windows-1252 for some reason, even though there's no meta tags in the theme for anything but utf-8, so unsure of why - but after resetting it specifically to UTF-8, it did correct it. FF was fine after setting the theme configs, and Opera acted the same as Chrome, but once Chrome was correct, it too was working without any further tweaks.
These settings are set in both Webmin->Webmin Configuration->Language just as in Webmin->Change language and Theme.
Make sure that both have correct value and try forcing encoding in case it doesn't work.