Support » Plugin: WP Bottom Menu » Menu behaves like it should, except for one page…

  • Resolved worldpeaceengine

    (@worldpeaceengine)


    Hi.

    First of all, thank you.
    Your plugin provides a very very clean bottom navigation with no flaws.

    The menu behaves like it should, except for one page on my site. (about us)

    There it shows no icon on the first column and another icon then the chosen one in the fifth column.

    I already checked if i use custom scripts on this page, but i dont.

    Hope you can help me.

    PS: i had Fixed Bottom Menu plugin before and had similar problems with it on all pages after a crash, not showing the icons at all or just a some from the dashicon repository.
    I already re-installed WordPress.

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author J4

    (@j4cob)

    Hi, thanks for your feedback!

    This plugin use the FontAwesome v4.x and Elementor plugin use the FontAwesome 5.x. Therefore elementor plugin is override v4.x. So go to Appearance > Customize > Custom CSS to add this css code .wp-bottom-menu-item i{font-family:FontAwesome;}

    Thread Starter worldpeaceengine

    (@worldpeaceengine)

    cool. thx. that helped to show the right icons.

    but i notice, that they appear to have thicker lines than on the other pages…

    Plugin Author J4

    (@j4cob)

    I saw it. Fontawesome 4.x use the different icons than v5.x. Delete this code .wp-bottom-menu-item i{font-family:FontAwesome;} and add this code .wp-bottom-menu-item:first-child i{font-family:FontAwesome;}. This will give you the solution (temporarily) for the current problem.

    • This reply was modified 6 days, 9 hours ago by J4.
    Thread Starter worldpeaceengine

    (@worldpeaceengine)

    thank you so much, but it didnt had any effect.

    never mind, you solved my problem already, maybe one of the next updates gets rid of it…

    thanks a lot, that was a lightning fast response!!!

    Plugin Author J4

    (@j4cob)

    Glad it was resolved.

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