Trailing commas should not be a problem. Is it only a problem with this other plugin? (i.e. If you deactivate that plugin, does it then work correctly?) What is that plugin for? Is it some kind of caching?
Either way, we can make a note to remove the trailing comma in the next update.
Hello. We had the same error produce in Search Console: “Parsing error: Missing ‘}’ or object member name.” For us, it identified the “}” as the culprit, not the comma.
**error from search console **
“contactPoint”: {{“@type”: “ContactPoint”,”contactType”: “Telephone”,”telephone”: “(480) 812-1998″}},”hasMenu”: “”,”email”: “info@iboaz.com”,”openingHours”: [“Mo,Tu,We,Th,Fr 8:00-17:00”] }
***
It appears to be missing a closing }
Same here on every website where I use this plugin. Please see this test result.
Thanks
JP
We’ve just pushed a development version of 2.2.4. It should correct both of these issues. However, we will not have time to complete testing before the weekend, so we are not releasing it yet as a stable release (i.e. you won’t get a notification to update in your admin).
If you’d like to install it now, you can get find it in the list of available versions here: https://ww.wp.xz.cn/plugins/business-profile/advanced/
Please let me know if this does indeed correct your issues. We will complete our testing and release it as a stable update next week.
@jpnl In this version, we’ve also updated the Whatsapp field so that the number used to send the message has all non-numerical characters stripped from it. This way you can enter the number how you would like it formatted in the contact card, and it will stay correctly (un)formatted for the message send.
Thanks!
-
This reply was modified 3 years, 9 months ago by
jaysupport.
Thread Starter
dpaiha
(@dpaiha)
The dev-version has fixed the problem, thanks.
Regarding your question around proxy_fcgi: that is an apache module for handling fast-cgi-protocol. the php process itself is running inside php-fpm (php-fastcgi process manager). THe website of my customer is running at a plesk-based shared infrastructure from an ISP hosting more than 1000 different customers.
Thanks for confirming that. We’ve just pushed the stable release for 2.2.4, which includes a fix for this and the other mentioned issue.