[Suggestion] Timestamp information

I will look into it.
as a first thought, maybe we can provide this in a different block, when you install the module you get a (timestamp)ed block.
what do you think?

Awesome, lets add the timestamp field
Its the datetime field that tells the entity visiting time.
We might call it, 'Entity visiting time'.
Cool and intuitive you think?

Hey come on,
It's not a problem.
I think that it's a cool idea 😁
Sometimes ideas contribution can totally change the way of the implementation.

I'm on a tight schedule right away. Will find sometime and work on it!

Thank you 😊

Hello Toprak,

I have done the changes, now there is a new block with the timestamp as long as a new DateTime field called "Entity visiting time"

hopefully, this makes your experience better now :)

Hi, installed alpha5 versione, but i cannot see changes: no new entity time field, no new block, and no db changes.
The last time the entity is visit was already present in alpha4.
Do I have to remove and install new version maybe?
I'm using d8-8-5
thanks
Bye

Hello @toprak,
That's mainly a view configuration to separate the user,
I will fix it in the ready block though.
For the time, do you think we should be updating the time on every visit? maybe we can add a new configuration in the configurations for to check/uncheck this option "Update time on every visit" and setting it by default to false.

@alternivo, yes you will have to reinstall the module to update the configurations available in the config/install directory.
or if you have content there already, you can import the configurations from config/install directory manually

check this https://www.drupal.org/docs/8/modules/d8-rules-essentials/importing-and-... for more info about importing configurations manually.

thank you for the helpful responses guys :)

Hi miodel, thanks for the suggestion for the module update...and for your work :)
Just to understand: i create a custom view with users visit on current user, with the last visit time on the title, so when a new user visits current user profile, then the last visit time is updated.
What should be great is to have the single timestamp of each visit of other users...is it what you implemented in version alpha5?
bye

Hello alternativo,

No, what I've actually implemented is the first visiting time only and it's not being updated yet.

I was asking toprak if I should make such option configurable. I think that some people would love to have it the first visit time only and some people could want it to be updated on every visit.
What do you think?

Hi miodel,

now I understand what you implemented: so the timestamp is unique, specifying the first time a user/node page is viewed globally, that should be the already existent 'created' time.
But it's not what we (i'm guessing this..) aspect: considering the image, I aspect to see 4 dates, one for each (first) time visit by 4 users.

About your question, I think we have to focus.
If you want to make updatable the timestamp you added in alpha5, there is yet the field 'modified' time that updates last time a user/node is visited.

I think the need is to have the time visit field for each user visit of the user/node page.

ie: user A id the target visited profile.

block of users viewed the profile A:
NAME VISIT TIME
user B - 11/03/2020 12:36
user C - 10/03/2020 10:55
user D - 06/02/2020 07:11

if a user make a new visit of user A profile, the relative visit time will be updated.
This should be the best...in my opinion of course.

Thanks

Hello @toprak and @alternativo :)

I think that the @toprak's advanced option is cool yes, that makes more sense and looks more like Linkedin's way.
whenever the user visits the entity, we keep a record of it.

don't you think there could be a use case for showing only the last visits ( the basic option) without duplications?
maybe I will try to make a new configuration that is "Log all the visits even if it was duplicate" or if you can think of a better configuration option?

let me do an alpha6 tonight and get back to you :)

Great,
I was meaning duplicate in terms of the visitor.
But yes the visiting time is different.

I'll be adding the two options anyways since the advanced option's database consumption is higher.
Every visit is a new record. If someone needs the last visiting time only not all the times.
This can make a lot of extra records, hence a big database space consumption over the time.

So, there will be that configuration option (show only last visits per user) which will be disabled by default meaning that you are using the advanced option (every visit for each user) and if you enable it you get the basic option (only the last visit of each visitor)

What do you think?

Hi,
sure having the option to choose between the 2 option will be perfect, so depending on the features of your site, you can select the one you need.
My logic should be to have the basic option by default - less db consumption, and the advanced to enable: but it doesn't make big difference.
Thanks :)

Hello guys :)

can you please try the latest changes

I will make a new release after you try it and tell me what you think.

here's the git command

git clone --branch 8.x-1.x git@git.drupal.org:project/entity_vistiors.git

I have done what we agreed on for the last visiting time, added a configuration option under /admin/config/entity_visitors/entityvisitiorsconfig for that.

any feedback will be welcome :)

Thank you.

here are some notes:

• maybe I should choose to the basic option by default, now the advanced is selected by default, right?
• maybe we need a more descriptive text for the field titles and the descriptions, can you help me with that?

Hi, can't install with git , errors:
Warning: Permanently added 'git.drupal.org,140.211.10.58' (ECDSA) to the list of known hosts.
git@git.drupal.org: Permission denied (publickey).
fatal: Could not read from remote repository.

Tried to unistall alpha5 e install dev, but error:
Fatal error: Trait 'Drupal\Console\Command\Shared\TranslationTrait' not found in C:\localhost\d8-8-5-dev0\modules\contrib\entity_vistiors\src\Form\EntityVisitiorsConfig.php on line 15

Did you notice there are some files and code with 'visitiors' instead of 'visitors'?
could be a related problem?..i remember first time i installed alpha4 version, i did not manage to enable module via drush because of the bad naming, so I enabled using admin controls.

Hello @toprak :)

can you please try the latest code changes, and after you install the module you should see a message showing you the confiugration
page.

also, I have made the configuration page accessible from /admin/config.

I have updated the module with your images, by the way, thanks to you :)

would love it if you guys can help me testing the mailing functionality too, it's there now. hopefully, you like it!
Thanks you guys for the support.

Hello @alternativo,

Sorry for the dumb typos.

Since we are still in the first stage of development, I think I will stop supporting this module and create a new one since this one has a typo
entity_vistiors.

I will work on fixing any other typos in the files!

hopefully, I will be stabilizing the module in the next couple of days.

well well well,

a lot of changes today :)

to fix the Drush issue and so many other issues, I had to create a new module to fix the typo issue.
there was no way to edit the module short name according to the infra team.

you can access the module from here
I have fixed some issues there including the translation trait in Version alpha7.

I have also created a duplicate issue here. let's continue there if you have any more comments.