[TYPO3] Processed Images Don't Show
tronno22556 at gmail.com
Thu Apr 6 21:42:44 CEST 2006
> Hi again,
> On 4/6/06, Gilles Deacur <tronno22556 at gmail.com> wrote:
>> Tapio Markula wrote:
>>>> I can't erase or change permissions on GB/, cs/, or the pics/ folder.
>>> How they are created - if they are not automatic created
>>> by typo3 but FTP you can't delete them and change permission
>>>> Still get the exact same errors.
>>> quixplorer and the default file manager has the same owner
>>> GB/, cs/ have for some reason different owner
>> Okay, I went into the folder with my FTP and was able to delete
>> everything that quixplorer couldn't.
>> So the entire typo3temp directory is now empty.
>> Now, when I go into my "Image Processing" menu and "Reading Image
>> Formats", the red flags go up for every format under that heading. Not
>> even the images on the right hand side of the comparisons.
>> Same with "Writing GIF and PNG" and "Scaling Images".
>> "Combining Images" looks the same as the first post. I get the alert
>> error in the 1st section, but at least I can see the images.
>> "GD Library Functions" looks the same as the first post too. I can see
>> the boxes, but the font is too big for the image on the left, and I get
>> all those errors in the top of the screen.
>> Warning: imagegif(): Unable to open
>> for writing in
>> /hsphere/local/home/.../typo3/t3lib/class.t3lib_stdgraphic.php on line 2603
> There may be two problems with your install currently:
> 1. The php scripts cannot write to the folders they need to. This is
> obvious from the 'Unable to open' errors, and from the fact that you
> were able to delete some folders but not others via ftp.
> This would have been obvious to you as well, had you visited the
> 'Basic Configuration' screen in the install tool (as I suggested you
> should)! You would have--still will--an error showing that some
> directories are not writeable.
I did go into "Basic Configuration".
Here is a clip and paste of that screen:
> Have your host run a command like the following from shell:
> chgrp -R nobody typo3conf typo3temp uploads
> ('nobody' is a common name for the webserver user, it may be different
> on your server, but your host should know this...)
I asked my host previously to do this:
Q: I need a few file permission changes as outlined in this email I
received from a support forum:
If your site is on a linux box--I don't really know, in enough detail
to help you out, how it works on Windows--the user that executes php
scripts (often this user is called 'nobody') must be able to execute
scripts and read and write to certain files and directories. At the
same time, it's usually necessary for the account owner's username to
be able to read and write many or all of the same files and
directories. This can be done by making both users members of the same
Since your host is unlikely to allow your user to be a member of the
group that the 'nobody' user belongs to, the solution will probably be
to change the appropriate files so that their _group_ is 'nobody' (or
You'll need your host to do this (unless you're running a dedicated
server or VPS), but what needs to be done is something like the
following series of commands (broken up for readability):
[Assuming you're in 'public_html' or equivalent...]
chgrp -R nobody typo3conf
chgrp -R nobody typo3temp
chgrp -R nobody fileadmin
chgrp -R nobody uploads
[Assuming you're in the directory containing the directory typo3_src-3.8.1]
chgrp -R nobody typo3_src-3.8.1
So, I need the following 5 files changed:
And I got this reply from them:
Unix security does not allow users to chown(ownership) only chmod
(file permissions) -
if permission are correctly set - chown is not needed
I finally got them to change something that got rid of the errors in the
Basic Configuration screen, and was able to get to the log in screen,
but had another error. So I was able to get them to fix that error and
now I can see my back-end and the front end is navigatable. Now I can't
see images in the front end.
> 2. If this doesn't get IM working, it may be that a) IM is not
> installed, or is at a different path than you've specified--again, you
> can tell this from the 'Basic Configuration' screen in the install
The Basic Configuration screen shows exactly what I posted in an earlier
reply within this thread.
More information about the TYPO3-english