font awesome menu items based on url fields in header

This support ticket is created 5 years, 10 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	9:00 – 12:00	9:00 – 12:00	9:00 – 12:00	9:00 – 12:00	9:00 – 12:00	-
-	13:00 – 18:00	13:00 – 18:00	13:00 – 18:00	14:00 – 18:00	13:00 – 18:00	-

Supporter timezone: America/Jamaica (GMT-05:00)

Tagged: Front-end display, Layouts plugin, Toolset Theme integration, TwentySixteen integration

This topic contains 3 replies, has 2 voices.

Last updated by Shane 5 years, 10 months ago.

Assisted by: Shane.

Author

Posts

June 7, 2018 at 5:09 pm #910755

timothyS-3

I have 3 fields -- one for LinkedIn, one for Facebook, one for Twitter -- that are profile fields as well as a name (I need to echo it) that I need to display in the header using Font Awesome icons. I'd appreciate any direction you can provide.

June 7, 2018 at 7:46 pm #910823

Shane

Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Timothy,

Thank you for contacting our support forum.

Would you mind explaining a bit further as to what is meant by font awesome in the menu ?

Is it that you want the font awesome icons to show up in the menu ?

Please let me know.

Thanks,
Shane

June 11, 2018 at 3:21 pm #911910

timothyS-3

what I need is some way of using field references to reference social media fields stored either in user's profile, or if that doesn't work, in a cpt.

June 11, 2018 at 3:46 pm #911921

Shane

Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Timothy,

You can store the font awesome classes in the custom fields and then display it like this.

<i class="[types field='icons'][/types]"></i>

Thanks,
Shane

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.