Weston Font

Tagged: 

Viewing 15 posts - 1 through 15 (of 15 total)
  • Author
    Posts
  • #2556
    Anchormdanchormd
    Member

    Having a difficult time getting Weston to work. Could you send specific installation instructions? Thank you!

    #2568
    Livemeshlivemesh
    Keymaster

    Just load the child theme that comes with the theme. The Weston font should now work. The required markup is in the style.css file of the child theme. Pls have a look. You still have to install the font on your server since the child theme will initially point to fonts installed on our servers. Here are steps –

    1) Download the Weston font from –

    http://fontfabric.com/weston-free-font/

    2) Go to http://www.fontsquirrel.com/tools/webfont-generator and follow onscreen instructions to generate the webfont kit from the downloaded Weston font.

    3) You can follow instructions from Step 6 provided in the below post once you download the Weston webfont kit –

    https://www.livemeshthemes.com/support/faqs/install-custom-fonts/

    If you still have trouble, pls email me a temporary login to your site or leave a private message here with the login and I can try to find out what’s happening. Thanks.

    #2671
    Dvhughesdvhughes
    Member

    Holy Smokes, I have followed that tutorial link about 5 times now using every possible variation and even went so far as to download Museo Slab and do it again from the very beginning. Nothing seems to get it done. I think it might be missing a step, or I am clearly an idiot. I have triple checked everything. I would really like to not only stop drinking the Weston milkshake from your servers (Firefox issues) but I have big plans for another font.

    Could you check that tutorial again and make sure that it is correct?

    I am developing on a client’s site in a subdomain and the only other reason I can think of for my difficulties would be that my paths are messed up.

    I have tried all of these. What do you think?

    src: url('http://dev.mydomain.com/wp-content/webfonts/museo_slab/26B0C6_0_0.eot');
    src: url('http://mydomain.com/dev/wp-content/webfonts/museo_slab/26B0C6_0_0.eot');
    src: url('http://dev.mydomain.com/public_html/wp-content/webfonts/museo_slab/26B0C6_0_0.eot');
    src: url('http://mydomain.com/public_html/dev/wp-content/webfonts/museo_slab/26B0C6_0_0.eot');

    #2672
    Livemeshlivemesh
    Keymaster

    Sorry you are having trouble with this. Pls reply as a private message here with the site URL and a temporary login to the WordPress dashboard and I can take a look. You may also email me the same (see bottom right box in my profile page). I have replicated the steps in the tutorial and able to reproduce the custom font on my site at least. Thanks!

    #2678
    Dvhughesdvhughes
    Member
    This reply has been marked as private.
    #2687
    Dvhughesdvhughes
    Member

    Did you do that or did I? (I suspect you did, but I was monkeying with it just now and got frustrated and stopped.)

    Its working now and I really have no idea why.

    Can you explain what I missed?

    #2688
    Livemeshlivemesh
    Keymaster
    This reply has been marked as private.
    #2689
    Dvhughesdvhughes
    Member

    Firefox really doesn’t like importing these fonts.
    Works with Chrome and Safari.

    #2690
    Livemeshlivemesh
    Keymaster

    I am seeing these fonts working in Firefox too. See attached screenshot. This is Windows version and I have my Mac desktop at my workplace and hence cannot check that right now.

    #2692
    Dvhughesdvhughes
    Member

    All good to go. Firefox is now cooperating.

    So was the problem in the Custom CSS or the Extinct Child style.css?
    (I cannot see reply #2688, so I suspect it was not for me.)

    Really appreciate you getting in there for me and resolving it.
    I have a lot of patience and can usually figure this stuff out on my own, but this was truly dumbfounding me and felt I had to ask for ask for help.

    Thanks again.

    #2693
    Livemeshlivemesh
    Keymaster

    Ok I did not realise this. Since you are not the one who started the thread, you could not see the private message. Here is the message in full –

    I was able to get the fonts working. I changed the URLs a bit. For Weston, I had to change the URL from https://www.livemeshthemes.com/extinct/wp-content/fonts/weston/https://www.livemeshthemes.com/extinct/wp-content/fonts/Weston/

    For outage font, I had to change the font-family in the markup in the style.css. Looks like you missed changing the font-family to outagregular for heading styles in the child theme style.css even though you inserted the URLs for the font there.

    To make outage work in Firefox I changed the URL to http://acmescenery.com/dev/ from http://dev.acmescenery.com/ for the font artifacts.

    I am really sorry this caused trouble for you. Obviously, in most cases like this, a single step missed will invalidate everything else. It will help others too if you can tell me the exact step I missed since we sometimes we just assume certain things.

    #2694
    Dvhughesdvhughes
    Member

    Yes..I knew there must have been a step I missed or a font name that I neglected to swap out.
    I really thought I got them all.
    I also thought that perhaps that I may have had a conflict with editing the style.css directly and then also in the Custom Styles tab. It was a bit of a cluster****.

    Due to the fact that the above tutorial is using a particular font and all of the instances need to be swapped out, the steps might be better served with a screenie of the code with all of the font-family changes highlighted as well as the URLS.

    Also, I think I may have gotten a little confused with the instructions in the style.css editor. I liked that they were there, and they were quite clear, but being an intermediate and working with a brand new theme can lead to bold but pointless .css editing when something is not working after a few hours. I ended up going back and forth several times and wasn’t sure which code was the true cause of the problem. You may want to add another /* line reinforcing the Custom CSS Tab override. The appearance of redundancy can cause confusion. (Did for me anyway.)

    Hope that helps.

    Finally, two things:…
    I would like to stop pulling Weston from your site. I should just be able to use the working Outage code and swap out URLS and font-families, correct?

    And finally…Can I now import the Outage font into the Rev Slider? I tried just calling it up in the “Edit CSS” tab, but I know I must need an @import line. Can you help me out here or would you like me to start a new thread?

    Again..THANK YOU SO MUCH FOR YOUR HELP!
    If there was a 6th star to give, I would gladly give it.

    #2696
    Dvhughesdvhughes
    Member

    Ok…I finally figured out what was going on with Firefox.
    The fonts do not load in a subdomain. However, they appear when the browser is pointed to the directory. Chrome and Safari work either way.
    Hopefully this issue will resolve itself when I migrate the site.

    #2702
    Dvhughesdvhughes
    Member

    And finally…Can I now import the Outage font into the Rev Slider? I tried just calling it up in the “Edit CSS” tab, but I know I must need an @import line. Can you help me out here or would you like me to start a new thread?

    Resolved

    #2712
    Livemeshlivemesh
    Keymaster

    Sorry for the delay in replying. Have been real busy from past 2 days. Thanks so much for all the input you provided. I am sure this thread will be of help to others too for troubleshooting some of the custom font issues. I plan to update the docs to reflect the additional input you provided.

    Regarding the query on revolution slider, looks like you figured out already. You just have to specify the font-family as “outageregular” without the need to import anything. Thanks again.

Viewing 15 posts - 1 through 15 (of 15 total)
  • You must be logged in to reply to this topic.