Not found
The not-found context in a StoreOS Fluid theme — when it renders, its widgets and data, and an example.
The not-found context renders when a visitor opens a page that doesn't exist. It is returned with a 404 status.
When it renders
- A product, collection, page or blog post URL whose item doesn't exist, such as
/products/old-hoodie. - A URL that matches no page at all, such as
/summer-sale-old.
Shopper pages your theme hasn't taken over, checkout and order confirmation never show it.
Widgets
layout/not-found.fluid, or the widgets listed under pages.not-found inside layout/theme.fluid.
{ "pages": { "not-found": ["not-found-message"] } }Without either, StoreOS shows its own not-found page.
Data
| Object | Contents |
|---|---|
page_title | Page not found |
Plus the data on every page. StoreOS never indexes this page: its SEO tags say noindex, follow.
Example
{% comment %} widgets/not-found-message.fluid {% endcomment %}
<section class="not-found">
<h1>{{ page_title }}</h1>
<p>The page you're looking for has moved or no longer exists.</p>
<form action="/search" method="get">
<input type="search" name="q" placeholder="Search products">
</form>
<a href="/collections/all">Keep shopping</a>
</section>For a different shell around this page, see Page layouts.
Shopper pages
Account, sign-in, orders, profile, cart, wishlist and order tracking in a StoreOS Fluid theme, and how to load the shopper's data in the browser.
Layout and theme document
The page shell in layout/theme.fluid, per-page layouts, the starting widgets in config/document.json, pages, regions and theme settings.