#beta editor + new xkit.

[eriny3s]

♯  𝑒𝑟𝑖𝑛𝑦3𝑠 .  .  .  ❛ 𝑣𝑒𝑛𝑔𝑒𝑎𝑛𝑐𝑒 𝑎𝑛𝑑 𝑟𝑒𝑡𝑟𝑖𝑏𝑢𝑡𝑖𝑜𝑛 ; 𝑤ℎ𝑎𝑡 𝑢𝑛ℎ𝑜𝑙𝑦 𝑡𝑒𝑟𝑟𝑜𝑟 . ❜ 𝗧𝗛𝗘 𝗘𝗥𝗜𝗡𝗬𝗘𝗦 , 𝑏𝑜𝑟𝑟𝑜𝑤𝑒𝑑  from  ʰᶦˢᵗᵒʳʸ  ↝  worshiped  by  star  ; ²  /  ²³  . indie  &    𝑝𝑟𝑖𝑣𝑎𝑡𝑒  .  inspiration  taken  from  𝗰𝗹𝗮𝘀𝘀𝗶𝗰𝗮𝗹  𝗺𝘆𝘁𝗵𝗼𝗹𝗼𝗴𝘆  ,  modern  retellings  ,  &  personal  headcanons  .  compatible  with  sgg's  ²⁰¹⁸  release  ,  hades  .  this  blog  will  be  low  activity  ,  selective,  & iconless  .    

ˢᵗᵘᵈʸᶤᶰᵍ    𝑡ℎ𝑒𝑚𝑒𝑠    of    : greek  mythos  ,  the  final  girl  ,  the  monstrous  divine  feminine  ,  girl  as  sin  ,  loyalty  ,  blood-soaked  truths  ,  retributions  dealt  swiftly  ,  and  FAMILY .

#beta editor + new xkit. #aka twcebrn / mageiia / fantasmagorey / mortshe / n1ghtshe / faunisms / deathstined.

[deathstined]

♯   𝑑𝑒𝑎𝑡ℎ𝑠𝑡𝑖𝑛𝑒𝑑   .   .   .   ❛  𝑎𝑙𝑙  𝑤𝑖𝑙𝑙  𝑓𝑎𝑙𝑙  𝑡𝑜  𝑑𝑒𝑠𝑝𝑎𝑖𝑟  .  ❜  𝗠𝗢𝗥𝗢𝗦  ,  𝑏𝑜𝑟𝑟𝑜𝑤𝑒𝑑  from  ʰᶦˢᵗᵒʳʸ  ↝   worshiped   by   star ; ⁰²  /  ²⁴  .   indie   &   𝑝𝑟𝑖𝑣𝑎𝑡𝑒   .   inspiration   taken   from   𝗰𝗹𝗮𝘀𝘀𝗶𝗰𝗮𝗹   𝗺𝘆𝘁𝗵𝗼𝗹𝗼𝗴𝘆   ,   modern   retellings   ,   &   personal   headcanons   .   compatible   with   sgg's   ²⁰¹⁸   release   ,   hades   .   this   blog   will  be   low   activity,   selective,   &  iconless   .

𝑨  𝑺𝑻𝑼𝑫𝒀  𝑰𝑵  :  power   and   duty   ,  the  inhumanity  of  eternity   ,  family  as  power  ,  destructive  love  ,  the  ache  of  the  ancients  ,  drudgery  ,  inevitability  ,  fate  ,  responsibility  ,  &  force  . 

#beta editor + new xkit.

[mageiia]

