Nathan Paton
It seems some people have forgotten that when you update your site to the latest version, you are running the risk of some modifications (such as direct file modifications) ceasing to work correctly, or at all. This can be caused by a lot of things, from the updating of a function, or its complete removal and even the deletion of files which no longer serve a purpose may cause this to happen. This isn't reserved for just Dolphin. Even Drupal and Joomla modifications suffer from this. It's not the see more script developer's purpose to ensure compatibility at the cost of features and enhancements. It is the modification developer's responsibility to remain on top of changes and make them as needed to ensure their products remain compatible.

To make it short: This is not something that BoonEx can control, nor should they have to. It is the modification developer's duty to ensure their offerings remain compatible with the latest version. The same goes for companies such as Microsoft. While they try to keep as much compatibility with old software as possible, it does not mean that they will sacrifice complete overhauls of their code or a much needed update to some core component. No, for it is the developer's responsibility to update their software to work with these changes.

Oh, shoot. I accidently made them both equally long.
 
 
Below is the legacy version of the Boonex site, maintained for Dolphin.Pro 7.x support.
The new Dolphin solution is powered by UNA Community Management System.
PET:0.036302804946899