From what you have described, go with the relationships as per Juho's suggestion view reply

Okay i want to ask (maybe) once again  , what should i choose ? create_annotation or add_entity_relationship which one that use more resource (memory, CPU usage, etc) ? note: i will save data every user open full-view... view reply

Yep relationships will work too, just make sure you manage them in a spot where it's clearly the page for the content.  Eg. blog/all will load 10 blogs and output them with elgg_view_entity(), you don't want to log them all as... view reply

@juho i think it will work, thanks but how to get last 10 visited page  ? can i put 'limit'=>10 , 'order_by' => time_created dsc ? view reply

I think I would implement this by creating a relationship between the user and the piece of content: add_entity_relationship ($user_guid, 'has_read', $content_guid) This way I could always get the latest data. Consider... view reply

@dries : i've re-explained my purpose above , i hope you understand now and can help me :) view reply

@matt becket , so the conclusion the annotations is the best way ? okay i will try it view reply

Thanks Matt! Just about to. Im currently upgrading my servers again. Interestingly I did it on a server running Centos 7.2 and no issues. However that server is limited to some other projects I dont want to mix around so upgrading my server on the... view reply

okay, to avoid misunderstanding,  i will explain my purpose : I want to make a feature :  Recommendation (show entities list that contains user favourite topic) So i need data of user 's favourite topic Simple example: Alex... view reply

plugin settings aren't stored as arrays.  You could do that and store it as a serialized array if you want to pretend we're in wordpress ;) Annotations would probably be the best bet here - listen to Dries, just make sure you're... view reply

Aha, I think I got you wrong, Do you want to log what users visited your website? I thought you wanted to log every lastpage 'a user' visited view reply

okay it's too complicated for me what if i just use: $value = elgg_get_plugin_setting('lastvisited',$userguid,'lastvisited'); $url =... view reply

CSS: .hidden-fix, .elgg-page .hidden-fix {     display: none; } JS: var hiddenfix = function() { $('.hidden, .hide').removeClass('hidden').removeClass('hide').addClass('hidden-fix');... view reply

and in the case you only want the latest one (I thought I read somewhere you wanted the last 10 visits, but can't find it anymore) It would be: $user_guid = elgg_get_logged_in_user_guid(); if... view reply

I'm thinking updating isn't a good approach here, it might be better to just delete the oldest one and create a new one, just thinking with you... that would be this then: $user_guid = elgg_get_logged_in_user_guid() $count =... view reply

I honestly don't know, I'm sure there are better experts to answer your question then I, but you 'could' do something like this, to store only the last 10 annotation and only update the oldest one: But again, I don't know if... view reply

Hey, welcome to Elgg.  Learning curves can suck, but it sounds like you've got a background that would lend itself to this :)   Have you checked out the docs?  There is a section there about... view reply

check that the .htaccess is the one that comes with elgg.  You can find a copy at {elgg}/install/config/htaccess.dist view reply

You will get 'a lot' of annotations if it's storing every pagevisit of every user. what's the worst if i get a lot of annotations ? view reply

create_annotation($user->guid, 'lastvisitedpage', $_SERVER['REQUEST_URI']); You will get 'a lot' of annotations if it's storing every pagevisit of every user. view reply