Less Broken Than You Think

[Less Broken Than You Think]

Anonymous asked:

I'm getting error code OCP01 every time I try to use one-click postage. It's not a problem with third-party cookies; they're enabled. This happens on all posts.

new-xkit-support answered:

We are aware of this issue with Firefox and Safari, and are trying to locate a cause. In the meantime, Chrome does not appear to have this problem - please let us know if this does start occurring on Chrome for you.

[Less Broken Than You Think]

New XKit 7.8.2

This release fixes a potential security issue due to the expiration of xkitcs.com’s registration. You should see this release start to trickle down automatically over the next couple days.

Don’t want to wait for your XKit to automatically update? Check out 7.8.2′s release page for the version of XKit suitable for your browser.

As always, if you have any questions, you can stop by our live support chat (on Discord), swing by our always open ask box, or even send us fan mail!

[Less Broken Than You Think]

New XKit 7.8.0

[new-xkit-extension]

Welcome to the future! New XKit 7.8.0 is a comprehensive update of our base extension for Firefox, Chrome, and Safari with a bunch of improvements. New XKit is now fully a WebExtension on both Firefox and Chrome, which allows us to share the browser support code between both platforms. Most importantly, this means that your XKit will continue working on Firefox Quantum.

New XKit 7.8.0 should be automatically downloaded for you through your browser’s normal update process.

Note for Firefox users: You must already have New XKit 7.7.7 or higher for your data to be automatically transferred to 7.8.0. If you have a lower version, download 7.7.7′s xpi first at its release page. If you run into any trouble, follow the steps in this new-xkit-support post.

Also for Firefox users: If you have problems with One-Click Postage after updating, don’t worry—we’ve got you covered. Check out this post on new-xkit-support for more information.

Don’t want to wait for your XKit to automatically update? Check out 7.8.0′s release page for the version of XKit suitable for your browser.

As always, if you have any questions, you can stop by our live support chat (on Discord), swing by our always open ask box, or even send us fan mail!

[new-xkit-extension]

We made a point release (7.8.1) this afternoon to fix a critical bug in Firefox memory/RAM usage. If you were experiencing high memory usage when browsing individual blog pages (not the dashboard), you should update to this release to fix the problem.

https://new-xkit-extension.tumblr.com/firefox

[new-xkit-extension]

Reblogging this again since with the release of Firefox 57 (Quantum) this week, a couple users are finding that they hadn’t updated to the newest version of New XKit and couldn’t access XKit.

Please use this as a reference in case you run into similar issues!

[Less Broken Than You Think]

New XKit 7.8.0

Welcome to the future! New XKit 7.8.0 is a comprehensive update of our base extension for Firefox, Chrome, and Safari with a bunch of improvements. New XKit is now fully a WebExtension on both Firefox and Chrome, which allows us to share the browser support code between both platforms. Most importantly, this means that your XKit will continue working on Firefox Quantum.

New XKit 7.8.0 should be automatically downloaded for you through your browser’s normal update process.

Note for Firefox users: You must already have New XKit 7.7.7 or higher for your data to be automatically transferred to 7.8.0. If you have a lower version, download 7.7.7′s xpi first at its release page. If you run into any trouble, follow the steps in this new-xkit-support post.

Also for Firefox users: If you have problems with One-Click Postage after updating, don’t worry—we’ve got you covered. Check out this post on new-xkit-support for more information.

Don’t want to wait for your XKit to automatically update? Check out 7.8.0′s release page for the version of XKit suitable for your browser.

As always, if you have any questions, you can stop by our live support chat (on Discord), swing by our always open ask box, or even send us fan mail!

[Less Broken Than You Think]

New XKit Firefox 7.7.7

[new-xkit-extension]

Hey everybody, sorry for the delay in getting this out, but this release should solve the problems people were having with 7.7.6. If you’re using Firefox and you’re currently on 7.7.5 you need to upgrade to this version within the next 6 weeks to avoid possibly losing access to your settings. You can update to 7.7.7 by going to Tools > Addons > click the gear icon > “Check for Updates”

Firefox version 57 (currently on Nightly) removes support for “legacy extensions”, which includes Addon SDK extensions like New XKit. New XKit 7.7.7 is still technically a legacy extension, but it uses what’s called an “embedded WebExtension” to migrate your stored settings to the new version. That means that when we release New XKit 7.8.0, which will be a non-legacy WebExtension, all of your data will still be there.

If you’re currently using Firefox Nightly, then you’ll have to downgrade to an older version like Beta or Release to migrate your settings, if you didn’t have 7.7.6 installed already.

Users with lots of extensions, saved posts, or similar are also highly encouraged to make local XCloud backups of their data for peace-of-mind. As always, if you have any questions, you can stop by our live support chat (on Discord), swing by our always open ask box, or even send us fan mail!

[new-xkit-extension]

This update should happen automatically, but if you want to make sure, here’s how to check for updates:

External image

[Less Broken Than You Think]

New XKit Firefox v7.7.6

Hello everyone! In today’s New XKit update, we’re laying the groundwork for supporting Firefox 57′s release. This update adds WebExtension support for XKit and includes a migration step to make sure everyone keeps the same config both before and after the change. Because WebExtensions will be the only platform supported for Firefox going forward, it’s important that you install this update so you can continue to access your config in future versions.

