Forum

Thread tagged as: Problem, Hosting

data not showing despite passing compatibility test

Hello!

Here is the problem I am having today (with my first move of a Perched site to GoDaddy.com).

I am using Perch_v2.6.3.

I have moved my files from from my local server to a subdomain on GoDaddy that I created and named "staging". According to PHPMyAdmin, I successfully imported my database to the staging site and succeeded in creating a user with a password who has all privileges. I succeeded in passing the Compatibility Test again, this time at the staging level.

I have updated the config file with the same user, password, and server info used to pass the Compatibility Test and uploaded it to the staging site.

My next move was to bring up the Admin panel. Using https://staging.nameofsite.com/perch/core/ I succeeded, somewhat, in that I got an unstyled version of the login page to appear. I have tried multiple addresses to make the login page appear.

When I filled in the username and password and clicked on the Log in button, I got a 404 message. Hence I cannot give you a diagnostic report because I cannot get to it.

The interesting part of that message was that it revealed Perch was trying to connect to the name of the folder the site had been located in at the local level. This name is not on any folder I uploaded to the staging site.

This is the message I got: "The requested URL /local_folder_name/perch/ was not found on this server."

Do I need to go somewhere else in the code to tell Perch to go to the staging site? Why is it hanging on to a local site folder name if that folder hasn't been uploaded to the staging site?

The staging site is displaying all the html of the site files but none of the database information created at the local level. I believe this is the reason the Admin login page also appears unstyled.

Thank you in advance for your help! It is deeply appreciated!

Kimberly Olmsted

Kimberly Olmsted 0 points

  • 7 years ago
Rachel Andrew

Rachel Andrew 394 points
Perch Support

We would not advise developing in a subfolder if you want to make your transitioning to live seamless. You've not developed in an environment that matches the structure of your live site.

Have you updated the path to your Perch install in the config?

Having done that you will need to go into each page's settings in Perch admin and correct the path, until you do this Perch will not find the content as /myfolder/page.php is different to /page.php.

Hi Rachel,

Per your advise, I redeveloped the site locally making sure that the site had its own virtual host on MAMP.

In the subdomain I set up on the remote server I was successful in passing the Compatibility Test. I updated my config file with the same info used to pass the Compatibility Test and saved. Afterwards, I successfully uploaded the site and perch files to this subdomain (I remembered from past perch experience that a staging site needs to be in a subdomain, not a subdirectory).

The Admin log-in window came up just fine but when I tried to log in I was told that my license key was not valid for this domain. My license key staging site name matches the url I see above the login window.

This is very, very, very, frustrating. Can you advise again please?

Thank you!

Drew McLellan

Drew McLellan 2638 points
Perch Support

Have you entered https:// as part of the domain in your Perch account?

Yes I have Drew. I have even copied the url and pasted it in the license to be sure I haven't made a typo.

Drew McLellan

Drew McLellan 2638 points
Perch Support

Ok, then it should be fairly easy to correct.

Great! I wait for the solution!

Rachel Andrew

Rachel Andrew 394 points
Perch Support

You need to remove the https://

Live Domain is the domain name that the final site will go live at. For example, if your site is at https://www.example.com/, you should set this to www.example.com

Excellent! Worked like a charm. Thank you both very much!