One Click Postage Update: v4.0.3
This update to One Click Postage should fix the issue where q/r/d quickblogging keys prevented people from typing out posts (and reblogging things over and over again in the process).
This update to One Click Postage should fix the issue where q/r/d quickblogging keys prevented people from typing out posts (and reblogging things over and over again in the process).
Anonymous asked:
We just pushed an update to v4.0.2. Do you still have the problem after updating?
lastscionofkrypton-deactivated2 asked:
I’m not sure how Chrome handles cookies, but as long as the different sessions are using different sets of cookies you should be fine.
On Firefox, for example, the Multifox extension doesn’t work right because the profiles share cookies. However, I have Firefox (personal tumblr) and Firefox Developer Edition (xkit tumblr) open simultaneously without issue.
It should be pretty obvious if it’s not working—usually one blog will be unable to use One Click Postage if you’re having cookie issues. What do you mean by everything disappearing?
Anonymous asked:
It is! You can find us here. We love contributions! If you want ideas on where to start, you can check the issues page.
peachykeehn asked:
This should work now for queuing with One Click Postage 4.0.2. Queuing with the editor is harder to fix, but we’re working on it.
Anonymous asked:
We’ve noticed this sometimes happens if a post is reblogged while XKit is not finished loading. Try waiting until XKit is fully done loading and see if the same issue occurs. If it does, send us another ask.
digitalasteroid asked:
This is related to the Tumblr update to reblogs. We’re working on this and will let you guys know when it’s fixed!
Anonymous asked:
It’s no problem whatsoever, I forgot to add this to our FAQ: http://new-xkit-extension.tumblr.com/post/125093997449/how-do-you-force-your-xkit-to-manually-update-the
Happy updating!
Anonymous asked:
If it isn’t showing up at all, this may be related to the recent Firefox panic and may be solveable using the same technique. If that doesn’t fix it, can you share any output that shows up if you open up the JavaScript console (View > Developer > JavaScript Console or Ctrl-Alt-J)?
False alarm! Please return to your regularly scheduled blogging and irregularly scheduled updating. The update is your friend, love the update, cherish the update.