+1-888-365-2779
Try Now
More in this section

Forums / Set-up & Installation / upgrade from 3.5 to 3.6 SP1

upgrade from 3.5 to 3.6 SP1

8 posts, 0 answered
  1. Marko
    Marko avatar
    148 posts
    Registered:
    30 Jul 2008
    04 May 2009
    Link to this post
    Hi.  With all the talk about the benefits of embedded templates, I'm wondering what's the best way to do a "clean" upgrade to 3.6 sp1 for an EXISTING website which is currently in ver. 3.5. One of the things that was talked about is the fact that the number of files in the Sitefinity folders will be greatly reduced with the use of embedded templates.  However, if I just follow the steps outlined in Upgrade Instructions I will end up with the new version of Sitefinity, sure enough, but I will still continue to have all of the old Control Template files that came with the original installation of my Sitefinity-operated website.

    Is it that these original Control Template files are NOT USED unless mapped into a view (as described here), even though they're present in the file structure?  If so, that's good, but I still don't like that fact that there are hundreds of lingering files in the web site structure that are not being used for anything.  What's worse, it can be confusing and misleading when customizations to Control Templates are actually needed at some point.

    Basically, my question is: how does an existing Sitefinity website take advantage of the new and cleaner website structure?  Some advice and pointers would be great!  Thanks!


  2. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    04 May 2009
    Link to this post
    Hello Marko,

    Is it that these original Control Template files are NOT USED unless mapped into a view (as described here), even though they're present in the file structure? 

    Yes, the website will use the embedded tempalates unless you map an external template.
    The benefit of an exsisting site will be reducing the size and you can separate all customized templates. If you nedecide to make further upgrades you should only copy these templates and your ControlsConfig file with all mappings.

    Benefits regarding cusomization and development

    Introduction
    New architecture
    What has changed and what has not
    Overview

    Sincerely yours,
    Ivan Dimitrov
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Check out the tips for optimizing your support resource searches.
  3. Marko
    Marko avatar
    148 posts
    Registered:
    30 Jul 2008
    04 May 2009
    Link to this post
    Thanks, that helps explain things on an overall level, and overall benefits of the new architecture.

    "The benefit of an exsisting site will be reducing the size and you can separate all customized templates."

    I understand, but exactly HOW do I take advantage of those things for my existing site?  What do I need to do, now that I am upgrading to 3.6, and I have all the old files and properties still there?  Should I simply go through all subfolders underneath Sitefinity\Admin\... and Sitefinity\ControlTemplates\... and DELETE all control template files that are NOT going to be mapped in the Configuration xml file?

    Also, what happens to the existing front-end control properties that have been set all along?  For example, if a have a page which uses an EventsView control, and let's say that it's been there, unmodified, since ver. 3.2 or something like that, and now I go to 3.6, what will happen to that "front-end" control template sitting inside that particular web page?  Since its properties would be unmodified when I go to 3.6 (right?), it would probably have an "ItemListTemplatePath" in its properties still set to "~/Sitefinity/ControlTemplates/Events/Modes/ListPageMaster.ascx" or whatever.  But if I haven't mapped that to be a custom control template, what will this EventsView control display, then? Embedded template?  The one referenced in the ItemListTemplatePath?

    Sorry to be annoying, but I really need to understand this correctly if I am to go and upgrade our main company website to the latest version of Sitefinity.
  4. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    05 May 2009
    Link to this post
    Hi Marko,

    "I understand, but exactly HOW do I take advantage of those things for my existing site?  What do I need to do, now that I am upgrading to 3.6, and I have all the old files and properties still there?  Should I simply go through all subfolders underneath Sitefinity\Admin\... and Sitefinity\ControlTemplates\... and DELETE all control template files that are NOT going to be mapped in the Configuration xml file?"

    You can delete all files under ControlTeplate folders - for the backend and frontend if you are not going to use them after upgrade. All templates( for GC modules) form version 3.6 are embedded into assemblies.
    In case you have made any changes to your templates and you want to apply them after the upgrade you should map them.

    "Also, what happens to the existing front-end control properties that have been set all along?  For example, if a have a page which uses an EventsView control, and let's say that it's been there, unmodified, since ver. 3.2 or something like that, and now I go to 3.6, what will happen to that "front-end" control template sitting inside that particular web page?

    The control will start using the built in template set by one of the public properties ( example: ItemListTemplatePath).  There are no changes to the templates that will dramatically affect the appereance of your events. We have not modified the templates html.

    "Since its properties would be unmodified when I go to 3.6 (right?), it would probably have an "ItemListTemplatePath" in its properties still set to "~/Sitefinity/ControlTemplates/Events/Modes/ListPageMaster.ascx" or whatever."

    There will not be anything set for this property. You can map your template directly through this property.

    Let us know if there is anything else unclear. We will be pleased to help you.

    Sincerely yours,
    Ivan Dimitrov
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Check out the tips for optimizing your support resource searches.
  5. Marko
    Marko avatar
    148 posts
    Registered:
    30 Jul 2008
    05 May 2009
    Link to this post
    Ivan,

    Thanks for the clarifications.  All of that made sense to me, and I started transitioning things to ver. 3.6 in my development environment.  However, I noticed a couple of things, soon after:

    Marko: "Since its properties would be unmodified when I go to 3.6 (right?), it would probably have an "ItemListTemplatePath" in its properties still set to "~/Sitefinity/ControlTemplates/Events/Modes/ListPageMaster.ascx" or whatever."

    Ivan: "There will not be anything set for this property. You can map your template directly through this property."

    This doesn't seem to be true.  After upgrading to 3.6, I went an opened a page in Sitemap and opened properties of an EventsView control which had been placed all along in that page.  The ItemListTemplatePath property was still set to the old value of "~/Sitefinity/ControlTemplates/Events/Modes/ListPageMaster.ascx."  So if I had went ahead and deleted all files under ControlTemplates folder, that would have broken my EventView control on that page (and bunch of other controls throughout the website).

    All front-end controls throughout the website are STILL having a particular value in their properties tied to particular control templates, which negates my ability to delete those control template files.  It sounds like I would have to go through EACH page and EACH control and clear out the values that are specifying the particular Control Template PLUS delete the files in ControlTemplates folder.  Unless I'm still getting this wrong???
  6. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    06 May 2009
    Link to this post
    Hi Marko,

    For the front end templates( used by Presentation mode of Generic Content based controls ) you are right. For the backend - templates can be removed.
    During the upgrade the settings for controls properties are not removed as they are stred in the database([sf_CmsControlProperty]).

    In this case there are two possible options.

    1.Check the pages manually.
    2. Execute a script against the database to remove the references by setting empty string.

    Example:

    UPDATE sf_CmsControlProperty 
    SET Value = '' 
    WHERE Name = 'SingleItemTemplatePath' 
    AND ControlID IN 
    SELECT ID 
      FROM sf_WebControlBase 
       where Type like 'Telerik.Lists.WebControls.ListDisplay%' 
       or Type like 'Telerik.Cms.Engine.WebControls.GenericContent%' 
       or Type like 'Telerik.Events.WebControls.EventsView%' 
       or Type like 'Telerik.News.WebControls.NewsView%' 
    )  

    Regards,
    Ivan Dimitrov
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Check out the tips for optimizing your support resource searches.
  7. Marko
    Marko avatar
    148 posts
    Registered:
    30 Jul 2008
    06 May 2009
    Link to this post
    Ivan, just to be sure... When you guys say "backend" control templates, do you mean control templates that are used for things throughout the Sitefinity admin interface (stuff underneath ~/Sitefinity/Admin/ControlTemplates folder)?  And by "front-end" you mean control templates for public controls (~/Sitefinity/ControlTemplates)?

    Just making sure I'm on the same page.
  8. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    07 May 2009
    Link to this post
    Hi Marko,

    backend - is the Sitefinity admin
    frontend - the public part of Sitefinity

    Here is a link to Sitefinity 3.6 backend architecture form where you can gather more information about how the things work.Sitefinity 3.6 new backend architecture - documentation outline

    I hope this helps.

    Sincerely yours,
    Ivan Dimitrov
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Check out the tips for optimizing your support resource searches.
Register for webinar
8 posts, 0 answered