Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Database entries in VxUtG_podlove_downloadintentclean missing #926

Closed
juekr opened this issue May 8, 2017 · 4 comments
Closed

Database entries in VxUtG_podlove_downloadintentclean missing #926

juekr opened this issue May 8, 2017 · 4 comments

Comments

@juekr
Copy link

juekr commented May 8, 2017

Expected behavior

Earlier today, the analytics section showed somewhat around 1.900 downloads over all of our podcast episodes.

Actual behavior

Comparing an older backup file (this morning) with a current database dump (a few minutes old) shows: the newer file has ~280 less rows in the table VxUtG_podlove_downloadintentclean.

System information (see Podlove > Support menu)

Website http://das-a.ch
PHP Version 7.0.14-nmm1
WordPress Version 4.7.4
WordPress Theme Mon Cahier Child v1.0.0
Publisher Version 2.5.2
Web Player Version 2.1.1
Twig Version 1.32.0
open_basedir ok
curl Version 7.35.0
iconv available
simplexml ok
max_execution_time 30
upload_max_filesize 200M
memory_limit 256M
disable_classes
disable_functions
permalinks ok (/%postname%/)
podlove_permalinks ok
podcast_settings ok
web_player ok
podlove_cache on
assets
  - mp3 audio/mpeg http://das-a.ch/feed/mp3/
  - m4a audio/mp4 http://das-a.ch/feed/m4a/
cron ok

0 errors
0 notices
Nice, Everything looks fine!

@eteubert
Copy link
Member

Is it possible you used the "Download Intent Cleanup" Tool manually? Because the automatic hourly job only aggregates new data, but when you start it via the tools page, it calculates everything from scratch.

Now, deduplication works better when looking at the whole dataset at once, which means that you may seem to lose some downloads. However, running "Download Intent Cleanup" should always result in the same numbers.

I can't say for sure if that's what happened but it's my best guess for now :)

@juekr
Copy link
Author

juekr commented May 15, 2017

Thanks for getting back to me about that. No, to my knowledge nobody triggered a manual cleanup.

So does that mean that if I don't do manual cleanups from time to time, my numbers actually get way too high?

Cheers,
Jürgen

@eteubert
Copy link
Member

So does that mean that if I don't do manual cleanups from time to time, my numbers actually get way too high?

They may be higher but not significantly. I consider this a bug and hope I will find a way around this some day.

@juekr
Copy link
Author

juekr commented May 16, 2017

Okay, thanks for the insights!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants