Blog posts by Lee Crowe

Content search and replace

Wed, 19 Nov 2014 13:45:25 GMT

The development team I currently work in like to have content in line with production content but it very quickly becomes outdated.

To aid with this we have Go pipelines which restore production database backups over lower internal environment databases.

The CMS Site has many links to various other product journeys. These journeys have environment specific Urls. If we are are in our regression environment, we would like content links to hand off to the relevant regression product journeys.

Our go pipeline restores the production database and performs many content replacements by executing a search and replace stored procedure. Below you will find the stored procedure definition to search and replace content.

IF  EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[dbo].[usp_CustomSearchAndReplace]') AND type in (N'P', N'PC'))
      DROP PROCEDURE [dbo].[usp_CustomSearchAndReplace]
GO

CREATE PROCEDURE [dbo].[usp_CustomSearchAndReplace]
      @SearchFor nvarchar(1000),
      @ReplaceWith nvarchar(1000) = ''
AS
      SELECT * FROM [tblContentProperty] WHERE [String] LIKE '%' + @SearchFor + '%' OR [LongString] LIKE '%' + @SearchFor + '%'
      SELECT * FROM [tblWorkContentProperty] WHERE [String] LIKE '%' + @SearchFor + '%' OR [LongString] LIKE '%' + @SearchFor + '%'

      IF LEN(LTRIM(RTRIM(@ReplaceWith))) > 0
      BEGIN
            PRINT 'Updating published pages'
            UPDATE [tblContentProperty] SET [String] = REPLACE([String], @SearchFor, @ReplaceWith) WHERE [String] LIKE '%' + @SearchFor + '%'
            UPDATE [tblContentProperty] SET [LongString] = REPLACE(CAST([LongString] AS nvarchar(max)), @SearchFor, @ReplaceWith) WHERE [LongString] LIKE '%' + @SearchFor + '%'
            PRINT 'Updating unpublished pages'
            UPDATE [tblWorkContentProperty] SET [String] = REPLACE([String], @SearchFor, @ReplaceWith) WHERE [String] LIKE '%' + @SearchFor + '%'
            UPDATE [tblWorkContentProperty] SET [LongString] = REPLACE(CAST([LongString] AS nvarchar(max)), @SearchFor, @ReplaceWith) WHERE [LongString] LIKE '%' + @SearchFor + '%'
            PRINT 'Updating soft links'
            UPDATE [tblContentSoftlink] SET [LinkURL] = REPLACE([LinkURL], @SearchFor, @ReplaceWith) WHERE [LinkURL] LIKE '%' + @SearchFor + '%'
      END

ElencySolutions.MultipleProperty v1.6.3 Released

Mon, 22 Oct 2012 11:33:39 GMT

In the previous couple of minor releases I added some functionality to automatically render dynamic content correctly in presentation view, I had several requests from Developers for this ability.

The implementation ended up becoming more complex than it needed to be and there were issues when using this solution with composer.

After a little reflection I decided to rollback this functionality and provide an extension method instead hence the reason for v1.6.3.

New Features

A new ToPresentationString() extension method is now available which can be called on strings to render dynamic content correctly.

  1: using ElencySolutions.MultipleProperty.Extensions;
  2: 
  3: string html = entity.XhtmlProperty.ToPresentationString();

Installation

The easiest way to install the assembly is by installing it from the EPiServer Nuget Feed (once it has been made available). But if you are not down with the cool kids you can download it from codeplex.

On the codeplex site you will also find some useful documentation and example code to get you familiar with what the property offers. The example code is dependant on PageTypeBuilder.

Feedback

As always feedback is greatly appreciated. If you have any suggestions for new features or changes I am happy to hear them.

Just twitter me @croweman or send me an email.

ElencySolutions.MultipleProperty v1.6.2.1 Released

Tue, 09 Oct 2012 10:35:42 GMT

There was a bug with dynamic content rendering in Release v1.6.2 when in published view. This has been fixed in v1.6.2.1.

Installation

On the codeplex site you will also find some useful documentation and example code to get you familiar with what the property offers. The example code is dependant on PageTypeBuilder.

Feedback

As always feedback is greatly appreciated. If you have any suggestions for new features or changes I am happy to hear them.

Just twitter me @croweman or send me an email.

ElencySolutions.MultipleProperty v1.6.2 Released

Tue, 02 Oct 2012 10:55:17 GMT

A new version of my MultipleProperty assembly is now available.

For more information regarding the ElencySolutions.MultipleProperty assembly please refer to codeplex which has several links to useful resources.

Background for the v1.6.2 Release

I have had a number of issues raised to me in the last few weeks mainly to do with PropertyImageUrl properties.

The issue is caused when VPP images are either deleted, moved or renamed.

When Edit mode is loaded and there is an invalid VPP image link within a multiple property Edit mode will fall over with a 500 error .

This then makes it very difficult for an editor/developer to fix the invalid image link!

All Fixes in v1.6.2

Edit mode will no longer fall over with a 500 error when a multiple property points to an invalid VPP image.
Dynamic content within XHTML properties will now render correctly in preview and published mode.

Further information around MultipleProperty and VPP images

When using standard PropertyImageUrl properties and deleting, renaming or moving VPP images you will be warned by EPiServer that image links will be broken.

Because of the way the MultipleProperty controls are built it is not possible (as far as I am aware) to hook into this functionality and inform the user that MultipleProperty image URL’s will also be broke.

I assume the way EPiServer handles this is that it would select records from tblProperty and tblWorkProperty and check whether there are any values in the String column that link to the VPP images that are being modified.

Multiple property serializes the entity values to xml and stores the values in the LongString column.

It may well be possible to hook into various UnifiedFile events and then execute some SQL to update column values but I think this is a bit messy/risky.

For now, I believe the safest option is to allow Edit mode to load and the value of the property to be empty. It would then be the content editors responsibility to fix the image links although they will not instantly be aware that the VPP image changes they are making will potentially have a knock on effect on various MultipleProperty properties throughout the site.

Installation

On the codeplex site you will also find some useful documentation and example code to get you familiar with what the property offers. The example code is dependant on PageTypeBuilder.

Feedback

As always feedback is greatly appreciated. If you have any suggestions for new features or changes I am happy to hear them.

Just twitter me @croweman or send me an email.

Building Hyperlinks in EPiServer

Fri, 10 Aug 2012 12:14:52 GMT

An issue was raised in one of the projects I was working on yesterday to do with some of the hyperlinks that are rendered on various components within the site.

