Register  |  Login   
HomeUniversal ListSupport ForumsPortfolioContact Us
Forum  
SearchForum Home
  Universal List  Universal List Version 4.x  module content ...
 module content not visible to registered user
 
 11/16/2007 4:58:57 PM
jillymc
14 posts


module content not visible to registered user

I have a UL installation that works perfectly when logged in as host.
I have 'registered users' set to add and edit, but when I log on as a registered user, when I go to the page with the module, all I see is the container.  The UL module content doesn't appear.   It looks like the 'loading' appears briefly, but than the container is blank.

I'm also having problems having to re-login on every page with a UL module.  

Any idea what I'm doing wrong?

Thanks,

Jill

 11/17/2007 9:49:42 AM
host
238 posts
4th


Re: module content not visible to registered user

Jill

In past we had problem with Medium Trust security level. It was same like you described. What level of security you use?

Thanks

 7/23/2008 8:20:35 PM
anoeth
4 posts


Re: module content not visible to registered user

Iam having this problem with the latest version of your module and the latest DNN version.

Can you help?

 7/24/2008 3:57:35 AM
host
238 posts
4th


Re: module content not visible to registered user
Please go to the "Configuration/Security" and define permissions for Unregistered users.
 7/24/2008 1:22:33 PM
anoeth
4 posts


Re: module content not visible to registered user

I did what you suggested and got this error message in the module on the web page.

I only want registered users to have access to the page and see the data.

UniversalList
 

Server Error in '/Tools/DotNetNuke' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

  Universal List  Universal List Version 4.x  module content ...
Free DotNetNuke dnndir.com DotNetNuke.fr About Us DotNetFreaks Asp.net Directory - Applications, Controls, ASP.NET hosting, Tutorials www.alldnnskins.com DotNetNuke Powered! Snowcovered
 
CookDNN