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 MVRider on
All,
I've been trying to come up with a way to explain this in a coherent manner...have found the way so here it is:
Simple Facts:
1) I created a new module (tsearch) that replaces the drupal search module for performance reasons (replaced with PostgreSQL TSearch2).
2) I have another module that handles images that are uploaded. It resizes them and displays them via something like so:
<img src="image.php?file=path/image_name.jpg">
This upload module has been working perfectly for about 1 year. So this is not a concern. I have also added many modules since it has been installed.
Final Result/Problem:
When I enable the new search module the images in my other module stop displaying...wtf. I've had multiple people look at it and they have no idea what could be causing it. The only thing that makes sense is that the httpd headers are being broken some how which then the client browser has no idea how to render it.
I hit the image.php file directly in the browser and see the raw image file being returned so I know it's finding the files.
Any thoughts would be great!
Cheers!
Comments
Also tested....
Forgot to add that I tested the search module enable but a blank file no data at all in it.
The images still stopped displaying, I disable the search module and they come back.
WooHoo Fun for Me!
Without code it is hard to guess
Without code it is hard to guess, but if the module is moduled after the search module, it does not do much except when performing a search. As such I would not expect it to output much except for the search block. One thing to try then would be to comment out the block function and see what happens. Other things to look for are calls to drupal_set_head() and drupal_set_header() or other code that is producing output.
One approach to looking at this is disable your search module, visit some page with images, view the html source and save. Now enable your search module, visit the same page and again view and save the html (to a differenct file). Now compare the two files and examine what your search module adds to the output.
Completed part of that...
The search module doesn't modify the header at all. And I removed all data from the module to see if it was data related and still had the issue. It was as if I enabled to many modules or one too many.
I will try the code diff with and without the module just for the sake of trying everything.
tsearch2 module?
Could you please share?
--
The news is Now Public | Drupal development: making the world better, one patch at a time.
--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.
Contribute?
chx,
Not sure what you are asking...code, module (contribute), etc.
I will be more then happy to contribute the module once I have worked out all my issues. It is based on PostgreSQL and will not work with MySQL.