Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Premium module functionality still stuffed up in 5.6.2Premium module functionality still stuffed up in 5.6.2
Previous
 
Next
New Post
3/26/2011 7:47 AM
 
The premium module functionality worked perfectly all through 4.x and up to the mid 5's when it was broken. This is sitting in a dead ticket in Gemini, and has been in the forum as well. I'm just warning anyone who relies on the feature here.



Installing a module update wipes all premium module assignments for that module across all portals - this is real nasty.



And something has generally gone buggy with the feature: Premium module availablity is now totally inconsistent. This may depend on whether the module has been on the system through upgrades or is brand new - I'm not sure. Some modules just can't be made unavailable to portal admins, although they are always available to the host. Sometimes they are available to admins, but not to page editors.



Also something related is that creating new portals from portal templates affects module availablity. I can see that the portal templates now have all the module information in them, which did not used to be the case. It means that an imported portal template will override your premium module assignments, resulting in a totally random assignment of modules depending on where the template was exported and imported.



Overall the feature is just buggered now. Someone must have been messing with it and just not checked anything afterwards. I can't get any response on the Gemini ticket, so all I can do is check every new release and repeat myself.



oh and p.s. Just found yet another, albeit minor, bug in the feature - The lower double arrow that moves all modules from assigned to unassigned doesn't work in 5.6.2



 
New Post
3/27/2011 8:15 AM
 
Rodney,
please log the errors at support.dotnetnuke.com. Thank you.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
8/1/2012 4:44 AM
 

BTW, this issue is not fixed in DNN 5.6.8, you have to upgrade to 6 to solve the issue.

Issues:

http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=15329&PROJID=2

http://support.dotnetnuke.com/issue/V...

 
New Post
8/2/2012 4:01 PM
 
ROBAX wrote:
The premium module functionality worked perfectly all through 4.x and up to the mid 5's when it was broken. This is sitting in a dead ticket in Gemini, and has been in the forum as well. I'm just warning anyone who relies on the feature here.


ROBAX:

Don't hold your breath on this ever getting fixed.

I have logged this in Gemini, AND tracked down the general cause (and ultimately the specific DNN SQL update that broke it), AND provided one SIMPLE method to fix the issue, only to be told that it would STILL not be fixed.

On the DNN Upgrades including "optimization" of SQL Procedures.  The update to the DeletePortalDesktopModules stored procedure is the problem (the update specifically mentioned that it was to improve performance, and it should be pretty clear as to why it breaks).

My current StoredProc is listed below.  The BOLD text are the additions that fix the problem.

----

set QUOTED_IDENTIFIER ON
GO
ALTER PROCEDURE [dbo].[DeletePortalDesktopModules]
@PortalID int,
@DesktopModuleId int
AS
BEGIN
IF @PortalID is not null AND @DesktopModuleId is not null
DELETE FROM dbo.PortalDesktopModules WHERE PortalId = @PortalID AND DesktopModuleId = @DesktopModuleId
IF @PortalID is not null AND @DesktopModuleId is null
DELETE FROM dbo.PortalDesktopModules WHERE PortalId = @PortalID
IF @DesktopModuleId is not null AND @PortalID is null
DELETE FROM dbo.PortalDesktopModules WHERE DesktopModuleId = @DesktopModuleId
END

----

DNN 6 uses a different stored proc which works.

This does NOT restore the Add All/Remove All functionality, but you will be able to remove a single module on a single from the list of Premium modules WITHOUT it removing ALL Premium modules from ALL Portals.

 

 
New Post
8/14/2012 12:14 AM
 
Thanks for posting this Mike.

They really wrecked this entire section of module functionality in DNN. I just suffered on through and eventually managed to get onto DNN 6.1.5 where some of it works again.

What still doesn't work is that modules lose the premium setting and portal assignments whenever they are upgraded, so you have to remember and reassign this afterwards. That would be a total showstopper in a system with different settings per portal, but thankfully my settings are system-wide at the moment.

I've been able to work around the other problem where premium module settings are now included on portal templates by manually removing all of the relevant sections in the template. This makes new portals abide by the premium settings on the target system. This would be a showstopper for anyone creating and applying portal templates on a daily basis.

Not sure if any of this has been fixed in 6.2.x, but they have other new showstoppers anyway, so it doesn't matter.
Rob
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Premium module functionality still stuffed up in 5.6.2Premium module functionality still stuffed up in 5.6.2


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out