Post Migration Problems
Quote from: ajpee I think I am still missing the point somewhere. If I enter the URL http://ccgi.thehamptons.plus.com/pixelpost/index.php/ into a browser I see the attached screengrab.
As far as I understand it, putting a "/" at the end of a URL calls up a "directory" rather than a page. So, http://ccgi.thehamptons.plus.com/pixelpost/ calls up whatever is in the pixelpost directory (by default will call up an index page if such exists, be that index.php, index.htm or index.html [not sure of which would appear if more than one of those existed]), or would show a listing-of-contents if there wasn't any index page (you can test this by simply removing the index.php page and calling up that address).
Putting a "/" after a page address (in the URL you quoted, ie after index.php) is effectively calling up an index.php directory, which (in the address you quote) would be a subdirectory of the pixelpost directory. Obviously no such subdirectory exists, hence maybe why what appears looks like a listing-of-contents (though I'm not entirely sure why it wouldn't simply call up a 404).
Quote from: ajpee I logged into Filezella using the info spraxyt suggested and I uploaded a new image here http://ccgi.thehamptons.plus.com/pixelpost/index.php?showimage=520
I am still not sure whether I am looking at the old host url or the new host url.
As far as I'm aware, if you've been migrated then you're looking at the "new host" URL (the main ccgi.username.plus.com address should have carried over, browser-wise, as it were, even if many of the other factors have changed, as regards how you access or modify your site's content behind-the-scenes).
If you uploaded the image *only* to the "new host" (ie by using the recently-provided log-in/access details), then if that image is viewable on line (ie not just on your hard drive) it must (logically) be the "new host" URL that you're looking at.
Hope that helps clarify things
a bit, anyway.