Bug #14131
closed
undefined function imagegif() when using the 1-2-3 step installer
Added by old_fred_veuerstein over 20 years ago.
Updated about 6 years ago.
Description
After installation of quickstart bigfeet-site anything works well and the logo is shown correctly in the upper left frame. Doing the manipulations of your tutorial with repeated look to the frontend, the logo is shown correctly, too.
Then, changing the color in template [1] - NEW SITE, based on standard i.e. from # 007000 to #008000 (or red, as suggested in the tutorial, the frontend doesn't show the logo but
Fatal Error: call to undefined function imagegif() in
c:\sever\xampp\htdocs\quickstart\t3lib\class.t3lib_stdgraphic.php on line 1405
IE 5.0
Apache 2.049
PHP 4.3.6
(issue imported from #M42)
Please specify your TYPO3 version! Obviously you're not using the latest version.
This looks pretty much like if your GD library just doesn't support GIF file generation!
Search Google for 'typo3 undefined imagegif' and you should find all relevant information.
Anyway, since this is really one of the top 10 questions on the install mailing lists, I suggest that we add a big red warning window in the install tool if imagegif() is not present.
This is because you have done the 1-2-3 step installation and nothing more... go to the install (typo3/install/index.php) and go to the section "1: Basic configuration"... Click on "Update localconf.php" and try again in your front end... it work for me (with 3.6.0)
OK this means that the 1-2-3 installer should check for imagegif as well, or even better: It should perform the same checks like on section 1: Basic configuration".
The installer should not call any function of a PHP extension hat might not be present without checking for the extension first.
Perhaps it could do a global check on step 1, thack check eg for PREG etc.
PHP dies/errors are not acceptable in an installer, whatever the user does.
That's an easy one. Who wants to fix it?
can we close this one?! For 4.2 we require PHP 5.2 which ships with gd with gif capabilities - so this one is obsolete now.
Well, any default installation of PHP may ship with GD, but some weird admin could have chosen to compile PHP without GD support. IMHO the installer should expect next to nothing (perhaps not even PREG) and be very defensive.
Things to check: PHP version, required extensions (eg PREG, GD, mysql), other?
I disagree, we have clear system requirements and if some is so "weird" (read stupid) to leave gd or gif support out it's his own fault. We shouldn't need to care about whether someone read the system requirements.
And come on, how likely is it that someone really compiles php without gd of gif?
We're talking about an installer. Any good installer will tell you if it can procced with the installation. But let's take the discussion to somewhere else, it's a bug tracker not a forum. And BTW, GD is in theory still optional.
The installer (in 1-2-3 mode already) could do so many checks. It could e.g. check the memory limit, which is I would say much more often a problem then the missing gd2 libraries. But it does not.
And one final note on that: Install.txt in current trunk states that GD2 is a minimum requirement for running TYPO3.
This makes it even more simple: If you want to install the system, you should (really) read at least some of the documentation coming with it. And this documentation is exactly clear on that point: GD is simply a mandatory requirement.
That should be enough of a notice to the user, right?
Martin, although I generally agree with you saying that a really good installer should warn you, if something is wrong, we can impossibly check every possible problem in the 3 steps.
That is what the rest of the install tool is there for.
So in the end: After two years of complete inactivity on this issue I think we can savely close it.
Resolved with "won't fix"
I agree with Christopher that gd is mentioned as a requirement in the docs and every recent php-package bundles it. So it's up to an admin if he decided to not compile php with it for some weird reason.
Even if the installer could and maybe should test these basic things, this is probably a task for a rework of the whole thing and we probably won't fix it in the current version.
If someone still feels that this is an important issue: Feel free to open the ticket again and provide a patch.
- Status changed from Resolved to Closed
Also available in: Atom
PDF