9 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

You'll receive a confirmation email with a link to create a password (optional).

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Scott commented  ·  April 22, 2012 04:17  ·  Flag as inappropriate  ·  Delete

  Would it not be simple to have a "Web Part Template" and when adding a new webpart you have option of standard webparts, or webpart templates. Any changes made to the webpart template changes all page templates using this templated webpart

• Dimitris Rakopoulos commented  ·  October 20, 2011 13:04  ·  Flag as inappropriate  ·  Delete

  What you suggest on the last comment is exactly the way this should be implemened.

• Jiveabillion commented  ·  October 18, 2011 06:47  ·  Flag as inappropriate  ·  Delete

  I just realized that my proposed solution didn't directly address the last part of ryan.weale's initial description. "If I need to change a value for that web part, I can do so in one place, and the changes affects all instances which reference it."
  I think that would be a great feature, and it could be done similar to the way that Document Type inheritance was done in version 6. Give us the option to have the web part inherit it's settings from a preset and whenever the preset that is currently inherited is changed, it will also be changed on all web parts that inherit it. Of course, the option to break inheritance will also be available. That will give us a central location to edit properties on all web parts that inherit a preset as well as the options that I illustrated in my mockup. I have a pretty good handle of how this would work in the UI and in code. Martin, if you would like to discus this you may contact me via the email that I used to send you the mockup.

• AdminMartin Hejtmanek (CTO) (Admin, Kentico CMS) commented  ·  October 14, 2011 13:25  ·  Flag as inappropriate  ·  Delete

  Got the message and I like it, no promises yet, but I will try to push it to version 7 ;-)

• Anar commented  ·  October 14, 2011 13:08  ·  Flag as inappropriate  ·  Delete

  Great idea, now there is no way it won't be implemented :)

• Jiveabillion commented  ·  October 14, 2011 12:38  ·  Flag as inappropriate  ·  Delete

  Here is a link to a quick mockup of how the UI could be done
  http://www.image-share.com/ipng-996-159.html

• Jiveabillion commented  ·  October 14, 2011 12:09  ·  Flag as inappropriate  ·  Delete

  I think a good way to implement this would be to create a child object of Web part that simply stores configuration values that we can name. Sort of a preset repository. Then, when we create or edit a web part, we can choose from our list of presets and it will automatically set those properties to the saved values, which we can then save or edit from there. Also, in the Web part properties dialog, there should be a button to save the current configuration as a preset. I have a good idea for a UI and can send a sketch of it.

• AdminMartin Hejtmanek (CTO) (Admin, Kentico CMS) commented  ·  October 12, 2011 02:54  ·  Flag as inappropriate  ·  Delete

  What we plan is to allow for "real default values" which means that you will be able to set that particular web part property should always use the value from the web part settings in site manager. This is little different from what you need because it covers only specific properties that you will set this way and is not in current version.

  What you can do to achieve what you need is to define a page template, where you put your preconfigured web parts, and then in the place you want them you use the Page placeholder web part with the Default template property set to this template, and you basically inject this template to another. Doing this on several templates will provide you with centralized control over particular template section.

  We would like to have this enabled in some nicer wat, but we didn't yet figure out how the UI for it and the configuration process should work, so if anyone has idea or can give us sketches for how you feel it would be intuitive enough, send it to us, we will appreciate it.

• Anar commented  ·  October 10, 2011 13:46  ·  Flag as inappropriate  ·  Delete

  One might say that you can achieve what you want by creating a user control containing let say <cms:CMSRepeater ...>. A feasible, but not very practical. You will need to open the ascx file to edit instead of using the portal engine webparts.

  Please add this feature!