Liquid Themes

Thanks for your feedback. Fixed in v2.2.3. Please update the plugin to the latest version.

Fixed in v2.2.2. Please update the plugin to the latest version.

Thanks for the feedback. Please wait for the next releases.

Hi,

1. Make sure Font Awesome Pro Files are working on your website: https://fontawesome.com/docs/web/setup/host-yourself/webfonts
2. You should write the full icon name for your Font Awesome version. Example: fa-brands fa-wordpress

Kind Regards,

Hi @dperfectstorm ,

Click Hide Notification text at the bottom right.

Hi @oak1997 ,

You can select the Custom SVG option and add IMG tag.

Hi @webfantastic ,

There is no filter for menu items. We’ll consider for the next updates!

Hi @webworksafrica ,

WPBM is compatible with all themes and plugins. Can you provide this information so we can assist you?

• Browser console log
• Debug log
• etc.

Hi @webworksafrica ,

WPBM is compatible with all themes and plugins. However, in some cases, the themes you use can affect the style of the icon packs. So you can use Custom SVG option or you should make sure your Fontawesome css file is not managed by theme.

Could you try remove ?customize_changeset_uuid=4eb7a1d2-3d47-4a66-9a3b-a74969a69d56 from 资讯 menu?

Hi @webpp

You can use .wp-bottom-menu-icon-wrapper class for hide icons.

Full code:

@media screen and (max-width: 768px){
.wp-bottom-menu-icon-wrapper{
display: none;
}
}

Active menu icons working only on the different pages. Could you share your site address for more details?

Hi @befreeman11 ,

It appears that you are using the FontAwesome v6 option. FontAwesome v6 requires the full icon name. For example, for your “Trips” icon, you have only added fa-road, but you need to write fa-solid fa-road.

If you want to display WPBM on specific pages only, follow these steps: Navigate to Appearance > Customize > WP Bottom Menu > Conditions screen and configure the plugin accordingly.

Hi @webfantastic ,

thanks for your feedback. Current version does’t have custom class or id selector. We’ll implement this for next versions.

Could you give details for full URL error?