PS: unfortunately I had to hold back TurboDNN release for DNN 7.4.0 due to issues identified during testing.
I spent the whole weekend to trace it down - finally finding an issue in this version of DNN core framework (DNN-6601).
Please be careful upgrading any DNN, if it doesn't have a site with portalID = 0 or contains sites with a different default language as Portal 0.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

Sebastian.. How about you do a pull request whenever you have time and stagger your effort over time, starting with the ones which provide the most performance improvements? As Joe mentioned, it makes sense to do a separate pull request for each so they can be tested in isolation. It doesn't have to be an all or nothing effort.

Maybe even if you can divide the pull requests with other volunteers?

We'll gladly accept any change which provides real performance or stability improvements as long as they don't also introduce additional bugs.  If there are any specific items which you think were unfairly rejected, I would be happy to review them and work with you on getting them to a state where they can be accepted. 

I wouldn't consider TurboScripts as a dataprovider because it doesn't install in a manner that is consistent with providers which results in conflicts during upgrades and complicates support issues.  I definitely think that if you package and install it as a dataprovider it would help to minimize upgrade conflicts and simplify troubleshooting issues.  It would also make it clear that database related issues should be handled by the TurboScript dataprovider maintainers.

---

Joe Brinkman
DNN Corp.