dkpeer

I'm also going to ask this question of tech support.

I installed typo3 through Fantastico about 2 months ago for 2 different sites. I got the basics up and running for a highschool alumni site, www.hawks84.org , then had to take about a 3 week break for job training. So yesterday I try to log into the "Back End" as typo calls it and kept getting redirected back to the main index page. After a couple of hours of checking message boards I looked at the error log via cpanel and notice typo3 complaining about the file permissions (folder being writable (fix that) then file being writable (fix that) ect...). Long story short (I did a fresh test install today) typo3 install through Fantastico creates all files and directorys chmod 0777. I don't know if typo3 has a "grace period" before it starts redirecting to the index page when the file permissions are incorrect. I do know it worked for the first couple of weeks. It is kinda cool that typo3 refuses to serve up a file or work in a folder when it percieves the file permissions being incorrect.

I thought at first my site was compromised and someone changed the permissions, but the xoops installs in the same public_html folder remained unchanged, and the site wasn't defaced.

I'm going to ask support if the file permissions are something that they can set as a default in Fantastico for Typo3 ie 644 for files and 755 for the directories. Otherwise if you do a Typo3 install immediately change the file permissions *Before* starting development on your site. Any extentions installed through Typo3 are owned by "nobody" and you cannot easily make changes afterward so you have to set the permissions mask also in the "Back End" install configuration (the menu choice "install" under tools). I finally figured out that if I updated the extentions I had installed (after setting my file/folder mask in install) Typo3 would write the new file permissions.

Hope this helps someone, it took me 9 hours to figure out what was going on, then to fix it. Typo3 is a cool CMS, but it does have a steep learning curve.

Anyone else here using Typo3? if so what do you think

-Dan

demontech

This will be a change for this later read on:
[Big Changes] PHPsuexec to be implemented on new servers

But you shoud be able to only restrict a specific user to chmod files or dirs. but not sure how.

dkpeer

Thanks for the reply demon,

Support has verified that Fantastico/Typo3 install by default with 777 permissions, making it necessary to change by hand to 755(folders) 644(files) though they have offered to make any permission changes if given the path to the installation (support rocks! I even flagged my help ticket as low and still got a responce in less than 12hrs). They are going to try to duplicate my situation and will get back to me later.

I am on SH86 so I'm not sure if they have made the changes to that server yet or not.

PS. I've given as much detail in my 2 posts incase anyone else runs into the same problem in the future and searches the forum for a solution. What I did may not be the best fix, but it got me back online (granted 9 hrs later).

dkpeer

Demon, you nailed it on the head, support verified that they have installed php suexec on the server SH86.

They also verified that Fantastico installs Typo3 with permissions of 777 which will cause the problem. Their solution (if you don't want to change the permissions on the hundreds of files and folders yourself) is to send support a ticket with the path to the installation and they will change the permissions for you.

Fantastico also installed another script (one of the project management scripts) with permissions of 777.

Issue Resolved

-Dan

demontech

Happy you got it sorted out

keyzer0

i've got similar problem with chmod and typo3 fantastico installation.
so 775 for dir and 644 for file fix the problem?

to dkpeer:
for downloaded extensions i have to set filecreatemask and foldercreatemask in backend install tool??

thanks in advance...

dkpeer

Yes it did. oops <edit> 755 for folders, I didn't try 775 </edit>

If you open a ticket with the help desk giving them the path to your install directory they can make the changes for you.

If you have time to kill making them yourself will solve the problem. Be sure the first thing you do when you can log into the backend as admin is (under "tools" on the left side) click on "install" and root out where you set default file permissions for files and folders the software creates. The default is 777. (where you found folder and file createmask (yes, to specifically answer your question)

(I'm being lengthy on my details incase someone else runs across the same issue)

Hope this helps
-Dan

keyzer0

(i've edited message. i've typed 775 instead 755. of course all 775 are 755. 775 not work)

wow! you're faster than surpass support ;-)...
thanks very much for reply...

i can do that trough ftp client...
now i'm setting files and folders to 755.
do you think that's good??

last, i have to set filecreatemask and fold.... to 755 or to 777??
my default in dummy package is 775

t.v.m.

KeyZer0

dkpeer

You're welcome,

I used my ftpclient (ws_ftp) to make the file permission changes. It allowed me to select multiple files (within a directory-not recursively) and apply the change at once.

I changed all files to 644. filecreatemask should be 644 and foldercreatemask 755, so I'd leave 755 unchanged if that is what it already is.

Those were the only issues I've ran across so far with my typo3 install. I've been really pleased with it.

-Dan