-
Search Results
-
When a costumer have made an order, they get an email.
I tried the best i could to change the design on that, but with not 100% success.
I know its woo commerce, but maybe i am lucky you also know this?
I only need to change the headlines about the BANK info, but i can’t find out WHERE to change that..
This is a screen dump of the mail a costumer receive when putting an order…
Topic: Header font size
How do i change header font size and color?
Topic: Icon shortcode
Topic: Entypo icon alignment
Hi,
I have tried searching the forums for an answer and the replied code don’t work. I require assistance on 3 matters:
1) I would like to change the logo size to 785px x 180px
2) I would like to increase the padding of the top of the logo.
3) I would like to use google fonts for the theme:
Text such as blog entries or body text to be > https://www.google.com/fonts/specimen/Sorts+Mill+Goudy
With the following css:
color: #999999;
font-size: 14px;
font-style: normal;
font-family: OFLSortsMillGoudyTTRegular,Garamond,Palatino,Georgia,serif;
text-transform: none;
line-height: 1.25em;
font-weight: 400;Navigation bars/menu items and post title/entry title to be > http://www.fonts2u.com/melbourne-light.font
With the following css:
color: #000000;
font-style: normal;
font-size: 14px;
font-family: melbournelight,Arial,Helvetica,sans-serif;
text-decoration: none;
text-transform: uppercase;
letter-spacing: 1px;How can I change the font color of the button in the sidebar?
I placed this code in a text element in the widget:
[av_button label='Direct een taxatie aanvragen' link='page,31' link_target='' color='green' custom_bg='#444444' custom_font='#ffffff' size='large' position='center' icon_select='no' icon='ue800' font='entypo-fontello']But changing the custom font doesnt have any effect.
http://interboedel.nl.testbyte.nl/taxatie-van-bedrijfsinventaris/
Addition:
The theme is great and very powerful, but it is disappointing to spend a lot of time getting things how you want them in a prior release, only to have things “stop working the same way” in a new release! As the other Poster notes below, others are having similar problems with various features of Enfold 2.7.1. This makes folks (understandably) very wary of updating!
I’m hoping the Kriesi team (or anyone on this great forum) might have some insights as to what is making this custom CSS NOT work correctly in 2.7.1, whereas it WAS working fine in 2.5.2 (details below)?
#socket { font-size: 15px !important; position: fixed; bottom: 0px; width: 100%; overflow: hidden; }
#socket .container { padding: 4px 0 6px 0; }
html {background: #ffffff; }Orginal Post:
Although I realize “sticky sockets” are not officially supported in Enfold, under 2.5.2 I had precisely the “sticky socket” behavior I wanted working very nicely for me using the following custom CSS code:
#socket { font-size: 15px !important; position: fixed; bottom: 0px; width: 100%; overflow: hidden; }
#socket .container { padding: 4px 0 6px 0; }
html {background: #ffffff; }With this custom CSS code under 2.5.2, I would ALWAYS have my socket on the bottom of ANY browser window, no matter how large/small the window was, no matter whether or not a scrollbar was present, no matter how much/little content any given page had, no matter whether mobile or not: my socket was always showing at the bottom of the view window. It was great, and exactly how I wanted it.
Unfortunately . . . when I updated to 2.7.1, this code stopped working in the SAME way. Now with the same custom CSS under 2.7.1, the same socket appears, but ONLY when a scrollbar is present on the right-hand side of the browser. When page content is too little (i.e. no scrollbar), the socket no longer shows like it did in 2.5.2 (using the exact same custom CSS).
HOWEVER, even when no scrollbar is present in 2.7.2, the sticky socket is still THERE at the bottom of the page — i.e. the hover links are still present and available to click — you just can’t SEE the socket unless the scrollbar is present. It seems like whatever the “background” color in “html {background: #ffffff; }”, is now (in 2.7.2) “covering” the socket now when no scrollbar is present — whereas in 2.5.2 under these conditions, the socket was BOTH clickable and visible on pages with no scrollbar.
So something seems to have changed in the internal code of the 2.7.2 update (versus 2.5.2), that makes the above code work differently in 2.7.1 versus how it worked in 2.5.2. I wonder if it relates to the new “transparency” features?
I would really love to have my socket working the way it was in 2.5.2, otherwise I might have to revert back to 2.5.2, which I would prefer not to do, as using “older versions” is not an ideal long-term viable solution.
Is there anything you can think of that might have resulted in this “change” in socket behavior between 2.5.2 and 2.7.1, and if so, can you think of any code that might fix it, so my socket again works like it did in 2.5.2 — i.e. it is ALWAYS at the bottom of the page, whether or not a scrollbar is present on the window?
