Hi,
After getting DNN 7 to work on my local computer, I migrated the database and folders to my arvixe host.
I had to go into the portal alias table to update the HTTPAlias. The site comes up ok and I can even log in. But on the home page, the spinny just runs, the banner images (awesome cycle banner images) do not display and when I scroll down the page all the images on this page are X'd out?
The rectangle for the rotator displays, but of course does not change.
Also, when I go to edit the page, and click edit content, all I see is an "X" inside Slide 1, 2 etc.
All regular dnn icons display correctly though.
I am wondering where to look next?

thanks for your advice

Check the URLs for the images.

If I were guessing, I would guess that you developed on a system in which DotNetNuke was not in the website's root. If that is the case, you should find that there is an extra directory in the URLs. The other guess is that the URLs are absolute, and refer to the URL of the development site.

In either of those cases, you have a bit of work to do.

The good news is that there is a free module from Engage Software called F3. You will find it at store.dotnetnuke.com. It is a free module. With it, you can a blanket cut and paste in all HTML modules.

Thank you Joseph, that was exactly the problem.

When it was on my local laptop the path to my images was one thing, but up on my hosting I needed to change the path to what it should be on my hosting server.
For others who run into this and who might be wondering what the correct url is, you can ...
1 - go inside your text/HTML module editor.
2 - Click the edit pencil icon and edit content.
3 - Click on the HTML (it might be greyed out on some skins, but it
can still be clicked on).
4 - Now you can see the current path to the images.
5 - Click design and go back.
6 - click insert, manage images and pick an image.
7 - Click the HTML button again and you will see the path for this new image you just selected. This is the path your images need.

Take a look at F3. You can search and replace the URL across all modules in one (or a couple of steps), assuming that you know how to change the URL.

If your host lets you install DotNetNuke in the "root" (which is the way it should) you should also install DotNetNuke in the root in your development environment. On reason that I like the dnndev.me domain is that it simplifies doing that.

I forgot to also say that you should ALWAYS use relative urls.