Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

_frontpage-2021 not displaying at the home page in NextJS boilerplate #207

Open
jguix opened this issue Oct 17, 2022 · 0 comments
Open

_frontpage-2021 not displaying at the home page in NextJS boilerplate #207

jguix opened this issue Oct 17, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@jguix
Copy link

jguix commented Oct 17, 2022

Component(s) affected: Next.js Boilerplate - Complete ecommerce

Description
The _frontpage-2021 folder contents are not displaying in the root page.

How to reproduce

  • Create a new empty tenant.
  • Install the local service API with npx @crystallize/cli my-api-project and selecting:
    • Vercel platform
    • own tenant
    • no dummy data
  • Install the Next.js Boilerplate with npx @crystallize/cli my-project, selecting:

Run yarn dev on both projects and navigate to localhost:3000. An empty page with no content is shown (only the menus, shop logo and footer).

Although selecting always that I am using my own tenant, the new empty tenant is polluted with a catalog, with "Shop", "Stories" and "About" folders, together with "_frontpage-2021" and "_assets". The "_frontpage-2021" has a title "Retail eCommerce demo powered by Crystallize" but this title doesn't show in the home page of my running site. If I write more content in the "_frontpage-2021" as explained in the videos it is not displaying.

I repeated the process many times so I am sure that I didn't accidentally selected to use the FRNTR data, so that is not why my catalog is full of pages that I didn't create.

Possible Solution
I couldn't find any reference in the frontend code to "_frontpage-2021", but only to "frontpage-2021" without the leading underscore. I tried renaming the catalog folder just in case it had been renamed in the code and not updated in the videos, but it didn't fix the issue.

Additional context

Site home page:

frontend_site

Catalog folders (polluted by some script, I never created them):

catalog

@jguix jguix added the bug Something isn't working label Oct 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant