{"action":"created","issue":{"url":"https://api.github.com/repos/hypeJunction/hypeLists/issues/23","repository_url":"https://api.github.com/repos/hypeJunction/hypeLists","labels_url":"https://api.github.com/repos/hypeJunction/hypeLists/issues/23/labels{/name}","comments_url":"https://api.github.com/repos/hypeJunction/hypeLists/issues/23/comments","events_url":"https://api.github.com/repos/hypeJunction/hypeLists/issues/23/events","html_url":"https://github.com/hypeJunction/hypeLists/issues/23","id":162473908,"number":23,"title":"how to default to rendering only the end of a list of comments?","user":{"login":"propertunist","id":513903,"avatar_url":"https://avatars.githubusercontent.com/u/513903?v=3","gravatar_id":"","url":"https://api.github.com/users/propertunist","html_url":"https://github.com/propertunist","followers_url":"https://api.github.com/users/propertunist/followers","following_url":"https://api.github.com/users/propertunist/following{/other_user}","gists_url":"https://api.github.com/users/propertunist/gists{/gist_id}","starred_url":"https://api.github.com/users/propertunist/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/propertunist/subscriptions","organizations_url":"https://api.github.com/users/propertunist/orgs","repos_url":"https://api.github.com/users/propertunist/repos","events_url":"https://api.github.com/users/propertunist/events{/privacy}","received_events_url":"https://api.github.com/users/propertunist/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2016-06-27T15:02:25Z","updated_at":"2016-07-08T18:07:04Z","closed_at":null,"body":"the default view for comments in elgg is to have the newest at the top and oldest at the bottom. this means that we are reading the thread in a way that is backwards to the usual way of reading text.\r\nthere is an option in elgg_list_entities called ''reverse_order_by' that solves that problem, but when i use it with hypeLists i get inconsistent results across my servers and also unexpected placing of the 'load more' buttons. i don't know why i am seeing inconsistent results across my servers, but what i would like to have is:\r\n\r\n* newest comments at the bottom\r\n* the visible list of comments being limited in size\r\n* the 'load more' button being at the top of the list of comments, so that older comments can be loaded as desired.\r\n\r\nso far i have tried adding the following parameters to elgg_list_entities, but i haven't found a combination that works:\r\n\r\n* data-reversed\r\n* data-paginationPosition\r\n* position\r\n* reverse_order_by\r\n\r\ni have seen that in some cases i get a 'load more' button appear at both the top and the bottom of the list, but only when the page was opened via a river link for a mid level comment in the thread. this does not always work though as sometimes i click such a link and i just see the standard set of comments that i would see anyway when viewing the entity through a standard URL for it's page.\r\n\r\ndo you have any tips on how to achieve the desired outcome here?\r\nthanks"},"comment":{"url":"https://api.github.com/repos/hypeJunction/hypeLists/issues/comments/231431135","html_url":"https://github.com/hypeJunction/hypeLists/issues/23#issuecomment-231431135","issue_url":"https://api.github.com/repos/hypeJunction/hypeLists/issues/23","id":231431135,"user":{"login":"propertunist","id":513903,"avatar_url":"https://avatars.githubusercontent.com/u/513903?v=3","gravatar_id":"","url":"https://api.github.com/users/propertunist","html_url":"https://github.com/propertunist","followers_url":"https://api.github.com/users/propertunist/followers","following_url":"https://api.github.com/users/propertunist/following{/other_user}","gists_url":"https://api.github.com/users/propertunist/gists{/gist_id}","starred_url":"https://api.github.com/users/propertunist/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/propertunist/subscriptions","organizations_url":"https://api.github.com/users/propertunist/orgs","repos_url":"https://api.github.com/users/propertunist/repos","events_url":"https://api.github.com/users/propertunist/events{/privacy}","received_events_url":"https://api.github.com/users/propertunist/received_events","type":"User","site_admin":false},"created_at":"2016-07-08T18:07:04Z","updated_at":"2016-07-08T18:07:04Z","body":"ok, so from looking here: https://github.com/hypeJunction/hypeInteractions/blob/8bb4bfbc8df0d8d2b29d78225222220a4f386893/views/default/framework/interactions/comments.php\r\nit appears that i would just need to use the offset and maybe offset_key. does that sound correct?"}}
{"actor":{"display_login":"propertunist"}}