Can you please report the issue over at Github () as per my request? I don’t give support here on the WP.org forums for the simple reason that there are no collaboration possibilities.
Furthermore a few more details would be helpful. Is your site a multisite or a standalone site? Does the error also show on the frontend? Is the site working or is it impossible to access your dashboard now, does the error show only when debug is on or also when it’s off, what it the exact content of the error, etc.
Bedankt,
Piet
As a quick follow up:
2014.04.16a fixes this bug
I also would like to say this:
Although I appreciate the bug-report and I will of course fix those type of things instantly, I am not impressed with the fact that you completely and therefore disrespectfully have ignored all the requests to post issues via Github.
As it turns out:
- it was not an error, but a warning; BIG difference
- the warning only showed with debug set to
true
Anyways, it is fixed now, you can continue using my excellent plugin and it would be very nice if you would show your appreciation by leaving a 5-star rating!
Bedankt,
Piet
No problem Piet, I did not see the part you only give support on Github … missed that part. It concerns a standalone site and yes the error showed also on the frontend and in the admin widget. I am using the 2014.04.16 update and it shows this when trying to connect to WordPress.com:
Warning: Invalid Jetpack option name: wpcc_options in /home/spanje/public_html/wp-content/plugins/so-jetpack-stats-only/class.jetpack-options.php on line 46
Warning: Cannot modify header information – headers already sent by (output started at /home/spanje/public_html/wp-content/plugins/so-jetpack-stats-only/class.jetpack-options.php:46) in /home/spanje/public_html/wp-includes/pluggable.php on line 896
Anywway, I will commend on Github and yes … 5 star is in place (I have to give stars more often). Thanks Piet (en niet boos worden, ben geen plugin wizard)
Hi Remco,
You don’t need to add this to Github anymore as I already released the bugfix. Next time you can use Github, but then again, hopefully next time around a bug report is not necessary 🙂
Just out of curiosity: why do you have debug set to true on your site?
Piet
PS Ben niet boos hoor, vond het een beetje jammer, want ik wil het liefst alle issues op Github hebben…
I actually don’t have Debug set to True but on FALSE !! But I suppose you are looking at the solucioneswebplus.com website. I am talking about http://bit.ly/1lNw9as this website where I did the update and where the problem occured. I will stop now on this forum and switch to Github.
BY THE WAY: The issue is indeed resolved thanks to the quick action of Piet!
