.liquidtemplate files to
.jsontemplate files. This impacted the process of installing Nosto in any of the version 2.0 themes as Nosto mostly expects and modifes
.liquidfiles. Nosto has recently released support for version 2.0 themes and this documentation will discuss the details in-depth. For more information Shopify side of changes, visit corresponding links below,
Following table lists existing JSON templates that will be updated while installing Nosto
Each of the section values/properties introduced in the section above needs the corresponding liquid present under sections group of the theme. Following sections will list all the new liquid template files that will be introduced along with it's content
templates/404.jsontoday and leave the rest of their theme setup as it is and continue using the liquid template files. In that case, a customer will be using scheme structure of both
version 2.0themes. Nosto has implemented support for this scenario under the recent release. It will automatically identify those files that are still using
version 1.0liquid templates and injects content, into the liquid template, using the existing logic. Also identifies those that belongs to
version 2.0json templates and injects content, into those json templates, using the approach discussed in above sections.
version 1.0and has Nosto installed already. When such a customer is migrating to
version 2.0, they can do either of the following,
index.jsonis configured with 20 sections, will cause issues during Nosto installation and eventually cause issues with rendering front page placements. In such scenario, modifying
templates/index.jsonto use 19 sections and reinstalling Nosto will fix the issue. This approach has to be followed until either Shopify increases this limitation or removes the limitation altogether.