Menu error after update to 1.2.14

After updating to 1.2.14, my menu appearance has issues… instead of the arrow for drop-down menus, a small square box appears. My site is https://map.peace-ed-campaign.org/

FYI - upon inspection, I’m getting the error

"DevTools failed to load source map: Could not load content for …/wp-content/themes/shapely/assets/css/bootstrap.min.css.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

I’m having the same error on my site, wimdi.com

Can you let us know how to fix it?

Hi again… I see several others posting this as an issue… but I’ve yet to receive a response. Can you please help?

Ditto - After the Update 1.2.14 on my site also instead of the arrow for drop-down menus, a small square box appears for the top menu. Also, the social icons are not working all after the new update. Please fix this soon. Thank you.

Hi there

Please add this css code in the Appearance > Customize > Additonall css:

@import "https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css"

I added this line to the custom css but it has made absolutely no change to the menu issue. See here:

I continue to get the same error as before:

DevTools failed to load source map: Could not load content for https://map.peace-ed-campaign.org/wp-content/themes/shapely/assets/css/bootstrap.min.css.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

***** Is the problem here possibly related to the error in the url for the min.css? Why is “.map” added to the end of the resource url???

Hi there

@pttony code was probably added not correctly, check this out how it looks like: Screenshot by Lightshot
Please provide screenshot of the code in the css box

It worked for me only when you insert the code in the first line of the custom css.

An dont forget the ; at the end of the code
so

@import "https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css";

Aha! Indeed - my error… as @Thyrant notes above, I forgot the “;” at the end. This issue is fixed now…thank you.

Well, that’s nice to hear :slight_smile:

Case closed