Webinterface menue in 2 rows after update

td_miles

Cached CSS sheets?

Yes, it would seem like it, problem is I can't find WHERE. Searching for this issue (cached CSS in chrome) yields numerous suggestions on clearing cache, "CTRL+F5" refresh, "CTRL+SHIFT+R" refresh. Have tried "clear browsing data" in chrome and selected all check boxes "since beginning of time" & restarted browser. Tried them all multiple times, but still seeing the old CSS.

Not sure how/where it's being cached. It can't be on the server side as I've verified the file is correct on the server (assuming it is served from '/usr/local/www' and not somewhere else ?). The firewall has also been rebooted after the downgrade, so it can't be cached in web server RAM.

Anyway, this is probably my browser issue, not specifically relevant to the pfsense menu problem, so probably bext to not worry about it for now and hope that at some point when the CSS is changed on the firewall again it will update in my browser cache.

hcoin

The safest workaround is to go to the bother of downloading and installing the Tahoma font. Other workarounds are good only if the system you use to visit the pfsense website isn't used for much of anything else. The other workarounds involve removing fonts or packages of fonts which can break non-pfsense websites, word processing, slideshow type presentations and so forth.

Some systems appear to work if the resolution is reduced, caches are cleared and so forth but those are not sure to work across a deployment, especially as the problem appears in the firefox browers, the chromium browser, the chrome browser and across distros.

Install ttf-mscorefonts-installer, then use these steps to install tahoma:

http://linux-unix-tips.blogspot.com/2012/07/install-tahoma-font-in-ubuntu-linux.html

jdillard

To those that were having issues, if you want to try the newest snapshot at https://snapshots.pfsense.org, I committed a fix for the top nav wrap.

https://forum.pfsense.org/index.php?topic=81165.msg443999#msg443999

java007md

@hcoin:

The safest workaround is to go to the bother of downloading and installing the Tahoma font. Other workarounds are good only if the system you use to visit the pfsense website isn't used for much of anything else. The other workarounds involve removing fonts or packages of fonts which can break non-pfsense websites, word processing, slideshow type presentations and so forth.

Some systems appear to work if the resolution is reduced, caches are cleared and so forth but those are not sure to work across a deployment, especially as the problem appears in the firefox browers, the chromium browser, the chrome browser and across distros.

Install ttf-mscorefonts-installer, then use these steps to install tahoma:

http://linux-unix-tips.blogspot.com/2012/07/install-tahoma-font-in-ubuntu-linux.html

Thanks, per the link, this resolved the issues for me under Kubuntu 14.04:


wget http://download.microsoft.com/download/ie6sp1/finrel/6_sp1/W98NT42KMeXP/EN-US/IELPKTH.CAB
cabextract -F 'tahoma*ttf' IELPKTH.CAB
mkdir -p /usr/share/fonts/truetype/msttcorefonts/
mv -f tahoma*ttf /usr/share/fonts/truetype/msttcorefonts/
chmod 644 /usr/share/fonts/truetype/msttcorefonts/tahoma*
fc-cache -v
rm -f IELPKTH.CAB

Guest

@Supermule:

Problem is the GUI itself. If it was W3C compliant then fonts would not be an issue.

http://validator.w3.org/

patches accepted.

Guest

@exlfrnk:

I wouldn't put my money on them cleaning this mess up:

https://redmine.pfsense.org/issues/3841

The Bug was outright REJECTED.

Go figure.

It was rejected as a duplicate: "Please use the current/open ticket #3842 and not this incorrect/old ticket."

Stay classy, exlfrnk.

strebor

I can work around this by using the pfsense theme or untick the 'alow pages to chose their own fonts….' in Firefox prefs

kejianshi

My work around is to wait…

Criggie

I fixed it in fedora 18 by installing these two RPMs


wine-tahoma-fonts
wine-tahoma-fonts-system

Now I get this and the webgui looks better.

[criggie ~]$ fc-list | grep -i tahoma
/usr/share/fonts/wine-tahoma-fonts/tahoma.ttf: Tahoma:style=Regular
/usr/share/fonts/wine-tahoma-fonts/tahomabd.ttf: Tahoma:style=Bold

I haven't found a debian package that supplies tahoma yet.

asayler

It's been fixed on my machine by default for the last month or so of builds. I believe they changed the spacing a bit to make it work even in the absence of the ideal font.

pygo

I was having a hell of a time getting this working. Till I googled how to install Tahoma on Ubuntu. I came accross this script on Ubuntu forums, with people saying it worked. So I gave it a try and it worked!

vi addfonts.sh

#!/bin/bash
# Install Microsoft Fonts (Including Tahoma)

if [ "$(id -u)" == "0" ]
then
  if apt-get install msttcorefonts; then
    mkdir temp-tahomafont
    cd temp-tahomafont
    if wget  http://download.microsoft.com/download/ie6sp1/finrel/6_sp1/W98NT42KMeXP/EN-US/IELPKTH.CAB;  then
      cabextract IELPKTH.CAB
      if cp *.ttf /usr/share/fonts/truetype/msttcorefonts/; then
        if fc-cache -fv; then
          cd ..
          rm -r temp-tahomafont
          echo "Microsoft fonts are now installed"
        else
          echo "Could not rebuild font cache"
          exit -1
        fi
      else
        echo "Could not copy the font to  /usr/share/fonts/truetype/msttcorefonts/"
        exit -1
      fi
    else
      echo "Could not download Tahoma font"
      exit -1
    fi
  else
    echo "Could not install msttcorefonts package" 
    exit -1
  fi
else
  echo "Run 'sudo ./addfonts.sh'"
  exit 0
fi

chmod +x addfonts.sh
sudo ./addfonts.sh

Now how about the devs at pfsense get off their butts and fix it so we don't need M$ crap on our systems? I thought I was using opensource/bsd licensed software. Why is Tahoma even an option if it's M$ only? Even Google doesn't have Tahoma in their collection of Open Fonts. This appears to be such a simple fix too - don't use Tahoma. Why isn't it fixed already?

jimp

@pygo:

I was having a hell of a time getting this working. Till I googled how to install Tahoma on Ubuntu. I came accross this script on Ubuntu forums, with people saying it worked. So I gave it a try and it worked!

Thanks for the script, there is a manual equivalent to that posted around here somewhere but that makes it easier for some.

@pygo:

Now how about the devs at pfsense get off their butts and fix it so we don't need M$ crap on our systems? I thought I was using opensource/bsd licensed software.

It has already been fixed on 2.2, unless there is a major security issue there won't be another 2.1.x release.

@pygo:

Why is Tahoma even an option if it's M$ only? Even Google doesn't have Tahoma in their collection of Open Fonts. This appears to be such a simple fix too - don't use Tahoma. Why isn't it fixed already?

Tahoma is only a problem if your system already has Verdana installed. If you have Verdana installed you've already dipped into the Microsoft pool, so the complaint is not valid.

Tahoma isn't required, but preferred. If you have neither Tahoma or Verdana the system picks another similar font (e.g. Liberation Sans) and it works fine. I'm sure that will be fixed in other ways in the future.

frrebora

i write from Italy. I had the same problem on Win 7 64 bit / Chrome 64 bit. I have solved in this very simple way. Uninstalled Chrome completely (iobit uninstaller free). Reinstalled, logged in the chrome account for the favorites (in which i have the favorite for web interface). Logged in pfsense. All good. In other PC (generally i have ubuntu 64 or some free unix, windows is only on the pc that have programs not virtualizable for windows) I had no problem. When i had the problem, the metallic theme was not affected. Only ng_theme was affected.