In the course of upgrading Pelican from 3.7.1 to 4.0.1, I found that we have duplicate tags that now interact with Pelican's content discovery logic in a way that introduces different output across builds (e.g. a tag's representation might be "Data Science", "data science", or "data-science", all pointing to the same tag slug URL). The changes that would resolve this issue are:
In the course of upgrading Pelican from 3.7.1 to 4.0.1, I found that we have duplicate tags that now interact with Pelican's content discovery logic in a way that introduces different output across builds (e.g. a tag's representation might be "Data Science", "data science", or "data-science", all pointing to the same tag slug URL). The changes that would resolve this issue are:
slugifyfunction) are not added in future data contributionsredirects.txtfile where applicableadd_filesmethod from thePyVideoArticleGeneratorclass