Posted by jackiepeters on July 5, 2009 at 6:23pm
Jump to:
| Project: | Teaser Thumbnail |
| Version: | 6.x-1.4 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
I'm using FCKededitor.
I have the ImageAPI and ImageCache modules enabled.
I have set up a preset.
I have tried both updating existing content and creating new content.
There are no records in the teaserthumbnail table in my DB.
Any idea what might be the cause?
Comments
#1
Same is happening for me. I have one site and it works. The other does not. I've spent two days trying to figure out a difference.
-The site that does not work is using the Pixture Reloaded theme, but I switched to Garland to no avail.
-I too am using FCKEditor
-I set up a preset called "thumb" and set Teaser Thumbnail to use that. It is set to resize and crop to 100X100
-I'm uploading images since i realise that Teaser Thumbnail does do linked images
-I set all permissions regarding teaser thumbnail
-I am trying to update old content as well as create new content
The only difference with my working site is that in /sites/files/imagecache/thumb, there are two directories created: imagecache and userfiles. In the site that does not work, no directories are created inside thumb. The only thing that is there is the imagecache_sample.png. I checked the permissions on the folder and set it to 777, but that did not work.
Any ideas would be greatly appreciated.
[EDIT] - it is suppressing the full-sized images from the teasers, so it is doing something--it is just not putting the teasers in.
#2
Exactly the same is happeing for me - would love to have a solution for this.
#3
I found out (half of) what was happening for me. It turned out the difference between the two sites was that the one that didn't work was in a subdirectory. When I moved the site to the root after launch, it worked properly. I did try the troubleshooting steps listed for sites in a subfolder by modding the .httaccess file, and that actually helped with some images but not for images inside the "userfiles" directory,
What I can say is whatever it was it was not the TeaserThumbnail module, but was definitely an issue with ImageCache, as other modules I later installed that relied on it also did not work. I also noticed that the preview while setting up the ImageCache preset did not work. I would look in that module's issue list for further tips to try to fix this.
Thanks,
Carl
#4
I had the same problem (no thumbnail image created and no records in teaserthumbnail table in the database).
In addition to ImageAPI and ImageCache, I am using IMCE and TinyTinyMCE (with TinyMCE) for uploading and inserting images.
After spending some time looking into the source code of teaserthumbnail module, I found what was wrong with my case. The reason of no teaser thumbnail images was because I was using absolute URLs for the inserted images by IMCE. So I changed it to use relative URLs at the common configuration page of the IMCE module, and then edit all the nodes and inserted all images again to change the image URL from absolute to relative. With this change, teaser thumbnail is now working OK.
I hope this helps.
#5
I am preparing a new version of this module that handles that use case.
#6
check out http://drupal.org/node/637714
will work with absolut URIs
#7
If i create a view that displays full nodes, this works. But if i have a view (as a block) that displays specific fields of the node, and i select both teaser AND teaser thumbnail in the View creation, it does not work. I put a dvm() in teaserthumbnail.module:teaserthumbnail_node_api() : case view. It doesnt even come to that code path, so not surprising nothing shows up in the view.
leading me to believe this module is not set up to work for Views where fields are displayed rather than the full node.
Thoughts?
#8
great module,. wasted..
#9
I'm very much aware that there are several things to be fixed; that will be done for Christmas.
#10
Once again; many people do not properly set their imagecache module or simply expect Teaser thumbnail to handle remote pictures. There may be in the future support for these use cases but if please check that:
1. Imagecache is properly installed and working (check that you have a preview when adding a preset).
2. The picture ou are including in the nodes are local (meaning in your files folder).
#11
//2. The picture ou are including in the nodes are local (meaning in your files folder).
holy shit..
that shud be sth mentioned in the module description..
u wasted so much of my time..
the module description says:generate thumbnails for your node teasers and RSS feeds from the pictures included in the body ....
such misleading advertisement of the module should be avoided..
#12
I don't find it misleading, though I am preparing documentation & tutorials for this module, moreover about 2 seconds of investigation of the code or the previous issue threads would have made you understand this. There are many modules facing that restriction, and from what I know none as yet provided a viable solution. Copying remote pictures and manipulating on your server raises copyright issues.
You're very welcome to watch your language and behavior when posting in the issue queue Tanay; all Drupal contributors are volunteers producing code that is GPL-licensed (thus free of any warranty). If you find it unsatisfying I very much encourage you to chose one of these solutions;
1. Start actually commit patches, or, hell, even your own modules (though this does include work).
2. Buy a licensed product (like Microsoft WebsiteSpark); you'll probably be able to trash their hot-lines.
Have a good day.
#13
> The reason of no teaser thumbnail images was because I was using absolute URLs for the inserted images by IMCE
I am using the wysiwyg module with tinymce.
The images are uploaded using the cck imagefield module (dependent on CCK and cck filefield).
The images are then inserted into the node using the insert module (previously known as FileField Insert).
The url to the images ends up as 'absolute'. Eg. http://domain.com/files/images/uid5/image.jpg
That's just the way this set-up works; I don't know whether it is the browser doing that (firefox does have a very long standing bug whereby if you drag an image within a wysiwyg area, it changes the url to absolute), or wysiwyg, tinymce or the insert module.
Obviously I would much prefer to have the url to images as a root relative for portability purposes, but that's a hell of a mess to sort out with all those modules as potential candidates. Any advice on this is welcome.
Anyway, the reason for this post is that the teaserthumbnail module appears to be working with the absolute url.
Also, if I manually edit the url in tinymce to /files/images/uid5/image.jpg (ie. the root relative url) it also works.
Interestingly, I have a user who (and I don't know how or why they're doing it) has managed to use www in his absolute links. Eg. http://www.domain.com/files/images/uid5/image.jpg. This DOESN'T work, and I am currently having to go through all his posts deleting the www. Teaserthumbnail appears to be *trying* to work, but imagecache does not create the thumbnail if www is in the path.
#14
Hi -Anti-,
One thing that could help me figure things out would be to have the dump of the latest entries in the teaserthumbnail table (or at least the lines for which the thumbnail is not displayed): teaserthumbnail should in theory extract the relative path from absolute URLs and save it, it actually only works IF the picture is a local resource. The entry added in the teaserthumbnail table in the end should be a relative path.
#15
Oh, I misread your post. I am wondering about the reason why your users would have discrepancies in their image addresses; if they are posting pictures from http://example.com/ then pics should be of the type http://example.com/, and if from http://www.example.com/ then pics should be of the http://www.example.com/ kind. There may be some static setting somewhere specifying the domain; settings.php? One of the modules involve in picture uploading?
#16
> if they are posting pictures from http://example.com/ then pics should be of the type http://example.com/,
> and if from http://www.example.com/ then pics should be of the http://www.example.com/ kind.
Yes, I discovered this was the problem. The url in the browser bar is used for constructing the absolute paths to the image...
I used http://domain.com to access the site, and everything worked.
The user was accessing the site using http://WWW.domain.com, and it was failing.
I have worked around the problem by forcing 'no-www' urls (using a rewrite in the htaccess file).
However, the real underlying problems are:
1)
why absolute paths are being used by the wysiwyg editors at all. Every link or path used in Drupal content should be root relative to preserve site portability. Eg. img src='/sites/default/files/resize/uid5/image_200x500.jpg' I'm going to go to the wysiwyg module project page and see if I can find out why tinymce is doing this.
2)
Why imagecache doesn't work with absolute paths containing www. This seems like a bizarre issue.
> teaserthumbnail should in theory extract the relative path from absolute URLs and save it
I don't know what's in the database, but looking at the source code of the teaser list page, the image path being used to display the teaserthumbnail is absolute.