Per Nergård (MVP)
+2
Feb 2, 2016
visibility 6538
star star star star star
(5 votes)

Order tabs with drag and drop

To get that smoth editorial experience in edit mode a correct ordering of the tabs play an important part.

In most projects I tend to do a last minute check and change ordering and access rights. Unfortunately the Edit Tabs view in admin mode is a pain to use since you need to click edit on each row in order to change index number and access rights. 

As a remedy Episerver has given us the [GroupDefintion] attribute which lets us declare tabs and set access rights from code. Be aware that when using the [GroupDefinition] attribute all editing of tabs in admin mode is locked down, forcing you to do a code change, recompile ,deploy just to do a small tab change. Not good in my opinion.

So what to do.. Drag and drop tab ordering plugin to the rescue.

It's a simple admin mode plugin that lets you drag and drop order of tabs and change accesslevels without needing to click edit first. Just order the tabs and change access rights and hit save and youre done. 

You can change sort order of tabs defined by code but for some reason you cant change access rights. I always start the sortindex value counter at 100 and use a step of 100. For some reasons the numbers on tabs defined in code doesn't show the correct number but the new values are there.

To handle the drag and drop support I have used the excellent and very simple to use Dragula.js.

You can get the code over at my Gist

Image tabrreorder.png

Feb 02, 2016

Comments

Daniel Ovaska
Daniel Ovaska Feb 3, 2016 11:50 AM

Nice work! I like

Arild Henrichsen
Arild Henrichsen Feb 4, 2016 12:59 PM

Nice! I like that Dragula works on touch devices too. 

A quick question: I know that manual reordering of properties on content types via the admin UI overrides ordering from code. (until CMS 7 it was the other way around).
Is it the same with ordering of tabs and categories now? (manual overrides code)

Obviously, if code always overrides manual changes, you would mess up any settings the editor made each time you deploy. But if everything is stored in the db now and persisted through deploys, that is great for keeping sites consistent between deploys and environments.

error Please login to comment.
Latest blogs
Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |