Seems to be picking up the feed properly now although I get this error above the stats graph:
Warning: max() [function.max]: Array must contain at least one element in/home/fatclub/public_html/wp-content/plugins/feed-stats-plugin/fs-render.phpon line 30
I’m guessing this might be to do with there being no stats in the graph yet?
It is also still loading the sidebars of my blog when I test the feed.
so will the error disappear once the stats start building in the graph?
Or is there something wrong with the feed?
>> Seems to be picking up the feed properly now although I get this error
>> above the stats graph:
>>
>> Warning: max() [function.max]: Array must contain at least one element
>> in/home/fatclub/public_html/wp-content/plugins/feed-stats-plugin/fs-render.phpon
>> line 30
That appears to be a regression of some sort. I recall fixing that a
while ago. I'll go suppress the warnings/add better chart error
handling.
I really need to start doing unit testing to catch this.
>> I'm guessing this might be to do with there being no stats in the graph
>> yet?
Yes. That's probably correct, especially if, as Bram said, you just
burnt the feed.
>> It is also still loading the sidebars of my blog when I test the feed.
Looking at your site, that may be happening because of a 404 error.
Is the awapi-test.php file in your feed-stats-plugin folder? If not,
try re-uploading the package. The awapi-test.php file is what tests
the FeedBurner feed.
Thanks again for testing!
Jonathan Wilde
>I really need to start doing unit testing to catch this.
I'm still getting the same error and no feed stats.
>Yes. That's probably correct, especially if, as Bram said, you just
>burnt the feed.
My feed has been active since last year and Feedburner stats are displaying
fine through my Google accounts admin page.
>Looking at your site, that may be happening because of a 404 error.
>Is the awapi-test.php file in your feed-stats-plugin folder? If not,
>try re-uploading the package. The awapi-test.php file is what tests
>the FeedBurner feed.
Yes awapi-test.php is definitely in there...
> I'm still getting the same error and no feed stats.
The error has been fixed in trunk.
However, it was a bigger problem than just a new feed. Manual tests
of the Awareness API on your FeedBurner link indicate that your feed
doesn't have the Awareness API enabled.
https://feedburner.google.com/api/awareness/1.0/GetFeedData?uri=thefatclub
For some reason, FeedBurner was sending a 401 unauthorized message
instead of the usual XML error. The code wasn't catching this. This
has been fixed in trunk as well.
> Yes awapi-test.php is definitely in there...
Are there any non-standard directives in your .htaccess file that
might cause the URL to awapi-test.php to be rewritten into WordPress?
Awapi-test.php runs as a standalone PHP script.
In trunk, I've worked around this potential issue by having it run
inside of WordPress admin.
All of these fixes are present in version 1.0.5 beta 3. You can
download beta 3 at:
http://downloads.wordpress.org/plugin/feed-stats-plugin.1.0.5-b3.zip
Thanks again for your help,
Jonathan
On Fri, Feb 20, 2009 at 1:26 AM, Bram Vandenbussche <arb...@gmail.com> wrote:
> On pt 2 of this last email I'd like to add:
> "same problem here"
> I keep getting this message when i check my stats:
> There weren't any items that were clicked on in your feed yesterday. If you
> just turned on item stats, wait a day or two for information to start
> showing up.
>
> And I don't know what I have to turn on for that.. I think I've got most of
> it turned on already...
As far as I know, there's nothing extra to turn on. When I manually
browse the item stats for your feed, I get a 500 error:
This appears to be a bug with FeedBurner's new Awareness API. I did a
quick check of the FeedBurner Support Google Group and it has been
reported twice already:
http://groups.google.com/group/feedburner-for-developers/browse_thread/thread/6899eb3c315d37d7
http://groups.google.com/group/feedburner-for-developers/browse_thread/thread/3705b0af9f60e7d4#
In the meantime, I've made one change to the code in trunk so that you
can at least see a graph of your reach stats.
> On Fri, Feb 20, 2009 at 10:12 AM, Alexei Lee <al...@kikbakmusic.com> wrote:
>> 1. The graph horizontal axis is too small to display the dates in that
>> format, they are overlapping quite a bit so are unreadable. A small thing
>> but thought I would let you know.
I'm planning to fix this in two ways:
1. I'll have the charts auto-resize to fit the tabbed areas (with
an option to disable that behavior).
2. Create a maximum number of chart labels.
Eventually, I'll look into a nicer (and more space efficient) way to
display chart labels.
Thanks for your help,
Jonathan