Hello again

Thanks to Juho for his tips. I was reviewing the console-log() and I found a depecated event that no longer worked in version elgg 2.0 because it uses jquery 2.2.0 and other small bugs. Through apache access.log finally I found the failure that happens in the infinite-scroll when the next page loads, I do not know why the failure happens but I know what is the solution.

All my test installations have the name of elgg version (eg elgg-8, -11, -12 ...) for some reason when the route contains 2 the Get of apache changes to 1 to call the next page loaded into the infinite-scroll, for that reason failed elgg-version 1.12 and/or 2.0.

::1 - - [10/Feb/2016:17:57:25 +0100] "GET /tester/doce/elgg1134567890/core?offset=20 HTTP/1.1" 404 1343 "http://localhost/tester/doce/elgg1234567890/core" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko"

The xampp htdocs folder /tester/doce/elgg1234567890/core
/elgg1234567890 is the name of the folder that contains the installation of elgg and has that name to test if another number changes as well.
/core is the name of the page where masonry is applied.

Only changes the 2 for 1 anywhere on the route when it's trying to load the next page, only happens with infinite-scroll. I found in jquery.infinitescroll.js file a regex that identifies the 2 and change the route

path = path.match(/^(.*?)2(.*?$)/).slice(1);

I don´t know well the language JavaScript but will try to modify or try a different version of infinite-scroll to resolve this issue, it is part of learning; D

In relation to make available the plugin, It took me a long time working on it, even I do not have a functional version because it is related with other plugins and theme, I have not done an administer interface to apply on specific pages yet, it is also necessary to modify or adapt the river views or objects to a brick, but I did it from other plugin. Work on it to share it with the elgg community as soon as possible even if not fully operational for other themes or plugins out of the included on the installation.

thank you so much.

That regex seems weird. Which infinite scroll library and version are you using?

Sorry for my late reply.

I test with infinite-scroll by Paul Irish version 2.0.2, it´s an unmaintained release but works fine except for the regex of '2' ;D

https://github.com/infinite-scroll/infinite-scroll/releases

the newest versions of David DeSandro's masonry not include this infinite scroll since v.3, i don't work with the new 4 version because I like the behavior of v.2, perhaps later I test the new masonry to see what advantages does

thank you Juho for your interest

You should use xdebug, which allows you to walk through the execution of elgg_get_entities() to see what's going wrong. Here are the slides for a recent presentation I did on that tool that may or may not be useful.

thanks Steve
I'm working on it (as recommended had me on github) and when I have some progress or solution I'll post here for future reference
but I had to do other things and had not ever used xdebug, but I anticipate will be a very useful tool for my next attempts to create plugins

resolved
in 1.7 the function returns the entity site by adding 'site_guid' => null, in 1.8 it is not necessary
thanks