Forum

Search Home

1
2
3
4
5

Home

Public

Skinning

Problem with skin using DNN Smart Mobile.Redirect Module

6/3/2014 1:35 PM

Paul

Joined: 3/25/2014

Posts: 2

Problem with skin using DNN Smart Mobile.Redirect Module

We are trying to use the DNNSmart Mobile Redirect Module recently described here on DNN Hero using different desktop, tablet and mobile skins, but are having problems. Rather than place modules in the specified containers when Mobile.Redirect changes a page's skin modules are all dumped into the ContentPane div of the new skin. This, of course, screws up the desired layout.

I am fairly new to DNN so hope that someone with more experience can tell me what's going on here. This is our setup:

We are using DNN 7.2.1

We use distinct custom pc, tablet and mobile skins. Every pane in these skins has a uniquely named container and each of these containers is simply an asp.net web 'Control' containing a single 'ContentPane' div. (I created the containers so that I could use the Mobile.Redirect feature that appears to be able to map Modules into different containers on each skin.) In every skin, Mobile.Redirector is placed into a container named 'mobile_redir' and all but admin pages use our custom skins.

Mobile.Redirector 'mobile settings' are configured to place each module in a page into specific containers in each of that page's pc, tablet and mobile skins.

Other settings are defaults except these:

Module 'Settings': 'Display Module on all Pages' is checked. (Per Aderson's video)
View Permissions: 'Inherit' unchecked, View for 'All Users' is checked. No other permissions checked (admins, of course, view and edit).
Page Settings: 'Display Container' unchecked.
DNNSmart settings: Url-only method. Stylesheet unchanged.

Thanks for any help you can give! -- Paul Schnackenberg

6/3/2014 2:10 PM

Aderson Oliveira

Joined: 12/28/2009

Posts: 1011

Re: Problem with skin using DNN Smart Mobile.Redirect Module

Hi Paul,

This can be simple to solve but you will have to do some work on the mobile skin.

The problem is that on the destop skin you have panes with names like "RightPane", "LeftPane", "TopPane". When the mobile skin gets loaded, most likely it doesn't have these panes with the same names. So what happen is that DNN can't find these panes and dump all of them inside the default pane which is the "ContentPage".

To fix that and add the module in the correct order that you want, you would have to modify the mobile skin by adding these other panes, most likely one on top of the other. This way when the mobile skin comes up, the right panes will be available to place the modules inside.

As you can see, this has nothing to do with the containers that you are using. The problem and solution is just related to the skin itself.

I hope this makes sense to you.

Best regards,

Aderson