We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 15003
    • 85 Posts
    I’ve just taken my site live and in the configuration panel I’m getting the following warnings:

    Warning: Unexpected character in input: ’’’ (ASCII=39) state=1 in /hermes/web05/b2306/pow.massagecntrs/htdocs/manager/includes/lang/bulgarian.inc.php on line 244

    Parse error: syntax error, unexpected ’<’ in /hermes/web05/b2306/pow.massagecntrs/htdocs/manager/includes/lang/bulgarian.inc.php on line 244

    I thought that this might be from files not uploading correctly so I uploaded my lang folder again, but it didn’t make any difference. Does anybody have any ideas on what I should be looking for?
    Thanks ~Jules
      • 9207 ☆ A M B ☆
      • 2,475 Posts
      What’s on line 244 of that file? Sounds like it might be an encoding issue...

      Important question: are you actually using Bulgarian?

      Oh... and it might be that you uploaded a utf file using the FTP ascii mode. Or maybe I got that backwards... anyway, depending on how you upload files with your FTP client, it can corrupt certain special characters (e.g. the ones found in a language file).

      What are your FTP settings?
        • 15003
        • 85 Posts
        Thanks for the response Everett

        I guess it would have been good to add that I wasn’t actually using Bulgarian. I had been up all night trying to upload a site to a hosting company I don’t normally use, but it was the client’s preference so what are you going to do smiley

        It ended up being my worst "going live" experience, never had so much trouble uploading to a server before. There server was slow to close file connections after they were uploaded and as a result I kept getting the error message: 530 Sorry, the maximum number of clients ( 8 ) for this user are already connected. I still had trouble after I went down to a maximum of only 2 simultaneous transfers. I ended up baby sitting the upload process and pausing it whenever the server got jammed up. There help desk thought it was my fault that the server wasn’t closing out connections and suggested I use FireFTP (I was using Filezilla) Didn’t make any difference, but after what you said I checked and their default transfer type was Binary, I had Filezilla set to auto. I ended up uploading the lang folder again and used the ascii mode. The configuration panel works fine now.

        Sorry for the long story, but it did make me feel better to grumble about it.

        Cheers!
        Jules
          • 9207 ☆ A M B ☆
          • 2,475 Posts
          no problem. Glad you got it sorted out.

          Yeah, I’ve had some nightmares with "going live" -- I’ve altered my contracts so that it specifically says that it’s NOT included by default. I make sure the client knows that the push to the live environment needs to be a line item deliverable (ie. billable), and having things like SSH access can be a prerequisite to sanity, or the difficulties are reflected in the project cost.