yariyumi asked:
Thanks for the information! I’m answering this publicly in case it helps out anyone else.
yariyumi asked:
Thanks for the information! I’m answering this publicly in case it helps out anyone else.
Anonymous asked:
I can’t reproduce this locally, but other people with doubling issues fixed their problems by making sure that the old XKit was uninstalled. If you can provide more information about your operating system and the versions of Editable Reblogs and XKit Patches that you are using it will be easier for us to figure out what is happening.
Anonymous asked:
This should be fixed in Profiler version 1.2.1, coming soon to a New XKit near you (click the update button if you want to come sooner)
Anonymous asked:
Thanks for the report! This should be fixed in Themes+ 0.2.5 and XKit Patches 3.1.6.
poiisons asked:
This is has hopefully been fixed in Mute 2.3.1 with XKit Patches 3.1.4 (visible via the internals option which is on the “Other“ pane).
akxchii asked:
One person reported fixing this by restarting Firefox and clicking the “Update All Extensions” button on the Other pane of XKit.
Anonymous asked:
We just fixed this in Editable Reblogs v1.0.2. You may need to restart your browser to get the update because caching is the worst.
tjb0607 asked:
Open in New Tabs is not installed by default. After you install it it will be enabled, and can be disabled by uninstalling it. There’s probably some confusion because it didn’t do anything at all until a couple of minutes ago. Sorry for the disorientation! If it persists after uninstalling and refreshing please let us know.
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:
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.