I have a Font Awesome conflict between Views 1.11.1 and the Salient theme from ThemeNectar. Using WordPress 4.3.1
When views is activated the Font Awesome menu icon disappears.
Views is deregistering the Font Awesome version that the theme is using and supplementing its own. Tried to deregister the Views version but could not. I was also concerned that if I did deregister would it adversely effect Views.
Please advise.
Dear robert,
Since it is a compatibility problem, please post a downloadable URL for the "Salient theme from ThemeNectar", and describe detail steps to duplicate same problem, I need test and debug it in a live website, thanks
Hi Luoy,
Can you send me a link to post those download links privately.
Best, Rob
Please fill below private message box with a downloadable URL of the the "Salient theme from ThemeNectar", and describe detail steps to duplicate same problem, thanks
Thanks for the details, I can download those theme files, could you describe detail steps to duplicate same problem?
Where can I see the the disappeared Font Awesome menu icon? thanks
Hi Luoy,
When both the Salient theme and the latest version of Views are activated AwesomeFonts does not work properly.
Set up a site with just the Salient theme activated and when you close down the window the 3 bar menu icon appears.
Then activate Views and close down the window. You will see that the icon has disappeared.
Rob
Are we talking about the three menu item in wordpress dashboard:
Home Slider, Nectar Slider and Salient
I can not duplicate same problem with the latest version of Views + fresh wordpress (4.4) installation
See the screenshot: 7.jpg
I suggest you try this:
Deactivate other plugins and test again.
Hi Luoy,
Thanks for your help.
I was able to fix the problem through the child theme.
Basically what was happening was that the version of font-awesome.min.css used by the Salient theme was being replaced by the version used by Views.
When I ran a comparison between the two files I found that aside from the few upgrades to the standard code there were a number of additional unique styles. So I put those styles into the style.css in the Salient child theme. That solved the problem.
Hope this helps others
Rob