Open item4 opened 8 years ago
@item4 is this still a problem?
I ran across this bug on lektor-atom 0.3 as well - I moved the project on my disk and it ended up generating new IDs for all items in the RSS feed. Quite annoying for all my subscribers.
@item4 is quite correct as to the cause, since lektor-atom uses Lektor's project id in the item ID here. Maybe the ID generated by lektor-atom should be independent of Lektor's project id? Just using the path should be unique enough.
I'm using travis-ci for publish lektor.
If travis change build dir, lektor produce different id value (
ctx.env.project.id
).See this code for detail
I think you may make way to fix project id or suggest to mitsuhiko to make unique id without path.