You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed in our site logs that traffic was going to the ajax view that handles the pagination page view ("/news/home-articles/page/?page=2"). I was able to recreate myself by right clicking the load more link and selecting open in new tab. I also suspect that the bots crawling the site might be generating this traffic too.
Calling preventDefault() in the JS click event might do the trick and would be easiest fix, but I'm not sure if that would handle the bots.
A more involved and perhaps better long term approach is to update the JS code to be more markup agnostic and replace the with a or and moving the page url from href to data-page-url or something like that. Right now it's tied to there being an href attribute, which means it's gotta be an . This limits what changes people can make to the template and might have unintended consequences with indexing bots.
I will try to make a PR with the proposed solution for this when I have the time. Thanks for the great project!
The text was updated successfully, but these errors were encountered:
I noticed in our site logs that traffic was going to the ajax view that handles the pagination page view ("/news/home-articles/page/?page=2"). I was able to recreate myself by right clicking the load more link and selecting open in new tab. I also suspect that the bots crawling the site might be generating this traffic too.
Calling preventDefault() in the JS click event might do the trick and would be easiest fix, but I'm not sure if that would handle the bots.
A more involved and perhaps better long term approach is to update the JS code to be more markup agnostic and replace the with a or and moving the page url from href to data-page-url or something like that. Right now it's tied to there being an href attribute, which means it's gotta be an . This limits what changes people can make to the template and might have unintended consequences with indexing bots.
I will try to make a PR with the proposed solution for this when I have the time. Thanks for the great project!
The text was updated successfully, but these errors were encountered: