What about ANS?...and have you *fixed* the unicode issue?

[Sassy Romano]

CTL thanks for FINALLY listing the JIRA's as a sticky but you mention that you're pushing the failed payments through but have you fixed the underlying issue with unicode in product listings.  You didn't say either way.

Also, what about ANS?  Many of us can't even migrate to DD yet because of this missing feature.

When and where are the Q&A sessions commencing on the 2nd April?

[Zanara Zenovka]

RE: and have you *fixed* the unicode issue?

CTL, please just use the original folder name.

I can see that it might have seemed like a neat idea to deliver the exact name of the item listing, but the problems are too great for minimal gain. Think of it this way:

 - Listing name = display name - easily changed, does not necessarily give exact detail about the items delivered, sometimes just used as a dumping ground for search terms

- Upload folder name = user name - Name of the actual boxed item/folder that is delivered. May contain version numbers and other specific info that is important for inventory organisation and subsequent customer support

If you force remove the unicode from listing names you mangle people's listing titles, deliver folders with names that possibly don't make sense and damage important search terms. And how would you be communicating this change to non-English language users, esp frequent users of Unicode?

-

[Josh Susanto]

>Also, what about ANS?  Many of us can't even migrate to DD yet because of this missing feature.

Don't worry too much.

I suspect that's the next thing on their list right after making sure all the Magic Boxes are disabled.

[Michi Lumin]

"I suspect that's the next thing on their list right after making sure all the Magic Boxes are disabled."

 

^^^ this.

 

Have not heard a word directly from LL as far as ANS goes.

 

LL: A lot of us depend on ANS, not just for record keeping but for external functionality.  Support kiosks. Databases. Updates. Accessory vendors. All sorts of things. We all have different customer service models, many of them which depend on ANS.  Saying we have to rely only on 'transaction history' and manual downloads or manual views is going to crash the party for a lot of people.

 

Please. ANS. Soon. (As in, before magic boxes are disabled.)  -- As soon as you guys have ANS working, my Magic Boxes will be gone *THAT DAY*.  Promise.



[Sharie Criss]

You may want to wait until they fix the redelivery bug where it delivers gifted items to the buyer and not the recipient! It's crazy that they haven't fixed that bug yet.

[Sassy Romano]

---

Sharie Criss wrote:

You may want to wait until they fix the redelivery bug where it delivers gifted items to the buyer and not the recipient! It's crazy that they haven't fixed that bug yet.

---

 

Somewhat since that's just a trivial change of "Buyer" to "Recipient" as the deliver target.

While focussing on all the big issues is obviously important, to put a complete stop on also performing some wash up on the low hanging fruit does tend to call into question the priority handling.

This change would take mere MINUTES and before anyone at LL yells about all the QA and regression testing, seriously, you don't need to regression test a change of recipient from TOTALLY INCORRECT to RIGHT CHOICE, that's a given.

It's not a coding change that would have impact as such.

[Dartagan Shepherd]

---

Sassy Romano wrote:

---

Sharie Criss wrote:

You may want to wait until they fix the redelivery bug where it delivers gifted items to the buyer and not the recipient! It's crazy that they haven't fixed that bug yet.

---

 

Somewhat since that's just a trivial change of "Buyer" to "Recipient" as the deliver target.

While focussing on all the big issues is obviously important, to put a complete stop on also performing some wash up on the low hanging fruit does tend to call into question the priority handling.

This change would take mere MINUTES and before anyone at LL yells about all the QA and regression testing, seriously, you don't need to regression test a change of recipient from TOTALLY INCORRECT to RIGHT CHOICE, that's a given.

It's not a coding change that would have impact as such.

---

Agree that they need to stop taking things away when they implement changes as someone said above ... they already know that ANS has a good in-world use cases. If they don't, a bit of homework will fix that on their part. Or they could scan their list of calls to the old ANS, I'm sure they can see that.

On the small fixes, yes ... agree that there's plenty of obvious quick-fix issues. After you scan your own forums (which they do seem to read) and see after 50 or so posts, that a feature is pretty much a majority request for those interested, then that's something that's probably safe to go ahead and do.

Email alert for reviews or Facebook Likes ... decisions, decisions.

The larger mess in all this with the quick fixes is that for all the usefulness of development procedures, some of these no-brainer fixes can be done faster by literally writing it on a post-it note and walking it over to the persons desk and sticking it on their monitor rather than Jira's and hurry up and wait 6 months. A complete waste of money, time and resources for some of this.

Maybe they should get creative and try teal tie-dyed carrier pigeons. Then they can handle getting the memo to remote workers busy in game and side project windows as well. It's still faster and cheaper than their processes.