Immediately after upgrading you may encounter a brief pause where Tumblr or Firefox ceases to respond to you for a couple seconds before everything runs normally. This is should only happen if you are running Firefox on a toaster made out of wood, but we want to make sure that you know there is nothing to be afraid of.

Your XKit should update automatically within the next few days, but if you want to hurry the process along, you can download it directly from https://github.com/new-xkit/XKit/releases/firefox-v7.7.6/ (XPI file)

[Less Broken Than You Think]

github.com

New XKit Signed Release

For Firefox 43 and above

[new-xkit-extension]

Without further ado, we’re proud to present a version of New XKit that works with Firefox 43! Nothing else has changed, it’s literally exactly the same extension you have installed, but working. You’ll still have to download it directly from our github for now because Mozilla won’t show it on their store, but that’s a minor inconvenience in the long run, and we’re working on addressing it.

Anyway, let us know if you have any questions! And as always, if you run into any trouble with New XKit, swing by our support chat room so the devs can help you out!

[new-xkit-extension]

Hey everybody! It looks like Mozilla released an update today that disabled unsigned addons completely, so if you didn’t update New XKit back in December when we first released the signed version, make sure to do so now!

To check if you need to update, go to about:addons, or press ctrl-shift-A. Look for New XKit’s entry, and if you see a warning message about the extension being “unsigned”, then you need to update it immediately.

download the signed .xpi for firefox here

[Less Broken Than You Think]

github.com

New XKit Signed Release

For Firefox 43 and above

Hey guys, we’ve been made aware through various channels that about two weeks ago Mozilla changed their policies on Extension Signing—something that we were never notified about, even given that we had reviews open at the time—and we were able to get our extension signed without re-writing it, contrary to what we had been told earlier by Mozilla volunteers.

Anyway, without further ado, we’re proud to present a version of New XKit that works with Firefox 43! Nothing else has changed, it’s literally exactly the same extension you have installed, but working. You’ll still have to download it directly from our github for now because Mozilla won’t show it on their store, but that’s a minor inconvenience in the long run, and we’re working on addressing it.

Anyway, let us know if you have any questions! And as always, if you got any trouble with XKit, you are welcome to join our support chat room. (hosted on gitter, if you want to join with a github account)

[Less Broken Than You Think]

About Firefox 43, New XKit and Extension Signing

A lot of you people using Firefox probably already realized: The update to Firefox 43 completely disables New XKit due to it not being signed/verified.

Let me begin by saying that all of us are truly sorry for this inconvenience.
We are trying our best to fix this but currently are unable to give an ETA on how soon this is going to happen.

Mozilla published their plan for extension verification in Feburary, so even when the New XKit project started in July we knew that it was something we were going to have to deal with eventually. We submitted our extension initially to Mozilla on July 20^th, and did not hear back from them until November 16^th_, when Mozilla removed our extension from their online gallery, telling as that we do not meet their requirements to be a publicly listed extension. We then submitted as an “unlisted” extension, which was theoretically a more lenient process. This time they got back to us within about a week, but they would not still not accept the extension the way it was currently written.

There are a lot of technical details that go into the situation, but the bottom line is that we need to rewrite the core of how XKit handles extensions almost completely before getting signed. We’re currently about half-way through that process, and hope to have something to share with you as soon as we can pass validation. The biggest downside that comes with this rewrite though will be our reaction time—we will have to update the entire extension whenever we want to change one of the individual packaged extensions, and third-party (non-signed) XKit Extensions will no longer work.  

Until signing happens though, we can offer you 3 workarounds:

1. Use another browser like Chrome or Opera with New XKit. This is the best solution, as it allows you to still be on the most up-to-date browsers while also using New XKit. You can grab the Chrome version of New XKit from the Chrome Web Store and find instructions for using New XKit with Opera on our blog
   
2. Downgrade Firefox to v42. This is less recommended then option 1, but more recommended the option 3. Mozilla provides instructions on how to do this on their wiki
3. Disable signature checks in Firefox v43. (NOT recommended)

WARNING! Signed extensions a security feature added by Mozilla. Disabling that feature may put you at risk of installing viruses and ad-ware! 

Additionally, this fix only works until Firefox v44 hits and the switch gets removed.

If you still want to proceed, type “about:config” in your Address Bar, look for “xpinstall.signatures.required” and double click on it so it has the value “false”.

And as always, if you got any trouble with XKit, you are welcome to join our support chat room. (hosted on gitter, if you want to join with a github account)

[Less Broken Than You Think]

Blank comboboxes in Firefox fixed!

A lot of you that use Firefox have reported weird behavior regarding the comboboxes of the XKit Control Panel lately, specifically them being blank but options can still be selected and change.

With the update of the internal XKit Preferences extension to 6.0.3, this should be fixed! Either wait for the update or force an update under XKit Control Panel > Other > Update All > Update all my extensions

As always, if you got any trouble, either send us an ask, or join our live support chat or if you have a github account, our gitter support chat! If no one responds in the live chat, it means the developers are currently busy/away/sleeping! Just wait a bit and someone will get back to you!