The issue was mainly to do an editor setting a PageReference property to point to a page that has the “Target frame” set to open in a new window. This option appears on the Shortcut tab below:

Unfortunately most of the components within the site just render the LinkUrl which has been fine up until now. The editor expects the link to open a new window if the “Target frame” value is set to “Open the link in a new window” on the page being referenced.

This makes sense but is a potentially large amount of effort to implement throughout the site.

So for anyone else who isn’t aware of this potential pitfall I have created some helper methods for building link URL’s which mayprove useful.

The helper class can be downloaded from here. But the code within the class is also shown below.

  1: namespace Project
  2: {
  3:     using System;
  4:     using System.Text;
  5:     using System.Web;
  6:     using EPiServer;
  7:     using EPiServer.Core;
  8:     using EPiServer.SpecializedProperties;
  9:     using EPiServer.Web;
 10: 
 11:     public static class WebUrlHelper
 12:     {
 13:         public static string BuildLinkHtml(PageReference pageReference, string text, string title = null, 
 14:             string cssClass = null, bool fullyQualified = false, bool newWindow = false)
 15:         {
 16:             string linkUrl = "#";
 17: 
 18:             if (!PageReference.IsNullOrEmpty(pageReference))
 19:             {
 20:                 PageData pageData = DataFactory.Instance.GetPage(pageReference);
 21:                 PropertyFrame propertyFrame = pageData.Property["PageTargetFrame"] as PropertyFrame;
 22: 
 23:                 if (!newWindow && !string.IsNullOrEmpty(propertyFrame.FrameName) && 
 24:                     string.Equals(propertyFrame.FrameName, "_blank", StringComparison.OrdinalIgnoreCase))
 25:                 {
 26:                     newWindow = true;
 27:                 }
 28: 
 29:                 linkUrl = GetPageUrl(pageData, fullyQualified).ToString();
 30:             }
 31: 
 32:             return BuildLinkHtml(linkUrl, text, title, cssClass, newWindow);
 33:         }
 34: 
 35:         public static string BuildLinkHtml(string linkUrl, string text, string title = null, 
 36:             string cssClass = null, bool newWindow = false)
 37:         {
 38:             if (!string.IsNullOrEmpty(title))
 39:                 title = string.Format(" title=\"{0}\"", title);
 40: 
 41:             if (!string.IsNullOrEmpty(cssClass))
 42:                 cssClass = string.Format(" class=\"{0}\"", cssClass);
 43: 
 44:             return string.Format("<a href=\"{0}\"{1}{2}{3}>{4}</a>",
 45:                 linkUrl,
 46:                 cssClass,
 47:                 title,
 48:                 newWindow ? " target=\"_blank\"" : string.Empty,
 49:                 text);
 50:         }
 51: 
 52:         public static Uri GetPageUrl(PageData pageData, bool fullyQualified = false)
 53:         {
 54:             PageShortcutType propertyLinkType = (PageShortcutType)Enum.Parse(typeof(PageShortcutType), pageData.Property["PageShortcutType"].ToString());
 55: 
 56:             UrlBuilder url = new UrlBuilder(pageData.LinkURL);
 57:             bool getPageUrl = true;
 58:             bool changeHostAndScheme = true;
 59: 
 60:             if (propertyLinkType == PageShortcutType.Shortcut && 
 61:                 pageData.LinkURL.IndexOf("id=", StringComparison.OrdinalIgnoreCase) != -1)
 62:             {
 63:                 string id = pageData.LinkURL.Substring(pageData.LinkURL.IndexOf("id=", StringComparison.OrdinalIgnoreCase) + 3);
 64: 
 65:                 if (id.Contains("&"))
 66:                     id = id.Substring(0, id.IndexOf("&", StringComparison.OrdinalIgnoreCase));
 67: 
 68:                 int pageId;
 69: 
 70:                 if (int.TryParse(id, out pageId))
 71:                 {
 72:                     pageData = DataFactory.Instance.GetPage(new PageReference(pageId));
 73:                     url = new UrlBuilder(pageData.LinkURL);
 74:                 }
 75:             }
 76: 
 77:             if (propertyLinkType == PageShortcutType.External)
 78:             {
 79:                 getPageUrl = false;
 80:                 changeHostAndScheme = false;
 81:             }
 82: 
 83:             if (UrlRewriteProvider.IsFurlEnabled && getPageUrl)
 84:                 Global.UrlRewriteProvider.ConvertToExternal(url, pageData.PageLink, Encoding.UTF8);
 85: 
 86:             if (changeHostAndScheme && fullyQualified && HttpContext.Current != null)
 87:             {
 88:                 url.Host = HttpContext.Current.Request.Url.Host;
 89:                 url.Scheme = HttpContext.Current.Request.Url.Scheme;
 90:             }
 91: 
 92:             return url.Uri;
 93:         }
 94:     }
 95: }

There are two BuildLinkHtml methods that can be called and also a GetPageUrl method.

Hopefully this will prove of some use to other people

Feedback

As always feedback is greatly appreciated. Just twitter me @croweman or send me an email.

ElencySolutions.MultipleProperty v1.6.1 Released

Fri, 03 Aug 2012 15:03:51 GMT

A new version of MultipleProperty has now been released .

New Minor Features

Edit captions will now be used in error messages rather than property names. In previous versions if there was a property named “ImageGalleries” collection with an ImageGallery entity having a property named “Gallery name”. The error message would have referred to the property name as “ImageGalleries_GalleryName” where as now edit captions will be used so they will appear like this “Image galleries – Gallery name”.
A new setting has been added to the multiple property configuration to allow asterix’s that appear next to the label text for required fields to be hidden. This setting is named “showAsterixForRequiredFields” and it’s default value is true.

Installation

The easiest way to install the assembly is by installing it from the EPiServer nuget feed (once it has been made available). But if you are not down with the cool kids you can download it from codeplex. The assembly is built for EPiServer CMS 6 and onwards.

On the codeplex site you will also find some useful documentation and example code to get you familiar with what the property offers. The example code is dependent on PageTypeBuilder.

Feedback

As always feedback is greatly appreciated, if you have any suggestions for new features or changes I am happy to hear them.

Just twitter me @croweman or send me an email.

ElencySolutions.MultipleProperty v1.6 Released

Tue, 26 Jun 2012 17:29:16 GMT

A new version of my multiple property assembly is now available.

New Features

You are now able to add custom validation to singular or collection based entity properties.

Making use of the new validation functionality

Two new virtual methods have been added to the MultiplePropertyBase class. These methods are named ValidateEntity and ValidateEntities. Example validation code is below:

