Per Nergård
Jul 13, 2011
  3444
(1 votes)

Overview of Visitor group content in your site

The new Visitor group functionality in EPiServer looks very interesting and I was so fortunate that I got a demo by Mats Hellström earlier this year but have been busy so haven’t had time to blog about my thoughts.

As I said earlier It looks very interesting but  my first impression was that the built in functionality had been focusing too much on making it easy for both developers (how can I nag about this?) and editors to create new visitor groups and use them to present content and totally forgetting about how to manage all this new content.

Since I’m currently working with a very large installation with many sub sites and a lot of pages my guess is that if we let the editors loose with this, we would in a couple of weeks have massive problems with visitor group driven content all over but no one knowing exactly where.

So how to improve this then.? My first thought was to add an icon to the page tree.

Since I did this during another session and on a colleague's laptop I didn’t have my playbox machine available but a quick googling I found an excellent post by Anders Hattestad.

With some modifications I got it running and the result looks like this:

Visitorgroup 

Of course this need to be developed further with possibility to filter from a list by available visitor groups, maybe modify the tooltip and more but at least it’s something.

This is something that could help the editors find their pages with visitor group content but I believe that some additional module is necessary to supply an overview of visitor group content for the chief editors and for example decision makers of a certain campaign.

Maybe in an R2B release?

Hot to get it running.

1. Get file

2. Add to project and modify namespace, class name if you want.

3. Modify the adaptermappings.browser file with changes from .2.

<adapter controlType="EPiServer.UI.WebControls.PageTreeView" adapterType="EPiServer.PageTreeViewAdapter" />

4. Done.

Jul 13, 2011

Comments

Hampus Persson
Hampus Persson Aug 2, 2011 10:48 AM

Excellent and would be very useful.

Please login to comment.
Latest blogs
Plug-in manager is back in CMS 12

Plug-in manager is back in the UI, what is it and how can i use it?

Luc Gosso (MVP) | Oct 6, 2022 | Syndicated blog

Display Child Pages in Content Delivery API Response

The below example will implement an instance of IContentConverterProvider to customise the serialisation of PageData and output child pages in the...

Minesh Shah (Netcel) | Oct 4, 2022

Bring the Report Center back in Optimizely CMS 12

The Report Center has been a part of Optimizely CMS since its first debut in version 5R2 in 2008, but in CMS 12, it's removed! Don't despair! Make...

Tomas Hensrud Gulla | Oct 4, 2022 | Syndicated blog

Customizing Property Lists in Optimizely CMS

Generic property lists is a cool editorial feature that has gained a lot of popularity - in spite of still being unsupported (officially). But if y...

Allan Thraen | Oct 2, 2022 | Syndicated blog

Optimizely names Luminary Senior Developer, Ynze Nunnink, OMVP

Luminary Senior Developer and Optimizely Lead, Ynze Nunnink has secured the coveted position of Optimizely MVP. Earning a Platinum badge for his...

Ynze | Oct 2, 2022 | Syndicated blog

Content Delivery API – The Case of the Duplicate API Refresh Token

Creating a custom refresh provider to resolve the issues with duplicate tokens in the DXC The post Content Delivery API – The Case of the Duplicate...

David Lewis | Sep 29, 2022 | Syndicated blog