Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By Anonymous (not verified) on
Why does the image module not generate thumbs? Has anyone a work around for this? I just downloaded, installed and configured the image module for drupal 4.1.
the broken url of the preview image is mysite.com/tmp/tmpimg_ and a look in that directory has an image, but has unique node/or session or something id appended to it- why isn't the url getting generated to what it truely is? My feeling is that the image gets uploaded first to the images/ directory (it is there) then is put in the tmp/ directory (it is there, but a broken url), and then is put into the thumbs/ directory (is not there)
ANy suggestions appreciated
Comments
fix the release!
my goodness, lot's of people can't seem to get image module to work! http://drupal.org/node/view/1189
no thumbs, no preview, image added to wrong albums- Help! why doesn't the release get updated with these simple bug fixes, instead of all of us having to edit the module manually- all over the web there are working examples of the image module- how did they get theirs to work?
Much help kindly appreciated.
Bugfixes
Yeah a lot of bug fixes seem to stay for a long time. The only flaw with drupal is the slowness in fixing bugs and that you can't easily tell when theres a new version of a module as they not say version numbers and updated dates on the module and themes download pages.
I think something has to be thought up to improve this weakness with drupal. I have updated and bugfixed a couple of modules I use, and no doubt many people have done the same. But it shouldn't have been down to the users to all bugfix the same bugs in their modules and drupal but obviously CVS version changes daily so send the bugfixes for main version then.
Send patches to mailing list
Just send your patches to the mailing list and they do get reviewed/committed.
not only bugfixes...
Another problem is that drupal api/interface between the engine and the modules evolves fast, breaking modules written by people not involved in the engine development. And it is difficult to stick to a drupal version if you want the bug fixes and new features. The concept of 'node' in Drupal is great, and in my opinion a particular node author should have to deal mostly with managing the functionnal aspects of its node (content semantic, and features), not spending effort in adapting to a always changing interface.
unit tests
Yes, I find the "will it work" crapshoot to be frustrating as well. It would be really cool if there were a standard way to specify a set of unit tests to verify which features a module can run in its current environment, whatever version of drupal, database, other modules, etc... perhaps for foo.module, looking for an associated foo.t Then, when you install a module, you can just click on the "run tests" in the admin page, and see exactly what will, and will not work up front
here are some patches
The bug fixes for image.module for drupal 4.1
By the way, I never had trouble with generating thumbnails with GD
Could some one add this to the drupal 4.1 image.module?
\\ $obj->image_id = $edit["image_id"];
\\ return _image_tempname($obj);
\\ should be ... fixes preview thumbnail
$node->image_id = $edit->image_id;
return _image_tempname($node);
\\ $children = taxonomy_get_tree(variable_get
\\ ("image_nav_vocabulary", ""), $term_id, 1);
\\ should be ... fixes photos displayed in wrong album
$children = taxonomy_get_tree(variable_get("image_nav_vocabulary", ""), $term_id);
I was forced to write my own
I was forced to write my own image gallery scripts...
Oh yeah, the url for my site
Oh yeah, the url for my site is http://zidzari.sourceforge.net