We have an issue where a client is trying to upload a full res photo, it is saying the file size is 2MB in the Mac finder window, however when opening in photoshop it is saying it is 60MB... As you can see it is full res, 5000 x 3700 pxs (approx)
When uploaded in the backend it shows broken in the image preview, but it is showing on the front end..
Has anyone else experienced this? What is the best way to handle/deal with this apart from getting the client to resize all the photos themselves?
ifusion, try heyday's optimisedimage module. We've used it to prevent this type of thing in the past.
Related
Since about a week back, I’ve started to experience failures in uploading images using the “upload files” option in “Add media”. When it fails, the upload eventually times out and I get the following error message:
Post-processing of the image likely failed because the server is busy or does not have enough resources. Uploading a smaller image may help. Suggested maximum size is 2500 pixels.
The images are relatively small. 900x500px and about 80kb in size, so the message is probably a generic one. Strangely, when I go back later to check the media page, the images have been uploaded although it gave me that error message and was stuck loading.
I don't believe it's a server issue because on my other sites which use the same theme and are on the same server, I don't have this issue.
I tried deactivating one plugin at a time but that didn’t help. Later I noticed that if I upload the original image (400 kb) it uploads with no issue. If I compress it in Photoshop (80kb) as I have always done in the past without any problems, then it gives me the error.
This is so odd. Compressing in Photoshop by setting quality to 50% (or lower) suddenly now fails upload (but work only a week ago). However, setting quality between 51-100% works fine when uploading.
Any suggestions?
I use - (BOOL)addCachedImage:(UIImage *)image name:(NSString *)name API of WKInterfaceDevice to store images.
The issue is that most of the time, when I try to use those cached image by using setImageNamed: on WKInterfaceImage, I get this Unable to find image named XXX on watch error that results in an empty image on screen.
I insist on the fact that this does NOT happen all the time.
This occurs both on simulator and on device.
Go to Assets.xcassets in the Project Navigator on the left sidebar in XCode.
There choose the image that is not found.
For me it worked as soon as I had the image placed in the "2x" placeholder.
If you just import the images they are placed in the 1x spot, but the Apple Watches seem to need at least the 2x resolution. Just optimize your images and it will all work seamlessly.
I figured out that image names that are too long (character count > 255) lead to the bug. As soon as the image name used to cache the image is shorter, I don't get the error anymore.
Seems like an Xcode bug, I am facing this issue in Xcode 7 beta 4 but not in beta 2. I researched and experimented many things including various suggestions, and it turns out that if the images are set at Universal they are not getting picked up (http://iphone.tagsstack.com/unable_to_find_image_named_ldquo_xxrdquo_on_iwatch_error). However, if you select them separately for each of the watch size, they will show up and the issue is resolved.
I've been dabbling with JCrop and I can get it working so far as uploading an image, selecting a region and then saving what I've selected to a cropped version of the original image. I can also get the thumbnail preview working, so that whatever I've selected (however big or small fits into a 150px*150px region)..so far all good.
The only problem I'm having now is saving what is in the thumbnail preview which is 150*150 and as mentioned contains whatever I have selected...
I've had a good look around on google and can't see anything to save the thumbmail preview..
Anyone come across this before?
Ok bascially what I'm doing is saving the cropped image and then saving it again but resizing it to whatever dimensions are in the preview pane....I'm not sure it gives me the an exact replica of what's in the preview pane in terms of quality but it's not so bad I guess.
When attempting to share a page on FB, many images seem to only appear AFTER running the page that contains the image through the debugger first. Additionally, the debugger seems to throw different errors for the same page in some cases, even though I've made absolutely no changes to the page. Sometimes it tells me the image url cannot be found, and after clicking on "Scraped URL:" or "Graph API: the image url is found and the image then appears in the debugger?! However, nothing seems to happen consistently and it is very difficult to replicate these issues.
I tried unsuccessfully to post the code here, however, I'm using a modified version of a script provided by Chad Von Lind (http://vonlind.com/?p=539).
Sample pages (that did not display an image until after they were submitted to the debugger):
http://greatmomentsinparenting.com/photos/warning-parents-keep-out/
http://greatmomentsinparenting.com/photos/12-hours-in-a-car/
I don't understand why the images appear sometimes, and not at other times. Is it a caching issue? Does it take time for the image to show up in the cache for a newly published page? Can I force FB to cache the image on the first try? Or is it because I'm using a dynamic image url? And by the way, the image sizes are 203x203 pixels.
Thanks!
It's media temple. I have been working with them for weeks to fix it.
Facebook 503 502 Same html different servers different results
I am working on an image management application. We have an Adobe AIR client talking to a WAMP server. The MySQL DB stores the images as blobs.
We have an image search feature. Upon searching, I am displaying the results as XMLList in a popup window and provided a download button. Downloads work fine. I also want to add a preview button to the popup.
Please let me know how can I code this. Without having the file on the client, I cannot preview. But when I use save() method, the os dialog opens up. Anything to be done on the PHP side?
Please help.
Regards
Jad.
Don't you mean to display an Image? Wouldn't the normal work? Of course, for performance issues, your PHP code must render smaller images (thumbnails).
Correct me if wrongly understood your question. :(