This is what comes up everytime I try to archive a post from a user’s blog
Just fixed this!
Anonymous asked:
We’ve been getting quite a few messages like this, which is bizzare because we both run Firefox (I run 39.0) and neither of us have this problem. If those of you with this problem could give us additional details (OS, browser version, blacklist extension version, other extensions (browser and XKit), anything else you find relevant) by replying to or reblogging this post, that would be great.
Anonymous asked:
Not a thing in Firefox as far as I can tell, unfortunately. Posting for Chrome users.
Anonymous asked:
Header Options has an option to fix it to the top of the page so it won’t scroll with you.
I’ve made an update to Post Archiver that should allow you to save your archived posts via an import/export function.
To get this on Old XKit follow these instructions:
If something breaks the first time, don’t panic! Something probably went wrong with the pasting in, but this should never cause you to lose your data. Simply try again, and if it’s still broken, send us an ask detailing what you did (the more detail, the better) and what error you’re getting.
hemorrhaging-knight asked:
Make sure to uninstall the old XKit before installing our New XKit. Because we are a fork, Chrome does not recognize us as the heir to the XKit name and will not automatically replace it with New XKit.
codenamemorgana asked:
new-xkit-extension answered:
Thank you for your kindness and diligence in updating! If you have Firefox, you can safely uninstall and reinstall the extension to force a version update. On Chrome, if there is an option to enable Developer Mode on the chrome://extensions page then you can click it and spam the Update Extensions Now button. Otherwise, pick a god and pray.
On Firefox, if you downloaded from the Addon Store previously (i.e., if you’re running New XKit and did NOT get your current version from github), you don’t even have to uninstall. It’ll overwrite for you.
codenamemorgana asked:
Thank you for your kindness and diligence in updating! If you have Firefox, you can safely uninstall and reinstall the extension to force a version update. On Chrome, if there is an option to enable Developer Mode on the chrome://extensions page then you can click it and spam the Update Extensions Now button. Otherwise, pick a god and pray.
This update prevents XKit from running directly on blogs and increases the amount of location context provided to extensions. This fixes the issues with Themes, Themes Plus, and Timestamps.
Anonymous asked:
Thanks for the report! This is related to an issue in the Themes+ extension and possibly the Themes extension. A fix to Themes+ was just published and investigation into Themes is underway.