Views: 3366
Number of votes: 0
Average rating:

ElencySolutions.MultipleProperty v1.6.2 Released

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 Sad smile.

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

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.

    (By Ian Causton , 02 October 2012 12:20, Permanent link)

    Legendary business! Thank you for the fixes!

    (By Erik Nordin Wahlberg , 02 October 2012 13:24, Permanent link)

    If you add an image/page to an XHTML-string then you get the delete-warning aswell, so you can probably get that function to work with your property to. I have no idea how though.. :)

    (By Steve Celius , 04 October 2012 20:10, Permanent link)

    Have a look at the IReferenceMap interface. Here is a good start:
    http://marekblotny.blogspot.no/2009/02/episerver-outgoing-links.html

    It might help.

  Please login to post a comment