Niall a11n

Hi @cowebbraunfels,

Thanks for the update!

I had a look at https://wp.kunden2-das-webconcept.de/?product=muster and several other pages, but do not see any review placeholders.

Next, I had a closer look at your System Status Report, and found that you have our premium Storefront Reviews plugins.

If you purchased Storefront Reviews on WooCommerce.com, please contact us at WooCommerce.com > My Account > Support.

Also, please include a link to this forum thread, so that we can keep track of what’s already been done. Please also make sure to switch back to the parent Storefront theme, so we can troubleshoot from there, as we do not support child themes and other customizations.

We will be able to help you further there.

Hi @vansite,

Thanks for sharing the fix you found.

Indeed, changing the font-weight seems to fix the problem per @dcka’s recommendations:

.star-rating span {
font-weight: 900;
}

Please let us know if you have any questions!

Great question! Per the Update Font Awesome to version 5.12.1 closed Github issue, it looks like this feature would not be implemented anytime soon:

as Storefront uses the SCSS files instead of the CSS file, including the latest Font Awesome CSS file remote, as suggested in that issue, will not work.

Please let me know if you have any further questions!

Hi @brodward,

Thanks for reaching out to us!

This issue is currently being investigated by our developers in this bug report:

https://github.com/woocommerce/facebook-for-woocommerce/issues/1777

As we have no further information to share other than what is in that report, we recommend subscribing to the report to follow the process. This step will allow you to be the first to find out when the bug is fixed.

You can subscribe by selecting this button on the GitHub repo (this will only be visible if you have a GitHub account, which can be done for free):

Link to image: http://cld.wthms.co/2EmX9K

I’ll go ahead and mark this thread as resolved now. If you have any further questions, I recommend creating a new thread.

Hi @freelylw,

My apologies for the misunderstanding. I had a closer look at the thread and it looks like you would like to display the logo _and_ the tagline at the same time, right?

This functionality will require some additional customization and settings, as it is not possible to display both the logo and tagline at the same time. By default, the logo replaces the site title and tagline.

To display the logo and tagline at the same time, please do the following:

1. Visit Appearance > Customize > Site Identity
2. Select Remove to remove the logo from displaying. Also, please make sure to add a site title (we will hide the site title later on via code) and tagline and Publish the changes if you have not already done that.
3. Add this code to the Appearance > Customize > Additional CSS section of your site’s Customizer:

/* Storefront - Display logo and site title | SF forum wp.org */

.site-branding .site-title a {
	display: none;
}

.site-branding::before {
    content: url(/wp-content/uploads/2021/06/cropped-luut-2.png); /* Change the logo's URL if needed */
    background-repeat: no-repeat;
		width: 120px;
		height: 70px;
}

You may need to reload the page to see the changes, which should look something like this:

Link to image: https://d.pr/i/RN4LUM

In short, the code hides the site title and displays the logo in its place (you will need to update the logo’s URL in the code if you decide to use a different logo image).

Does that work for you?

Hi @pablomiralles,

Thanks for the update. Yes, we are indeed using the glyphs like \e000. I recommend checking the Font Awesome Cheatsheet for the glyphs, which appear right next to the icon names.

For instance, \e000 is caravan-alt:

Link to image: https://d.pr/i/bjXhX3

The e000 is meant for use in CSS, whereas the caravan-alt is meant for use as HTML or for targeting the icon via CSS to style it.

It would be great if you could share a screenshot of the problem the next time you see the icons not appearing correctly.

Based on the “” characters you shared, it seems like there is an encoding problem related to this existing Font Awesome bug.

Does the bug report look similar to the problem you are having?