Processing Image placeholder

Jul 27, 2011 at 7:18 PM

When uploading a large amount of pictures in 1 session (70+) I tend to get a few images that retry several times leaving me with a "Processing Image" placeholder or an empty picture in it's place. I don't think I've had an instance yet where the actual image fails to upload when I'm left with one or more of the "Processing Image" placeholders or empty pictures (image name shows up, but there really isn't a picture there). It is like it has a hiccup the first time it tries to send, retries, then the actual image shows up.

For instance, last night I uploaded 121 pictures to an album. When I went to SmugMug, it showed 126 pictures there. I then went to the gallery, many photos, delete: there were 5 of the images that either showed a "Processing Image" thumbnail or just a horizontal line with the image name.   All of these of course were in addition to the actual photo.

Has anybody else seen this (or does my explanation of what I’m seeing even make sense)?

Developer
Jul 27, 2011 at 7:22 PM

Have you checked the SmugMug upload log? Maybe there is some useful info there.

Alex

Jul 27, 2011 at 7:33 PM
Edited Jul 27, 2011 at 7:36 PM

You are fast.  Didn't even know there was an upload log.

These are not showing as errors, but as in queue.  Here is a sample:

IMG_0179.JPG 1402911933_hexstuff 2011-07-26 21:54:21 PST Complete in 20s
IMG_0177.JPG 1402911862 2011-07-26 21:54:18 PST In Queue
IMG_0178.JPG 1402911601_hexstuff 2011-07-26 21:54:12 PST Complete in 23s
IMG_0177.JPG 1402911466_hexstuff 2011-07-26 21:53:57 PST Complete in 15s

Developer
Jul 27, 2011 at 7:47 PM

I am not seeing anything that would say why the file failed to upload... Does the log contain any information about an image that failed to upload?

Did you get any exceptions in the app? If so, what were they?

Alex

Jul 27, 2011 at 7:56 PM

I can only think of 1 pictures out of around 1,000 that has failed to upload - maybe dealing with a transport stream error.

If you look at the IMG_0177 example, it actually uploaded completly, sent image 178, then 177 shows up again as in queue.

The program I'm creating is looping through each selected image in an imagelistview, and calling the upload function.  It shouldn't be requesting to send the same picture more than once (since the image is only in the listview once).

 

Developer
Jul 27, 2011 at 8:00 PM

Can you share the code you are using to upload?

This can also be something related to SmugMug. You can contact them directly and see if their logs show something more about why that happened.

Alex

Jul 27, 2011 at 8:07 PM

Sure, thanks for the help.

Private Sub My_BgWorker_DoWork(ByVal sender As Object, ByVal e As System.ComponentModel.DoWorkEventArgs) Handles My_BgWorker.DoWork
        Dim oAlbum As Album
        Dim KeyWords As String
        Dim MaxPics As Integer
        Dim i As Integer
        Dim x As Integer
        Dim sKeywords() As String
        Dim KeyWordsOut As String
        Dim blnHidden As Boolean

        oAlbum = ChosenAlbum
        MaxPics = imageListView1.SelectedItems.Count

        For Each img In imageListView1.SelectedItems
            ' Has the background worker be told to stop?
            If My_BgWorker.CancellationPending Then
                ' Set Cancel to True
                e.Cancel = True
                Exit For
            End If

            ' Get Keywords
            KeyWords = DB_Get_Keywords(img.Tag)
            KeyWordsOut = ""
            blnHidden = False

            If KeyWords <> "" Then
                sKeywords = Split(KeyWords, ",")

                For x = 0 To UBound(sKeywords)
                    If LCase(sKeywords(x)) = "hide" Then
                        blnHidden = True
                    Else
                        If KeyWordsOut = "" Then
                            KeyWordsOut = sKeywords(x)
                        Else
                            KeyWordsOut = KeyWordsOut & ", " & sKeywords(x)
                        End If
                    End If
                Next
            End If

	   i += 1

            ' Do Work
            UploadImage(oAlbum, img.FileName, img.FileName, i, MaxPics, KeyWordsOut, "", 0, 0, 0, blnHidden)

	   ' Update Progress
            My_BgWorker.ReportProgress(CInt((i / MaxPics) * 100))

        Next
    End Sub
Private Sub UploadImage(oAlbum As Album, img As String, img_Name As String, count As Integer, total As Integer, keywords As String, caption As String, latitude As Single, longitude As Single, altitude As Long, hidden As Boolean)
        ' Upload pictures to the album

        Dim up = oAlbum.CreateUploader()

        AddHandler up.UploadCompleted, AddressOf img_UploadCompleted
        AddHandler up.UploadProgress, AddressOf img_UploadProgress

        Try

            UpdateStatus_ThreadSafe(Me.toolStripStatusLabel, "Uploading Image " & img_Name & "(" & count & " of " & total & ")")

            If keywords <> "" Then up.Keywords = keywords
            If latitude <> 0 And longitude <> 0 Then up.Latitude = latitude : up.Longitude = longitude
            If caption <> "" Then up.Caption = caption
            If hidden = True Then up.Hidden = True
            If altitude <> 0 Then up.Altitude = altitude

            up.UploadImage(img)
        Catch ex As Exception
            MsgBox(img_Name & " : " & ex.Message.ToString, vbInformation, Application.ProductName.ToString)
            UpdateStatus_ThreadSafe(Me.toolStripStatusLabel, "Error Uploading Image " & img_Name)
        End Try

        RemoveHandler up.UploadCompleted, AddressOf img_UploadCompleted
        RemoveHandler up.UploadProgress, AddressOf img_UploadProgress
    End Sub
Developer
Jul 27, 2011 at 9:50 PM

I am not seeing anything that might cause the image to behave strangely in the code above.

If you did not see any exceptions while you were uploading the photos I am inclined to think that this is a SmugMug issue.

Did you email them by any chance?

Alex

Jul 27, 2011 at 9:52 PM

Not yet, was mainly just wondering if anybody else had seen anything similar.

Thanks Alex & Maria for this great interface.

Developer
Jul 27, 2011 at 9:58 PM

Now that I think about it, I did see something similar last weekend when I uploaded some photos. 

I happened to use their web interface and there was one photo out of 20 that did have this. I remember now because I had 20 photos that were uploading and 21 that were showing up.

I did not think much about it  -- and strangely, it did not occur to me even when you mentioned it.

Another place to see if this is known is dgrin.com.

If you hear back from SmugMug would you mind letting us know what they said?

Alex

Jul 27, 2011 at 9:59 PM

Sure, I just sent them an email

Jul 28, 2011 at 12:34 AM
From SmugMug:

This is actually a known issue that our engineers are aware of. Hopefully they will be able to get it fixed soon. I apologize for the inconvenience.

So, good it's on their end.

Thanks for the help Alex

On Jul 27, 2011, at 3:58 PM, alexgh <notifications@codeplex.com> wrote:

From: alexgh

Now that I think about it, I did see something similar last weekend when I uploaded some photos.

I happened to use their web interface and there was one photo out of 20 that did have this. I remember now because I had 20 photos that were uploading and 21 that were showing up.

I did not think much about it -- and strangely, it did not occur to me even when you mentioned it.

Another place to see if this is known is dgrin.com.

If you hear back from SmugMug would you mind letting us know what they said?

Alex

Developer
Jul 28, 2011 at 4:58 PM

Thanks for letting us know!

Hope they fix it soon! :)

Alex