failed to open stream: Permission denied

[platte]

Well, so much for that. Believe me, I am not inexperienced with a little code, but that (upgrade) resulted in not being able to get to the admin area. After fooling around with some permissions, I get this:


Warning: main(includes/application_top.php): failed to open stream: Permission denied in /home/sitename/public_html/zen-cart/admin/index.php on line 10

Fatal error: main(): Failed opening required 'includes/application_top.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/sitename/public_html/zen-cart/admin/index.php on line 10


So, I guess my best solution is to start from scratch, again.

[DrByte]

The "Permission denied" message is telling you that your /admin/includes/application_top.php file has permissions set on it too low for the server to be able to access, or whatever you used to upload the file caused it to be owned by someone that the webserver doesn't have permission to share files from. That can happen if you use browser-based tools for transferring files, instead of using a proper regular FTP program. And proper access permissions for files are typically 644 for files (and 755 for folders).

[platte]

I am using Adobe GoLive to transfer files, should be a considered a proper ftp program. Permissions on application_top are 644.

[DrByte]

GoLive isn't exactly dedicated to FTP. It's more like it's got FTP capability bolted on. But, that said, while I've seen tons of FTP problems using Adobe Dreamweaver, the reports of problems with GoLive are decidedly fewer.

[Website Rob]

You do not need to start again from scratch, nor should you. What you should do is use another program to verify file permissions and ownership. A regular FTP program would be a good choice for such a thing.

[platte]

I did reinstall from scratch. So many things were going on, it seemed like the cleanest solution. And now all is fine, but I am a little hesitant to update from 1.3.9c, to 1.3.9d.

I did have plenty of other headaches along the way, as my host installed a new ip for the SSL, AND I figured out GoLive was adding encoding to php files as I opened them. I would erase the encoding info and reupload, but there it still was. Now, how did I remain patient through that!!!

Anyway, that was fixed with some global settings changes in GoLive, so now it tells me everytime when opening that the page has no encoding, and I am comforted at the thought it is telling me and not just changing the files.

So I think the problems I was having was way more than just permissions.

[platte]

Oh, and I came to prefer changing permissions through cpanel's file manager, as I figured it was doing a better job, and GoLive does not have the number translation available. Nice to see the chmod numbers as you click the boxes.

[Website Rob]

All programs come with their quirks and we either get used to them or change programs. Don't use GoLive but sounds like you will be able to live with its quirks.

[platte]

Yep! We expect the programs to be perfect, but then we get to know them. Thanks for your input, Website Rob and DrByte.

[frank18]

..... And now all is fine, but I am a little hesitant to update from 1.3.9c, to 1.3.9d....

That upgrade is the easiest of them all - shouldn't take you longer than 10 mins. No database upgrade required either.