Why is that adding modules has to be such a PITA? Other CMSs offer an easy way to add custom data like Kentico’s custom tables and Ektron’s smart forms. Sitefinity allows custom data to be added through modules, but the implementation is way, way to complicated – I’m not talking about adding a filed to the news section, I’m talking about completely custom data structures.
I recently used Sitefinity 3.7 to create a solution for Hostess brands. The implementation of a custom module was complex. Since them implemntation used standard .Net for its controls I was able to create a Visual Studio template to expedite the process though.
I’m currently working on a project that is using Sitefinity 4.2. I recommended this product over Kentico since I had already jumped through all of the hoops to create an easy workflow. But, the Sitefinity team decided to change the underlying data structure – I get it you want people to buy your Fluent ORM (good luck, LINQ toSQL works just fine).
I have setup a repeatable structure to create new modules in 4.2; I’m still having a couple of issues related to images though. But, this whole thing has made me think, Why should the end-user have to have a .Net/Sitefinity specialist just to implement new data elements? And, beyond that why should the implementation consist of 16 files -- see the documentation for 4.2.
An admin user should be able to add new modules through the cms interface. I think this should be priority #1 for the sitefinity team; afterall it is one of the most fundemental pieces of a CMS implementation. I should be able to implement a new module with the following steps:
This really shouldn’t be all that hard to accomplish. It would basically be the same thing as the Forms module, only for the backend.
As for now, I’m going to struggle through my current project, but will be very hesitant about suggesting this product for future projects until this is resolved.
Can someone confirm this, and if so is there a release date set?
- Confirmed. The first version of the Sitesync/Publishing will be available with 4.3, then we will expand it and it will be operational with 4.4, by the end of November/beginning of December. We cannot comment on strict release dates for now. The situation with the Module Builder is identical.
There's one thing that is certain - we will not stop the Module Builder development anytime soon. The Module builder will be under heavy development during the next Q as well, which means that 5.1 will also bring new features to it. 5.0 will bring module deletion and module data export.
As for the features you suggest - they are all are great, and I'll make sure to pass them to the guys.