Hi All,

Has there been any update on this? My client's site is on 1&1 running 6.0.2 fine. I tried to upgrade to 6.1.2 to solve the issue with embedding YouTube iframe code and then the site returned the same error at the start of this thread.

When creating a test page with the ASP code referenced earlier in this thread, I did get the message "Request for the permission of type 'System.Security.Permissions.EnvironmentPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=[removed]' failed.".

So, I am at a standstill. I need to upgrade our site to fix one issue and the client resource manage feature breaks the system. Is there any way to just upgrade ad disable CRM?

Thanks for any advice...

--Phil

Hi Cathal,

Thank you very much for your interest in the issue we've raised. I foresee this being a complication on more than a dozen of the 50+ sites I host and hope for a workable solution.

I never assume that issues are logged, but it is sometimes difficult to separate hosting issues vs. DNN core bugs vs. Upgrade anomalies. As a developer, I am often held hostage by my clients' choice in hosting companies. I do maintain my own dedicated server and have not had issues on those sites, but I realize that hosting companies try to mitigate their security risks through proprietary measures that go uncommunicated. This often wreaks havoc on the broad base of users, which raises the question of making such potentially breaking changes without advance warning, especially when DNN recommends upgrades for moderate to high-level security alerts. Could potential breaking changes be optional enhancements in upgrades rather than mandatory, hidden, undisclosed and irreversible?

I fully support the progression of DNN, and I am happily and heavily invested at this point. But sometimes we need to temper/adjust our advancement for the sake of support/deployment on a global scale.

Please keep me in mind if you are aware of a patch or workaround to either issue as I am in a very difficult position. And I appreciate your swift acknowledgement of the problem!

--Phil

Cathal,

I would like to reaffirm my absolute support and admiration for everyone associated with DNN, yourself included. You have made it possible to elevate the web to a level that every other CMS should be envious. The framework is flexible enough that I have always been able to find a workable solution for my clients, but the latest issue on 1&1 pits DNN directly against security policy at hosting companies. They are not my first choice...but they are one of the largest hosting companies and they have been able to support DNN up to v6.1 in my experience.

CRM has been available in DNN for a while now, but it wasn't until 6.1 did I realize that it was so fully integrated that there was no way to remove it after upgrading. As the developer who started this thread stated, why did the feature have to utilize a way to determine hostname outside of the way that the DNN framework does. This in my humble estimation is a breaking change outside of DNN's framework. If this is the crux of the issue, it should be a relatively easy out-of-band fix on codeplex.

Thank you again for the update, and I will do my best to keep the native's at bay...but it isn't going to be easy. It has been bad enough dealing with the lack of embedding YouTube videos into the Telerik Radeditor HTML control...but it is another thing entirely when the solution is out of reach because we can't upgrade.

Respectfully,

Phil