#and they certainly couldn't ever discover errors in their old posts or want to update them because their beliefs or opinions have changed

[say-duhnelle]

Fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck you fuck youuuuuuuu

Hello, Tumblr. 

If you joined us before November 2022 and predominantly post on web, you will be familiar with the two post editors—the legacy editor and the “new” web editor (formerly known as the “Beta editor”).

Beginning May 15, we’ll gradually be working to remove the legacy editor as an option for creating new posts. New posts created on web will be created in the new web editor. We hope to complete this change by July 15. 

This change only affects accounts created before November 2022. Newer accounts already default to the new web editor.

This will not affect posting on the apps because we switched to this new editor on the apps about four years ago. If you use the apps, you’ve been using the new editor all this time!

This will not affect what you can include in a post, only how you get there: You can still include all the different types of media in a post, only now, you’ll do that via the new web editor’s content blocks instead of selecting a post type from the post type bar at the top of your dash. So, if you’re halfway through a text post, and you decide that what this post really needs is your pet reptile, then click on the little red image icon in the post editor, select an image, and voilà. Lizard boy steals our hearts.

If you still prefer to post on web using the legacy editor, please keep reading because the rest of this post is for you.

How can you prepare for this change?

Once we have completed this update, you won’t be able to create posts using the legacy editor. You will be able to edit posts made using the legacy editor, at least for now. 

Start using the new web editor ahead of the switch. This will help you help us troubleshoot any issues you might encounter. It’ll also mean you’ll already know the ropes before the switch is final. 

Talk to us. Send us feedback. Especially if you’re switching from legacy to the new web editor. We want to hear about your experience: Are there any specific workflows or features in legacy that you want to see in the new editor?      

If you use a theme, make sure to check whether it supports posts made using the new web editor, and update it if that’s not the case. 

For those of you trimming reblogs: @rpschtuff has created an incredibly detailed master post that gets into the nitty gritty of that practice in the new web editor.

XKitters: XKit Rewritten was explicitly designed with the new web experience in mind. This means that you will need to use XKit Rewritten when creating posts in the new web editor.

That’s all for now. Remember, you can always get in touch with us. If it’s regarding the new web editor, then Support is the place for you. If it’s about something else, @wip is your guy.