A bit of a two part question... I'm wondering if someone can shed some light on how the paging works in the Gossamer Threads installs.
I ask because we've had some trouble in the past where after switching the site between static and dynamic, the 'more2', 'more3' etc paging stopped working. We contacted GT then and rewrite rules were apparently put in place to resolve the error it was giving.
But there are other installs on the site that weren't resolved, likely because re-write rules haven't been put in place for that install.
So at this time, on one of our pages - every paging button that links to URL/example/more2.html returns a Page not Found error. And I'm wondering if I must go through the process of reaching out and asking for those same rules to be implemented for that install too.
The second part, is wondering where these more2.html, more3.html files are kept and how they are generated.
On all pages we have a right sidebar with a global login box, and when one is on the first page (before using the paging feature), the login box correctly shows whether the user is logged in or out. But once you hit page 2 (more2.html) the login box shows the user as logged out. I am suspecting this may be due to an if statement checking the page_name, which may not be getting set in the more*.html pages.
I ask because we've had some trouble in the past where after switching the site between static and dynamic, the 'more2', 'more3' etc paging stopped working. We contacted GT then and rewrite rules were apparently put in place to resolve the error it was giving.
But there are other installs on the site that weren't resolved, likely because re-write rules haven't been put in place for that install.
So at this time, on one of our pages - every paging button that links to URL/example/more2.html returns a Page not Found error. And I'm wondering if I must go through the process of reaching out and asking for those same rules to be implemented for that install too.
The second part, is wondering where these more2.html, more3.html files are kept and how they are generated.
On all pages we have a right sidebar with a global login box, and when one is on the first page (before using the paging feature), the login box correctly shows whether the user is logged in or out. But once you hit page 2 (more2.html) the login box shows the user as logged out. I am suspecting this may be due to an if statement checking the page_name, which may not be getting set in the more*.html pages.
Paging Link Details