A quick addendum: when I go to the listing after the error message, the listing is perfect. I don’t see any issues with the result itself.
…Although I do occasionally have a spurious “Anniversary Date” that pops up in listings after we edit the info. (The “Anniversary Date” is always the day’s date that we made the edit.)
But that’s a different issue!
BTW, our Connections page is at:
http://thenadb.org/nadb-directory
Thanks again!
Plugin Author
Steven
(@shazahm1hotmailcom)
@varsitysports
Can you confirm that the line number for the warning is 206
? I’m nearly 100% certain but I want to make sure.
In regards to the anniversary date… I’ve never seen that before. I assume you are not adding any dates correct? What are is Fieldset Config settings for the Date fieldset (found on the Connections : Settings admin page under the Fieldset Config tab)?
Steven,
You are correct — the line number is 206
.
I neglected to include the full error message. There are actually THREE lines that come up:
Warning: count(): Parameter must be an array or an object that implements Countable in ../wp-content/plugins/connections/includes/geocoder/provider/class.algolia.php on line 206
Warning: Cannot modify header information - headers already sent by (output started at ../wp-content/plugins/connections/includes/geocoder/provider/class.algolia.php:206) in ../wp-includes/pluggable.php on line 1251
Warning: Cannot modify header information - headers already sent by (output started at ../wp-content/plugins/connections/includes/geocoder/provider/class.algolia.php:206) in ../wp-includes/pluggable.php on line 1254
There has to be a clue in there somewhere!
Thanks again,
DJ
Plugin Author
Steven
(@shazahm1hotmailcom)
@varsitysports
Thanks… I have implemented a second check so PHP should no longer output the initial warning. With no initial warning the two other warning should not display either. 🙂
I’m planning on releasing an update by end of day tomorrow which contains this fix.
In the meantime… please see this FAQ:
How do I hide PHP Warnings and Notices?
This is considered to be a best practice on live sites.
Hope this helps!
ps.
If you have a moment, I would truly appreciate a review as they really do make a difference.
Thanks in advance for your time!
-
This reply was modified 5 years, 5 months ago by Jan Dembowski. Reason: Removed review link with filter=5 on it
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
@shazahm1hotmailcom Thanks for asking for a review but don’t add filter=5
to the link. That intentionally hides all of the other reviews and is a little disingenuous.
I’ve removed your link from your post.
Steven,
Thanks for the update — and I had already read your article about hiding PHP warnings. I figured that was my next step.
I will start a separate topic on my “Anniversary Date” issue. (Unless your next update covers that, too.)
And I posted a mega-positive review for Connections months and months ago — I wish all plugin authors would be as responsive and proactive as you are!
Thanks again!
DJ
Plugin Author
Steven
(@shazahm1hotmailcom)
@varsitysports
RE: I will start a separate topic on my “Anniversary Date” issue. (Unless your next update covers that, too.)
Yes, please open another issue… the next update will not contain a fix. One reason is because I can not even begin to think of a reason why that would occur.
If you can take a screenshot of the Date Fieldset Config and share it in your new support issue post, that would be a great first step.
From wp.com support site, here are a few ways you can share that screenshot with me:
- Upload the screen shot to a third party service like Snag.gy, Droplr or CloudApp and then share the image link from that service with support
Thanks!