Announcement

Collapse
No announcement yet.

Old server addresses

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Old server addresses

    We've recently switched hosts. On our old server, the address of the acatlog for our USA site was httpdocs/us/acatalog. On the new server it is public_html/us/catalog. naturally I have changed all the network addressing to reflect the new structure.

    When I'm testing the site though, clicking through to the checkout produced the error:

    Error: Error opening configuration file ../httpdocs/us/acatalog/A000.cat. No such file or directory

    I can see the A000.cat file sitting in the folder, but something is causing the old addressing to execute instead of the new.

    Any ideas as to how I can get rid of the old stuff? Here are my current settings:


    HTTPPROXYMODE 0
    HTTPPROXYADDRESS
    HTTPPROXYPORT 80
    HTTPPROXYUSER
    HTTPPROXYPASSWORD
    FTPPROXYMODE 0
    FTPPROXYADDRESS
    FTPPROXYPORT 21
    FTPPROXYUSER
    FTPPROXYPASSWORD
    SCRIPTID 1
    SCRIPTEXT .pl
    SMTPHOST localhost
    WEBSITEURL http://www.calarecords.com/
    IGNOREPASSIVEERRORS true
    USERELATIVECGIURLS true
    PATHTOPERL /usr/local/bin/perl
    USEENHANCEFTP true
    FTPCLIENTTIMEOUT 15000
    FTPRETRYDELAY 3000
    FTPSILENT false
    FTPMAXRETRIES 3
    FTPCONNECTTIMEOUT 25000
    SMTPAUTHREQUIRED true
    SMTPUSERNAME ******
    SMTPPASSWORD ******
    CATALOGURL http://www.calarecords.com/us/acatalog/
    CGIBINURL http://www.calarecords.com/us/cgi-bin/
    PATHFROMCGITOCATALOG ./../acatalog/
    CODEBASE ./
    FTPHOST 70.39.249.136
    FTPUSERNAME *******
    FTPPASSWORD *******
    PATHTOCGIBIN /public_html/us/cgi-bin/
    USEPASSIVEFTP true
    FTPPATHFROMCGITOCATALOG /public_html/us/acatalog/

    #2
    Have you done a web > refresh website?
    Does the site pass a network test?

    Comment


      #3
      The site passes the network test. At the moment I'm working in Test Mode, so the site was refreshed into that.

      Comment


        #4
        have you changed the name servers to point to your new host?
        i notice your using an ip address for the new server and you have ./../acatalog in one of your paths?

        my suggestion is to create a new ftp account under this host that only has access to the public_html then you can remove all the extra bits in your network settings. Using your master ftp account that has access to your complete hosting area means you need these extra settings and these can sometimes give you more problems if actinic is looking in the wrong part of the server.

        Comment


          #5
          Hi Darren, I'm sure that's good advice but I haven't the fainest idea how to implement it! (I'm not a developer or even a webbie). I use the IP address because that's what we've always used. The ./../acatlog path is something I'm testing because up till now only ../acatalog has worked, but doesn't seem enough for a subsite.

          As for your second paragraph - sounds great but how do I do that??? :-)

          Comment

          Working...
          X