Not sure if this will be helpful to the admin, but I noticed a bug today where upon going through photos by clicking on them, advancing to the next, the page occasionally hangs. Upon hitting refresh, the view count on the photo is advanced 20-100 views past what it was previously. I've duplicated this effect a few times now as seen here:
First
Second
Third
Second bug I noticed is when a photo has more than one page of comments, switching between pages adds 1 to the view count, as seen here
Also noticed refreshing occasionally adds a view to photos, and on this discussion page refreshing adds 1 view per every refresh. It should be noted this happens while I'm logged in, with adblocker disabled, cookies enabled, using Firefox 45.0.2 on Win8.1
Tags:
Looking into it Colton - thanks for bringing it to my attention.
Simple page refresh also increments view count by 1 for posted photos, unless the photo is one's own! Unfair?
Blogs as well, whether one's own or other.
In the case of one's own photo, it used to be that text edits incremented the view count upon saving, then someone fixed that. But still if one edits one's own blog and saves, the view count does increment.
All a little irregular.
I have been in contact with Ning about this and this is there reply - after several clarifications and it appears that we are stuck with this ....
"In Ning network each page view (each reload) counts as a view on your blogs, forum posts, and other content items. This isn't limited to a single session, where the same member might view the same blog 3 or 4 times. So we're not counting unique views here (how many individuals viewed a given blog), but absolute views—how many times the blog was displayed in a browser, even the same browser. Unfortunately, there isn't a way for us to change that." (Ning Help Center)
Strange. This only started happening recently
They do not address all issues here, however. For example, when a posting has more than a page of comments - they could easily distinguish a page change from a refresh.
One of the things happening is that they have assumed that everyone has upgraded from Ning 2.0 to 3.0 -this is where all the support is It is also where the extra charges come into play so unless we want to spend a whole lot more for what we have currently (like close to $1000/yr instead of the current $250) I'm opting to stay with what we have - bugs and all. I will continue to research the user knowledge base and will apply any fix I come across.
I'll bet that the first bug Colton talked about, the sticky page advance causing excessive counter incrementation, wasn't NING's problem, but something that happened en route, so they did receive, say, 100 page refresh requests.
Like a sticky trigger on a machine gun. Just a guess.
(Or the client has been drinking too much coffee.)
Wendy, I notice that we are using just over 33Gb, well in excess of our allocated 10Gb. Do we pay for that?
Now I notice that NING 2.0 PRO has been upgraded to 500GB for $599.90 annually. So I guess this is us.
Doug they haven't billed up for that - the upgrades in pricing went into effect in January and when our billing cycle came around in March we were billed at the old rate.
The other problems that Ning has been having has kept me locked out - this is the first day I have seen the entire site since last Monday....i truly hope they have everything fixed !!!!
Funny that we see more than you, but after reading comments from other NING clients, I think we may have been (relatively) lucky as it was.
© 2024 Created by Wendy Rosier. Powered by