Closed j9t closed 3 years ago
Problem update: A first test with the Eleventy Base Blog suggests that the page list simply shows all pages of all previous export targets (until deleted). I didn’t yet go as far as using a path like ~/foo/bar
yet, but it seems that’s what catches Eleventy off-guard.
Solution update: I managed to contain the issue by adding /~/
to the .eleventyignore file.
Update: Could identify the offending folder (where I had formerly deployed the site to), removing of which helped solve the problem.
Not an issue then, especially as working with .eleventyignore had already helped.
Describe the bug On the page list (in the starter governed by page-list.njk) I have entries for pages that don’t exist. They point to locations that I used to set as export/deploy targets—and it seems something went wrong here: They point to paths like
/~/foo/bar
, and while Eleventy seems to have deployed there, I can’t access and delete these pages.Cleaning the site export (
_site
folder), removingnode_modules
, re-installing the respective project have no effect.To Reproduce Not sure! Raising this early in case this rings a bell. Will try to reproduce with the Eleventy Base Blog fork.
Expected behavior Only the pages under
_site
(or whatever the export folder) should be listed.Screenshots Will try to add them when testing with the Eleventy Base Blog fork.
Environment: