Announcement

Collapse
No announcement yet.

Heart Internet settings

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

    Heart Internet settings

    Hi All, been searching the forum for the past week for a solution to allow me to upload Actinic stores to a Heart Internet Reseller accounts and found nothing of use. Heart internet have a page of Actinic settings in their own support section but the do not work for v7, v8 or v9.

    I have now, through trial and error, found a solutions and wanted to share it. It does not just apply to Heart Internet but to any other hosting where the cgi-bin is fixed at root (same level as th public_html directory, not in it) which does not seem to work with Actinic.

    Error messages like:

    "The directory specified as the path from the CGI-BIN to the acatalog directory does not exist on the web server. Check the path. Also see the on-line help for "Path from FTP server to Catalog".

    and

    "The script does not have permission to write to the web site directory."

    and

    "Your Catalog URL appears to be invalid. The files uploaded to the given 'Path from cgi-bin to acatalog directory', can not be downloaded via the browser on the given Catalog URL. These two access routes don't point to the same destination on the server."

    Are common if this is the case. I don't fully get what they all mean but can say I know them all off by heart from the last weeks misadventure.

    Solution:

    It's simple really, in your 'public_html' directory you need to make an 'acatalog' folder with permissions set to 777 and also a 'cgi' folder with permissions set to 755. You CANNOT use 'cgi-bin' as a name for this folder as the hosting does not recognize it.

    I don't know why you have to make both folders yourself but I found that unless I did I get the second error above.

    Finally, the settings I have used are:

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


    Hope that helps someone else, from lookinf at other posts I can see the ame applies to quite a few other hosts like Xcalibre, Supanames and technoweb.
    Steve - Fluidfusion

    #2
    Heart propagation

    Oh, one last note, setting up any domain or domain reference on Heart seems to take a while to settle. Make sure you leave plenty of time before you try to upload your store or you get ftp errors like:

    "Unable to connect to the FTP server because the specified username or password is incorrect."

    Even if there is no domain propagation it does seem to take about 24 hours for a hosting account to behave consistantly.

    Why use Heart internet??? Cheep as chips and really easy to use. But then, I moved there from Fasthosts!
    Steve - Fluidfusion

    Comment


      #3
      Many thanks for the above. Two years later and it is still extremely helpful.

      Can I add ... I have found that pasting settings into the Actinic setup can also prove problematic. I know its a bore, but typing them in solved all issues for me.

      Comment


        #4
        For info, I use Heart for many of my Actinic stores and I have never had to follow those instructions given. The cgi-bin provided at the same level as public_html has always worked for me.

        Settings I use for Heart are :

        HTTPPROXYMODE 0
        HTTPPROXYADDRESS
        HTTPPROXYPORT 80
        HTTPPROXYUSER
        HTTPPROXYPASSWORD
        FTPPROXYMODE 0
        FTPPROXYADDRESS
        FTPPROXYPORT 21
        FTPPROXYUSER
        FTPPROXYPASSWORD
        SCRIPTID 8
        SCRIPTEXT .pl
        SMTPHOST localhost
        WEBSITEURL http://www.xyz.co.uk
        IGNOREPASSIVEERRORS true
        USERELATIVECGIURLS false
        PATHTOPERL /usr/bin/perl
        USEENHANCEFTP true
        FTPCLIENTTIMEOUT 15000
        FTPRETRYDELAY 3000
        FTPKEEPALIVEINTERVAL 30000
        FTPSILENT true
        FTPMAXRETRIES 3
        FTPCONNECTTIMEOUT 25000
        SMTPAUTHREQUIRED false
        SMTPUSERNAME
        SMTPPASSWORD
        COMPRESSIONPACKETSIZE 1024
        COMPRESSEDUPLOAD true
        CATALOGURL http://www.xyz.co.uk/acatalog/
        ONLINESTOREFOLDERNAME acatalog
        CGIBINURL http://www.xyz.co.uk/cgi-bin/
        PATHFROMCGITOCATALOG ../public_html/acatalog/
        CODEBASE ./
        FTPHOST ftp.xyz.co.uk
        FTPUSERNAME xyz.co.uk
        FTPPASSWORD xxxxxxxxxxxxxxxx
        PATHTOCGIBIN /cgi-bin/
        USEPASSIVEFTP true
        FTPPATHFROMCGITOCATALOG


        These apply to shared hosting/reseller accounts. The settings for use with their dedicated servers are almost certainly different (I can't remember - I moved my dedicated servers last year).
        Elysium:Online - Official Accredited SellerDeck Partner
        SellerDeck Design, Build, Hosting & Promotion
        Based in rural Northants

        Comment

        Working...
        X