Please Add thie Legacy Bug to the Active Bug List ! And Read Latest Info in Thread!
Ok, Moraine or whoever: it's now been over a week since there was any response at all to this problem, & that doesn't include the years since it showed up. :cry Could we please just get this onto the Active Bug List already? I mean, this is getting very tiresome and ancient. Just peek through this thread and see how much time I've wasted trying to just get this fixed. It's been acknowledged, replicated, half-understood by some people & understood by others. Please, when putting it on the Active list, do not use my original title. That title is old news. The bug is worse now, in several ways.
Please refer, therefore, to my very latest post, #31 http://dgrin.com/showpost.php?p=1911963&postcount=31 , right before this, in which I correct some info in Moraine's response. I shouldn't need to keep wasting my time on this, unless SmugMug would like to give me some months of fees back in exchange for all the bug-chasing I've worked on for ya just in this one "little" old thread. Thank you.
Ok, Moraine or whoever: it's now been over a week since there was any response at all to this problem, & that doesn't include the years since it showed up. :cry Could we please just get this onto the Active Bug List already? I mean, this is getting very tiresome and ancient. Just peek through this thread and see how much time I've wasted trying to just get this fixed. It's been acknowledged, replicated, half-understood by some people & understood by others. Please, when putting it on the Active list, do not use my original title. That title is old news. The bug is worse now, in several ways.
Please refer, therefore, to my very latest post, #31 http://dgrin.com/showpost.php?p=1911963&postcount=31 , right before this, in which I correct some info in Moraine's response. I shouldn't need to keep wasting my time on this, unless SmugMug would like to give me some months of fees back in exchange for all the bug-chasing I've worked on for ya just in this one "little" old thread. Thank you.
Adding it to the bug list doesn't change the priority. It is added to the list after it has gone through the proper backend channels.
So Anna Lisa, is this happening in New SmugMug for you? I cannot recreate in new SmugMug, nor can anyone on my team. If this is a Legacy only issue, it will not be fixed.
So Anna Lisa, is this happening in New SmugMug for you? I cannot recreate in new SmugMug, nor can anyone on my team. If this is a Legacy only issue, it will not be fixed.
I am not in New SmugMug. I've stated over & over again, loudly & clearly, that this is a Legacy issue (although there are plenty of other caption-keyword-title box issues in New SmugMug too). So I don't even know why the heck you would try to recreate this in New. Does no one read??? I've also stated clearly why this needs to be fixed in Legacy. Everyone here in these forums who's been on Legacy for a long time & has lots to migrate as I do has given many many reasons why various tasks need to be completed in Legacy before we migrate, as a host of issues exist in the migration process... things that can't be fixed without days worth of work once migration starts. I hope to heavens I don't need to list all those things for you one by one. The problem is that some of these tasks involve keywords / keyword-related organizational tasks. It becomes impossible to do these things (or maybe only possible after 12 hours of waiting in-between) now that this bug is so bad.
So how the heck do you propose that all these Legacy site-owners get around such a basic thing as not being able to see their freaking keywords that they've entered? I mean, is this really such a tough thing to fix? Seeing keywords? Making them visible? It gives me no confidence whatsoever in your team if they can't quickly pinpoint such a widespread, easy-to-replicate bug. I mean, if Andy replicated it??? Really. When Andy thought it was a bug, let me tell you, it was a bug. Some of us can't think of migrating until the ascending/descending thing is fixed, until apostrophes work, until multi-keywords work, until gallery links, group collecting, & case-sensitivity are straightened out... for starters. Why was I told that the Active Bug list was for both Legacy & New, if it's not?
I am not in New SmugMug. I've stated over & over again, loudly & clearly, that this is a Legacy issue (although there are plenty of other caption-keyword-title box issues in New SmugMug too). So I don't even know why the heck you would try to recreate this in New. Does no one read??? I've also stated clearly why this needs to be fixed in Legacy. Everyone here in these forums who's been on Legacy for a long time & has lots to migrate as I do has given many many reasons why various tasks need to be completed in Legacy before we migrate, as a host of issues exist in the migration process... things that can't be fixed without days worth of work once migration starts. I hope to heavens I don't need to list all those things for you one by one. The problem is that some of these tasks involve keywords / keyword-related organizational tasks. It becomes impossible to do these things (or maybe only possible after 12 hours of waiting in-between) now that this bug is so bad.
So how the heck do you propose that all these Legacy site-owners get around such a basic thing as not being able to see their freaking keywords that they've entered? I mean, is this really such a tough thing to fix? Seeing keywords? Making them visible? It gives me no confidence whatsoever in your team if they can't quickly pinpoint such a widespread, easy-to-replicate bug. I mean, if Andy replicated it??? Really. When Andy thought it was a bug, let me tell you, it was a bug. Some of us can't think of migrating until the ascending/descending thing is fixed, until apostrophes work, until multi-keywords work, until gallery links, group collecting, & case-sensitivity are straightened out... for starters. Why was I told that the Active Bug list was for both Legacy & New, if it's not?
Anna Lisa,
This will not be fixed on Legacy. I apologize, but better to tell you the truth then keep you hanging on. This is not an issue in the new SmugMug, and this has zero impact on the migration process.
This will not be fixed on Legacy. I apologize, but better to tell you the truth then keep you hanging on. This is not an issue in the new SmugMug, and this has zero impact on the migration process.
Unbelievable. I just explained (more earlier in the thread) why this is makes the pre-migration tasks so difficult. And here I've been, steadily wasting my own time for two years and several pages, trying my darndest to help you guys pinpoint this & get it fixed. It's something that affects everyone, not just certain browsers or certain sites, & now every way of adding keywords (bulk AND under the photo) doesn't work. But all of that time, just because in those 2 years SmugMug would never get around to fixing it, I was wasting my breath... No thanks, no fees refund, not even one shred of caring that I've honestly tried patiently to help here. It really is becoming a sorry place. Not the SmugMug I knew, not the SmugMug I want to see. Thousands of sites where people are adding keywords and can't see them & it's just fine & OK with the site.... unbelievable. And then they can't even do some of the pre-migration work. We long-term customers are what made SmugMug what it is today, but one sure wouldn't know that by the disregard we feel.
Unbelievable. I just explained (more earlier in the thread) why this is makes the pre-migration tasks so difficult. And here I've been, steadily wasting my own time for two years and several pages, trying my darndest to help you guys pinpoint this & get it fixed. It's something that affects everyone, not just certain browsers or certain sites, & now every way of adding keywords (bulk AND under the photo) doesn't work. But all of that time, just because in those 2 years SmugMug would never get around to fixing it, I was wasting my breath... No thanks, no fees refund, not even one shred of caring that I've honestly tried patiently to help here. It really is becoming a sorry place. Not the SmugMug I knew, not the SmugMug I want to see. Thousands of sites where people are adding keywords and can't see them & it's just fine & OK with the site.... unbelievable. And then they can't even do some of the pre-migration work. We long-term customers are what made SmugMug what it is today, but one sure wouldn't know that by the disregard we feel.
If the keyword is being successfully saved, as you stated, but is not "visible", why does it have an affect on your migration? Once you migrate, you will see that keyword in your photo. The keyword is there, in Legacy or New SmugMug. I am just not understanding how not seeing a keyword that is there in Legacy is preventing you from migrating.
This is not an issue in the new SmugMug, and this has zero impact on the migration process.
Hey Michael, I understand not fixing this in legacy smug, and agree that it doesn't impact migration, but I have seen the issue at least once in New smugmug. As Moraine stated, people have reported it on new Smugmug, but haven't identified the pattern that makes it start happening. If I see it again I'll definitely try to do a better job of recording more details about my process flow when I see it.
Hey Michael, I understand not fixing this in legacy smug, and agree that it doesn't impact migration, but I have seen the issue at least once in New smugmug. As Moraine stated, people have reported it on new Smugmug, but haven't identified the pattern that makes it start happening. If I see it again I'll definitely try to do a better job of recording more details about my process flow when I see it.
Comments
Ok, Moraine or whoever: it's now been over a week since there was any response at all to this problem, & that doesn't include the years since it showed up. :cry Could we please just get this onto the Active Bug List already? I mean, this is getting very tiresome and ancient. Just peek through this thread and see how much time I've wasted trying to just get this fixed. It's been acknowledged, replicated, half-understood by some people & understood by others. Please, when putting it on the Active list, do not use my original title. That title is old news. The bug is worse now, in several ways.
Please refer, therefore, to my very latest post, #31 http://dgrin.com/showpost.php?p=1911963&postcount=31 , right before this, in which I correct some info in Moraine's response. I shouldn't need to keep wasting my time on this, unless SmugMug would like to give me some months of fees back in exchange for all the bug-chasing I've worked on for ya just in this one "little" old thread.
DayBreak, my Folk Music Group (some free mp3s!) http://daybreakfolk.com
Adding it to the bug list doesn't change the priority. It is added to the list after it has gone through the proper backend channels.
Facebook
Google+
Twitter
Photo Blog
Facebook
Google+
Twitter
Photo Blog
So how the heck do you propose that all these Legacy site-owners get around such a basic thing as not being able to see their freaking keywords that they've entered? I mean, is this really such a tough thing to fix? Seeing keywords? Making them visible? It gives me no confidence whatsoever in your team if they can't quickly pinpoint such a widespread, easy-to-replicate bug. I mean, if Andy replicated it??? Really. When Andy thought it was a bug, let me tell you, it was a bug. Some of us can't think of migrating until the ascending/descending thing is fixed, until apostrophes work, until multi-keywords work, until gallery links, group collecting, & case-sensitivity are straightened out... for starters. Why was I told that the Active Bug list was for both Legacy & New, if it's not?
DayBreak, my Folk Music Group (some free mp3s!) http://daybreakfolk.com
Anna Lisa,
This will not be fixed on Legacy. I apologize, but better to tell you the truth then keep you hanging on. This is not an issue in the new SmugMug, and this has zero impact on the migration process.
Facebook
Google+
Twitter
Photo Blog
DayBreak, my Folk Music Group (some free mp3s!) http://daybreakfolk.com
If the keyword is being successfully saved, as you stated, but is not "visible", why does it have an affect on your migration? Once you migrate, you will see that keyword in your photo. The keyword is there, in Legacy or New SmugMug. I am just not understanding how not seeing a keyword that is there in Legacy is preventing you from migrating.
Facebook
Google+
Twitter
Photo Blog
Hey Michael, I understand not fixing this in legacy smug, and agree that it doesn't impact migration, but I have seen the issue at least once in New smugmug. As Moraine stated, people have reported it on new Smugmug, but haven't identified the pattern that makes it start happening. If I see it again I'll definitely try to do a better job of recording more details about my process flow when I see it.
Thank you! Keep me posted
Facebook
Google+
Twitter
Photo Blog
I am having this issue on the new SM. Keywords added to an image with existing keywords will not save.