Hello,

I would like to add a new content font in “enfold/general styling/defines the font for the body text. I have created a quick CSS as you mentioned in this spot:

add_filter( ‘avf_google_content_font’, ‘avia_add_content_font’);
function avia_add_content_font($fonts)
{
$fonts[‘Roboto’] = ‘Roboto’;
return $fonts;
}

Nothing happens in the drop down list “defines the font for the body text”. Could you please help me?
Carine

Hi again,

I’m sorry that got rid of the Enfold custom widget area creator. I’m not sure how that is possible, and it works fine in my own version of Enfold. I guess you will have to just wait for the official release.

To add to what Josue has said, what is shown in his screenshot will appear if you put add_theme_support( 'avia_conditionals_for_mega_menu' ); in functions.php (or better yet, your child theme’s functions.php). I was deliberately vague about it in case the support staff thought the Nav Menu Roles plugin was the better way to go, but that’s how you do it. I believe it will only work if you have not also commented out add_theme_support('avia_mega_menu');, and the line in class-megamenu.php also becomes unnecessary.

Hi Bruno,

thanks for posting this!

Meanwhile I did some research and figured it out.
I’ll explain the procedure for everyone in the forum.. so do not wonder about the redundant parts…

Go to fontello.com and choose the fonts you want to use in your project (these can be from different series on the fontello site as far as I understood it)

After your marked them watch this video: http://vimeo.com/75743285
It explains how you can import fontello web fonts into enfold.
As the fontello download function seems to have changed a little meanwhile you will have to zip-compress the complete folder after downloading the webfonts.

Now you should have all the fonts you want to use in your zip file.
Go to the Enfold Theme Options within WordPress and choose the Import/Export-Tab.
Via the Icon-FontManager import the zip file you just created.

Now Enfold knows how to decode your chosen web fonts.

If you want to use a down arrow for example at the end of a section to have a smooth down scrolling effect, put a code element from avia somewhere on the page.

Now put this line into it:
<a href='#next-section' title=''" class='scroll-down-link' data-av_icon='' data-av_iconfont="fontello" title="Nächste Sektion"></a>

Two things to take care of here:
data-av_icon and data-av_iconfont

So lets start with data-av_iconfont:
This is the name of the package as it is stored in the Webfont-Manager.
If something does not decode correctly have a look into the Webfont-Manager and name it accordingly in your code.

Now it is time to take care of the weird rectangle in data-av_icon=’’.
This is where we seem to address the correct font from the stored set in the web font-zip.

Again go to fontello.com
With your wanted fonts still chosen click on the “Customize Codes” tab.
You will see all the chosen fonts.
They all have this weird little rectangle on top of each.
Right click on the rectangle, copy it and replace the rectangle seen behind data-av_icon= with the copied one.
Looks the same-but seems to be a different unicode character.

Now save.

Save/Update the page.

Reload website.

Hope it worked for your too!

Cheers
Marc

• This reply was modified 11 years, 7 months ago by mw75.

Thanks Dude,

I did this (in my child theme, so I created the dirs and then copied the original PHP file) and it stopped the exact same error, but I still see the first two error messages reported right under the Yoast panel in the pages I’m editing…

Notice: Undefined index: index in /home/***/***/***/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/slideshow_layerslider.php on line 118

Notice: Undefined index: index in /home/***/***/***/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/slideshow_layerslider.php on line 121

Any

Hi guys,

Nav Menu Roles does not yet work with the public version Enfold. I know because I am pretty sure I’m the guy who helped get support for it (and a few other menu plugins) in the upcoming version. I am guessing staff dev versions are a little ahead of the public version here.

It is easy enough to add this code to line 510 or so of class-megamenu.php until the release:

do_action( 'wp_nav_menu_item_custom_fields', $item_id, $item, $depth, $args );

But, actually, I’m surprised everyone forgot about add_theme_support( 'avia_conditionals_for_mega_menu' ); ;) That should solve it without a plugin.

• This reply was modified 11 years, 7 months ago by mayorninja.