Migrated from localhost to web

Hey everyone!

I have a problem after migrating my Concrete5 website from localhost to web, I moved the files on the ftp and the database on phpmyadmin online.

All the pages of my website are white, nothing appear and I can't understand why because on my dashboard everything seems OK.

Here is the link to my website : wsfr.ellair.fr

Have you already met the same problem or do you know how to fix it or both?

Hope some of you can help me!

Thanks in advance!!!


View Replies:
c5dragon replied on at Permalink Reply
wsfr replied on at Permalink Reply
Thank you for the link. I think this is a 500 error .htaccess but I don't know how to fix it…
mnakalay replied on at Permalink Reply
When I visit your site it seems to be working just fine. Did you manage to solve your problem?
weyboat replied on at Permalink Reply
I thought the same as you @mnakalay that the issue was resolved, but then I visited
http://wsfr.ellair.fr/a-propos/historique... and clicked the sitename anchor tag it threw an error, the anchor tag was referring the browser to http://localhost:8888/index.php....
So this does look like an htaccess issue.
mnakalay replied on at Permalink Reply
I really don't think it is an htaccess problem because that problem doesn't appear on every page and when you hover over the faulty one, you see the URL is the localhost one instead of the proper one. SO your situation is not a proper URL being redirected to a wrong one by htaccess. The wrong URL is already there in the code.

You might have something in your theme that's doing it.

To verify, check what is the page type of the page with the faulty logo URL then find another page with the same page type and see if it has the same problem.
weyboat replied on at Permalink Reply
Yes, you are correct, it isn't on every page?
The area used for the image/link cannot be a global area (sitewide) otherwise the error would occur on all pages.
So it will be a case of editing the faulty pages to insert the correct link.
mnakalay replied on at Permalink Reply
not the faulty page, the faulty page type.

You see you have a number of page types (left sidebar, right sidebar, full, blog post...) defined in your site. And every time you create a page, you select which page type you want to be applied to it.

Most likely, the page type used by the page with the problem si responsible and will do the same to all pages it is applied to. Which is a good thing because it means you can solve the problem across the whole site by fixing only 1 file