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.
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.
Anonymous asked:
It looks like it does. Any fork of Firefox that has incorporated the changes to the addons API made after version 32 should work.
demijaxon-deactivated20151209 asked:
If you’re able to recreate the Aw Snap! error that is probably a bug that the Chrome developers would be interested in knowing more about. Their bug tracker is https://code.google.com/p/chromium/issues/list, although given they probably already know about the crashes with all the telemetry they have.
Anonymous asked:
new-xkit-extension answered:
As of now, there are two ways to get your account info in your sidebar, and both are slightly broken:
You also can install tampermonkey and use this script
https://wuffleton.com/code/tumblrsidebar/
it works really really well! You can even customize its appearance slightly.
Anonymous asked:
As of now, there are two ways to get your account info in your sidebar, and both are slightly broken:
Anonymous asked:
We’ll look into it. It might be related to how XKit currently doesn’t work in private browsing. Posting for other people with this problem.