Here we go … While I was away, my customer reset the statistics. I therefore had to wait a few days to get the values back to a workable state.
As already mentioned, the problem occurs with websites that are completely installed in a subdirectory (i.e. also the index.php – and not the installation variant where the index.php remains in the root directory). It makes some difference whether the cookies function is used in Koko Analytics or not (I have both variants for you to look at). The discrepancy is slightly smaller.
It should also be mentioned that there is now a WordPress installation in the root directory. But that makes no difference either. I have had the same problems without, already tested this (more below).
The scenarios in which issues arise are therefore as follows:
Scenario 1:
- empty (root)
+ WordPress 1 (subdir) *
+ WordPress 2 (subdir)
Scenario 2:
- WordPress 3 (root)
+ WordPress 1 (subdir) *
+ WordPress 2 (subdir)
(*) using Koko with cookies (for testing purpose never blocked by our Privacy/Cookie plugin)
Scenario 2 is what is currently used, while scenario 1 was used when I started this thread. For certain reasons, we had to forego the use of a multisite installation. However, we have made some changes in the root’s htaccess, mainly, as additional support for caching and security plugins that we also use (but would also work without) – e.g. use of RewriteCond %{REQUEST_URI} !^/subdir/.*$
. Regarding Koko-Analytics it makes no difference at all.
As I have temporarily deactivated the blocking of statistics cookies, I will not publish the links here, but will send them to your email address mentioned above, including screenshots of the current statistics overviews.
Regards