![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
saffronharePart 17: When one receives a message stating, "[ItemCodeA]* is not [ItemCodeB] please change file names."
If one were to read this message, and see that all one's files were named [ItemCodeA], one might think, "Hey! I'm all set! Mine are correct already!"
Except one would be mistaken. Because the sender of this message intended to write this instead: "[ItemCodeA]* is now [ItemCodeB] please change file names."
Changes everything, doesn't it? Which is what I had to do. Change everything. Which broke all the links in MailShop. Which then had to be re-linked. About two hours of work, made even more ass-chapping because I thought for one brief, shining moment that I wouldn't have to do it after all.
*Here, item codes are keys that allow one system to access another and determine things like inventory. Not so very exciting, but there you go. Very important to my life.
If one were to read this message, and see that all one's files were named [ItemCodeA], one might think, "Hey! I'm all set! Mine are correct already!"
Except one would be mistaken. Because the sender of this message intended to write this instead: "[ItemCodeA]* is now [ItemCodeB] please change file names."
Changes everything, doesn't it? Which is what I had to do. Change everything. Which broke all the links in MailShop. Which then had to be re-linked. About two hours of work, made even more ass-chapping because I thought for one brief, shining moment that I wouldn't have to do it after all.
*Here, item codes are keys that allow one system to access another and determine things like inventory. Not so very exciting, but there you go. Very important to my life.
