More in this section
Forums / Bugs & Issues / 5.0 to 5.1 - Custom Module no longer functional

5.0 to 5.1 - Custom Module no longer functional

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.
1 posts, 0 answered
  1. Anthony
    Anthony avatar
    15 posts
    03 Sep 2010
    26 Jul 2012
    Link to this post
    We had developed a simple custom module for our Sitefinity 5.0 website in a separate solution leveraging the existing 'Products Module' tutorial located at creating-products-moduleThis was working perfectly in 5.0 -- Both the CMS administrative section and front-end views were functional and had no errors.

    Since choosing to upgrade to 5.1, and following Telerik's suggested guide to upgrading, this custom module is completely broken.  The module shows in the back-end System > Modules listing as 'active', but it is not available from the Modules menu so there is no way for the CMS administrators to access it.  The System.Config has an entry for the module as being installed as version (which is correct) and there is no "errorMessage" attribute on the corresponding <module> XML element.

    Furthermore, the OpenAccess API is broken for the front-end view.  When using the custom 'Manager' class to query items from the database is breaks when evaluating the following LINQ-expression:

    var manager = new CustomModuleManager();
    var items = manager.Where(x => x.IsActive).ToList();

    The exception details are:

    Identifier 'IsActive' is not a parameter or variable or field of 'CustomModule.CustomItem'. If 'IsActive' is a property please add the FieldAlias or Storage attribute to it or declare it as a field's alias.

    The "Breaking Changes" documentation states nothing about custom modules not functioning correctly in 5.1.  Is there any logical reason that custom modules would be completely non-functional in this version of the CMS?  What am I doing incorrect during this upgrade?  Any help from members or support staff would be much appreciated.

    I can provide source code at request.
1 posts, 0 answered