MSPSS: is there life after the helpdesk?

sharing solutions to uncommon IT problems

Posts Tagged ‘dotnetnuke

DotNetNuke – Error during upgrade “A newer version of this package is already installed”

leave a comment »


Hello,

When I tried to upgrade our DNN portal from 7.1.2 to 7.2.0 I got a blocking, very cryptic error: “Upgrade A newer version of this package is already installed”.

The error log showed the following lines:

01/12/2014 17:55:09 [INFO] DotNetNuke.Services.Upgrade.Upgrade Start InstallPackage:D:\MyWebsite\Install\Module\DNNCE_CoreMessaging_07.00.04_Install.zip
01/12/2014 17:55:10 [ERROR] DotNetNuke.Services.Upgrade.Upgrade A newer version of this package is already installed – 7.1.2

The problem was that I had copied over the upgrade files without first deleting the old Install folder. In the install folder we had old modules alongside with the new modules.

Apparently the DNN Install/Upgrade routine tries to install all modules in the module folder without any particular order or rule. When it tried to install a very old version of the coremessanging module it prompted the error above.

Deleting the Install folder (best practice anyhow) fixes the problem.

HTH,
Roberto.

Written by zantoro

January 13, 2014 at 9:19 am

Posted in DotNetNuke

Tagged with ,

DotNetNuke – Upgrade to 7.1.1 – DDRMenu doesn’t work anymore

with 5 comments


Hello,

After upgrading DNN PE to 7.1.1, the DDRMenu suddenly stopped working due to a JS error: “Uncaught TypeError: Object function (e,t){return new b.fn.init(e,t,r)} has no method ‘curCSS'”.

the JQuery CurCSS method has been deprecated in JQuery 1.8.

DNN 7.0.x used JQuery 1.7 while DNN 7.1.x uses JQuery 1.9.1

The DDRMenu has not been updated to work with new versions of JQuery and they don’t seem to have a new version in the pipe on their website http://dnnddrmenu.codeplex.com/

The fix is quite easy but it might get overridden next time we upgrade the DDRMenu:

Edit \DesktopModules\DDRMenu\DNNMenu\DNNMenu.min.js and replace all “curCSS” method calls (2) with “css”

Update: DNN support replied that everything worked fine with a “out of the box” skin and therefore the problem was caused by my custom skin which was out of support (they don’t give support on Skin development).
By comparing my skin with one of the OotB, we found out that we were using <DNN:NAV instead of the more common <DNN:MENU. The DNN:NAV should still work but I get a feeling that is slowly dying (I can only find documents related of this menu in connection with DNN4 and 5, nobody seems to have used it since…)

We will investigate further but in the meantime, we are considering switching our menu to <DNN:MENU

Update2: Replacing the DNN:NAV with a DNN:MENU was easier than I thought and I get the feeling this incompatibility is the tip of the iceberg. Your safest bet is to download a free, prebuilt menu (superfish works pretty well out of the box), copy it in the skin folder and link it from the template (menustyle) and tweak the look and feel.
FYI: here is what they write on the DNN website about DNN:NAV:
Note that while it is also possible to use a dnn:NAV control with the DDRMenuNavigationProvider and CustomAttributes to render a non-DNNMenu template, it adds complexity and brings no particular benefits, so is not recommended.

HTH,

Roberto.

Written by zantoro

September 18, 2013 at 12:01 pm

Posted in DotNetNuke

Tagged with , , ,

Dotnetnuke 7 + ActiveDirectory module: login prompt

with 3 comments


Hello,

we are setting up an evolutionary prototype of Dotnetnuke which will eventually replace our current extranet portal.

I’ve setup the new, out-of-the-box DNNPro_ActiveDirectoryAuthentication module.

Everything works as expected (ie: AD users can login successfully) but often, the first time you open the website you are presented with a login prompt.

Untitled

If you hit cancel, the system shows that /DesktopModules/AuthenticationServices/DNNPro_ActiveDirectory/WindowsSignin.aspx is asking for credentials.

In other words, DNN is trying to get you to automatically sign-in using your system credentials, then, when the login fails, it prompts you with a login box.

you may say: but I never asked to be logged in automatically! Neither did I and I struggled to find a reason and a solution.

In the module there’s no way to enable/disable this feature, but you can limit the automatic sign in to a range of IPs:

I simply limited the range of “allowed” IP to an unused internal ip (e.g.: 192.168.200.10) and that did the trick

Untitled

UPDATE: The solution I provided above was also causing a runtime error: “Index and length must refer to a location within the string. Parameter name: length”. In the end, in order to fix the problem, I had to disable auto-login altogether by commenting out the following line in the <modules> section of the web.config:

<add name=”Authentication” type=”DotNetNuke.Professional.Authentication.ActiveDirectory.HttpModules.AuthenticationModule, DotNetNuke.Professional.Authentication.ActiveDirectory” />

Written by zantoro

June 12, 2013 at 12:51 pm

Posted in DotNetNuke, IIS

Tagged with , ,

DotNetNuke: use DNN libraries in a common aspx page – Get the username

leave a comment »


Hello,

We are trying to migrate our portal to DotNetNuke. We have several applications developed in ASP.NET which we don’t want to convert into DNN modules all at once.

What we plan to do is convert only the entry point page from aspx to ascx and keep using all sub web forms modifying as little as we can (for the moment).

Initially we thought we could not retrieve the authenticated user info in non-module pages but actually, as long as the web page (aspx) is a member of the module you can reference to all DNN classes and retrieve whatever info you need.

Here, for example, is how I retrieve the logged in user:

——–

Imports DotNetNuke.Entities.Modules.PortalModuleBase

——–

Dim uinfo As DotNetNuke.Entities.Users.UserInfo = DotNetNuke.Entities.Users.UserController.GetCurrentUserInfo()
Label1.Text = uinfo.Username

——–

 

HTH,

Roberto.

Written by zantoro

April 11, 2013 at 7:49 am

Posted in DotNetNuke

Tagged with ,