0.122 allowed permalinks to point to host root baseurl/XXX now broken?

support
1

I am fairly sure I found a bug, but since it’s possibly an intentional change that doesn’t seem to appear in release notes I felt that I should post here for support first before submitting as a bug. Essentially in 0.122 I could set a permalink in the configuration file as

permalinks:
  pages:
     /:filename

When I tried upgrading to 0.136.5 and 0.137 that configuration would throw an error
Error: error building site: render: alias “/” resolves to website root directory
If I changed it to /pages/:filename it would build again.

Unfortunately, this is an issue, I really need it to continue to work. Obviously, I can stay with version 0.122 but would prefer that I could upgrade. Does anyone have any insight on if this was a planned change?

Thank you.

2

The word pages is not a page kind. Use the word “page” instead.

permalinks:
  page:
    /: '/:filename'
1 Like
3

Thank you that configuration worked. I think I was confused about what “pages” referenced as it seemed from the documentation that it referenced the directory the files were in, ergo why I used “pages”, but anyway, appears I was incorrect, and this fixes the issue. Appreciate your time.

1 Like
4

Well, sadly, I spoke too soon. I thought this fixed the issue but it did not. After rereading the documentation on permalinks I understand a bit better but I still can’t solve the issue. Under the content directory I have folders, one of those folders is called “pages”. I want all the content in that directory to render right after the hostname…
So, if inside the content > pages folder I have a folder for “community” with an index.mb file in it I want that community link to be https://mywebsite.com/community.

As I said in 0.122 that worked as I shared my configuration. Your change would, as I now understand it, only fix the root content, of which I have none. I tried fixing it more by doing this in my config.yml

permalinks:
  page:
    portfolio: /portfolio/:filename
    pages: /:filename

But that give the same error:
Error: error building site: render: alias “/” resolves to website root directory

Any other ideas, i’m likely just still holding it wrong :slight_smile:

5

YAY, I solved it. And it was me. Somehow one of the aliases of a piece of content in the pages directory had gotten an extra “” alias added. That was the issue, so the pages: /:filename when added was causing the issue because one of the pages inside was a bad alias. Anyway, again thank you for your help.

1 Like
6

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.