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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsGalleryGalleryGallery compatibile with 5.5?Gallery compatibile with 5.5?
Previous
 
Next
New Post
2/3/2011 10:56 AM
 
Hey Thanks Sebastian.  I failed to include a few more  pieces of info.  first, i'm hosted on godaddy.  second, i can't seem to find anywhere on godaddy to control such privs.   in the File manager screen, i can set the dotnetnuke folder to give the application read/write privs and for all subdirectories to inherit those privs (which i have done).

I don't think there is anywhere i can control grants specific to the windows account used by asp.net.   does anyone know if that's possible.

also,  when i first installed the gallery and built the page, it worked.   and now it has stopped working.  i cannot see anything that has changed?

Any thoughts?

Dave
 
New Post
2/3/2011 12:31 PM
 
David,

As Sebastian indicated that error is definitely a file system permissions issue. I am not familiar enough with the GoDaddy hosting control panel to know if you can grant a child folder full permissions for the ASP.Net worker process account (IIS Identity Account) . I am sure, however, that GoDaddy blocks you from doing so on the root install folder. Most likely you will have to contact their support to set permissions for you.

First, however, log in to the site as host and navigate to Host-->Host Settings. Near the top of page will be a line captioned "ASP.Net Identity" Copy down the value that you see there. Then submit a support request to GoDaddy - something like the following "Please grant full file system permissions on the root folder of my website to the ASP.Net worker process account (<value from host settings page>) and propagate them to all child folders."

As for what may have changed, consider if you had recently upgraded DotNetNuke or made any changes to your sites FTP user or IIS settings in your GoDaddy control panel. If GoDaddy is using a Plesk control panel it is known for causing a change in permissions for accounts such as the IIS Identity account anytime a change is made in the web site/IIS settings.


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
2/5/2011 9:12 AM
 
So...i did what was suggested above.   I received note back from support saying i can do that myself in the "File manager" (which i had previously done anyway.   I didn't realize that the file manager would be necessarily granting the privs to the asp.net worker id, i didn't know exactly what it would do....anyway....)

So bottom line, it appears that the host id has the priv.   I should mention also that i have 2 gallery pages on the site, and i can add pictures/edit albums on one...but he second one returns the error.

I don't know much about trust settings, but in the return email they mention this:

Our ASP.NET 3.5 and 4.0 shared hosting servers use the default Medium trust level with the addition of OleDbPermission, OdbcPermission, and a less-restrictive WebPermission.

Applications operating under a Medium trust level have no registry access, no access to the Windows event log, and cannot use ReflectionPermission (but can use Reflection). Such applications can communicate only with a defined range of network addresses and file system access is limited to the application's virtual directory hierarchy.

any other ideas?

thanks, Dave

 
New Post
2/6/2011 2:03 PM
 
It appears that your hosting provider  may be confusing file system permissions for the ASP.Net worker process account with the role based permissions that may be applied in the DotNetNuke website's File Manager. While I would check the File Manager's permissions to be sure that any Gallery folder to which users in a particular DotNetNuke role (for example Registered Users) should be able to upload images is showing Write permission for that role.

This issue, however, appears to be caused by insufficient file system permissions (outside of DotNetNuke). The necessary permissions (full permissions including modify) for the ASP.Net worker process account would need to be applied either in your website hosting provider's control panel (not from within DotNetNuke Host or Admin menus). It may be possible that you can do that yourself - at least on folders below the top level website root folder.

By default, Gallery files are stored in the following folder tree:

< website root folder >
     |--- /Portals
              |--- /< portalid# >
                          |--- /Gallery
                                   |--- /< moduleid# >
                                   |           |--- /_source
                                   |           |--- /_thumbs
                                   |           |--- /< child album name >
                                   |           |             |--- /_source
                                   |           |             |------- /_thumbs
                                   |           |
                                   |           |--- /< child album name 2 >
                                   |
                                   |------ /< moduleid# >

If you have more than one instance of the Gallery module on the site and only one of them is returning the error, I would suspect that one of the /< moduleid# > folders and its child folders are the ones lacking necessary file system permission. Alternatively if you have only one instance of the Gallery module and one child album is returning the error, I would suspect the corresponding /< child album name > folder and its child folders is the one lacking permissions.



                                                                                

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsGalleryGalleryGallery compatibile with 5.5?Gallery compatibile with 5.5?


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