Less Broken Than You Think

[Less Broken Than You Think]

Editable Reblogs 3.0.4 – return of the dropdown button and other matters

Today we are releasing Editable Reblogs 3.0.4. This update to the ER extension contains a number of major fixes, including:

• Restoring the dropdown post button (including post scheduling and private posting)
  
• Fixing a bug which was causing the wrong date to be attached to edited posts.
  

We’d also like to apologize again for any confusion around the interface changes in the previous version of ER. Our solution for editable reblogs at this point basically bypasses Tumblr’s interface completely and adds our own in order to solve some major bugs we were encountering; the three-button interface was always meant to be temporary in order to get those bug fixes out the door fast, but we underestimated how much of an impact that would have on many people’s Tumblr use, so we’re glad to be able to restore the dropdown to you!

(Some of you told us you liked the three buttons, and we’ve heard you too! If there’s enough support they might come back as a tweak. :) )

In the same vein, this has also been a catalyst for us to start thinking about a better approach to beta testing big extensions like this before releasing them to everyone, so keep an eye out for that hopefully coming soon.

Thanks to everyone for their patience and bug reports; as always, you can continue to get in touch with us by sending an ask to @new-xkit-support or @new-xkit-discussion​ or visiting our live 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!

[Less Broken Than You Think]

New XKit 7.7.1 Release (Firefox Users Must Manually Upgrade) – Solves “Can’t Connect To Server” Popup Issue

We have a fix for the “Can’t Connect to Server” popup issue!

In order to completely disconnect from the now-expired Old XKit servers, we have released an update to the core XKit code, making this New XKit 7.7.1!

Chrome Users: You don’t have to do anything! The Chrome store should automatically update you to 7.7.1, although you can use these instructions to manually force your extensions to update.

Firefox Users: Due to our extension being unsigned by the Firefox store (we’re in the signing queue but haven’t been processed yet) you will have to manually update your extension rather than getting an automatic update. You can do this by visiting http://new-xkit-extension.tumblr.com/firefox and clicking the “Add to Firefox” button; the updated core code will install over the old core code, without changing any of your XKit extension data.

If you have XKit version 7.5.x or below: You have old XKit! Visit http://new-xkit-extension.tumblr.com/chrome or http://new-xkit-extension.tumblr.com/firefox to install New XKit instead (and be sure to uninstall the old version to prevent conflicts).

If you have any questions or encounter any issues, feel free to let us know in our support chat or bug list.

[Less Broken Than You Think]

“Can’t Connect To Server” Error on New XKit - Don’t Panic!

Some of you on loading Tumblr today may have received a popup that looks like this:

This popup is in fact lying. Some of Old XKit’s services finally expired and stopped running today, and while we operate our own codebase, there are some references to the old one in a few places that triggered a notification when they went down.

New XKit still works.  In fact, if you reload the page, the notification should no longer display and New XKit should still function normally.

If you are still using Old XKit, now is a great time to download New XKit! 

Firefox: http://new-xkit-extension.tumblr.com/firefox

Chrome: http://new-xkit-extension.tumblr.com/chrome

As always, feel free to let us know if you encounter issues by submitting to our bug list or using our support chat.

[Less Broken Than You Think]

Blacklist Text Search Has Been Fixed

We’ve received a number of reports that the Blacklist extension was not able to search post content after the advent of the New Design. We’ve released an update with Blacklist 2.7.6 which should resolve these issues and correctly register blocked words in posts again.

This update should roll out to all XKit users shortly, but if you’re impatient, you can manually update using the control in the “Other” tab in XKit preferences.

As always, feel free to let us know about any issues in our support chat or on Github.

[Less Broken Than You Think]

Editable Reblogs Bug When Adding Images to Posts

Hey, all! This announcement is just to let you know that we’re aware of a bug with Editable Reblogs causing posts to disappear if an image is included using the “camera” button on a new line. This seems to once again be rooted in Tumblr’s rather brittle parsing strategy; we hope to have a fix ready by sometime tomorrow.

In the meantime, one workaround that seems to be effective is dragging and dropping images directly into the post.

Updates on this bug can be found at https://github.com/new-xkit/XKit/issues/523.

As always, feel free to contact us with any questions.

[Less Broken Than You Think]

Fixing Missing Posts