♯ 𝑚𝑎𝑔𝑒𝑖𝑖𝑎 .  .  .  ❛  𝑐𝑙𝑒𝑣𝑒𝑟 𝑎𝑠 𝑡ℎ𝑒 𝑑𝑒𝑣𝑖𝑙 𝑎𝑛𝑑 𝑡��𝑖𝑐𝑒 𝑎𝑠 𝑝𝑟𝑒𝑡𝑡𝑦 .  ❜  𝗠𝗔𝗚𝗜𝗦𝗦𝗔  ,  daughter  of  ℎ𝑒𝑟𝑚𝑒𝑠  &  𝗰𝗶𝗿𝗰𝗲 , 𝑐𝑜𝑛𝑗𝑢𝑟𝑒𝑑  from  ᵗʰᵉ ᵐᶦⁿᵈ ᵒᶠ  ↝ star;  ¹  /  ²³  .  indie  &    𝑝𝑟𝑖𝑣𝑎𝑡𝑒  . compatible  with  sgg's  ²⁰¹⁸  release  ,  hades  . inspiration  primarily  from  madeline  miller's  novel  circe  , + 𝗰𝗹𝗮𝘀𝘀𝗶𝗰𝗮𝗹  𝗺𝘆𝘁𝗵𝗼𝗹𝗼𝗴𝘆  ,  modern  retellings  ,  &  personal  writings  .  this  blog will be  low  activity,  selective,  & iconless  .   

ˢᵗᵘᵈʸᶤᶰᵍ    𝑡ℎ𝑒𝑚𝑒𝑠    of    : gods  and  fear  ,  generational  trauma  ,  what  makes  a  family  ,  greek  mythos  ,  (  im  )  mortality  ,  the  nature  of  secrets  ,  &  finding  new  futures  amidst  the  rubble  of  the  past  .

#beta editor + new xkit. #aka twcebrn (dionysus) / n1ghtshe (nyx) / faunisms (mumu) / fantasmagorey (toni & sal; ocs) / mortshe (thanatos) / eriny3s (furies).

[fantasmagorey]

♯ 𝑓𝑎𝑛𝑡𝑎𝑠𝑚𝑎𝑔𝑜𝑟𝑒𝑦  .  .  .  ❛  𝑡ℎ𝑒 𝑗𝑎𝑤𝑠 𝑡ℎ𝑎𝑡 𝑏𝑖𝑡𝑒 , 𝑡ℎ𝑒 𝑐𝑙𝑎𝑤𝑠 𝑡ℎ𝑎𝑡 𝑐𝑎𝑡𝑐ℎ .  ❜  𝗔𝗧𝗢𝗡𝗜𝗔 + 𝗗𝗬𝗦𝗔𝗟𝗬𝗢  ,  children  of  𝕙𝕪𝕡𝕟𝕠𝕤  &  𝗺𝗮𝗴𝗶𝘀𝘀𝗮 , 𝑐𝑜𝑛𝑗𝑢𝑟𝑒𝑑  from  ᵗʰᵉ ᵐᶦⁿᵈ ᵒᶠ  ↝ star;  ⁴  /  ²³  .  indie  &    𝑝𝑟𝑖𝑣𝑎𝑡𝑒  .  characterization inspiration  taken  from  𝗰𝗹𝗮𝘀𝘀𝗶𝗰𝗮𝗹  𝗺𝘆𝘁𝗵𝗼𝗹𝗼𝗴𝘆  ,  modern  retellings  ,  &  personal  writings  .  this  𝘀𝗶𝗱𝗲𝗯𝗹𝗼𝗴 will be  low  activity,  selective,  & iconless  . 𝑎𝑠𝑠𝑜𝑐𝑖𝑎𝑡𝑒𝑑 𝑤𝑖𝑡ℎ @singofus 𝑎𝑠 ℎ𝑦𝑝𝑛𝑜𝑠 + 𝑟𝑒𝑠𝑝𝑒𝑐𝑡𝑖𝑣𝑒 𝑡𝑤𝑖𝑛 𝑝𝑎𝑖𝑟𝑠 .   

ˢᵗᵘᵈʸᶤᶰᵍ    𝑡ℎ𝑒𝑚𝑒𝑠    of    : family , greek mythos , dark + light balance , siblings , catching dreams before waking , useless sapphics , and too - sharp grins .

#beta editor + new xkit. #aka twcebrn (dionysus) / mageiia (maggie; oc) / faunisms (mumu) / n1ghtshe (nyx) / mortshe (thanatos) / eriny3s (furies).

[rpschtuff]

Beta Editor / Trim Reblogs Masterpost

This is just a spot to gather all my posts about the beta / legacy editors and cutting posts into one place, mostly so it's in one easily shareable link for people who ask. (Last updated February 21, 2023.)

WHAT'S EVEN GOING ON — This long post explains pretty much everything in great detail. It covers the different editors, the different extensions required for cutting posts and how they work, some glitches you may encounter, and reasons the two systems aren't compatible. I highly recommend reading this one before any of the others, as it provides the most context.

TRIM REBLOGS GUIDE — An overview to just Trim Reblogs.

USING TRIM REBLOGS WITH THE LEGACY EDITOR — If you aren't willing to commit to the beta editor yet, at least learning how to use trim reblogs will make a world of difference to your partners using it.

BETA EDITOR OVERVIEW — An overview to the beta editor, the differences it has from legacy as well as its new features.

TRANSFERRING THREADS TO BETA / TRIM REBLOGS — An overview of how to actually go about transferring threads cut with the old system (editable reblogs) to the new system (trim reblogs).

DOUBLE POSTING GLITCH 1 + HOW TO FIX — Goes over a glitch you may encounter when using trim reblogs on a post that was originally made with the legacy editor, causing your reply to duplicate upon posting.

DOUBLE POSTING GLITCH 2 + HOW TO FIX — Goes over a glitch you may encounter when using editable reblogs on a post that was originally made with the beta editor, causing your partner's reply to duplicate upon posting.

#rph #rpt #rpc #beta editor #trim reblogs #legacy editor #editable reblogs #xkit #new xkit #xkit rewritten #*my stuff #*my tutorials #*beta editor masterpost

[heartxshaped-bruises]

✧･ﾟ A short and easy workaround for Reblogs with Beta & XKit Rewritten

Disclaimer: This also seems to work with old Legacy-Threads when reblogging with the new Beta-Editor bc XKit Rewritten doesn’t work with Legacy. The whole trimming order and process of both combined can be confusing, but it’s important so the post doesn’t get fucked up. So technically, it's also helpful for Beta-Reblogging in general.  (video below)

SO, IF YOU WANT TO AVOID DOUBLE-POSTING of your own reblog, do the following:

Hit reblog (make sure you’re using Beta).

Enter reply, whatever.

Safe to drafts.

Remove the first post with Trim Reblogs.

Safe.

Refresh drafts.

Remove your own reply that now shows twice with the Beta-Editor. You will only have one option to remove here, so that makes it easy.

Refresh.

Tadaaa.

In this way you can preserve your partner's reply if you want to, since the blockquote-format won't work like that anymore. So hopefully, reblogs with the Beta-Editor & XKit Rewritten should be easier now for you and your partners without having to move your whole Legacy-Thread to a new post after this measure. I am very nostalgic over my old stuff, so that's a reason why I don't want to do it. If you have additions or experience possible errors, feel free to add them.

PLEASE NOTE THAT THIS WILL ONLY WORK if your partner reblogged their response without any XKit-Extension. Just a plain reblog.

#rph #rpc #beta #editable reblogs #trim reblogs #xkit rewritten #new xkit #legacy editor #tutorial #*mine: edits #[ I just needed a short guide for my horrible brain ] #[ just short; no additional info ] #[ just wanted the essentials to get rid of the double reply issue ] #[ maybe it helps you too ]

[dhampiravidi]

Owls!OT4

continued from here (moved to a new thread to use Beta editor):

When Rye leans into the kiss that Jayn presses to her head, Jayn already knows what her friend, her college sweetheart, is going to do. She's smiling on the inside, and that makes her feel sick--guilty, because it's the little bit of Owl that she hasn't scraped off. It's the part of her that goes into a bloodthirsty rage when she's confronting someone who's hurt innocent people, especially children. It's the part of her that used to seduce tall men with dark hair and green eyes, or curvy women with red hair, telling them whatever they wanted to hear so they wouldn't mind too much when she came on their fingers screaming someone else's name. It's the part of her that she fears she was born with, evidenced by when she looks back and sees all the times she got in trouble with her mom. She feels horrible because she knows she told Rye exactly what she needed to, in order to get the girl to say yes.

Janice Wayne was an Owl. But Jayn Katherine Loren isn't.

"I think Rye should be with me a couple of hours before. Just me." She holds her hand up in Tim's direction, stopping him before he can bark some snippy retort or start planning her '"accidental" death. "If it's like this again, where it's all four of us together, Dick will know we're planning something." They'd all been trained to be paranoid enough. "He knows that Rye and I have a past, and it'll seem like we're just catching up, which we are. We'll talk...and then I'm going to train her. The way Selina trained me." Selina, bless her, actually wasn't a creep of any kind, so she hadn't touched Jayn so much as let her watch while the Pussycat (it was the name of her establishment, but you were supposed to call her Mistress) showed her some seduction techniques. "It'll keep Dick satisfied...until we come in." She also planned on giving Rye a nice bath, maybe with some candles, to help her wind down, but Tim didn't need to know that. He'd die of jealousy.

Tim feels like a goddamn raccoon trying to hiss and fend off the asshole humans who are dumb enough to ask for their trash back. Why is Jason seriously trying to fight for Jayn's affection when she's obviously got her own agenda?, he's wondering. Tim was pretty fucking sure that she hadn't bothered trying to contact her lost love since she first left. Jason should've given up on her and buried his face in the cunt of Ultraman's niece Kara, like he seemed so eager to do the few times that they happened to be in the same room together. She might've (accidentally) killed him, depending on how she liked it, but at least he wouldn't be pining and looking pathetic now. And of course, Tim's glaring daggers at Jayn every second he isn't focused on trying to murder Dick. Why did she conveniently arrive the night he privately announced his engagement to Rye? Maybe Jayn's whole presence is just a test from their father...but he can't attack her yet. As much as he hates to admit it, Jayn is part of Rye's chance to survive her time alone with Dick.

So when Jayn gives Rye a chaste kiss, Tim is initially livid. If Rye hadn't come back to him a second after Jayn kissed her head, he would have found a reason to put the brunette in a chokehold. But Rye manages to calm him with her yes. He wraps his arm (possessively) around her waist, whispering how she's gonna be perfect, and he'll never see it coming. When Jayn begins to deliver the specifics of her plan, he clenches his jaw (something his dentist had warned him against doing any more than he already had). "It's up to you," he tells Rye, and he means it. Because once Dick (and Bruce, since he won't stand for his oldest's assassination) was dead, Rye would be Tim's forever. He'd seen how she looked at him when the Court of Owls introduced them, compared to how she looked at him now. He had already won her over. She'd get her engagement ring after she slept with Dick, since it would be a distraction (or knowing the Talon, a weapon). The wedding was just a formality--one of many luxuries that Rye would be able to enjoy as his new wife.

@ashortgothamite

#jlw: thread #ashortgothamite #owls!au #the romantic/fluffy sex & bath is a new idea so I won't be mad if you/Rye says no-- #but I figured it'd be both practical & a way for them to catch up #btw if you didn't know Beta editor lets you trim posts if you have xKit...otherwise stuff stays long so I made a new thread

[ulfhrafnx]

since this seems to be a recurring issue ( and honestly the reason why i had to switch over to the beta editor for good ) it’s worth mentioning again that there’s no cross compatibly between the legacy editor and the beta editor. meaning if you’re writing with someone whose using legacy and you’re using beta you’re going to eventually encounter problems , the main one being not being able to trim posts. the only way to fix it is to use the beta editor and to also make sure you have xkit rewritten installed. it’s a browser extension. better resources found here , here and here.

#☽✦☾ | can i pet that dog ? ( ooc ) #`` I personally prefer the beta editor #but i know a lot of people don’t #it’s a necessary evil if you want to be able to write #old xkit doesn’t work the way it should anymore with the legacy editor #and anyone making a new blog doesn’t have the option #to switch between the two #they’re stuck with the beta editor by default #which i suspect is going to be the same across the board soon enough

[toyfulbox]

cnt. from here || @universalcrossover

"Ahh.. this is such a long-lasting brain freeze!!" Mitsuru complained, then standing up to dash in place, running all over the dorm room would cause a big ruckus and wake the rest of the sleeping members.

"Hurry, hurry Shiina-senpai!!!" Though the dashing was already working, he was working up a sweat! "I'll keep it up though, until I get worn out!" Mitsuru spoke in between breaths and panting as he continued to dash in place... that is, before he plopped down on the couch all tired-like!

#universalcrossover #💨 dash dash da ze! mitsuru tenma #(( i had to move the old thread to a new post because i'm using the beta editor #along with the xkit extension it wont let me trim the old post properly.. so have a new one !

[sharp-teeth-and-archived]

Game plan: I'm sure eventually we'll have to merge over to the beta editor, but for the moment, I'll just use the usual trim editor (the pencil one) with the legacy thing for my current threads in my drafts (since we already were using that format to reply). I'm fairly certain all of my threads in my drafts were posted with the legacy editor. I'll just convert stuff over when we finally have to use the beta editor so there's less confusion. But for new threads, asks and everything, I'll be using the beta editor.

#( ooc ) #( I still have tried xkit rewritten and I believe you can use both xkits? ) #( I don't have any new threads here so this will likely be the case on my other blogs ) #( gonna actually try to write now ) #( let me know if you would prefer for me to move our thread to a new post if you prefer the beta editor ) #( haven't tried xkit rewritten* oops ) #( I guess the new beta editor lets you fix tags than completely deleting it and retyping it all out? )

[yasashite]

#{ ;;ooc - Out of Patience } #I'm becoming frustrated... #legacy editor won't be sticking around and it's the only way I know how to RP here on tumblr.. #the new xkit rewritten doesn't help as I can't keep my current format with 2 responses at a time.. #it's frustrating as I don't know how to trim posts in the new beta.. #I just remade these blogs.. I don't want to have to leave tumblr to Discord for good..

[keikakudori]

