After publishing content as page or blog, and the ediing that item, the number of reads given is suddenly bloated, e.g. http://www.mightyzero.com/node/20 from 1 to 18446744073709551614.

CommentFileSizeAuthor
#4 bloated content reads.tiff172.06 KBchueewowee

Comments

beginner’s picture

beginner commented
Version: 4.7.2 » x.y.z

What?

Do you always get this bug?
How can we reproduce on a fresh Drupal install?

chueewowee’s picture

chueewowee commented

It always happens on each edit with my update to 4.72 from 4.71. I have only one installation.

*I could try updating another site.
*Perhaps there is a conflict with another module: If that is so, could you suggest which are likely and I switch them off?
*If you wish to open an account at www.mightyzero.com and tell me your name, i could give you editing privilidges for you to try and see the bug in action yourself.

chueewowee’s picture

chueewowee commented
Title: node edit bloats statistics for reads » node submit bloats statistics for reads

I just posted a new quote and got nine 'reads' upon submittal (published).

chueewowee’s picture

chueewowee commented
Title: node submit bloats statistics for reads » Edit content bloats statistics - why? please.
Version: x.y.z » 4.7.2
StatusFileSize
new bloated content reads.tiff172.06 KB

go to this page: http://www.mightyzero.com/popular/alltime and you will see the number of reads for newly created but once edited posts. They show millons of reads. EAch edit does this.

1)WHat table is responsible for logging reads?
2) with what module could a conflict be happening?

chueewowee’s picture

chueewowee commented

When I submit an edit I get this error message:

query: DELETE FROM page_title WHERE nid = 20
error:

beginner’s picture

beginner commented

You mention that this may be a conflict with a module, which is the most likely.
Can you turn off all contrib module and see if you can still replicate the bug with only core modules.
If not, turn on each contrib module on one at a time and see the one that causes the problem.

chueewowee’s picture

chueewowee commented

Update: I removed the module 'page_title' and things have improved. The statistics are no longer bloated.
Now when I submit an edit the read statistics actually drop, e.g from 10 reads to 7!

How do I clear the bloated numbers?

beginner’s picture

beginner commented
Project: Drupal core » Page Title
Version: 4.7.2 » 4.7.x-1.x-dev
Component: node.module » Code

Apparently, there is a serious bug with the Page Title module.
I don't know this module at all.
I have reassigned the bug: maybe the module maintainer can help you, now.

robertdouglass’s picture

robertdouglass commented

I'll take a look but have a real hard time seeing how this issue could be related to page_title. All the module does, after all, is set one variable for the page.tpl.php file.

chueewowee’s picture

chueewowee commented
Title: Edit content bloats statistics - why? please. » Preium Module bloats read statistics - after submit Edit Content

Thanks.

I took the time to remove modules one at a time. Page_Title gives the query: DELETE FROM page_title WHERE nid = 20
error. It does not bloat the reads statistics. Premium module does.

Issues remian: When I removed this module and edited a post with 21 reads, it dropped three reads, as observed before with other posts. (Bizarre, I know).

PLease advise: how to clear number of reads, or reset to desired number?

robertdouglass’s picture

robertdouglass commented
Project: Page Title » Premium
Version: 4.7.x-1.x-dev » master

not sure what version to set this too, but sending it on to the Premium module issue queue

chueewowee’s picture

chueewowee commented
Title: Preium Module bloats read statistics - after submit Edit Content » Premium Module bloats read statistics - after submit Edit Content

I got it fro the 4.7.2 repository. I'm running Drupal 4.7.2.

Any ideas , please Robert, on resetting my read numbers...i.e which tables am I loking for?

robertdouglass’s picture

robertdouglass commented

I think truncating your accesslog table will do the trick but try it on a backup first.

allie micka’s picture

allie micka
she/her
commented

Just like page_title, I have a hard time believing that premium has anything to do with this. Premium does not mess with data in any way; it simply replaces the node's body with its teaser content during a view operation.

Can someone provide a clear picture of how to reproduce this problem?

chueewowee’s picture

chueewowee commented

take a look at my site, given above which was only recently launched and the number of reads. As I said
I also doubted Premium's role for just the same reasons.

But twice I carefully switched off one module at a time and tested the problem, after switching off the two problematic modules together. I can give you the WHOLE list of active modules, if in case it is a compounded problem. Otherwise, simply install 4.7.2 and the excellent Premium module, and post then edit your posts.
Use your drupal ID to authenticate and post a page or blog. Edit it. Then inform me via feedback, and I will switch on just Premium for you to edit again and view the result.

Does anyone know how I can reset mypost numbers. If not how can you be certain the module cannot affect post numbers? If so I would like to do justy that as it is a live site.

Thanks,

John Plumridge

chueewowee’s picture

chueewowee commented

following on, if you wish to use my problematic installation in the wya described above, instead of creating your own installation, I meant log in with your drupal ID to www.mightyzero.com

chueewowee’s picture

chueewowee commented
Title: Premium Module bloats read statistics - after submit Edit Content » Premium Module bloats read statistics - duplicated on two installations

I have duplicated the problem on two installations now, one on my home computer with a fresh Drupal installation. Premium Module was isolated by switching on and off. It happpens on blogs and pages. It doesn't matter wether the post is pretocted by Premium or not, so long as themodule is active.

beginner’s picture

beginner commented

I don't use Premium.module, so I won't be able to help you with this bug. Provide clear step by step instructions to reproduce the bug and hopefully, the module maintainer will be able to help you.

If you want to reset your count pages, look in phpmyadmin at the {node_counter} table of your installation: there you have stored the node ID, the day and total counter (page views) and the timestamp of the last access date. Once the bug is sorted, you can reset everything to 0 in that table.

chueewowee’s picture

chueewowee commented

Thanks Beginner. I beleive the production of the bug is clear as written and repeated:
simply editing a post with the module installed and activated under modules causes the bloated 'read' counts.

chueewowee’s picture

chueewowee commented

Caching may have led me astray. Also some weird behavour. Anyway, appears to be the browscap module

chueewowee’s picture

chueewowee commented
Title: Premium Module bloats read statistics - duplicated on two installations » Statistics Filter Module bloats read statistics
Project: Premium » Statistics Filter

I have tracked it down for sure now to the statistics filter module

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

This is probably because the statistics filter module runs db_query('UPDATE {node_counter} SET daycount = daycount - 1, totalcount = totalcount - 1 WHERE nid = %d', arg(1)); without checking if totalcount or daycount is greater than zero, since those fields are unsigned.

frank ralf’s picture

frank ralf commented

Thanks for the hint. This query is still in the code and might need some updating.

frank ralf’s picture

frank ralf commented
Version: master » 7.x-1.x-dev
Assigned: Unassigned » frank ralf

Will have a look at this issue while porting to D7.

thmnhat’s picture

thmnhat commented
Status: Active » Fixed

This is fixed in D7

thmnhat’s picture

thmnhat commented
Version: 7.x-1.x-dev » 7.x-1.1

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.