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
If slugifying each path element of the target name produces a different outcome, only then a redirect should be created from "2011/04/03/testing-utf-8-in-title-ā/" to "2011/04/03/testing-utf-8-in-title-a/index.html" and file be created as "posts/2011/04/03/testing-utf-8-in-title-a/index.html"
The text was updated successfully, but these errors were encountered:
aigarius
changed the title
Bugs in import_feed plugin
[import_feed] Path/URL bugs in import_feed plugin
Jun 27, 2021
* Actually consider generated redirects
* Do not squash post sub-folder structure (like date folders)
* Only generate redirects if URLs change
* Support having blog posts in a differently named top folder
Issue: getnikola#389
Pushed some code that worked for my case, not 100% sure it will work in all use cases. But given the above feed and specifying "blog" as the new top folder option, I got very reasonable output in both files and URLs (no redirects required).
Redirections are created before the page import happens, so the redirection map is always empty and no redirects are written into the config file
Folder structure of the posts is not re-created, so everything is dumped in the same folder (requiring redirections)
Redirections construct a wrong destination URL if the SITE_URL from the feed contains path elements (the path part gets included twice)
IMHO, when importing a RSS with SITE_URL set to "http://example.com/blog/" and posts like "http://example.com/blog/2011/04/03/testing-this-engine/" the output file should be "posts/2011/04/03/testing-this-engine/indext.html" with no redirect required. With SITE_URL set to "http://example.com/" and BASE_URL set to "http://example.com/blog/"
If slugifying each path element of the target name produces a different outcome, only then a redirect should be created from "2011/04/03/testing-utf-8-in-title-ā/" to "2011/04/03/testing-utf-8-in-title-a/index.html" and file be created as "posts/2011/04/03/testing-utf-8-in-title-a/index.html"
The text was updated successfully, but these errors were encountered: