# New editor: Adding Slice-Zone missing?

**URL:** <https://community.prismic.io/t/new-editor-adding-slice-zone-missing/14400>\
**Category:** Prismic for Content Creators\
**Tags:** page-builder\
**Created:** [October 29, 2023, 10:55pm UTC](https://community.prismic.io/t/new-editor-adding-slice-zone-missing/14400 "2023-10-29T22:55:42Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![leopold](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/leopold/32/6141_2.png) [@leopold](https://community.prismic.io/u/leopold)\
**Post date:** [October 29, 2023, 10:55pm UTC](https://community.prismic.io/t/new-editor-adding-slice-zone-missing/14400/1 "2023-10-29T22:55:42Z")

</div>

Is it just me or is the new content editor missing the add/remove feature for Slice-Zones? If so, why and could I set the older editor as a default?

 ![Screenshot 2023-10-29 at 23.46.32](https://europe1.discourse-cdn.com/flex013/uploads/prismic/original/2X/9/9bdd1c40568e0ac9801ded8aa39987975c8db43b.png)

 ![Screenshot 2023-10-29 at 23.47.53](https://europe1.discourse-cdn.com/flex013/uploads/prismic/original/2X/d/d8d0cdf366f0388f1022b965164cf95bf690b51e.png)

---

<div class="post-metadata">

**Author:** ![leopold](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/leopold/32/6141_2.png) [@leopold](https://community.prismic.io/u/leopold)\
**Post date:** [October 30, 2023, 10:51am UTC](https://community.prismic.io/t/new-editor-adding-slice-zone-missing/14400/3 "2023-10-30T10:51:58Z")

</div>

I think this is actually _unrelated_ (enabling legacy builder). On new repositories you can "enable legacy builder" to build document types like was done in the past, but editing individual documents now defaults to a new editor version.

That being said, I personally much prefer the _legacy_ document building.

---

<div class="post-metadata">

**Author:** ![vladimir.fomin](https://avatars.discourse-cdn.com/v4/letter/v/3e96dc/32.png) [@vladimir.fomin](https://community.prismic.io/u/vladimir.fomin)\
**Post date:** [October 30, 2023, 10:54am UTC](https://community.prismic.io/t/new-editor-adding-slice-zone-missing/14400/4 "2023-10-30T10:54:17Z")

</div>

Facing the same issue! We cannot add slices to new documents in the new builder.

---

<div class="post-metadata">

**Author:** ![nikola.jovanovic](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/nikola.jovanovic/32/8431_2.png) [@nikola.jovanovic](https://community.prismic.io/u/nikola.jovanovic)\
**Post date:** [October 30, 2023, 1:57pm UTC](https://community.prismic.io/t/new-editor-adding-slice-zone-missing/14400/5 "2023-10-30T13:57:33Z")

</div>

@leopold You are right.  
I deleted my comment.

---

<div class="post-metadata">

**Author:** ![Phil](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/phil/32/14_2.png) [@Phil](https://community.prismic.io/u/Phil)\
**Post date:** [October 30, 2023, 2:26pm UTC](https://community.prismic.io/t/new-editor-adding-slice-zone-missing/14400/6 "2023-10-30T14:26:57Z")

</div>

Hey Team,

So, in the new builder this button ➕ has been moved to the table of Slices on the side which shows previews of all the Slices:

 ![Screenshot 2023-10-30 at 14.55.12](https://europe1.discourse-cdn.com/flex013/uploads/prismic/original/2X/9/91cf77c804fe12d066d9c6f2ba0231383fe7e984.png)

If you're not seeing this, then it's probably because you have legacy Slices (pre-slice machine). We will be rolling out an update this week, so you'll have a representation of the legacy Slices in the side panel and can add new ones. 🎉

 ![Screenshot 2023-10-30 at 14.56.27](https://europe1.discourse-cdn.com/flex013/uploads/prismic/original/2X/8/81925e1054d2b1af12fee804f91a96aa73cf447e.jpeg)

We are also working on an upgrade tool so users will be able to upgrade legacy slices to the new format. 👷‍♂️

For anyone who wants me to reenable the legacy editor by default, you can send me your repo URL here, and I'll process that for you 🙂

---

<div class="post-metadata">

**Author:** ![leopold](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/leopold/32/6141_2.png) [@leopold](https://community.prismic.io/u/leopold)\
**Post date:** [October 30, 2023, 8:38pm UTC](https://community.prismic.io/t/new-editor-adding-slice-zone-missing/14400/8 "2023-10-30T20:38:41Z")

</div>

> [@Phil](#):
>
> For anyone who wants me to reenable the legacy editor by default, you can send me your repo URL here, and I'll process that for you 🙂

Thanks, if the update arrives soon, then there is no need 🙂

A bit of a side-note, but I wanted to mention it somewhere. If a document type has many tabs (I am for example working on things that have 7 tabs), they look quiet bad (cramped) in the new editor. In case you want to add an internal issue regarding that.

---

<div class="post-metadata">

**Author:** ![alexander.hagen](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/alexander.hagen/32/8531_2.png) [@alexander.hagen](https://community.prismic.io/u/alexander.hagen)\
**Post date:** [October 31, 2023, 9:30am UTC](https://community.prismic.io/t/new-editor-adding-slice-zone-missing/14400/9 "2023-10-31T09:30:20Z")

</div>

Hi.  
We would like to have the legacy builder enabled as default if that is possible.  
Repo is [mycall.prismic.io](http://mycall.prismic.io)

I would also like to second Leopolds side-note regarding the tabs. In our case it makes some documents unusable, as the tabs push the "Save" / "Publish" buttons out of the page.

---

<div class="post-metadata">

**Author:** ![yinan439](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/yinan439/32/6513_2.png) [@yinan439](https://community.prismic.io/u/yinan439)\
**Post date:** [October 31, 2023, 1:14pm UTC](https://community.prismic.io/t/new-editor-adding-slice-zone-missing/14400/10 "2023-10-31T13:14:49Z")

</div>

> [@leopold](#):
>
> I think this is actually _unrelated_ (enabling legacy builder). On new repositories you can "enable legacy builder" to build document types like was done in the past, but editing individual documents now defaults to a new editor version.
> 
> That being said, I personally much prefer the _legacy_ document building.

What a coincidence！I was stucked for four days and now i know it isn't my issue.

---

<div class="post-metadata">

**Author:** ![yinan439](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/yinan439/32/6513_2.png) [@yinan439](https://community.prismic.io/u/yinan439)\
**Post date:** [October 31, 2023, 1:17pm UTC](https://community.prismic.io/t/new-editor-adding-slice-zone-missing/14400/11 "2023-10-31T13:17:34Z")

</div>

how long it will go? i was waiting for 4 days~

---

<div class="post-metadata">

**Author:** ![Phil](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/phil/32/14_2.png) [@Phil](https://community.prismic.io/u/Phil)\
**Post date:** [October 31, 2023, 2:36pm UTC](https://community.prismic.io/t/new-editor-adding-slice-zone-missing/14400/12 "2023-10-31T14:36:38Z")

</div>

The tabs in the new UI has been marked as a place for improvement already 🙂

As for when we'll have legacy Slices in the table on the side, we're looking at the end of the week for that release.

---

<div class="post-metadata">

**Author:** ![carrethomas7](https://avatars.discourse-cdn.com/v4/letter/c/e9c0ed/32.png) [@carrethomas7](https://community.prismic.io/u/carrethomas7)\
**Post date:** [November 7, 2023, 12:19pm UTC](https://community.prismic.io/t/new-editor-adding-slice-zone-missing/14400/15 "2023-11-07T12:19:10Z")

</div>

Hey @Phil

Can I go back to the legacy builder as default if that possible ?  
I can't see my slices in documents :(

Here is my link : [https://floema-shop.prismic.io](https://floema-shop.prismic.io)

---

<div class="post-metadata">

**Author:** ![Phil](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/phil/32/14_2.png) [@Phil](https://community.prismic.io/u/Phil)\
**Post date:** [November 7, 2023, 12:39pm UTC](https://community.prismic.io/t/new-editor-adding-slice-zone-missing/14400/16 "2023-11-07T12:39:12Z")

</div>

Done 🙂
