24 Sep 2012
12 Aug 2011
Link to this post
Can I just say that sometimes I struggle to understand the development logic for Sitefinity 4 when something as seemingly simple and commonly used in website design as a breadcrumb doesn't make it into the third major release of a CMS.
Furthermore breadcrumb was in 3.7 so why spend time on creating a migration tool when you can't even migrate a clients site without having to say to your client "sorry, in the new version a breadcrumb hasn't been built yet so you can't have it when we "upgrade" you!". Clients say "well how can that be an upgrade" and then we have to convince them
to pay to upgrade and remove functionality.
A breadcrumb is simple UX element that is used all the time so why delay it but yet deliver new modules like ecommerce or email campaigns?
For all the great things about Sitefinity 4 it seems to me that really important but SIMPLE features that were in the previous version of Sitefinity and SHOULD be the new version are missing, yet time is being spent on delivering more complex features that we can't sell because Sitefinity can't do very simple functions or there is bugs in simple functions like:
No external page support
Still no bugless support for nested masterpages so we have had to revert to using user controls again for share functions
Still no support for shared content in templates
Is anyone out there at Telerik listening to us long time and experienced Sitefinity developers who have been working with the product from version 2 days?