Hello, thank you for your feedback. I apologize that this update caused such issues. This is currently being worked on and will be fixed in the next update. The live version of DocsAfterDark has been rolled back to v0.6.3 which does not have this issue.