Closed (outdated)
Project:
Drupal core
Version:
6.x-dev
Component:
system.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Jan 2007 at 00:03 UTC
Updated:
2 Mar 2016 at 22:18 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
drewish commentedQuick steps for duplicating:
- install image module
- copy the image.imagemagick.inc file from the images directory to /includes
- open up admin/settings/image-toolkit and select 'image magick'
- remove the image.imagemagick.inc file
- open up admin/settings/image-toolkit, there's no longer an option and you can't reset the
image_toolkitvariable.Comment #2
drewish commentedsomeone else ran into this over on: http://drupal.org/node/132833
Comment #3
drewish commentedi think that http://drupal.org/node/137755 and http://drupal.org/node/140401 would both be helped by this
Comment #4
drewish commentedsince this still affects HEAD i've rolled a patch that applies without offset
Comment #5
sunI'd rather stick to
because I prefer to omit a select list where nothing makes sense to select by default.
Comment #6
drewish commentedsun, i don't follow you. using the radio buttons is the current behaviour in core. in either case the user needs to be able to affect the setting, which they cannot do now.
Comment #7
sunok, let's get this into D6
Comment #8
gábor hojtsyErm, if I understand it right, the real problem is that unless the settings form can be saved, the old toolkit is tried to be used. So the description will be quite inaccurate, as it says the GD toolkit will be used, but this is not the case. Or does Drupal fall back on the GD toolkit anyway, if the selected toolkit is not available anymore? Then why not reset the setting properly at that place, where the missing toolkit is recognized? Either way, this patch does not seem to be the right fix to me.
Comment #9
drewish commentedmarking http://drupal.org/node/80019 as a dupe
Comment #10
dpearcefl commentedIs this still an active issue?