Tahir Naveed
Nov 17, 2016
  6023
(6 votes)

Adding a menu item into Context Menu - EPiServer 10.1 way

A while back, I blogged about how to customise the context menu in EPiServer 7. The code used to extend the context menu was not an approach supported by EPiServer and it was not guaranteed to work with any future releases.

I was looking at the EPiServer documentation and came accross plugin areas document in which EPiServer explains the introduction of "Plug-in areas" for EPiServer 10.1 and higher which can be utilised to customise context menu both for commerce and cms.

The end result will be same and will look like

Image Blog_1.png

The VS project looks like 

Image VS.png

The gist for the code is here.

Please note that this code will only work for EPiServer.CMS.UI version 10.1 and higher.

It is a very simple code but if you have any questions please feel free to ask.

Nov 17, 2016

Comments

Nov 18, 2016 12:34 PM

Nice post Tahir

Praful Jangid
Praful Jangid May 28, 2025 08:06 AM

This post is still very helpfull. Even with the CMS12. Thanks for sharing it with simplest example.

Please login to comment.
Latest blogs
A First Look at Optimizely Remote MCP Server for Experimentation

Optimizely just released a Remote MCP Server for Experimentation and I've been trying it out to see what it can do. If you don't know, MCP (Model...

Jacob Pretorius | May 1, 2026

Promoted and Certified

What a busy week

Andy Blyth | May 1, 2026 |

Announcing new library: SettingsManager

When you run .net app, there have been a few ways to store settings. Those can be set via appSettings.json, or via Azure Portal AppService...

Quan Mai | Apr 30, 2026

From Prompting to Production: Optimizely Opal University Cohort and the Future of Agentic MarTech

Most organizations today are still playing with AI. They experiment with prompts, test ideas in isolated chats, and occasionally automate a task or...

Augusto Davalos | Apr 28, 2026

Six Compelling Reasons for Upgrading to CMS 13

Most software updates ask you to keep up. Optimizely CMS 13 asks something different — it asks whether your digital strategy is built for a world...

Muhammad Talha | Apr 28, 2026

Optimizely CMS 13 breaking changes: GetContentTypePropertyDisplayName

When upgrading from CMS 12 to 13, resolving property display names may not work as before. Here’s what changed.

Tomas Hensrud Gulla | Apr 27, 2026 |