public class PropertyGalleryImages : MultiplePropertyBase<GalleryImages, GalleryImage>
{
     public override string ValidateEntity(GalleryImage entity)
     {
         if (entity == null)
             return string.Empty;
         if (!entity.LinkUrl.StartsWith("http"))
            return "A link URL must start with http";
     }
 }

public class PropertyGalleryImages : MultiplePropertyBase<GalleryImages, GalleryImage>
{
     public override string ValidateEntities(GalleryImages entities)
     {
         if (entities == null)
             return string.Empty;
         StringBuilder errorMessage = new StringBuilder();
         for (int i = 0; i < entities.Count; i++)
         {
            GalleryImage galleryImage = entities[i];
            if (!galleryImage.LinkUrl.StartsWith("http"))
               errorMessage.AppendFormat("Item {0} link url is invalid, ", i + 1);
         }
		  
         return errorMessage.ToString().TrimEnd(“, “);
      }
 }

Installation

On the codeplex site you can also find some useful documentation and example code to get you familiar with what the property offers. The example code is dependent on PageTypeBuilder.

Feedback

As always feedback is greatly appreciated, if you have any suggestions for new features or changes I am happy to hear them.

Just twitter me @croweman or send me an email.

ElencySolutions.MultipleProperty v1.5.1 Released

Tue, 01 May 2012 09:59:16 GMT

A few days ago I released a new version of my multiple property assembly. The previous version basically allowed you to set a default value for properties and also added some functionality which enabled you to turn on and off various list based buttons such as edit, delete etc. The button toggling changes came about because of some customizations a colleague of mine had to make for a client.

Unfortunately I made some assumptions about what he was trying to do and didn’t give him what he wanted (note to self do some requirements gathering up front). So I give you v1.5.1.

New Features/Bug Fixes

Copy as new button will no longer allow you to add more items to the list than the set maximum number of items.
New IMultiplePropertyEntityAbilityOverride interface.
New IMultiplePropertyEntityCollectionAbilityOverride interface.

Making use of the new ability override interfaces

You’re entity classes can now implement the IMultiplePropertyEntityAbilityOverride interface. The interface has the following methods:

- bool AllowEdit(PageData pageData, string propertyName);
- bool AllowDelete(PageData pageData, string propertyName);

Within your entity you can then define any custom logic to determine whether the edit and delete buttons can be enabled.

For entity collections List<TEntity> you can implement the IMultiplePropertyEntityCollectionAbilityOverride interface. This interface has the following methods:

- bool AllowAdd(PageData pageData, string propertyName);
- bool AllowEdit(PageData pageData, string propertyName);
- bool AllowDelete(PageData pageData, string propertyName);

This enables you to define custom logic to determine whether add, edit or delete functionality should be enabled across the whole list rather than an individual entity level.

Installation

On the codeplex site you can also find some useful documentation and example code to get you familiar with what the property offers. The example code is dependent on PageTypeBuilder.

Feedback

As always feedback is greatly appreciated, if you have any suggestions for new features or changes I am happy to hear them.

Just twitter me @croweman or send me an email

ElencySolutions.MultipleProperty v1.5 Released

Thu, 26 Apr 2012 17:12:25 GMT

For more information about the multiple property assembly please refer to codeplex. There you will find various links to previous posts, documentation, downloads and examples.

New Features

Some new properties have been added to the MultiplePropertyEntityAttribute:

- AllowAdd
- AllowEdit
- AllowDelete
- AllowSort

These new properties allow you to turn on/off various buttons and functionality in list mode. The default for all of these properties is true.

A new property has been added to the MultiplePropertyEntityPropertyAttribute.

- DefaultValue: This property allows you to define a default value for the property.

Installation

On the codeplex site you can also find some useful documentation and example code to get you familiar with what the property offers. The example code is dependent on PageTypeBuilder.

Feedback

As always feedback is greatly appreciated, if you have any suggestions for new features or changes I am happy to hear them.

Just twitter me @croweman or send me an email Smile

EPiServer Schedule Job Maintenance EPiServer CMS 6

Thu, 26 Apr 2012 16:08:01 GMT

In the past I have been plagued with issues where EPiServer scheduled jobs have suddenly stopped working and get stuck in a running state. This is possibly caused by application restarts/redeployments while jobs are in progress and many other issues.

I am pretty sure these particular issues may well have been fixed in hotfixes or service packs, but from past experience I have become very cautious about scheduled jobs and there reliability especially if you are using them for site critical functionality.

Because of my scepticism about scheduled job reliability I have knocked together a class which should get a job up and running if it gets stuck in a running state.

My Solution

Firstly you will have to download this class ScheduledJobMaintenance.cs and add it to your solution.

You will then need to hook into the begin request method within your Global.asax.cs file and add a call to ScheduledJobMaintenance.CheckScheduledJobs().

  1: protected void Application_BeginRequest(object sender, EventArgs e)
  2: {
  3:    ScheduledJobMaintenance.CheckScheduledJobs();
  4: }

The ScheduleJobMaintenance class has the following static properties:

MaximumJobRunTimeInMinutes – This defines the maximum length of time a job can be in a running state, the default is 60 minutes.
CheckTimeInMinutes – This defines the duration in minutes running jobs should be checked, the default is 11 minutes don’t ask me why .

What does it do?

Every time a request is made to the site the CheckScheduledJobs method will be called. This will then check the last time a check was made, if the duration has gone over the CheckTimeInMinutes then it will do the following:

Queue a new thread.
Check if there are any jobs in a running state that have gone over the maximum job running time.
If there are jobs that have met the previous condition then it will set the next execution time to be in the future, the way this is set is determined by the IntervalType.
Update the relevant rows in the tblScheduledItem table to turn them into runnable jobs again.
Update the last check time.

For info this currently does not fix jobs that have IntervalType’s of Years or Seconds.

PageTypeBuilder and EPiServer CMS 6 R2 Synching Issues – Important

Mon, 23 Apr 2012 11:01:32 GMT

Background

There have been a couple of issues that have been logged on codeplex to do with long start up times and default values not being set on page definition properties, the links to the issues are below:

- After upgrading to PTB 2.0, starting site takes a really long time

- Default value is not set

Basically there was a change in CMS 6 R2 which changed how sort orders are handled. When PageTypeBuilder is synching it will compare whether the page definition is different to the one stored in the database and if so it will update it.

In CMS 6 R2 a new method is now called named EnsureUniqueFieldOrder within the Save method of the PageDefinition.

At a high level this method does the following:

