Legacy - Multi-keywords Edited Directly Under Photo Get Separated on "Save"

WinsomeWorks

Just like my title says. There's a bug on the Active Bug List here: http://dgrin.com/showthread.php?t=240164 but it doesn't quite spell out the Bug for when you are on Legacy itself. So if I'm on Legacy and have a keyword such as " New York " (but without the quotes), that multi-keyword sometimes breaks into two like this: New, York when edited directly under a photo. I'm in a SmugMug style gallery & sometimes to break that keyword unintentionally, all I have to do is go into the keyword box by hitting "Edit" (to add more or whatever) and when I leave that box by hitting "Save", the multi-keyword will place a comma in-between the two words.

I'm sorry I have not yet figured out why it sometimes happens and sometimes does not. It just happened a few minutes ago, and now it's not. It's possible it only happens when adding keywords to a field with keywords in it that have already been indexed. (So, they've indexed, and then you try to add more, & any previous multi-keywords that were already indexed now break up). Will get back if I find more conditions. Problem is, due to the other bug where you can't see your keywords under the photo at all (!!) http://dgrin.com/showpost.php?p=1910379&postcount=25 it's hard to know which ones I've already keyworded in my tests! Aaargh.

Allen

I always add quotes around multiple word keywords. And now always end every keyword
with a semi-colon (;) especially the last one.

WinsomeWorks

Allen wrote: »

I always add quotes around multiple word keywords. And now always end every keyword
with a semi-colon (;) especially the last one.

Wasn't / isn't there a semi-colon problem?! And then, you know how in Legacy it adds a semi-colon after each word when you bulk edit captions/keywords ? What would that do then... Lord, I can't begin to keep track of what's fixed & not. And my problem with adding quotes is that I usually don't keyword for JUST SmugMug. Drives me batty when I have to keyword certain ways for just one site. If they could all do it the same it would be so, so, so amazing. I know that's not happening anytime soon. But quotations... they can make a real mess some places.

pbandj

It's actually worse on new Smugmug...you can inadvertently break your multi-word keywords by going in to edit a caption or title. This has been reported in new Smug and is on the active bug list: http://dgrin.com/showthread.php?p=1906307

Maybe it'll get fixed in legacy as a side effect...

WinsomeWorks

pbandj wrote: »

It's actually worse on new Smugmug...you can inadvertently break your multi-word keywords by going in to edit a caption or title. This has been reported in new Smug and is on the active bug list: http://dgrin.com/showthread.php?p=1906307

Maybe it'll get fixed in legacy as a side effect...

Just wanted to say that yes, this bug on New Smug that you referenced has now been added to the Active Bug list (you probably saw it?) http://dgrin.com/showthread.php?t=240164 but from what I saw in other people's descriptions, it doesn't seem very fully or accurately described there. And I don't think it's only a rare case with certain migrated strings from Legacy, is it? Anyway, I think some of you who understand that New Smug bug thoroughly should ping M. Bonocore if the description needs to be filled out more. If it's "rare" it's not gonna get fixed soon, & I don't think it's "rare".

Just as a clarification for me and this other Legacy bug & my own migrating decision... this one's not even on the Active Bug list yet. And has the thing ever been resolved on New Smug with semi-colons? For awhile, New Smug didn't accept semi-colons as separators... can't keep track of all that's been resolved....

Allen

I have always only used only commas on legacy in the past but now started using semi-colons. Also always used
quotes for multiple word keywords. I have not had any problems on NewSmug.
Always end with a ; to be safe

key1; "key2 key3";
"key2 key3"; key4;

I've even put single quotes inside double quotes, only way I found to get KW's to sort first on keyword list
"'key ley'";

WinsomeWorks

Allen wrote: »

I have always only used only commas on legacy in the past but now started using semi-colons. Also always used
quotes for multiple word keywords. I have not had any problems on NewSmug.
Always end with a ; to be safe

key1; "key2 key3";
"key2 key3"; key4;

I've even put single quotes inside double quotes, only way I found to get KW's to sort first on keyword list
"'key ley'";

Thanks for that clarity, Al. That helps me understand the "end of the string" problem. But the big problem is, I certainly am not going to be going in & editing 100s of 1000s of keywords on New Smug just because it has stupid issues. Just... not gonna happen. I don't live for keywording! And what I was specifically referring to, is that at least when New Smug came out, there was the problem where it wasn't even accepting semi-colons as a valid separator! I assume from your post that that's been fixed. But it needs to accept semi-colons & commas as valid separators, and then it should accept multi-keywords with and without quotes. And unlike Legacy, it should keep hyphens in the word as well if it has a hyphen when added. This is the only site I know of that removes hyphens from my keywords, out of about 8 sites!

Allen

WinsomeWorks wrote: »

Thanks for that clarity, Al. That helps me understand the "end of the string" problem. But the big problem is, I certainly am not going to be going in & editing 100s of 1000s of keywords on New Smug just because it has stupid issues. Just... not gonna happen. I don't live for keywording! And what I was specifically referring to, is that at least when New Smug came out, there was the problem where it wasn't even accepting semi-colons as a valid separator! I assume from your post that that's been fixed. But it needs to accept semi-colons & commas as valid separators, and then it should accept multi-keywords with and without quotes. And unlike Legacy, it should keep hyphens in the word as well if it has a hyphen when added. This is the only site I know of that removes hyphens from my keywords, out of about 8 sites!

Hyphens were used for combining keywords so could not be used in legacy. Might be different now because they now use +