Vulnerability in EPiServer.Forms

Try our conversational search powered by Generative AI!

Anders Hattestad
Apr 26, 2010
  10006
(0 votes)

Itera.MultiProperty and CMS 6

I tried to take the current Itera.MultiProperty project and recompile it with the CMS 6. It compiled without errors. But when you use it it throws and error complains about Multiple custom attributes of the same type found

The error is caused by some of the properties that are tagged with a

[GuiPlugIn(SortIndex = 70,DisplayName="Sort")]
public class PropertyFilterSort : PropertySortOrder, IHavePageCollectionFilter
{

and PropertySortOrder are tagged with

[Serializable, PageDefinitionTypePlugIn]
public class PropertyFileSortOrder : PropertyNumber
{

 
The old CMS 5 public static PlugInDescriptor Load(Type plugin) get the attributes with this line
descriptor = Load(plugin.ToString(), 
plugin.Assembly.GetName().Name);
but the new CMS 6 public static PlugInDescriptor Load(Type plugin) starts to get the attribute with this line:
customAttribute = Attribute.GetCustomAttribute(
plugin,
typeof(PlugInAttribute)
) as PlugInAttribute;

Since GuiPlugIn and PageDefinitionTypePlugIn inherits from PlugInAttributes the latest get two attributes….

The quick fix is to remove

List/Filters/PropertyFilterSort.cs

and remove PageDefinitionTypePlugIn from List/PropertyIteraPagesSelector.cs

from the project and recompile.

 

The problem is of course that old code depending on that it’s possible to have 2 different plugin attributes will not work.

Apr 26, 2010

Comments

Sep 21, 2010 10:33 AM

And the full code is

CMS6:
public static PlugInDescriptor Load(Type plugin)
{
PlugInDescriptor descriptor;
if (plugin.Namespace == "ASP")
{
descriptor = new PlugInDescriptor(-1, plugin.ToString(), plugin.Assembly.GetName().Name, true);
descriptor.IsAutoGenerated = true;
return descriptor;
}
string key = "PlugInDescriptor." + plugin.FullName;
descriptor = CacheManager.Get(key) as PlugInDescriptor;
if (descriptor == null)
{
PlugInAttribute customAttribute = Attribute.GetCustomAttribute(plugin, typeof(PlugInAttribute)) as PlugInAttribute;
if (customAttribute != null)
{
descriptor = Load(plugin.ToString(), plugin.Assembly.GetName().Name, customAttribute.DefaultEnabled);
}
else
{
descriptor = Load(plugin.ToString(), plugin.Assembly.GetName().Name);
}
CacheManager.Add(key, descriptor);
}
return descriptor;
}




CMS 5:
public static PlugInDescriptor Load(Type plugin)
{
PlugInDescriptor descriptor;
if (plugin.Namespace == "ASP")
{
descriptor = new PlugInDescriptor(-1, plugin.ToString(), plugin.Assembly.GetName().Name, true);
descriptor.IsAutoGenerated = true;
return descriptor;
}
string key = "PlugInDescriptor." + plugin.FullName;
descriptor = CacheManager.Get(key) as PlugInDescriptor;
if (descriptor == null)
{
descriptor = Load(plugin.ToString(), plugin.Assembly.GetName().Name);
CacheManager.Add(key, descriptor);
}
return descriptor;
}
/ Anders Hattestad

Sep 21, 2010 10:33 AM

added and remove PageDefinitionTypePlugIn from List/PropertyIteraPagesSelector.cs
/ Anders Hattestad

Sep 21, 2010 10:33 AM

Have registered this as an bug
/ Anders Hattestad

Juan Londono
Juan Londono Aug 15, 2011 05:58 PM

Hi Anders.
The Itera.multiproperty is throwing and warning message on a PropertyMulitBase when adding multiple items:
"are you sure you want to navigate from this page?"

I added the following code to the method PropertyMulitBaseControl.AddButton(...)

Button add = new Button();
ScriptManager current = ScriptManager.Current;
if (current != null)
current.AddEventListener(add, new DisablePageLeaveEvent(EventType.Submit | EventType.Click));

with no success. Can you advice please?
Thanks

Patrick Heneghan
Patrick Heneghan Sep 19, 2011 02:44 PM

Hi Anders,

We are having a problem with the MultiProperty project, similar to Ticket #160 (assigned defect) on epicode.

On a particular page type, we have a MultiProperty with about 4 properties inside it, as well as two properties using the TinyMCE editor. We can add up to 4 instances of the MultiProperty without any problem.

However, when we add a 5th instance, the TinyMCE editors will disappear (except for the words 'Paragraph' and 'Styles')

Deleting the 5th instance results in the TinyMCE editor being displayed correctly once again.

This only happens in IE (8) but not in Firefox.

Do you have any idea how to fix this?

Nov 15, 2011 02:00 PM

Hi Anders
I also have some problems with MultiProperty and CMS 6. In the editor when clicking save, the property is not saved. It works fine using "Save and View" or "Save and Publish" but when I click save the page is reloaded, the property is also displayed but without values. Any ideas?

steven pap
steven pap Mar 8, 2012 12:08 PM

thanks guys. that helped me out a lot..

Jan 31, 2013 02:14 PM

I have the same problem as Kristina. It only happens when you're logged in with a non-admin account. Found any solution?

Please login to comment.
Latest blogs
Stop Managing Humans in Your CMS

Too many times, a content management system becomes a people management system. Meaning, an organization uses the CMS to manage all the information...

Deane Barker | Nov 30, 2023

A day in the life of an Optimizely Developer - Optimizely CMS 12: The advantages and considerations when exploring an upgrade

GRAHAM CARR - LEAD .NET DEVELOPER, 28 Nov 2023 In 2022, Optimizely released CMS 12 as part of its ongoing evolution of the platform to help provide...

Graham Carr | Nov 28, 2023

A day in the life of an Optimizely Developer - OptiUKNorth Meetup January 2024

It's time for another UK North Optimizely meet up! After the success of the last one, Ibrar Hussain (26) and Paul Gruffydd (Kin + Carta) will be...

Graham Carr | Nov 28, 2023

Publish content to Optimizely CMS using a custom GPT from OpenAI 🤖

Do you find the traditional editor interface complicated and cluttered? Would you like an editorial AI assistant you can chat with? You can!

Tomas Hensrud Gulla | Nov 28, 2023 | Syndicated blog

Optimizely Graph and Next.js: Building Scalable Headless Solutions

Optimizely Graph harnesses the capabilities of GraphQL, an intuitive and efficient query language to, transform content within an Optimizely CMS in...

Szymon Uryga | Nov 27, 2023

Getting Started with Optimizely SaaS Core and Next.js Integration: Testing Content Updates

The blog post discusses the challenges of content updates on a website using Optimizely CMS, Next.js, and the Apollo Client due to Apollo's local...

Francisco Quintanilla | Nov 27, 2023 | Syndicated blog