a9d6f52ca6
The shop pages products: every page is a full reload that throws away the grid the visitor was reading. This appends the next page to the grid instead, on scroll or on a "Load more products" click, per website. The controller does not duplicate /shop. The new /shop/lazy_products calls shop() and renders the cards out of the qcontext it prepared, so search, categories, attributes, tags, price filter, sort order and pricelists are supported by construction -- and so are the values other modules add to the listing, the wishlist state among them. Out of range pages answer empty rather than the last page again, which portal.pager would otherwise clamp to and the frontend would append as duplicates. The product loop of website_sale.products is replaced by a call to a shared template, so the first page and the appended ones are the same markup: a ribbon, a price or a button another module adds to products_item shows up on every card, not only on the ones the initial render produced. Progressive enhancement throughout: the first page and the pager are still what the standard controller renders, and the pager is only hidden once the widget is running. Without JavaScript -- and for crawlers -- the shop is exactly what it is without this module. The page size is the shop layout's "Products per page", the value the pager already uses, so there is nothing to keep in sync. The frontend takes no decision about what to show: the server sends the mode, the URL of the listing on screen and each page of cards. It observes a block below the grid rather than listening to scroll, restarts the public widgets on the appended cards, and keeps a button as the fallback for a failed request or a browser without IntersectionObserver. Tests cover the block rendering per mode, the filters travelling in the AJAX URL, and the endpoint on a next page, the last page, an out of range page, a broken page number and an unknown category. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
17 lines
919 B
ReStructuredText
17 lines
919 B
ReStructuredText
Go to *Website > Configuration > Settings > Shop - Products > Shop Product
|
|
Loading* and pick how the listing loads its pages. The setting is **per
|
|
website**:
|
|
|
|
* **Infinite scroll** (default): the next page is appended when the visitor
|
|
reaches the bottom of the listing. A *Load more products* button shows up as
|
|
a fallback if a request fails or if the browser has no
|
|
``IntersectionObserver``.
|
|
* **Load more button**: the next page is appended when the visitor clicks the
|
|
button. This is the friendlier option for keyboard and screen reader users,
|
|
and it keeps the footer reachable.
|
|
* **Pager (standard)**: turns the module off and leaves the standard
|
|
``website_sale`` pager alone.
|
|
|
|
The number of products of each page is **not** configured here: it is the
|
|
*Products per page* of the shop layout (open ``/shop`` as editor, *Edit* and
|
|
use the *Products Page* options), the same value the standard pager uses.
|