Hello Joe, Lee and others, I am trying to organize my clients background pictures in a special folder called background images so the main portal root doesn't become the melting pot that all images are dumped into as happened to another client of mine. Having said that I discovered using DNN 5.5.1 that when I went to Admin>Site Settings>appearance> background images and chose an image from a folder other than the portal root it would not get applied in my skin even after I clicked on update. Having said this I also noticed anytime I chose an image that was in the portals root be it bmp, gif, jpg, etc... as long as the image did not have a space in the name somewhere it would be applied to the skin upon clicking on update but never could I get an image from a folder other than portal root to actually apply to the skin. If I did try to select an image from a different folder I had created via file manager on DNN all that would happen was the default image that was orginally setup with the skin package would be applied but not the one I specified. I was wondering if you guys had any idea as to why this seemed to be the case or weather it had to do somehow with how the skin author may have wired the background image in the skin. I noticed in my case it was wired to images/bg.jpg which seemed appropriate to me. Anyway thanks for any suggestions you might have reguarding this as it would help in the organization of my clients file system.

This sounds like a bug to me. I would recommend that you report it.

Hello Joe,

I just basically copied and pasted this same question into gemini with a small tweak or two here is what I told them

-----------------------------------------------------------------------
I am trying to organize my clients background pictures in a special folder called background images so the main portal root doesn't become the melting pot that all images are dumped into as happened to another client of mine. Having said that I discovered using DNN 5.5.1 that when I went to Admin>Site Settings>appearance> background images and chose an image from a folder other than the portal root it would not get applied in my skin even after I clicked on update. Having said this I also noticed anytime I chose an image that was in the portals root be it bmp, gif, jpg, etc... as long as the image did not have a space in the name somewhere it would be applied to the skin upon clicking on update but never could I get an image from a folder other than portal root to actually apply to the skin. If I did try to select an image from a different folder I had created via file manager on DNN all that would happen was the default image that was orginally setup with the skin package would be applied but not the one I specified. I was wondering if you guys had any idea as to why this seemed to be the case or weather it had to do somehow with how the skin author may have wired the background image in the skin. I noticed in my case it was wired to images/bg.jpg which seemed appropriate to me. Anyway thanks for any suggestions you might have reguarding this as it would help in the organization of my clients file system.
--------------------------------------------------------------------------------------

What I got back from them was the following response:

"Bo -please check guidelines on the gemini home page.We don't troubleshoot or answer queries here. Please redirect your query to forums.dotnetnuke.com or if you are a Pro customer please create a ticket with our helpdesk. Many thanks."

I will put this in the technical support area of dotnetnuke but I didn't know if you had a better way you think I should word this so it sounded more like a bug than a technical support question?

The end answer to this issue was "Will not fix" Anyway just thought I would pass on the word of how Gemini dealt with this. I'll go and post it in their dotnetnuke forum and see if I can get anywhere there.

Thanks again,

Bo

Bo,

I just played with this a little bit. 

I found that I could upload an image to a directory called images in the portal root and specify that as the background image for the site.

I found that images with spaces in the filename could not be used as a background image.

In my mind, that might be considered a bug, but I have learned over the years that blanks in filenames often lead to errors.

You might want to rewrite that as a simple bug report that files with blanks in the filename don't work.  But, I wouldn't be surprised if that's deemed not critical.

Having reread your original post, I see that there is another twist and that is related to something in the skin specifying a background image.  If that is done in the CSS file, it may will overwrite what is specified in site settings.

Hello Joe,

Ya I found that to be the case to in regards to spaces in image names and in this case I noted that the background can't be applied weather it be located in the portal root or some subfolder like images from the portal root.

In my case this was just the case I was trying to apply a background image for a church site called "ChurchPhoto Full Page.jpg"

As you can see I had spaces in this image so I decided I would hyphenate it instead and renamed it

"ChurchPhoto-Full-Page.jpg"

Upon making this change this background image was applied appropriately when the image resided in the portal root even with the CSS pointing to the file called bg.jpg but when residing in a subfolder called background-images it wouldn't work.

I will try your suggestion in regards to perhaps taking out the pointer in the CSS body tag that points to bg.jpg as the background image.

I had actually purchased the transparent2 skin through snowcovered.com and they give you multipile backgrounds that can be applied I'm assuming through DNN's site settings and they initially pointed it to whatever was contained in bg.jpg for that skin.

I'm assuming this would be the default feel if no image was specified in the site-settings of the admin menu so for example by default when you first upload the DNN installation and than upload these skins and under Admin>Site Settings>Appearance it says for background image "NOT SPECIFIED" the skin would pull the default image specified via the css file pointing to bg.jp in the body tag.

That was my theory anyway but it certainly doesn't hurt to play around with the CSS and take out the bg.jpg file that the skin developer of transparent2 originally had in there and see if a background image located in any place else other than the portal root directory would indeed work.

It certainly does seem strange though that the image works correctly from the scope of the portal root even with the bg.jpg in the CSS of the skin and doesn't seem to incur conflicts but only when the image with the exact same name implementation that worked in the portal root is transferred to a sub folder of the portal root does the issue seem to show up in regards to the background not getting applied properly.

I'm a bit surprised this is merely a technical support issue and not a bug as you mentioned but I will look and see if I get an answer from the Dotnetnuke community about this or if it ends up simply being a "stale" thread in their forum machine.

That is one thing I really appreciate about you guys is that no matter how silly or educated a question may sound to you someone either you or Lee attempt on an answer even if it is simply to point them to one of your articles or some other place on the internet at least you answer.

I had posted some question to Mitch Sellers concerning his book on module development back in April of 2010 and I have yet to see him or anyone else on his forum attempt at a solution to my inquiry while other inquiries have had more than 15 comments.

I like to see that eventually it seems like all your threads at least have 1 reply even if the reply is only from you it shows that you guys are serious when on your video tutorials you say if you have any questions go on the forum and we will be glad to help Thank You so much for all the help you guys give to the DNN platform

To repeat, I didn't have any problems with the background inmage, just with spaces in the filename.  But, I didn't look extensively.

I don't think that the background image is even related to the skin file, but I haven't looked to see how it is implemented.

I'm not sure if it is a bug or not.  That's up to the DotNetNuke gang.

thanks for your feedback on this issue. I'll let you guys know further what I find out from the dotnetnuke forum if anything in regards to this issue as it may be a help to others who are trying to organize their images in folders other than the portal root.

Thanks,

Bo

Great.

well just as a follow up I haven't heard back from the dotnetnuke community yet concerning my question about what we have been talking about in this thread so if anybody in this forum happens to get wind of anything in regards to this let me know in the mean time I will post back to this thread if the dotnetnuke community gets to this issue on their forums.

Thanks,

Bo