post prior.

                a glorious look that some might have said about the gaze that aizen sousuke was leveling upon the pair before him -- for that eye was wide, that gaze was intense. a startled thing he appeared, unsure and uncertain of the world around him suddenly and left bereft of color and sound and life. but it was not something that would ever be a prolonged sentiment for a man such as him. for all that he was a divine beast, for all that aizen sousuke had come to reign over the halls of las noches and had become something truly dangerous, turned immortal from the piercing of that heart and more --- 

                curse or blessing, geas or benediction -- perhaps both at once for it had been by that blade of silver that he had been cut down and left tumbling from the great height which he'd risen to. arrogance, foolishness, stupidity -- all had been his folly when it had happened. and here, now, this was the locus of his own actions and hubris. this was proof of the work of years upon years culminated into the truest display of his own stupidity. of his own loss. and shock hung there in him, in his soul, hovering like a wound that had not verged near upon healing; there was no scar tissue to be found there for he was a thing made of blood and grief. how he BLED even now. how he agonized over it. and now this --- this QUINCY had somehow found gin, had found --- HOW? the thought ran through his head, hovered there, shuddered through him. HOW HAD THIS OUTSIDER FOUND GIN? HOW HAD THIS HAPPENED?

                the color of that skin -- it was wrong. the way gin was holding himself -- more. more more more --- signs that something was WRONG. how they screamed at him, those subtle things -- but there too was the command and the air was snarling. it was thickening. for all that the pale reiatsu of the younger shinigami slammed at aizen, he had grown considerably in the two years hence from that day. for all of that power -- for all of that weight -- 

                DON'T LET HIM HURT ME --- 

                a command? it seemed so. beneath the numbness, beneath that pain --- anger. anger was rising. it was blooming, it was surging upwards. what had happened was all, yes -- a flash. a blink of an eye a breath of air the beat of a heart --- A FLASH OF ENERGY AND POWER.                 the words had rolled from gin's mouth --- BANKAI, KAMISHINI NO YARI.

                powerful, precise -- how he had ever enjoyed watching gin's hand moving, sweeping across the canvas of what dwelt before them both, cutting down enemies like they were stalks of wheat to collect the chaff. such was how he knew the power of that blade, knowing that if he leaned in close enough, perhaps shinso would be hissing. for the first time in two years, however, he felt a stirring from ---

                a jolting thrust against his body, an impact; there and gone again and the concussive clap of the sonic boom would've been enough to tell him, even without the flash of pain through his torso from where the blade had plunged in and exited. the blood which flowed into the air like a crimson serpent in the wake of the wakizashi's exit was a threading of sorts, a reminder of a string that he had thought cut to be forever severed. but did not the saying proclaim that it could knot and tangle yet never be cut, never be broken? perhaps this was proof of that. yet how the pain was there, catching up with what had happened, aizen feeling the force of that strike. his raikoho had not landed, though how he had wanted it too, and even before he could begin to move and rush in in its wake, the blade was punching through the surface of his chest and out that broad back --- 

                a ribbon of blood in the air.

                a thread that tied them together.

                it was but something caught by a flash of brilliance upon the blade, red staining it, and already he had been moving even when the blade was rotated in that hand, aimed --- a FLASH. 

                black fluttered down towards the earth below, the band which had curled over his head drifting like a flurry of ash to settle gently upon the earth whilst the dark-haired traitor stood as if transfixed as shinso's blade cut through his HEAD. the black was left to drape and slip to conceal pieces of rubble. there seemed to be no sound. only when the blade was gone did aizen collapse as if he were empty garments falling from a hanger, crumpling into a heap of black bindings and limbs. 

                how abruptly the power in the air, cut off and no longer present. so it was he was left to lay there, sprawled, a heap even as the wound cutting through his head leaked blood and clear fluids alike, the wet red mouth of it gaping as if inviting a touch, a finger, a probing; gone was the eye of brown, burst and wounded into nothing but gelatinous aftermath that leaked across the skin of the god and an unseeing depth of violet upon crystalline silver gazed towards the heavens overhead. the monstrous beast laid there and he did not move, did not make any motion whatsoever. 

                --- felled. he had been felled. ah, how swiftly it had cut him, that lance of silver. 

                DEICIDE.

/ @godkilller & @zombiigrl

#t: tbt #[ verse: blood war ] as i cannot be the hero let me be the monster and lesson them in fear in place of love. #godkilller #zombiigrl #we're trying out a new post starting point to see if the xkit trim function works #with using the beta editor instead of the legacy #fucking hell staff why are you doing this to us #why can't we vote on these kinds of updates #you never please people when you do this to us

[enslaughts]

finally figured out how the hell beta editor works gd

#out. #hell on earth. all this time i've thought legacy was the new one lmao #god help me #why are u so complicated..... anyway #so if i randomly reply to a thread in a new post here or on jesper that is why <3 #since i'd rather just bite the bullet and use beta editor though i'm willing to switch for my partners ofc! #BUT xkit rewritten doesn't work on microsoft edge so. i will be migrating to a new browser #just gotta. decide which one. fuck chrome <3

[the-rat-house]

@traveling-forgo-warrior moved this thread here!

“My name is Morpho Knight.” They say, before bowing their head slightly in a mix of respect and greeting. “I do not know if my name is oft spoken by your people or not, but news of a new warrior never takes long to reach me. I wished to meet you personally.”

The knight did not really have time to go and check on who knows what about them - finding time to greet this warrior was already a miracle in and of itself. There were always souls to be judged, but non so powerful that the knight couldn’t make time for this.

#ic: morpho #rp #traveling-forgo-warrior #(I switched to using xkit rewritten and the beta editor so i had to move the thread to a new post) #(if that's an issue lmk!)

[yllowpages]

PSA:

i’ll likely be switching to the beta editor to make things easier on those who have no choice but to use the beta editor, just in case. 

#ooc. #i've had the xkit rewritten trim posts extension for a while now #but haven't ever used it #bc i've just used editable reblogs #since none of my blogs are new enough to have an issue with the beta editor #but i know it's unavoidable for some

[staff]

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.

#features #post editor