quan_flo

Hi,
I’m sorry, this is not the scope of the module. The plugin cannot help you at this point.

Hi ravg,
I’m, sory I do not understand your concern exactly. What do you want the plugin to do?

no, I ‘m sorry, that’s actually not in the scope of the plugin.

Please take a look at my user profile, the website linked there and use the email from my website for further correspondence. Thanks!

Hi @jacobian64

almost everything is possible. You can add some code directly next to the code that stores the visit in the database.
But this problem is not really tirival because you should consider that not every visit should send a mail to the visited user. What sould be done if a user visits a profile (maybe via page reload) 100 times a day? it’s no problem to update the values in the database with each visit (this is what is done) but in combination with mails this will end up in spam mails. So you should store and use some data to prevent this.

If you need help in coding this feel free to contact me, but I hope you understand that I cannot add this feature to this plugin for free – it’s just not in the scope I have for this plugin.

Regards
Florian

You can ignore this. Turn off the output for php warnings for your webserver and just log errors to the server log

AS the Plugin description says the sending of the messages is blocked, just try out the Plugin for Details.
There is no message send to the admin.

Of course they work together. Each filter handles a different lapse of time. They do not conflict with each other. the criteria that stops sending messages wins.
if you send 7 messages in 5 minutes but not 10 in 10 minutes the plugin will stop the message author

with this code you exclude the users with id 1, 5, 8 and 23 from beeing tracked.
The tracked visits before you added the code still exist. The code only affects new visits that are not tracked then

An integration of myCred is not planned.

A counter that tells users how often a profile was visited is not part of the module.

no sorry I cannot help here, I did not deal with moderated topics yet

The state is saved as user meta data in your database

fixed in version 2.7
thanks for your feedback!

I forgot to execute the query.
first query: first execution: 0.2075 seconds, next executions (sql cache) 0.0004 seconds. returns 11 results. wp_posts table has 391.064 rows.
second query: 0.24 seconds, next executions: 0.0005 seconds.
The queries seem to be quite similar in execution time at my system