darryl
May-03-2009, 09:55 PM
Does anybody else ever have problems like the following?
I was doing some keyword cleanup today, and a lot of times after making a change (replacing, adding, deleting), the changes would not immediately show up after clicking Save. However if I clicked on "edit", the keywords would be correct.
There was a similar delay using the Bulk Caption/Keyword Tool.
For bulk changes, I understand that some of these actions may be cached, and stuff has to reindex, whatever.
But the place where it's most disconcerting is where it seems most avoidable. If I've just edited a field, shouldn't that data be available immediately, and that's what should show up after I click Save? I guess it's just AJAX wonkiness, but I haven't seen problems like this on ... Flickr, for instance, whose database of keywords is arguably waaaay bigger.
Anyways, I wanted to try using the bookmarklet keyword shortcut hack, but the results I was getting (including completely losing some tags when trying to add more than 2-3 tags to a single photo) made it totally unreliable. I don't think it was all the hack's fault -- I think it had something to do with the AJAX lag.
Bummer. I'm currently starting to work on a Facebook-style pop-up tag editor for SmugMug (choose from a set list of tags, auto-narrow the list as you type). Ideally I could've just stayed all in JavaScript to pull the existing keywords, edited them and then post them back. But I've decided the AJAX calls are far too unreliable, so now I'm thinking of something far more hackish: open up my editor in an iframe that talks to my own server that will do all the keyword pulling and posting via the more reliable API.
I was doing some keyword cleanup today, and a lot of times after making a change (replacing, adding, deleting), the changes would not immediately show up after clicking Save. However if I clicked on "edit", the keywords would be correct.
There was a similar delay using the Bulk Caption/Keyword Tool.
For bulk changes, I understand that some of these actions may be cached, and stuff has to reindex, whatever.
But the place where it's most disconcerting is where it seems most avoidable. If I've just edited a field, shouldn't that data be available immediately, and that's what should show up after I click Save? I guess it's just AJAX wonkiness, but I haven't seen problems like this on ... Flickr, for instance, whose database of keywords is arguably waaaay bigger.
Anyways, I wanted to try using the bookmarklet keyword shortcut hack, but the results I was getting (including completely losing some tags when trying to add more than 2-3 tags to a single photo) made it totally unreliable. I don't think it was all the hack's fault -- I think it had something to do with the AJAX lag.
Bummer. I'm currently starting to work on a Facebook-style pop-up tag editor for SmugMug (choose from a set list of tags, auto-narrow the list as you type). Ideally I could've just stayed all in JavaScript to pull the existing keywords, edited them and then post them back. But I've decided the AJAX calls are far too unreliable, so now I'm thinking of something far more hackish: open up my editor in an iframe that talks to my own server that will do all the keyword pulling and posting via the more reliable API.