tcnet

I just updated to version 1.0.6 which should solve the problem.

Sames to be a bug in PDO in some PHP versions. Please open ProcessPageViewStat.module and change line 771 from: $query->bindValue(':rowlimit', $rowlimit, \PDO::PARAM_INT); to: $query->bindValue(':rowlimit', (int) $rowlimit, \PDO::PARAM_INT);

If someone doesn't want to see the IP addresses, they can hold their hands over them. Over and out!

Nobody except you can see the IP's! Where is the problem? If IP's stored with xxx in the database then it's no more possible to count the visitors and this would make the whole module worthless.

Thank you too! I was assuming that it's the database driver.

No, this are single quotes: '' I guess you uploaded the files in the wrong transfer mode. Otherwise, the stored int variables becoming strings. I don't know why. Or it has to do with PDO.

It seems to be the row LIMIT. But I cannot be reproduce it. Try to change the row limit in the configuration to another value. Please also search the problem in your PHP/MySQL environment. Did you uploaded the files with FTP in the right transfer mode?

Today I've tested VSCode. It's MBS! M stands for Mega. Anyway, project is on GitHub now. But it's probably the last time. For updates and new features check my blog. Thank you!

Version 1.0.1 doesn't have namespace. I couldn't reproduce it without namespace. But I can reproduce it with namespace. I've made changes now.

I'm pretty sure that I can live without GIT. I've been doing very well without GIT for 20 years now and I won't change that. I usually work with VC++, Java and Pascal. PHP for me is just a kind of hobby.

WAIT! $dt = new \ProcessWire\datetime(); This is NOT my code!!! Line 532 is: $dt = new DateTime();

I'll try it next week. Only for this module. Sure!

For some reason, GitHub/git will never be an option for me. Don't laugh, but for PHP I only use a text editor with highlighting. I'll try VSCode next week. Thank you for your explanation.

I don't use any versions controlling. I just created an account on GitHub a few hours ago. See: https://github.com/techcnet/ProcessPageViewStat But file oploading with browser don't work in GitHub. It's not a problem with the browser. I tried Chrome and Firefox. It's a problem with the upload on GitHub. I also tried GitLab. When I click the + to create a new project I get a white blank page. My browsers are ok. Seems to me they don't want any users.

Sorry. I tried it. But cannot upload on GitHub.

As far as I know, FieldtypeDatetime is installed by default in ProcessWire. Did you uninstalled FieldtypeDatetime or deleted the "datetime" field type?

Usually I don't work with GitHub. But if you insist and as soon as I've enough time, I'll upload it to GitHub, GitLab or something similar.

Not on github. Sorry. I posted it already in the modules directory at the same time like the first post here. Here is the link: https://modules.processwire.com/modules/process-page-view-stat/

Hello and Thank You! Of course I've some screenshots. I wasn't sure if these screenshots were appropriate to show here. I've made IP addresses unrecognizable.

Page View Statistic for ProcessWire is a module to log page views of the CMS. The records including some basic information like IP-address, browser, operating system, requested page and originate page. This module doesn't claim to be the best or most accurate. Advantages One of the biggest advantage is that this module doesn't require any external service like Google Analytics or similar. You don't have to modify your templates either. There is also no Javascript or image required. Disadvantages There is only one disadvantage. This module doesn't record visits if the browser loads the page from its browser cache. To prevent the browser from loading the page from its cache, add the following meta tags to the header of your page: <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" /> <meta http-equiv="Pragma" content="no-cache" /> <meta http-equiv="Expires" content="0" /> How to use The records can be accessed via the Setup-menu of the CMS backend. The first dropdown control changes the view mode. Detailed records View mode "Detailed records" shows all visits of the selected day individually with IP-address, browser, operating system, requested page and originate page. Click the update button to see new added records. Cached visitor records View modes other than "Detailed records" are cached visitor counts. Cached visitor records are collected on a daily basis from the detailed records. This approach is new in version 1.0.8 and ensures fast display even with many records. Another advantage is that the detailed records can be deleted while the cache remains. The cache can be updated manually or automatically in a specified time period. Multiple visits from the same IP address on the same day are counted as a single visitor. Upgrade from older versions Cached visitor counts is new in version 1.0.8. If you just upgraded from an older version you might expire a delay or even an error 500 if you display cached visitor counts. The reason for this is that the cache has to be created from the records. This can take longer if your database contains many records. Sometimes it might hit the maximally execution time. Don't be worry about that and keep reloading the page until the cache is completely created. Upgrades in general It seems that the upgrade function don't get called after an upgrade. This might be a bug in ProcessWire. This can lead to an error message ("Unknown column...") if you try to open the statistic page immediately after an upgrade. There are two ways to avoid this error message. Click the "Continue to module settings" button directly after the upgrade or open the Modules page and click the "Refresh" button. Time of view This module can record the time a visitor viewed the page. This feature is deactivated by default. To activate open the module configuration page and activate "Record view time". If activated you will find a new column (S.) in the records which means the time of view in seconds. With every page request, a Javascript code is added directly after the <body> tag. Every time the visitor switches to another tab or closes the tab, this script reports the number of seconds the tab was visible. The initial page request is recorded only as a hyphen (-). Execution time Starting with version 1.1.9 this module records the PHP execution time from the initialization of the module till the HTML output in seconds. Settings You can access the module settings by clicking the Configuration button at the bottom of the records page. The settings page is also available in the menu: Modules->Configure->ProcessPageViewStat. IP2Location This module uses the IP2Location database from: http://www.ip2location.com. This database is required to obtain the country from the IP address. IP2Location updates this database at the begin of every month. The settings of ProcessPageViewStat offers the ability to automatically download the database monthly. Please note, that automatically download will not work if your webspace doesn't allow allow_url_fopen. Dragscroll This module uses DragScroll, a JavaScript available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability in view mode "Day" to drag the records horizontally with the mouse pointer. PhpUserAgent This module uses PhpUserAgent available from: https://github.com/donatj/PhpUserAgent. PhpUserAgent is required to filter out the browser type and platform from the server request. New in version 1.1.0 A new feature in version 1.1.0 offers the possibility to record user names of logged in visitors. Just activate "Record user names" and "Record loggedin user" in the module settings. New in version 1.1.3 A new feature in version 1.1.3 offers an internal WHOIS function. In the module settings you can switch between internal and external WHOIS. New in version 1.1.4 Detailed records can now be exported as CSV-file. The file contains all data of the specified date regardless of the pagination. The button is located at the bottom of the page. New in version 1.1.8 The UserAgentParser was exchanged with PhpUserAgent due to some complaints.