Checks whether the sort order for the current page definition matches the sort order of any other page definitions for the page type and if it does it will set a new value for it.
If a sort order has not been defined and there are existing page definitions it will get the highest sort order and add 1 to it.

This then has a potentially huge knock on effect because the next time the application starts PageTypeBuilder will go off and work it’s magic, but because the EnsureUniqueFieldOrder method has changed some of the sort orders, PageTypeBuilder will determine that the page definitions are different and update the definitions again .

So to put simply this is not a bug in PageTypeBuilder or EPiServer it’s just a unfortunate side effect of not defining your Sort Order's in your page types or specifying duplicates. Over time we often have many common base classes that page types will inherit from and can often be a case for many duplicates.

Introducing PageTypeBuilder.SortOrderChecker

Some of you may be aware that I spend a lot of time commuting to and from London town and that I like to fill this time with knocking together useful modules and applications.

So last week to fill this time I decided to knock together a little console application which will scan a bin folder and tell you which page types have duplicate and undefined properties.

It can also fix all of the page type files for you (assuming you are programming in C#) and apply new sort orders for various property definitions including property groups. The fixing code will also fix sorting on page type and property group base classes too to ensure there are no duplicates.

Using PageTypeBuilder.SortOrderChecker

Firstly you will need to Download the executable and it’s config file from here and dump it in a folder on your machine. Then you need to follow the steps below:

1. Re-build your application to make sure all of your assemblies are up to date.
2. Backup any relevant EPiServer databases and source files

3. Then you can execute the tool with the following arguments to determine which properties have duplicate or undefined sort orders.

c:\Tools\PageTypeBuilder.SortOrderChecker.exe -t:0 -b:c:\episerver\sites\pagetypebuildertest\bin

You will be shown a window like the following:

4. You can then attempt to fix your page types by running the following command, please note you may need to close visual studio first just in case there are any file locks.

c:\Tools\PageTypeBuilder.SortOrderChecker.exe -t:2 -b:c:\episerver\sites\pagetypebuildertest\bin -p:c:\episerver\sites\pagetypebuildertest

You will be shown a window like the following:

5. Now that your files have been fixed, you will need to rebuild the solution. It may be possible that some classes/properties will not be updated, but this would probably be because of bad coding style, not by me of course

Now we have rebuilt we can run the tool again to check for duplicates and unassigned sort orders.

c:\Tools\PageTypeBuilder.SortOrderChecker.exe -t:0 -b:c:\episerver\sites\pagetypebuildertest\bin

This time you will hopefully be told that all duplicates and unassigned sort orders are no more .

6. One thing to be aware of is that as EPiServer has done it’s own thing for duplicate and undefined sort orders, it may still be likely that are some duplicates even though there are none in code.

To get round this you can run the tool again with the following commands.

c:\Tools\PageTypeBuilder.SortOrderChecker.exe -t:3 -b:c:\episerver\sites\pagetypebuildertest\bin -o:c:\temp\ResetSortOrders.sql

This will create a .sql file with the necessary SQL to reset all PageTypeBuilder Property Definition sort orders to 0, so you will need to execute the SQL against your database.

7. Now that sort orders have been reset you can run your application.

If you have a large number of page types and page definitions this initial update may take a bit longer than expected, but once this initial update is complete all future deployments/application restarts should be much quicker .

Checking Sort Orders on post build event

You can hook the sort order checking executable into your application build by calling it on a post build event, it's not particularly elegant but will fail the build if there are duplicate or undefined sort orders and will output duplications and undefined properties on page types to the output window.

Command for post build:

c:\Tools\PageTypeBuilder.SortOrderChecker.exe -t:1 -b:$(TargetDir)

Disclaimer

Although I have done testing around this there could be possible side effects. I take no responsibility for any adverse affects. So basically use at your own risk and backup your database and source code first.

Feedback

Please feel free to email or twitter me with any feedback @croweman

PageTypeBuilder v2.0 – Property Groups and Dynamic Properties

Mon, 19 Mar 2012 11:16:20 GMT

Some of you may have read Joel’s post on Working with Dynamic Properties and Page Type Builder but if not you may want to check the article .

The other day somebody asked me whether there was a nice solution to using property groups in a dynamic property kind of way as explained in Joel’s article.

This got my mind working a bit and although the solution I have knocked together is not particularly nice as it uses quite a bit of reflection it seems to do the job .

The Solution

Step One

Firstly you will need to download the PropertyGroupExtensions.cs class I have knocked together from here and add it to your solution.

The class contains an extension method for classes that inherit TypedPageData. The method is named GetPropertyGroupDynamicProperty.

Step Two

In this example I am going to demonstrate having an Image Property Group, the code definition is below. You will notice that the class implements IPropertyGroupComparer. This interface contains an IsNull method which you must implement to determine whether you would class the property group as being null or empty.

  1: public class Image : PageTypePropertyGroup, IPropertyGroupComparer
  2: {
  3: 
  4:     [PageTypeProperty(
  5:         EditCaption = "Image url", 
  6:         Type = typeof(PropertyImageUrl),
  7:         SortOrder = 100)]
  8:     public virtual string ImageUrl { get; set; }
  9: 
 10:     [PageTypeProperty(
 11:         EditCaption = "Alternative text", 
 12:         Type = typeof(PropertyString),
 13:         SortOrder = 110)]
 14:     public virtual string AltText { get; set; }
 15: 
 16:     public string GetHtml()
 17:     {
 18:         return string.IsNullOrEmpty(ImageUrl) ? string.Empty 
 19:             : string.Format("<img src=\"{0}\" alt=\"{1}\" />", ImageUrl, AltText);
 20:     }
 21: 
 22:     public bool IsNull()
 23:     {
 24:         return string.IsNullOrEmpty(ImageUrl) &&
 25:                 string.IsNullOrEmpty(AltText);
 26:     }
 27: }

Step Three

Now we have our property group defined. I shall add the property to my CommonPageTypeBase class. This is a class that inherits TypedPageData but also is used s a base class to all page types. So any properties that are added to this class will be available on all page types.

  1: public class CommonPageTypeBase : TypedPageData
  2: {
  3:     [PageTypePropertyGroup(
  4:         EditCaptionPrefix = "Header image dynamic property - ", 
  5:         StartSortOrderFrom = 150)]
  6:     public virtual Image HeaderImageDynamicProperty
  7:     {
  8:         get
  9:         {
 10:             return this.GetPropertyGroupDynamicProperty<CommonPageTypeBase, Image>
 11:                 (p => p.HeaderImageDynamicProperty);
 12:         }
 13:         set
 14:         {
 15:             // do nothing, this has to be implemented
 16:         }
 17:     }
 18: }

You can see in the class definition above that we have added a property group definition named HeaderImageDynamicProperty.

You will also noticed I have implemented the get and set methods.

The get method implementation calls the GetPropertyGroupDynamicProperty extension method with two Generic type parameters. The first one is a class that inherits TypedPageData, where as the second is a class that implements PageTypePropertyGroup and IPropertyGroupComparer.

When the get method is called it will basically go up the page hierarchy until it reaches the start page or finds a populated Image property group.

Feedback

As always feedback is greatly appreciated, if you have found any bugs or have any suggestions of improvement please let me know.

Just twitter me @croweman or send me an email

ElencySolutions.MultipleProperty v1.4 Released

Thu, 15 Mar 2012 13:39:54 GMT

For those of you who are interested but don’t know what ElencySolutions.MultipleProperty is, please refer to the documentation and various articles listed on codeplex.

I have recently had a couple of requests for some minor new features and during an unusually thorough testing phase I have come across a few bugs which have been fixed in this version.

Release Notes

When using list based properties, a copy button can be added to allow an editor to copy an existing item.
There are now some configuration settings that can be defined to set defaults for whether the copy property button and copy list item buttons should appear.
MultiplePropertyBase is now Serializable
There was a bug when using link item collections where the state of the list was not being maintained during post backs which is now fixed.
There was a bug when editing a multiple property list with child multiple property lists. When you edit one then click the add new button, the new item contained child list items from the previously edited item.

Installation

The easiest way to install the assembly is by installing it from the EPiServer nuget feed. But if you are not down with the cool kids you can download it from codeplex. The assembly is built for EPiServer CMS 6 and onwards.

On the codeplex site you can also find some useful documentation and example code to get you familiar with what the property offers. The example code is dependent on PageTypeBuilder.

New Configuration settings

There is now a configuration section you can add to your web.config to set some default values for the MultiplePropertyEntityAttribute properties. The configuration section is not required and when installing via nuget the configuration will be added for you.

  1: <configuration>
  2:   <configSections>
  3:     <section name="elencysolutions.multipleproperty" type="ElencySolutions.MultipleProperty.Configuration.MultiplePropertyConfiguration, ElencySolutions.MultipleProperty"/>
  4:   </configSections>
  5:   <elencysolutions.multipleproperty copyAsNewDefault="true" allowPropertyCopyingDefault="true" />
  6: </configuration

The image below shows a custom image gallery property built using multiple property.

Feedback

As always feedback is greatly appreciated, if you have any suggestions for new features or changes I am happy to hear them.

Just twitter me @croweman or send me an email

PageTypeBuilderUI v2.0 Released

Thu, 22 Dec 2011 11:29:50 GMT

As PageTypeBuilder v2.0 has now been released, thank Joel , I have now made PageTypeBuilderUI v2.0 available.

PageTypeBuilderUI v2.0 contains the following new features:

Built against PageTypeBuilder v2.0
Will now show mismatches when PTB page types or page type property definitions do not appear in the EPiServer database. This is usually caused by somebody deleting a property they shouldn’t or page type updating being disabled.
Custom property group rendering which will be described in more detail below.

PageTypeBuilder v2.0 has property groups as one of it’s new features.

One of the changes I have knocked together for v2.0 of PageTypeBuilderUI is custom rendering of property groups within edit mode. I am aware Anders Hattestad has done similar things with his Itera.Objects project. But to keep my mind occupied on my daily commute I decided to implement something similar which would fit in with PageTypeBuilder’s property groups

Now lets get to the point

If I added the following code somewhere into my solution:

  1: namespace EPiServer
  2: {
  3:     using Core;
  4:     using Security;
  5:     using SpecializedProperties;
  6:     using PageTypeBuilder;
  7: 
  8:     [PageType("3905865A-3C95-4707-98B2-1F2B98E2EA46",
  9: 	    Name = "[Public] PTB Property groups",
 10: 	    Description = "PTB Property groups",
 11: 	    Filename = "~/Templates/Pages/PageName.aspx",
 12: 	    AvailableInEditMode = true)]
 13:     public class PTBPropertyGroupsPageType : TypedPageData
 14:     {
 15:         [PageTypePropertyGroup(
 16:             EditCaptionPrefix = "Image link one - ", 
 17:             Tab = typeof(FooterTab), 
 18:             StartSortOrderFrom = 100 )]
 19:         public virtual ImageLink ImageLinkOne { get; set; }
 20: 
 21:         [PageTypePropertyGroup(
 22:             EditCaptionPrefix = "Image link two - ", 
 23:             Tab = typeof(FooterTab), 
 24:             StartSortOrderFrom = 200)]
 25:         public virtual ImageLink ImageLinkTwo { get; set; }
 26: 
 27:         [PageTypePropertyGroup(
 28:             EditCaptionPrefix = "Image link three - ", 
 29:             Tab = typeof(FooterTab), 
 30:             StartSortOrderFrom = 300)]
 31:         public virtual ImageLink ImageLinkThree { get; set; }
 32: 
 33:     }
 34: 
 35:     public class ImageLink : PageTypePropertyGroup
 36:     {
 37:         [PageTypeProperty(
 38:             EditCaption = "Image url", 
 39:             Required = true, 
 40:             DisplayInEditMode = true, 
 41:             Type = typeof(PropertyImageUrl), 
 42:             Tab = typeof(TabOne),
 43:             SortOrder = 100)]
 44:         public virtual string ImageUrl { get; set; }
 45: 
 46:         [PageTypeProperty(
 47:             EditCaption = "Link url", 
 48:             DisplayInEditMode = true, 
 49:             Type = typeof(PropertyUrl),
 50:             Tab = typeof(TabTwo),
 51:             SortOrder = 110)]
 52:         public virtual string LinkUrl { get; set; }
 53: 
 54:         [PageTypeProperty(
 55:             EditCaption = "Open in new window", 
 56:             DisplayInEditMode = true, 
 57:             Type = typeof(PropertyBoolean),
 58:             Tab = typeof(TabThree),
 59:             SortOrder = 120)]
 60:         public virtual bool OpenInNewWindow { get; set; }
 61:     }
 62: 
 63:     public class FooterTab : Tab
 64:     {
 65:         public override string Name
 66:         {
 67:             get { return "Footer"; }
 68:         }
 69: 
 70:         public override AccessLevel RequiredAccess
 71:         {
 72:             get { return AccessLevel.Edit; }
 73:         }
 74: 
 75:         public override int SortIndex
 76:         {
 77:             get { return 100; }
 78:         }
 79:     }
 80: 
 81:     public class TabOne : Tab
 82:     {
 83:         public override string Name
 84:         {
 85:             get { return "Tab one"; }
 86:         }
 87: 
 88:         public override AccessLevel RequiredAccess
 89:         {
 90:             get { return AccessLevel.Edit; }
 91:         }
 92: 
 93:         public override int SortIndex
 94:         {
 95:             get { return 110; }
 96:         }
 97:     }
 98: 
 99:     public class TabTwo : Tab
100:     {
101:         public override string Name
102:         {
103:             get { return "Tab two"; }
104:         }
105: 
106:         public override AccessLevel RequiredAccess
107:         {
108:             get { return AccessLevel.Edit; }
109:         }
110: 
111:         public override int SortIndex
112:         {
113:             get { return 120; }
114:         }
115:     }
116: 
117:     public class TabThree : Tab
118:     {
119:         public override string Name
120:         {
121:             get { return "Tab three"; }
122:         }
123: 
124:         public override AccessLevel RequiredAccess
125:         {
126:             get { return AccessLevel.Administer; }
127:         }
128: 
129:         public override int SortIndex
130:         {
131:             get { return 130; }
132:         }
133:     }
134: }

I would end up with the following:

A tab named ‘Footer’ which requires Edit permissions.
A tab named ‘Tab one’ which requires Edit permissions.
A tab named ‘Tab two’ which requires Edit permissions.
A tab named ‘Tab three’ which requires Administrator permissions.
One PageType named ‘[Public] PTB Property groups’. The PageType code definition has three Image link properties which are based on an ImageLink type which inherits PageTypePropertyGroup. The following property definitions will end up being added to the page type:

When viewing in edit mode the properties will appear like this:

If you would like the properties to be rendered in a friendlier format you need to add the following settings to the web config:

  1: <?xml version="1.0" encoding="utf-8"?>
  2: <configuration>
  3:   <configSections>
  4:     <section name="pageTypeBuilderUI" type="PageTypeBuilderUI.Configuration.PageTypeBuilderUIConfiguration, PageTypeBuilderUI" />
  5:   </configSections>
  6:   <pageTypeBuilderUI enablePageTypeUpdating="true" enableCustomPropertyGroupRendering="true" />
  7: </configuration>
  8:

If I then removed the tab definitions on the PageTypePropertyAttribute’s set against the ImageLink Property group page type properties and viewed the Footer tab in edit mode you would see the properties presented in the following way:

If I then add the tabs back on to the ImageLink Property Group page type properties and checked the Footer tab in edit mode again the properties will be displayed like the following:

As the ‘Tab three’ tab requires Administrator access if I log in as a user who does not have Administrator permissions the ‘Tab three’ tab will disappear like below:

How it works

When the enablePageTypeUpdating and enableCustomPropertyGroupRendering attribute values have been set to true an initialization module will add new properties to the page type. These properties are of type PropertyGroupProperty and are responsible for the custom rendering of property group properties. The module will also set the other page type properties to not show in edit mode. It is possible to modify the custom rendering property control used by setting the full type name in the customRenderingControlType attribute.

The image below shows you what property definitions will appear on the page type when custom property group rendering is enabled.

***** Points to note *****

The custom rendering code assumes that the EditCaptionPrefix defined in the PageTypePropertyGroupAttribute will end in either a “-“ or a “:” and does a substring at this characters.

Installation

The easiest way to install PageTypeBuilderUI is to install it from the EPiServer nuget feed once it’s up there. The assembly can also be downloaded from codeplex.

Feedback

Please feel free to email or twitter me with any feedback @croweman

FilteredPageReference v1.5 Released

Fri, 09 Dec 2011 15:18:44 GMT

My colleague David Knipe asked me yesterday whether it would be possible to add search into the FilteredPageReference page picker dialog as a client had requested it.

When I initially implemented FPR I decided to remove the search but I have now made it available in v1.5.

v1.5 New Features

You can now use the search box when picking pages. Matched pages will be restricted by allowed page types and must be a descendent of the start page if one has been specified.

Installation

This version of FilteredPageReference is dependent on EPiServer CMS 6 R2. It can be installed from the EPiServer nuget feed or from codeplex. Usage instructions can be found here.

Feedback

As always feedback is greatly appreciated. Just twitter me @croweman or send me an email

ElencySolutions Image Map and Hot Spot Editor v1.1 Released

Wed, 30 Nov 2011 16:04:18 GMT

I have just released a new version of the Image Map and Hot Spot Editor I created for EPiServer CMS 6.

The main reason for the new version was to fix issues that can be caused when using EPiServer Commerce, this caused my embedded resources to not be served through my VPP providers.

Also it’s now in a nuget feed

For more information about the properties please refer to my previous blog post.

The assembly can be found on the EPiServer nuget feed and codeplex.

ElencySolutions.MultipleProperty v1.3.3 Released

Mon, 28 Nov 2011 14:51:14 GMT

It seems like I am releasing a new version of this assembly every few weeks at the moment. The reason for this is I have been using it a lot recently and I keep seeing minor little things I would like to improve . I think I have sorted everything that was niggling at me now and this may be the last release for some time, unless anybody finds any bugs that need fixing

Release Notes

When using tabs, the selected tab should now be maintained on post back. In certain circumstances the selected tab would be reset.
Access rights can now be specified for tabs.
A few styling tweaks have been made.

For those who are not in the know

This assembly provides a developer with an easy way to build custom properties that are composed of various other properties. It can also be used to create collections of composite properties.

Some of the things it allows you to easily do but by no means all are briefly summarised below:

Create custom properties that comprise of other properties.
Create lists of properties
As the Multiple property entities make use of PropertyData objects you are able to pretty much have lists within lists.
Ability to define minimum and maximum number of entities.
Ability to copy the property to another page.
Ability to display entity properties in different tabs.
Ability to programmatically set property settings.

Installation

The assembly is dependent on EPiServer CMS 6 and can be installed from the EPiServer nuget feed or downloaded from codeplex.

Usage

The easiest way to get familiar with the assembly is to download the example from codeplex and add and include the files in your alloy tech site. Very useful documentation can be found on codeplex as well.

The example is dependent on PageTypeBuilder and contains 2 pages types, an image gallery page type and an image galleries page type.

ElencySolutions.MultipleProperty is not a replacement for EPiImage, this example just demonstrates how you could use it to create an image gallery, but you could create anything you like with it .

Pretty Pictures (for those who don’t like reading )

Image Gallery

Below are some images showing you what you would see if you used the non list based Image Gallery.

Image Galleries

Below are some pictures showing you what you would see if you used the list of image gallery entities property.

The image below demonstrates how you can make use of the property copying functionality.

Feedback

As always feedback is greatly appreciated, how many people are actively using this project within there EPiServer 6 solutions?

Also, if you have any suggestions for new features or changes I am happy to hear them.

Just twitter me @croweman or send me an email

FilteredPageReference v1.4.1 Released

Sat, 19 Nov 2011 11:28:40 GMT

A new version of FilteredPageReference has now been released which contains the following bug fixes and changes:

There was a bug when using the delegate to override allowed page type settings which has been fixed.
In previous versions if using PageTypeBuilder, all assemblies and types were scanned to find relevant page types and interfaces. You now have to specify valid assembly and full type name prefixes in the web.config, these configuration property values should be semi colon delimited. Configuration example is shown below:

  1: <configuration>
  2:   <configSections>
  3:     <section name="filteredPageReference" type="FilteredPageReference.Configuration.FilteredPageReferenceConfiguration, FilteredPageReference" />
  4:   </configSections>
  5:   <filteredPageReference validAssemblyNamePrefixes="EPiServer.Templates.AlloyTech;" validFullTypeNamePrefixes="EPiServer.TeamMeetingDemo;" />
  6: </configuration>

Installation

This version of FilteredPageReference is dependent on EPiServer CMS 6 R2. It can be installed from the EPiServer nuget feed or from codeplex. Usage instructions can be found here.

ElencySolutions.MultipleProperty v1.3.2 Released

Wed, 16 Nov 2011 12:26:15 GMT

For anyone who is currently using my MultipleProperty assembly, a new version has been released today which fixes the following minor bug:

When a user edits a page property and one of the MultipleProperty Edit or Delete buttons is clicked or the sort order is changed using drag and drop an alert was shown to to user asking whether they want to leave the page.

This update can be retrieved from the EPiServer nuget feed or codeplex.

For more information on the MultipleProperty assembly please refer to my previous blog posts or use codeplex as a useful point of reference. It contains documentation, links to blog posts and code examples.

ElencySolutions.MultipleProperty v1.3.1 Released

Fri, 04 Nov 2011 10:35:57 GMT

For those of you who are not using ElencySolutions.MultipleProperty in their projects please refer back to previous blog posts and the usage instructions linked to on codeplex to see how it could help you out.

Some of the things it allows you to easily do but by no means all are briefly summarised below:

Create custom properties that comprise of other properties.
Create lists of properties
As the Multiple property entities make use of PropertyData objects you are able to pretty much have lists within lists.
Ability to define minimum and maximum number of entities.
Ability to copy the property to another page.
Ability to display entity properties in different tabs.

What’s new in v1.3.1

Those of you who keep an eye on World will probably be wondering why I have released another version already considering I released v1.3 two days ago.

Well, it’s not because there were bugs in v1.3 (as far as I am aware). It’s because one of my colleagues wanted to do some additional things with property settings which the previous versions didn’t offer. More specifically she had a property which was essentially a list of FilteredPageReference properties and she wanted to use the list based property on various page types but wanted to restrict the page types that could be picked differently depending on the page type. She wanted to do this by modifying the filtered page reference settings for the page type property through admin mode..

So as I have plenty of time on the train, I thought I would extend the MultipleProperty offering to cater for her needs and as we are using the FilteredPageReference and MultipleProperty properties more and more I thought it would prove quite useful.

New features are summarised below:

A minimum number of entities can now be defined on a list of entities. If the number of minimum enters have not been added then the page will not be able to be saved.
There are now three ways of setting property settings on an entity property. Well if we are being picky two of them are pretty much the same but I wanted the solution to be backwards compatible.

Installation and Setup

ElencySolutions.MultipleProperty has been built to work with EPiServer CMS 6 and onwards. Advanced usage instructions (which are definately worth having a read of) as well as examples can be found on codeplex. The usage instructions also has an FAQ section which could prove quite handy.

The easiest way to install the assembly is to download the latest nuget feed from nuget.episerver.com.

The site on codeplex will also provide useful links for all blog posts that have been posted related to ElencySolutionsMultipleProperty.

Making use of MultipleProperty Entity PropertyData property settings

You are able to define property settings for a Property Control by setting the PropertySettingsCreator property within the MultiplePropertyEntityProperty attribute class.

The value of this property needs to be a type that implements IMultiplePropertySettingsCreator or IMultiplePropertySettingsCreatorAdvanced.

You are now also able to set the UseMatchingSettingsDecoratedOnPropertyType boolean property within the MultiplePropertyEntityProperty attribute class. If the value of the property is set to true then the relevant settings if found will be taken from the ones defined on the physical page type page definition property.

Code Examples

The code below demonstrate how to define property settings for a PropertyHtmlString property using both the IMultiplePropertySettingsCreator and IMultiplePropertySettingsCreatorAdvanced interfaces.

You will notice that for the WYSIWYGAlternative property it uses a property settings creator based on IMultipleSettingsCreatorAdvanced. This is a new interface for v1.3.1 and the implementation needs to have a method named CreatePropertySettings which accepts a page type id and property name parameter. This method allows you to conditionally based on the parameters create or load different property settings. You will also notice that the implementation of this method calls MultiplePropertyHelper.GetPropertySettings which allows you to retrieve property setting that have been defined on a property data instance of a page data object created from a specific page type.

  1: [Serializable]
  2: [DataContract]
  3: [KnownType(typeof(CustomProperty))]
  4: [MultiplePropertyEntity]
  5: public class CustomProperty
  6: {
  7:     public override string ToString()
  8:     {
  9:         return MultiplePropertyHelper.SerializeObject(this);
 10:     }
 11: 
 12:     [MultiplePropertyEntityProperty(Caption = "What you see is what you get",
 13:         Type = typeof(PropertyXhtmlString),
 14:         SortIndex = 100,
 15:         PropertySettingsCreator = typeof(WYSIWYGPropertySettingsCreator))]
 16:     [DataMember]
 17:     public string WYSIWYG { get; set; }
 18: 
 19:     [MultiplePropertyEntityProperty(Caption = "What you see is what you get alternative",
 20:         Type = typeof(PropertyXhtmlString),
 21:         SortIndex = 100,
 22:         PropertySettingsCreator = typeof(WYSIWYGPropertySettingsCreatorAdvanced))]
 23:     [DataMember]
 24:     public string WYSIWYGAlternative { get; set; }
 25: }
 26: 
 27: public class WYSIWYGPropertySettingsCreator : IMultiplePropertySettingsCreator
 28: {
 29:     public IPropertySettings CreatePropertySettings()
 30:     {
 31:         TinyMCESettings settings = new TinyMCESettings().GetDefaultValues() as TinyMCESettings;
 32:         settings.ToolbarRows.Clear();
 33:         return settings;
 34:     }
 35: }
 36: 
 37: public class WYSIWYGPropertySettingsCreatorAdvanced : IMultiplePropertySettingsCreatorAdvanced
 38: {
 39:     public IPropertySettings CreatePropertySettings(int pageTypeId, string propertyName)
 40:     {
 41:         TinyMCESettings settings = new TinyMCESettings().GetDefaultValues() as TinyMCESettings;
 42: 
 43:         if (pageTypeId == 33 && string.Equals(propertyName, "MyCustomProperty_WYWIWYG"))
 44:         {
 45:             settings.ToolbarRows.Clear();
 46:         }
 47:         else if (pageTypeId == 34 && string.Equals(propertyName, "MyCustomProperty_WYWIWYG2"))
 48:         {
 49:             // get the settings from a property defined on a page type
 50:             PageData settingsPage = DataFactory.Instance.GetChildren(PageReference.RootPage)
 51:                 .Where(current => string.Equals(current.PageTypeName, "Settings Page Type"))
 52:                 .FirstOrDefault();
 53: 
 54:             if (settingsPage != null)
 55:                 settings = (TinyMCESettings)MultiplePropertyHelper.GetPropertySettings(settingsPage.Property["SomeProperty"], typeof(TinyMCESettings));
 56:         }
 57: 
 58:         return settings;
 59:     }
 60: }

The following example will demonstrate how you could make use of settings that have been applied to a property definition belonging to a page type and edited through admin mode.

You will notice that the UseMatchingSettingsDecoratedOnPropertyType boolean property of the MultiplePropertyEntityPropertyAttribute is set to true.

In this example as the property control is a PropertyXhtmlString the code will look for TincyMCESettings that have been set on the property definition and if there are any it will apply the to the entity property.

  1: [Serializable]
  2: [PageDefinitionTypePlugIn(DisplayName = "PropertyCustomPropertyTwo", Description = "A custom property")]
  3: [PropertySettings(typeof(TinyMCESettings), true)]
  4: public class PropertyCustomPropertyTwo: MultiplePropertyBase<CustomPropertyTwo, CustomPropertyTwo>
  5: {
  6:     public override void CreateDefaultViewControls(Web.PropertyControls.PropertyDataControl control)
  7:     {
  8:         if (Value == null)
  9:             return;
 10: 
 11:         Gallery galleryControl = control.Page.LoadControl("~/MultiplePropertyExample/Units/Gallery.ascx") as Gallery;
 12:         galleryControl.PopulateControl(Value as ImageGallery);
 13:         control.Controls.Add(galleryControl);
 14:     }
 15: }
 16: 
 17: [Serializable]
 18: [DataContract]
 19: [KnownType(typeof(CustomPropertyTwo))]
 20: [MultiplePropertyEntity]
 21: public class CustomPropertyTwo
 22: {
 23:     public override string ToString()
 24:     {
 25:         return MultiplePropertyHelper.SerializeObject(this);
 26:     }
 27: 
 28:     [MultiplePropertyEntityProperty(Caption = "What you see is what you get",
 29:         Type = typeof(PropertyXhtmlString),
 30:         SortIndex = 100,
 31:         UseMatchingSettingsDecoratedOnPropertyType = true)]
 32:     [DataMember]
 33:     public string WYSIWYG { get; set; }
 34: }

Feedback

As always feedback is greatly appreciated, how many people are actively using this project within there EPiServer 6 solutions?

Also, if you have any suggestions for new features or changes I am happy to hear them.

Just twitter me @croweman or send me an email

Blog posts by Lee Crowe

Content search and replace

ElencySolutions.MultipleProperty v1.6.3 Released

New Features

Installation

Feedback

ElencySolutions.MultipleProperty v1.6.2.1 Released

Installation

Feedback

ElencySolutions.MultipleProperty v1.6.2 Released

Background for the v1.6.2 Release

All Fixes in v1.6.2

Further information around MultipleProperty and VPP images

Installation

Feedback

Building Hyperlinks in EPiServer

Feedback

ElencySolutions.MultipleProperty v1.6.1 Released

New Minor Features

Installation

Feedback

ElencySolutions.MultipleProperty v1.6 Released

New Features

Making use of the new validation functionality

Installation

Feedback

ElencySolutions.MultipleProperty v1.5.1 Released

New Features/Bug Fixes

Making use of the new ability override interfaces

Installation

Feedback

ElencySolutions.MultipleProperty v1.5 Released

Installation

Feedback

EPiServer Schedule Job Maintenance EPiServer CMS 6

My Solution

What does it do?

PageTypeBuilder and EPiServer CMS 6 R2 Synching Issues – Important

Background

Introducing PageTypeBuilder.SortOrderChecker

Using PageTypeBuilder.SortOrderChecker

Checking Sort Orders on post build event

Disclaimer Although I have done testing around this there could be possible side effects. I take no responsibility for any adverse affects. So basically use at your own risk and backup your database and source code first.

Feedback

PageTypeBuilder v2.0 – Property Groups and Dynamic Properties

The Solution

Step One

Step Two

Step Three

Feedback

ElencySolutions.MultipleProperty v1.4 Released

Release Notes

Installation

New Configuration settings

The image below shows a custom image gallery property built using multiple property.

Feedback

PageTypeBuilderUI v2.0 Released

Now lets get to the point

How it works

Installation

Feedback

FilteredPageReference v1.5 Released

v1.5 New Features

Installation

Feedback

ElencySolutions Image Map and Hot Spot Editor v1.1 Released

ElencySolutions.MultipleProperty v1.3.3 Released

Release Notes

For those who are not in the know

Installation

Usage

Pretty Pictures (for those who don’t like reading )

Feedback

FilteredPageReference v1.4.1 Released

Installation

ElencySolutions.MultipleProperty v1.3.2 Released

ElencySolutions.MultipleProperty v1.3.1 Released

What’s new in v1.3.1

Installation and Setup

Making use of MultipleProperty Entity PropertyData property settings

Disclaimer

Although I have done testing around this there could be possible side effects. I take no responsibility for any adverse affects. So basically use at your own risk and backup your database and source code first.