• Resolved huubl

    (@huubl)


    Hi,

    The value of page_id is 0 on every row in wp_burst_statistics DB table:

    Shouldn’t this be filled with the corresponding post_id (if available)?

    • This topic was modified 11 months, 4 weeks ago by huubl.
Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author Hessel de Jong

    (@hesseldejong)

    Hi @huubl,

    Some pages, like 404’s and archive pages, don’t have a page ID. But as you said normal posts and pages should have a page_id/post_id.

    Can you open the console on one of the pages? Visit the page > Right click > Inspect element > Click on the console tab.

    Then type in ‘burst.page_id’ and hit enter. Does that return a number?

    Kind regards,
    Hessel

    Thread Starter huubl

    (@huubl)

    Hi @hesseldejong,

    The page_id/post_id shows when using burst.page_id in de console.

    I looks like something is going wrong when the data gets insert into the database. When I put error_log(print_r($data, true )); before tracking.php#L685 it contains the page_id.

    Plugin Author Hessel de Jong

    (@hesseldejong)

    Hi @huubl,

    I’ve checked some of our databases and it appears there’s an issue when updating a hit. Burst sends a hit when a user visits a page and tries to update the hit when the user leaves the page. It seems to me that the update process overrides the page_id with 0.

    I have noticed some correct page_id’s, but most are set to 0. When the page_id is correct, the time_on_page is very low. I assume those hits are not updated, so I believe the issue lies in updating the hits. We made some changes a few weeks ago, so I think something went wrong at that time.

    Thankfully, we use page_url to generate the dashboard data, so it’s not a major issue. However, we will definitely create a fix for this issue. I’ll let you know when it has been resolved.

    Kind regards,
    Hessel

    Thread Starter huubl

    (@huubl)

    Hi @hesseldejong,

    Thanks for your fast reply and locating the issue.

    I noticed something else when testing. When using burst.page_id in de console on the blog page (post archive) it returns the ID of the first post. I think in this case it should return 0 or null?

    Plugin Author Hessel de Jong

    (@hesseldejong)

    Hi @huubl,

    It seems like you are correct. We use the ID from the Post loop, which returns the first ID. We have to figure out how we can exclude that for archive posts.

    I don’t have a fix ready for you immediately, but I will let you knwo when this issue has been fixed. Hope you understand!

    Kind regards,

    Hessel

    Plugin Author Hessel de Jong

    (@hesseldejong)

    Hi @huubl,

    These two issues have been fixed in the following branche on our GitHub: https://github.com/Really-Simple-Plugins/burst/tree/Page-id-fix

    This fix will be released with the following version of Burst Statistics. I hope it’s okay if I resolve this issue for now.

    Kind regards,
    Hessel

    Thread Starter huubl

    (@huubl)

    Hi @hesseldejong,

    Thanks, any idea when you will release a new version?

    Plugin Author Hessel de Jong

    (@hesseldejong)

    Hi @huubl,

    This will be released later this week or at the start of next week.

    Before releasing our upcoming version, we need to fix one bug and retest it. Once it’s done, we will release the new version with your issue resolved.

    Lately, updates have been slower than we would like, but we are doing our best to improve.

    Kind regards,
    Hessel

    Thread Starter huubl

    (@huubl)

    Hi @hesseldejong

    I see a new version is released, thanks!

    Plugin Author Hessel de Jong

    (@hesseldejong)

    Hi @huubl,

    Yess! We just released a quick fix. Because there was a minor issue while updating. So if please update to 1.6.4.1 🙂

    If your issue is not fixed with this update, please let us know!

    Kind regards,
    Hessel

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘page_id always 0 in wp_burst_statistics DB table’ is closed to new replies.