20 minutes and counting to replace one photo?

dogwood

I've been waiting twenty minutes now after clicking "replace photo" on a print order. That's twenty minutes for a single photo. They ordered six photos total-- please, please don't tell me it's going to take over two hours to replace all six photos!

I used to love proof delay, but I'm not feeling the love today. :cry

Isn't it time to consider another method of replacing photos? Bulk replacing using something similar to star*explorer?

dogwood

Update: I finally cancelled the replace photo (after 25 minutes) and then went to my control panel-- sales and looked at that print order. The watermark was different on that photo, meaning it was replaced, only my "replace photo" screen never went away.

How do we know photos were replaced if the "replace photo" screen doesn't go away?

jfriend

dogwood wrote:

I've been waiting twenty minutes now after clicking "replace photo" on a print order. That's twenty minutes for a single photo. They ordered six photos total-- please, please don't tell me it's going to take over two hours to replace all six photos!

I used to love proof delay, but I'm not feeling the love today. :cry

Isn't it time to consider another method of replacing photos? Bulk replacing using something similar to star*explorer?

This is just a work-around for the slow processing time, but you don't have to do your replace photo operations in serial order. You can start one, then open a new window, start another, etc... So, you can do them all in parallel and get it all done in 20 minutes or so.

It's still ridiculously slow and I've also asked for API support for replace photos so apps like StarExplorer could make a better way. That would be a nice enhancemenet, particularly now that replace photo is used so often by pros in combination with proof delay.

Andy

jfriend wrote:

I've also asked for API support for replace photos

Me too!

dogwood

jfriend wrote:

This is just a work-around for the slow processing time, but you don't have to do your replace photo operations in serial order. You can start one, then open a new window, start another, etc... So, you can do them all in parallel and get it all done in 20 minutes or so.

Oooohhh... this is a great idea! This never occured to me, thank you! I know it's not ideal, but better than the method I've been using (replacing one by one and only one at a time).

Nikolai

jfriend wrote:

It's still ridiculously slow and I've also asked for API support for replace photos so apps like StarExplorer could make a better way. That would be a nice enhancemenet, particularly now that replace photo is used so often by pros in combination with proof delay.

And once API is there I promise I'll do it asap...

dogwood

Nikolai wrote:

And once API is there I promise I'll do it asap...

That will be very, very nice!

jfriend

Nikolai wrote:

And once API is there I promise I'll do it asap...

Now all we need is for Devbobo to tell us when the new API will be ready!

devbobo

jfriend wrote:

Now all we need is for Devbobo to tell us when the new API will be ready!

I am working on it...unfortunately, I am not 100% dedicated to the API.

I would like to say it will be ready within the month, but we'll just see.

There is also a chance that I can roll out the replace photo functionality separately from the new API, but I have a configuration issue atm which is preventing me from testing my changes.

Nikolai

devbobo wrote:

I am working on it...unfortunately, I am not 100% dedicated to the API.

I would like to say it will be ready within the month, but we'll just see.

There is also a chance that I can roll out the replace photo functionality separately from the new API, but I have a configuration issue atm which is preventing me from testing my changes.

David,

it would be awesome to have it in the production one. The "New API" is too much of a pie to support quickly.

The easiest way (for me as a programmer to use, that is) to work with it would be to have an extra optional ImageID parameter in the upload image structure (maybe along with image keywords while we're at it? ). If it's not empty/not zero - it means replace the image with this ID.

Many, many Pros will be eternally grateful for this change. I can't tell you how many times I had to turn such requests down...

devbobo

Nikolai wrote:

David,

it would be awesome to have it in the production one. The "New API" is too much of a pie to support quickly.

The easiest way (for me as a programmer to use, that is) to work with it would be to have an extra optional ImageID parameter in the upload image structure (maybe along with image keywords while we're at it? ). If it's not empty/not zero - it means replace the image with this ID.

Many, many Pros will be eternally grateful for this change. I can't tell you how many times I had to turn such requests down...

Nik,

Yes, I am going to add an ImageID parameter to the existing upload methods.

Cheers,

David

Nikolai

devbobo wrote:

Nik,

Yes, I am going to add an ImageID parameter to the existing upload methods.

Cheers,

David

Sweeeeeet!
(and keywords? :hide)

devbobo

Nikolai wrote:

Sweeeeeet!
(and keywords? :hide)

maybe

Nikolai

devbobo wrote:

maybe

Say when, I'll help you with testing...
(shoot me a format of API, I'll prepare the version, you'll be able to use it as a test platform, too:-)

devbobo

Nikolai wrote:

Say when, I'll help you with testing...
(shoot me a format of API, I'll prepare the version, you'll be able to use it as a test platform, too:-)

Nik,

which upload method are you using ?

xmladd.mg or rawxmladd.mg ? or something else ?

Nikolai

devbobo wrote:

Nik,

which upload method are you using ?

xmladd.mg or rawxmladd.mg ? or something else ?

Don't remember, need to look in the code... will tell you in 2-3 hours.. One of the latest/fastest ones...

dogwood

Nikolai wrote:

Many, many Pros will be eternally grateful for this change.

Even us guys just trying to be pros would appreciate this change!