I tried to create a photo blog, very simple, and I thought that drupal 7 has everything I need. I just wanted to create a custom content type, with a title, story, image upload and tags. And because drupal 7 will be out soon it seems like a good idea to start developing in it.
But, with an out of the box install of Drupal 7 Alpha 6 I discovered that the image is uploaded properly, but no derivatives are created. Currently I run an nginx server with php 5.3.3, but I tried of course with a normal LAMP, on linux on windows, with php 5.2. Again nothing... Also, I have to mention that permissions are properly set, and accordingly to an existing bug report about jpegs with EXIF I tested also with and without EXIF in the images. Also I tested with png and gifs. Still nothing. I also have to mention that I am not using 3rd party modules, wysiwyg or themes; everything is by default in the core.

Am I missing something?

Thank you in advance,
Vlad.

Files: 
CommentFileSizeAuthor
#12 drupal.field-ui-php53.12.patch1.02 KBsun
PASSED: [[SimpleTest]]: [MySQL] 22,945 pass(es).
[ View ]

Comments

Version:7.0-alpha6» 7.x-dev
Priority:Major» Critical

I forgot to mention that it works in the stable 6.17 version of drupal with GD of Imagick.

care to try the latest dev?

Assigned:VladGh» Unassigned
Priority:Critical» Normal

this isn't critical (lost data), neither major (complete break one funcionality), it's a normal bug.

Also if is assigned to you, people will think that you are working on a fix.

I'm sorry for not posting this issue correctly, but I considered that an impaired function of one of the most important modules in drupal core can be considered critical or at least major (after all, drupal is a content management platform). In my defense, I studied the issue queue handbook, and the priority levels of issues, which are very clear:

Critical: When a bug renders a system unusable (not being able to create content or upgrade between versions, blocks not displaying…), and security vulnerabilities.

Major: For issues which have significant repercussions, but do not render the whole system unusable. For example a PHP error which is only triggered under rare circumstances or which affects only a small percentage of all users.

I don't see anything related to lost data or braked functionality.

PS ddorian: I tested also today's 7.x-dev and the CVS HEAD with the same result.

Is there any relevant information in your watchdog table or php logs? If you go to admin/reports/status are either of the GD related line items not green?

Status:Needs work» Closed (duplicate)

This is the only error I have in the watchdog:

Location http://dev.vladgh.com/system/ajax
Referrer http://dev.vladgh.com/admin/structure/types/manage/photo/display?render=...
Message Warning: Parameter 5 to image_field_formatter_settings_form() expected to be a reference, value given in module_invoke() (line 728 of /srv/www/dev.vladgh.com/includes/module.inc).
Severity warning

Status reports GD working properly, and no errors in the php logs.
I think the above mentioned error is due to php 5.3 so I will make some more tests with php 5.2.

After a few more tests I discovered that this is indeed due to php 5.3.3. It works great in 5.2. I also discovered that in Structure > Content Types > Manage Displays, the "submit query" button is not working (it was supposed to display the style options for each display such as full view, teaser etc.). I also tried the patch suggested in #844676: (Tests needed) Stream wrappers stream_seek() return is invalid without success.

Title:Image module does not create thumbnailsField formatter form parameter $form_state is not really passed by reference
Priority:Normal» Critical
Status:Closed (duplicate)» Active

Ok, I can confirm that the error message is legit. We apparently have some serious holes in the automated testing of the field UI :)

That said, I don't know how this could result in the thumbnails not being created.

Priority:Critical» Normal

Sorry, not critical until we confirm this is the source of the bug.

In the Drupal 7 RC1 we have to dedicate time to improve the tests..

Title:Field formatter form parameter $form_state is not really passed by reference$form_state not passed by reference to hook_field_formatter_settings_form()
Component:image.module» field_ui.module
Status:Active» Needs review
StatusFileSize
new1.02 KB
PASSED: [[SimpleTest]]: [MySQL] 22,945 pass(es).
[ View ]

Can this even be tested?

Status:Needs review» Reviewed & tested by the community

A classic. call_user_func_array() vs by ref args. My bad.

And yes, we do have some serious holes in Field UI testing - #600544: Tests for Field UI

Status:Reviewed & tested by the community» Fixed

Committed to CVS HEAD. Thanks.

Thank you guys, that was fast...

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.