Editable Reblogs v2.1.0 has just been released. This should resolve the issues mentioned in our previous post regarding Tumblr parsing changes which rendered ER posts invisible on the dash because it did not recognize the text as representing reblogs.

This update should resolve issues for anyone using the Rich Text editor or HTML editor as their default. In other words it should no longer require any manual changes by the user and you should just be able to hit the post button as normal. As always, if you’re having problems come to our live chat or stop by our askbox or github issues page

After updating to the new extension, you can also fix your old posts. First, find the post on your posts page, then click the edit button. Finally, confirm that the post looks correct and press submit. The post should automatically update to display correctly. If it doesn’t, drop us a line.

Happy Tumbling!

(Side note, there’s a small catch to all of this: Those using the Markdown editor will currently have problems using Editable Reblogs for now, although we hope to resolve this soon. In the meantime, switch to using the Rich Text or HTML editor by default)

EDIT: Should be deployed now, sorry everyone. These changes can be found in version 2.1.0 of Editable Reblogs—make sure you’re on that version before reporting any issues.

[Less Broken Than You Think]

Problem with reblogs not appearing on dashboard

It recently came to our attention that entire reblog sections of posts just disappear when viewed on the dash. We traced the issue back to tumblr changing their reblog chain detection yet once again and are currently working on adding a fix to Editable Reblogs to automatically clean this up.

In the meantime we have found a workaround for already affected posts:

Go to the HTML editor and to every link in the reblog chain add 

class=‘tumblr_blog’

with SINGLE QUOTES.

Be sure to use single quotes (apostrophes), as Tumblr’s parsing will strip the class out if it has double quotes.

Again, we are working on an Editable Reblogs update shortly which will do this automatically.

[Less Broken Than You Think]

Resolution for People Unable to Update Editable Reblogs on Firefox

We have located a solution for those people who have the Editable Reblogs extension installed on New XKit on Firefox, but were having trouble updating it from 1.0.9 to 2.0.0 (now 2.0.1).

It is likely, if you were encountering this problem, that you are running on one of the 7.6.x versions of New XKit, and Firefox has not auto-updated you to 7.7.0 because the extension is unsigned (we’re working on this but it’s a separate issue).

Note: If you are on 7.5.x or below, you are on the old XKit which we do not support, and need to uninstall it completely and install the extension from the link below instead.

What you will need to do is manually update to 7.7.0 by going to https://addons.mozilla.org/en-US/firefox/addon/new-xkit/ and clicking “Add To Firefox” – this will install 7.7.0 over your existing copy of New XKit and will maintain all your existing settings. After it is installed, you may need to close and reopen your browser to get XKit to work again.

Once you’re on 7.7.0 of the main New XKit extension, open your XKit control panel, navigate to the Editable Reblogs control panel, click Update, and confirm that you have updated to version 2.0.1!

[Less Broken Than You Think]

Reminder For Firefox XKit Users - Turn Off Private Browsing

We are still looking into why Editable Reblogs isn’t updating for some Firefox users. However, in response to a few other Firefox issues we have been fielding in our support chat, we would like to issue a reminder to anyone who is having issues with running XKit on Firefox:

Be sure you are not using Private Browsing. New-Xkit is not submitted to Firefox’s app store in a way which allows this and will only work in non-private mode, regardless of how old XKit worked.

As always, feel free to contact us with any questions. Thanks!

[Less Broken Than You Think]

Issues Updating Firefox to Latest Version of Editable Reblogs

Just as a heads-up – we are experiencing reports of people having trouble force-updating to the most recent version of Editable Reblogs (and possibly other extensions) in Firefox. We’re still trying to nail down what would cause this and will hopefully have a fix soon.

To be clear: if you have version 2.0.0 or newer, you’re fine. This is for people who are still stuck on 1.0.9. If you’re not sure, try updating all of your extensions from the XKit Menu (under “Other”) before doing anything else—you just may not have gotten the update yet.

In the meantime – updating definitely works on Chrome, and some people have had luck with a full uninstall and reinstall of XKit from their browsers to bring things up to date. (You can find a guide for saving your settings to XCloud at http://new-xkit-extension.tumblr.com/post/126630096169/how-the-fuck-do-i-use-xcloud-a-troubleshooting).

We will update further on this situation when we know more.

Thanks!

(Additionally, if you are on 2.0.0., please make sure that you uninstall the temporary greasemonkey script that was floating around—I have no idea how they’re going to interact)