You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Zola version: 0.14.0 (using the container docker.io/balthek/zola:0.14.0)
Expected Behavior
I'm migrating old articles and posts from another site which used UUIDs as the slug equivalent (it's awful I know). I've been organizing the posts in a way that Zola is expecting like so:
Adding a slug key in the top of slug: 2cd1b34b-64a5-4f9c-8ce4-fab586ec2b88 gives me the behavior I expect with a resulting URL looking like /articles/2cd1b34b-64a5-4f9c-8ce4-fab586ec2b88/. I've started going back through and trying to co-locate the assets along with the articles. This involves changing the directory structure above to the following:
I would expect that this change alone to have no effect.
Current Behavior
I'm not receiving any errors but the change to the directory structure results in the path to the article changing to /articles/2020-07-29-sample-article/. At the very least I'd expect the behavior to match the normal post slug re-naming behavior that removes the date prefix (which would result in /articles/sample-article/.
The file test_site/public/articles/c7637df2-530e-4bfc-9a97-1b5c93af62f5/index.html is correct. The test_site/public/articles/2021-07-29-sample-article-2/index.html I expect to have the path test_site/public/articles/994f8c4c-4b52-44bd-b2d8-e5c26166f8d0/index.html or at least test_site/public/articles/sample-article-2/index.html.
The text was updated successfully, but these errors were encountered:
Bug Report
Environment
Zola version: 0.14.0 (using the container
docker.io/balthek/zola:0.14.0
)Expected Behavior
I'm migrating old articles and posts from another site which used UUIDs as the slug equivalent (it's awful I know). I've been organizing the posts in a way that Zola is expecting like so:
Adding a slug key in the top of
slug: 2cd1b34b-64a5-4f9c-8ce4-fab586ec2b88
gives me the behavior I expect with a resulting URL looking like/articles/2cd1b34b-64a5-4f9c-8ce4-fab586ec2b88/
. I've started going back through and trying to co-locate the assets along with the articles. This involves changing the directory structure above to the following:I would expect that this change alone to have no effect.
Current Behavior
I'm not receiving any errors but the change to the directory structure results in the path to the article changing to
/articles/2020-07-29-sample-article/
. At the very least I'd expect the behavior to match the normal post slug re-naming behavior that removes the date prefix (which would result in/articles/sample-article/
.Step to reproduce
I wrote a script that shows this behavior here: https://gist.github.com/sstelfox/dae8d0aa225e7c784e0f347d700c6b41
Running that right now will produce the following output:
The file
test_site/public/articles/c7637df2-530e-4bfc-9a97-1b5c93af62f5/index.html
is correct. Thetest_site/public/articles/2021-07-29-sample-article-2/index.html
I expect to have the pathtest_site/public/articles/994f8c4c-4b52-44bd-b2d8-e5c26166f8d0/index.html
or at leasttest_site/public/articles/sample-article-2/index.html
.The text was updated successfully, but these errors were encountered: