Replace pagination with "show more" button / ajax post loading

Some people have added infinite scroll plugins with some success.

Thanks

I have only seen some plugins that, if they work with GD, a lot of GD features no longer work.
Feel free to test any infinite scroll plugins. Let us know how you went.

Thanks

I have added it as a feature suggestion and the developers will consider adding it.

Hi @grenzecho @guust @wyohost @ayecode_alex and @stiofan
I am very happy to see how others people are asking about infinite scroll.
You should considerate I asked to GD team about this feature 3 years ago… But from beginning no very good interest was showed from developers… and that surprised me because “infinite Scroll” is one of the most powerfull features maked in developer’s world.
So I tried to find an external solution. The unique solution I found was DMD plugin
I suggested to DMD developer to make a payment addon because free version was not all compatible.
So DMD developer opened the follow thread:
https://wordpress.org/support/topic/infinite-scroll-69/
in order to have more information, but I think finally DMD developer dont updated plugin with stiofan’s instruction.
Said that, the unique problem I remember I found was just the problem reported from Frabrice “it doesn’t integrate well with the map, which in our case is at the top of the page”.
Yes you are right. An infinite scroll cant be integrated with a upstair map… But what I dont understand is why you want integrate it with upstair map? It has no sense to do that due to “nature” of infinite scroll… INFINITE SCROLL is a feature to go scroll down and open automatically new posts, and when you find an interesting post it has no sense scroll up to see the map to look about its location… It has no sense… Sure… Of course…
To integrate INFINITE SCROLL with GD, solution shoul be different. Follow I give you my proposal:
GD must provide to administrato 2 solutions/options:
Solution 1: Pagination
Solution 2: Infinite Scroll
Who choose solution 1 can introduce map at the top of page
Who choose solution 2 can’t introduce map at the top of page, but should choose map in SIDEBAR. With this solution map always will follow user in its “state of searching posts” and when user find an interesting post it can see locatioon on the map hosted in sidebar, without scroll up at the beginning of page…
The unique problem is the follow: using DMD infinite scroll plugin when user do scroll new posts opened will populate old map where there are posts of previously paginations. So after to do scroll a few times map in SIDEBAR will show too much posts… Location of previously posts more new posts… and that is very confused.
So solution is to show in the map only posts of ACTUAL PAGINATION user is found. Maybe I am not explaning well… Follow an example:
First I decide to many posts I want to show, for example I decide to show 10 post for each page. Also decide to enable infinite scroll. Ok.
1. As first, user will see posts from 1 to 10 and in the map in sidebar will be showed location of posts from 1 to 10.
2. Now user will decide scroll down => posts from 11 to 20 will be automatically opened and in the map in sidebar will be showed location of posts from 11 to 20.
3. Now user will decide scroll down => posts from 21 to 30 will be automatically opened and in the map in sidebar will be showed location of posts from 21 to 30.
4. Now user will decide SCROLL UP to posts from 11 to 20. In this case in the map in sidebar will be showed location of posts from 11 to 20.
5. Now user will decide SCROLL UP to posts from 1 to 10. In this case in the map in sidebar will be showed location of posts from 1 to 10.
I think rhis example show perfectlly what I want to say.
This is the unique way to have an INFINITE SCROLL “with sense” for geodirectory.
Resuming is:
– Provide 2 options to administrator. (OPTION A: upstair map + optional sidebar map; OPTION 2: only optional sidebar map)
– Make the modification needed to show in the map only the posts of the ACTUAL POSITION where user is found.
I hope developer are in acording with this solution and finally administrator we can have an INFINITE SCROLL for geodirectory.
Is veritable so strange that after 3 years we are working around without to determine a GD correct solution for one of the powerfull feature for SOCIALS NETS. This is strange but this is real… I hope developer will reconsidere its positions and will reflexione about my proposal.
Please, let me know if there is some possibilities to have it running with my solution or if we can definitivelly forget INFINITE SCROLL for GD.
I hope your reply.
Thanks.

Hi @grenzecho first thanks for you reply.
Also thanks to accept I am right when I say that INFINITE SCRILL has not sense with a FIX MAP. It is absurd.
Map in sidebar is a solution for desktop devices.
For mobile divices solution should be a FLOTING/DROPDOWN MAP in order to show it when user want.
About your doubt (“should the map only show the places that are currently visible? Ideally, both should be possible”), has I explaned in my previously post I tested infinite scroll on my page, and when there are a lot of listings/posts (this is the case when user do scroll…) the resultate of the map is a too populate map with too icons.. and it is not a good map to show… it is very confused…
So good solution is to show only currently/visible listings/posts.
Another solution can be to show currently/visible listings/posts and show the others with “clouster map addon” so map will have a more confortable vision (but show with “clouster map addon” only the rest of listing and not current listigs.
As last, to know that INFINITE SCROLL as you say is “an option for us in the future” of course is a good notice… But it seams too many years we are waitig to get that (my first post was 3 years ago and it has not been implemented in GD V2.
Maybe only my doughter will see INFINITE SCROLL for GD hahahaha
As I said previously, in my opinion a good solution is always a flexible solution… and flexible solution is allow to admin to decide in setting:
– PAGINATION
or
– INFINITE SCROLL
depending each CUSTOM POST TYPE.
So developer should not decide what system… but implement both of them.
This is my opinion…