Error instead of "Thanks for installing CMS" screen

[philipcaplan]

Hello, all.

Following the "Quick Install via FTP" instructions, I get everything uploaded into a folder I've called "cms" in the "public_html" area of my hosted domain and changed the permissions on 4 files/folders (step 4) and the empty config.php I've created and uploaded (step 5). I then created an empty MySQL database using name/username/password as suggested in Step 6.

I then browse to *mydomain*/index.php and (instead of getting the "Thanks for installing CMS" screen, I get:

Parse error: parse error, unexpected T_CONSTANT_ENCAPSED_STRING in /home/*mydomain*/public_html/cms/index.php on line 141

Can you help me?  Thanks.  PHILIP CAPLAN

(One possibility is the permissions; I'm using an FTP client that describes permissions in a matrix of "Read"/"Read/Write"/"Execute" against options of "Owner"/"Group"/"Everyone".  I have assumed that chmod 777 eqauls all 9 boxes ticked; and chmod 666 equals all 3 boxes ticked for "Owner" and "Group", but none ticked for "Everyone"

[Ted]

Try uploading index.php again.  It sounds like the file didn't complete.

Oh, and to answer your question, 666 means that Owner/Group/Everyone has read and write access, but not execute.  However, I don't think that's related to your problem.

[philipcaplan]

Thanks for that, wishy.

It worked. I have now got to "Step 10" in the Installation Insructions (Database Information) but when I press "Continue" I get the following error message:

Warning: mysql_connect(): Access denied for user: 'cms_user@localhost' (Using password: YES) in /home/personal/public_html/cms/lib/adodb/drivers/adodb-mysql.inc.php on line 340
Connection failed

I tried leaving "Database host address" as localhost (got message above) and changing it to my domain name (got same message but with user 'cms_user@*domain*'

Could you help me again, please   :>   Thanks   PHILIP CAPLAN

[philipcaplan]

OK, I'm nearly there now!!

Turns out that my "Database name" and "Username" both needed to be prefixed with an abbreviation of my domain name -- that's the way my cPanel created them!

So, I got all the way through step 12, with everything marked [done], and the message: "Congratulations, you are all setup. Here is your CMS site"

So, I clicked on the link at "CMS site", but instead of my site coming up I got:

Warning: _get_plugin_filepath(/home/personal/public_html/cms/lib/smarty/core/core.assemble_plugin_filepath.php): failed to open stream: No such file or directory in /home/personal/public_html/cms/lib/smarty/Smarty.class.php on line 1362

Fatal error: _get_plugin_filepath(): Failed opening required '/home/personal/public_html/cms/lib/smarty/core/core.assemble_plugin_filepath.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/personal/public_html/cms/lib/smarty/Smarty.class.php on line 1362

Aaaaarghh!  What's missing now???????????????




"

[KnightWolfJK]

I recommend SmartFTP, I've been using it for years (free for personal use, nice GUI)

[philipcaplan]

Thanks, Patricia.  I looked at the file in my FTP client and discovered that its name had been truncated to end ".p" instead of ".php".

I renamed it, then went through the other files in that folder, and did the same to several others that had been similarly cut off.

And that did it.    :>

Also, thanks to KnightWolfJK for the suggestion of SmartFTP, but I'm on a Macintosh (using MacOS 9.2.2) so SmartFTP  isn't available to me :>  I'm using Fetch 3.0.3, which is I think the last version of Fetch to be freeware before they moved on to the paid-for versions.

Thanks again for all the help I've had here. Now to get started on the real adventure!!!  PHILIP

[Ted]

For the Mac, I use Transmit.  Granted, it isn't free, but it works incredibly well.

http://www.panic.com/transmit

[philipcaplan]

Fetch 3.0.3 seems to work OK for me. My earlier problems were *not* with my FTPing, it turned out, but with my un-zipping.

I used the Stuffit Expander I've had for a few years, and got no error messages, but some of the files on inspection turned out to have "garbage" at their ends.Re-unstuffing produced visually-intact files, which when oploaded worked perfectly.  :>

PHILIP