Patrick Robrecht

Hello Maman,

currently this is not supported, sorry. Maybe this will be added in some later version.

The feature of predefined time periods is available in the latest version (2.4) which has just been published.

Hi,

Statify – Extended Evaluation uses just the data from Statify and calculates any statistics on demand; no own settings or data are kept.

So if you leave the default value 14 days, Statify – Extended Evaluation can only evaluate the data of the last 14 days, as Statify comes with a cronjob which deletes the data longer than the time period set. That’s why Statify allows you to set the time period to any number of days.

I can select events from Events Manager for inclusion into Mailpoet v3 newsletters.

The feature I miss is to define a list of post types for the post notifications, e. g. all to include all posts and events from Events Manager.

Hello Flexxo,

that’s a great idea which will be realized in the next release. As the support forum is not the right place for feature requests, I moved the suggestion to this GitHub issue.

Hello Stefan,

from the FAQ:

Statify does not count the following views:

• feeds
• trackbacks
• searches
• previews
• views by logged in users
• error pages

This behavior can be modified with the statify__skip_tracking hook.

Google Analytics for example will count the views by logged in users if their JavaScript code for tracking is included on every page – that can be one reason why Google Analytics shows a higher number of views.

Which WordPress count do you mean? Another statistics plugin? You may check the criteria how the plugin counts views.

Currently there are no plans for AMT support.

• This reply was modified 7 years, 3 months ago by Patrick Robrecht.

I reproduced the error with WordPRess 4.4.x. Statify 1.5.1 is compatible with WordPress 4.7+ due to use of the 2nd parameter in wp_parse_url introduced in WP 4.7. In WP 4.4 the second parameter for wp_parse_url is not supported and the function returns an array – that’s why $data[‘target’] is set to ‘Array’ in statify_frontend.class.php::75.

Updating WordPress to 4.7+ should fix the problem.

As I wrote on Problem: Beste Inhalte I cannot reproduce your the error (this seems to be a problem with the old WordPress version you use – at least another user solved the same problem by updating to the latest WordPress version).

Hi buchaviso,

another user (@sabinerocktimes) reported the same error in this thread, but we couldn’t reproduce the error: entries really were saved in the database incorrectly, you may check whether this also holds for your case. She solved the problem with an update to the latest WordPress version.

Note that your WP version 4.4.1 is quite old (and even not the latest one of the 4.4 series).

Hi,
Statify comes with a cron job deleting database entries which are older than the period of data saving set via the widget Dashboard. This means there should be no database entries from 2014 anymore if the period of data saving is 365 days.

As Statify – Extended Evaluation loads the data from the Statify database table, the cron job seems to be not setup correctly on your WordPress. You can find details how to check the cron job setup on this GitHub issue.

Thanks for the feedback!

Hi csigncsign,

this plugin cannot display resuls at the frontend, but Statify Widget does (I haven’t checked whether it works with the latest WordPress version).

You can find a list of Statify extensions on the Statify FAQ (“How to extend this plugin?”)

Hi ITfee,

I’ve just published a bugfix release (2.3.1) – the errors in the yearly view should be fixed after the update.

Hi ITfee,

I can confirm the bug, a bugfix release is planned for the weekend.