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
Possibility to override post slug (and destination).
For example IMDb movie reviews, you could specify "slug: /reviews/movies/0379217" for review of Coffee and Cigarettes -review on your site.
Other use cases: automatically generated entries, twitter timeline mirroring ("slug: /twitter/[tweet id]").
You could check if the output folder has the entry.
The text was updated successfully, but these errors were encountered:
Interesting idea. Keep in mind that the way the document root is structured, the only ways to do this would be:
Add a Redirect to .htaccess for every custom slug, which is probably not a good idea.
Actually generate the folders and files to correspond to the custom slugs. So there would actually be a file in the document root at /reviews/movies/0379217, with all of the parent folders created as well.
I don't love either solution, but I guess the second would probably have fewer problems.
The second solution would be more like what I had in mind.
It would be important to be able to check does a specific entry exist. Wouldn't want to overwrite changes.
Current output naming scheme prevents reliable testing.
Possibility to override post slug (and destination).
For example IMDb movie reviews, you could specify "slug: /reviews/movies/0379217" for review of Coffee and Cigarettes -review on your site.
Other use cases: automatically generated entries, twitter timeline mirroring ("slug: /twitter/[tweet id]").
You could check if the output folder has the entry.
The text was updated successfully, but these errors were encountered: