Closed (fixed)
Project:
Acidfree Albums
Version:
4.6.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
9 Nov 2005 at 06:54 UTC
Updated:
15 Nov 2005 at 22:25 UTC
Jump to comment: Most recent file
Comments
Comment #1
vhmauery commentedYou need to go to admin/settings and set the path in the image toolkit section.
Comment #2
jt6919 commentedI already did that - that is what my message meant. The path I gave is the path that is in admin->settings and it works in drupal when I use the upload and image modules for pics. However, acidfree says it's not configured right (even though it is), and it gives the error message in watchdog (I pasted it into the first message).
what does the error mean and what can I do? admin->settings already has the right path to image magick, and you didn't answer my question as to what version of Imagemagick is required?
Comment #3
toddcortez commentedPerhaps it is an issue with the version of ImageMagick? I just downloaded and compiled the most recent version, perhaps that is the issue?
Comment #4
shouchen commentedChanging the issue Title confuses mere mortal like myself.
Comment #5
jt6919 commentedI guess I'll state the problem in detail since there haven't been any understandable responses:
I already have image and upload modules installed and working (I've uploaded pictures using upload). I already have ImageMagick installed under administer->settings and my path to ImageMagick is:
/home/site/www/ImageMagick/bin/convert
The ImageMagick version and path I'm using works fine to upload pics, I think the binary version is 5.5.3 or so (2003).
Acidfree documentation doesn't say what version of ImageMagick is required.
Per the Acidfree documentation, I went to www.site.com/acidfree/test in my site and it says that ImageMagick is not setup properly. When I go to Watchdog, this error is logged for the same time that I went to www.site.com/acidfree/test:
The selected image handling toolkit 'imagemagick' can not correctly process 'image_imagemagick_check_settings'.
So, ImageMagick works in Drupal for the upload and image modules - but it is not working and spawns that error for Acidfree.
1. Does anyone know why that error is generated or what to do?
2. The Acidfree documentation does not say what version of ImageMagick is required - who knows what is the minimum version it requires?
Comment #6
vhmauery commentedfile a bug with the image module that the image.imagemagick.inc file doesn't contain the function 'image_imagemagick_check_settings'.
That is what acidfree/test is checking -- that function should tell whether or not the image toolkit is working. Obviously it is working if it works with image or other drupal stuff.
As far as I know, there really is no version that is required. We are not doing anything really special -- just calling convert to resize things.
I just committed some changes to the image manipulation code. I don't know if it will help, but it might. Check out the latest 4.6 CVS stuff or wait for it to be repackaged. (another 6 hours or so.)
Comment #7
jt6919 commentedsubmitted error to image module.
tried latest version of Acidfree, no change....nothing works.
Comment #8
vhmauery commentedI am still not entirely clear what the problem is here. Please correct me if I am wrong.
Acidfree uploading/rotating pictures is working fine, but acidfree/test says you have errors with imagemagick.
If this is the case, since you opened the bug with the image module, you should close this bug because the problem is with image.imagemagick.inc, not Acidfree.
Comment #9
jt6919 commentedI get the error in acidfree/test as described, all other items on test page are fine
and
no uploads work in acidfree.
no image uploads, nor video. I have successfully created a gallery and that's it.
when you upload, the preview page you a link back to site.com for download and nothing more.
you can upload images outside of acidfree using create content->image only using image module.
Comment #10
jt6919 commentedI checked the server error logs and there is nothing there.
I download the latest filemanager.module from CVS with acidfree patch - but no change.
when you create an acidfree image, on the preview page after submit you get no image and the link is just http://site.com/node.
when you create an acidfree image, the link is http://site.com, and the windows media player embedded in the page just keeps saying "conecting" incessantly.
I have setup and input format with no filters whatsoever for testing other than acidfree.
I am using mod_rewrite, my site is www.smorgasbord.net.
Comment #11
jt6919 commentedmaybe I have a path problem too. When I try to use the inline file filter by itself in a node and add
[inline:95]
I get 'NOT FOUND:95' for an error on the preview page, even though node 95 exists. I have changed the number to another image (node) that exists and get the same error.
Comment #12
jt6919 commentedupon further testing, I was able to get image filter by itself to recognize it's tag:
[image:100 hspace=0 vspace=0 border=0]
so why can the inline file filter (and acidfree, and img_assist) not follow the paths to nodes for some reason, but image filter somehow is?
I tested acidfree/test again to be sure, and it still says image toolkit not setup, and watchdog generated the error message again:
Type php
Date Sunday, November 13, 2005 - 3:00am
User jtpratt
Location /acidfree/test
Message The selected image handling toolkit 'imagemagick' can not correctly process 'image_imagemagick_check_settings'.
Severity error
Comment #13
vhmauery commentedAcidfree has absolutely nothing to do with image.module, [inline] tags or image_assist. So I am confused why you are mentioning them at all. Acidfree has a filter that you can use to insert images into other node bodies, but that is [acidfree:nnnn]
You have mentioned previews a couple of times. Currently, I do not support those. Previews are listed as a known limitation on the Acidfree project page. Use them at your own risk. This goes for videos and images.
Comment #14
jt6919 commentedThe image modules uses ImageMagick - so does Acidfree. The image module works fine - Acidefree still says it isn't setup right per that error. The img_assist and inline image modules use bracketed image tags, and for some reason they don't get parsed right like variables don't get passed (remember mod_rewrite is turned on).
So - I mention it because could the problem be similar? Acidefree just gives site.com or site.com/node links like variables aren't being passed correctly to it either.
What do you mean about preview not being supported. You mean, I can't create a new acidfree image or video, and click the "preview" button instead of "submit" to see what it looks like before I click "submit" and make it permanent? Are you sure we're talking about the same thing?
Comment #15
jt6919 commentedI reread the module description and see what you mean about preview. So all these test have been bad because preview doesn't work anyway.
I tried mass import for some images, and I get this error every time:
Type php
Date Monday, November 14, 2005 - 12:33am
User jtpratt
Location /node/add/acidfree/mass/117
Message Invalid argument supplied for foreach() in /home/site/public_html/modules/user_related_content/user_related_content.module on line 345.
Severity error
However, even though that error occured for every single image in the mass import, the pictures did import ok and get in the album.
I tried to import a single image on it's own - and it worked fine.
So I uploaded 2 videos, and they work, but thumbnail doesn't. I setup mplayer in my own project space since I don't have admin rights on my virtual web host. I uploaded mplayer to /home/site/public_html/mplayer/bin/mplayer and acidfree setup took the path fine (I made the binary executable of course). I did this for the ImageMagick binary, and it works. Since I set the thumbs up to use mplayer this way - now the image uploads don't work anymore....you get sound for some reason and no video at all.
I got this error from the log when that happenned:
Type php
Date Monday, November 14, 2005 - 12:53am
User jtpratt
Location /node/add/acidfree/video
Message rename(/tmp/acidfree/mplayerabFo4g/00000001.jpg): failed to open stream: No such file or directory in /home/site/public_html/modules/acidfree/class_video.inc on line 95.
Severity error
and this error at the same time:
Type php
Date Monday, November 14, 2005 - 12:53am
User jtpratt
Location /node/add/acidfree/video
Message getimagesize(): Read error! in /home/site/public_html/includes/image.inc on line 88.
Severity error
So I changed the acidfree settings to upload my own thumbnail (option 2), and that seems to work. I would rather use mplayer for thumbnails rather than creating and uploading my own. Also, I went back to the two videos that I previously uploaded and tried to 'edit' and add my thumbnail - and it wouldn't work. I had to delete them and re-add to add a thumbnail. I guess if you add a video with one thumbnail option - and switch it in settings, there's no way to edit the thumbnail option from there. There isn't a way to edit (replace) the video with another version either that I can see....at least I didn't have that option.
I'm grateful to have gotten this far, but please let me know if any of the errors above can be resolved. Also, my PHP configuration upload limit (on the acidfree/test page) is 2MB. How can I change that to make it a higher limit? Since I'm a virtual site on a shared host - is that even possible?
thanks.
Comment #16
vhmauery commentedI have attached a patch that should stop the errors from user_related_content from showing up. I cannot make acidfree work well with every other module, but we can also work on making other modules work well with acidfree. The patch is to be applied to user_related_content.module.
I am currently working with another user to try to get mplayer thumbnail extraction working a little better. So you should be able to try that again in a future release.
I am also planning on allowing users to set the thumbs for uploaded items after they are already imported. But since this is a feature, it is not as high a priority as the list of bugs you see.
To change the upload size limits, you need to change /etc/php4/apache/php.ini or a similar file (depending on your installation). If you don't have rights to do this, ask someone who does. If they don't want to let you have a bigger limit, you can always do local imports for large items. You just copy the stuff to the server in a directory apache can read from and then tell the mass import page to import from that directory.
I am closing this bug since it seems that your imagemagick problems are gone. The mplayer problems are found in bug http://drupal.org/node/36645 and the custom thumbnails feature is http://drupal.org/node/34542
Comment #17
jt6919 commentedthank you for all your help - most appreciated.
Comment #18
vhmauery commentedI just made some changes to how mass import works. I posted a user_related_content patch here earlier. Well, these changes should make that patch not needed. And if not, I might have to add some more. We will see.
Check out the latest version in CVS or wait for a few hours for it to get repackaged.