More in this section
Forums / Bugs & Issues / Upgrading from 3.2 to the latest version, having an issue at 3.6 SP2

Upgrading from 3.2 to the latest version, having an issue at 3.6 SP2

The forums are in read-only mode. In case that you want to directly contact the Progress Sitefinity team use the support center. In our Google Plus group you can find more than one thousand Sitefinity developers discussing different topics. For the Stack Overflow threads don’t forget to use the “Sitefinity” tag.
2 posts, 0 answered
  1. Matt
    Matt avatar
    14 posts
    Registered:
    25 Jan 2012
    26 Mar 2012
    Link to this post
    Hello!

    We recently decided to upgrade from version 3.2 to 5, and I have begun plugging away. I was able to get 3.5 working just fine, and I have 3.6 SP2 working almost 100%.  The only issue I have is when hitting the blog detail page I get the following error:

    Invalid resource name (Telerik.Blogs.Resources.ControlTemplates.Frontend.ContentViewSingleItem.ascx) for assembly (App_Code.gopm62pp, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null) or empty template.

    I searched around for some answers on here and the two things I saw were to set the .ascx file as an embedded resource, but I don't believe I can do that as I am running the site as a .net web site project.  I don't see any Build Actions entry on the file's property window.

    The second thing I saw was to download the external templates file and in the app_data/configuration/Telerik.Sitefinity.Configuration.ControlsConfig.xml file make an entry mapping the view to a .ascx file in the sitefinity folder.  I tried that and that didn't fix the problem.

    Any help on this would be awesome, as I am sure it is something really obvious but I've been staring at it for too long.

    Thank you!

    Matt
  2. Matt
    Matt avatar
    14 posts
    Registered:
    25 Jan 2012
    27 Mar 2012
    Link to this post
    Well, I was finally able to solve this by setting the SingleItemTemplatePath property of the SinglePostUpdate control to the ascx that was used in 3.2, which is what I wanted anyways because we have customized it.

    Sorry for the false alarm.
2 posts, 0 answered