Firstly, when you’re getting your API key, enable Maps API and Places API
The plugin mentions Maps API in one spot then Places API in another.
Just flick them both to enabled and then create your API key once both are enabled.
To solve most of the grey exclamation mark issues, make sure when you are setting the restrictions to enter your website as follows including the asterisks’ and the first period:
*.yourdomain.com/*
Hope this helps someone
]]>Am I supposed to see what the error is? I just see an exclamation mark when I click view.
Many Thanks
Vernita
Have you seen this before?
Terri
]]>first of all: thanks for the amazing plugin!
I’ve got only one question:
I set a rule, so that a customer can only choose min. 1, max. 4 time slots.
Now if the rule gets proven wrong it shows an exclamation mark for 15 sec. in the front end and the red thumb down.
Is there a way to change the text displayed when the rule’s proven wrong?
Thanks for your help.
semsemann
https://www.ads-software.com/plugins/dnui-delete-not-used-image-wordpress/
]]>Thank you for this very nice plugin!!
Can you please tell me how to remove the exclamation mark after the price?
I tried using the Codestyle Localization and changed %s! to %s
However, did didn’t help.
Thanks in advance!!
https://www.ads-software.com/plugins/woocommerce-smart-sale-badge/
]]>apache error.log:
File does not exist: /[webroot]/wp-content/themes/purple-pastels/layout.css
File does not exist: /[webroot]/wp-content/themes/purple-pastels/color.cssI downloaded the source, and a I found out that it could come from print.css:
~/Downloads/purple-pastels$ grep -r layout.css *
print.css:@import url(layout.css);
Esthetically I have problems with an exclamation mark showing in from of a gravitar in the comments sections. Unfortunately I still didn’t find out what could cause this error. I guess it could have something to do with these missing files.
Example page: https://www.krusj.nl/?p=96#comments
It shows that sometimes KrusjMe has an exclamation mark, and other times not. Apparently only in the white comment boxes.
That’s all. 
Anybody an idea how to fix this?
I love your plugin, I installed it in all of my blog (granted, it sometimes mess up with computer code).
I request the following feature:
For French, add a narrow no-break space (U+202F) before an exclamation mark or a question mark. If there is already a space, replace it.
Code-wise, I suggest this:
– Delimiting the perimeter: a way to ensure the element is in French. Check that either “lang” or “xml:lang” is present/inherited and that the attribute is either “fr” ou starts with “fr-“.
– Search-replace:
[^\u202F]([!?]) => \u202F\1 (if there is no narrow no-break space, add it)
[\u2009 ]\u202F([!?]) => \u202F\1 (if there is a regular or thin space before the narrow no-break, delete it)
This could probably be optimized.
This could later be extended to more rules. I will not list them all here, one thing at a time
Thank you for taking time to consider it.
https://www.ads-software.com/extend/plugins/wp-typography/
]]>