Troubleshooting Site Generation

I intend to keep adding to this note as further issues crop up and workarounds are discoverd.

1- I found that when we use the same slug for different language versions of the same article.

pelican does a nice job of picking out the current default language's version for the site. When no version exists which matches the current default language, then pelican emits warnings and/or errors regarding the other language versions.

The work around is to always make sure you have all the language versions you are supporting, or just a single one. When that is the case it seems to behave adequately.

It seems sensible to translate attribute values too, other than slug of course.

Published by Pierre Bernatchez in «maintenance». Key Words: troubleshooting