Skip navigation
Replies 1 2 3 4 Previous Next
  • Currently Being Moderated
    Aug 21, 2012 11:24 AM   in reply to Noel Carboni

    well in my case i have a file which i use to create title graphics for slider images. many of the layers are re-used and most of them would never need editing but not being able to add new savavble layers is certainly worse then then just not being to edit old ones, granted obviously both still suck. i agree completey with your comments regarding Adobe addressing what is at this point a wide spread customer support issue in addition to being a technical one.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 27, 2012 2:12 PM   in reply to D.Estabrook

    Just wanted to add another (very) unhappy purchaser of CS6 .. this "bug" has now affected two projects and has cost me both time and money not to mention some client relation problems due to a missed deadline.

     

    Photoshop is the tool of choice for our detailed web comps and unfortunally for us these usually have many text blocks. Unacceptable.

     

    Please keep us updated on the progress of a fix or at least a workaround. And I agree with some of the other posters here .. this should really be told to any new purchasers of Photoshop CS6.

     

    Brian.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 27, 2012 11:55 PM   in reply to jointmedias

    The same happened to me....
    "Clicking on any text layer it is replaced by text from another layer in my document".. in my file the new text frame has moved a bit left from the original position

     

     

    I do agree with 81.jointmedias: "this should really be told to any new purchasers of Photoshop CS6." The bug was causing me a major panic while I was editing a huge website presentation for a customer... the whole project with corrupted text layers was gone one morning. Fortunately I was able to recover the files from the backup files, but it took me a lot of time to figure it out what was causing the problem.. So, I'm back with Photoshop CS5 and the rest of our designers until CS6 update..

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 28, 2012 9:19 AM   in reply to D.Estabrook

    I appreciate your frustration with how long this is taking to resolve. There's not a lot more I can offer about the status of this issue; as I've already indicated, this is a top priority bug, and has received considerable engineering and test resources over the past weeks. We continue to monitor the forums for posts about this issue, and as soon as I can share more information about how and when this will be resolved, I will do so. Sorry I don't have more at this time, but please don't mistake the lack of information for a lack of concern or a lack of committment to fix this problem.

     

    Paul

     
    |
    Mark as:
  • Noel Carboni
    23,496 posts
    Dec 23, 2006
    Currently Being Moderated
    Aug 28, 2012 9:37 AM   in reply to PDFerguson

    Paul, it's easy to see you've given us all the information you're allowed to give.  Thank you for that.

     

    But perhaps what D.Estabrook is implying is that Adobe's current policy that keeps you from offering more detail about the status of this issue should be reconsidered.

     

    It occurs to me that for cheap, simple software people are pretty much willing to deal with opaque development and "it is what it is, take it or leave it".  However, at the prices Adobe charges, a user purchasing a license is becoming a business partner with Adobe more than an end user.  This is especially true with the subscription model now.  People in partnership roles expect a certain amount of communication.

     

    Something you might pass back to your management is that it wouldn't be evil if you were to be allowed to say a bit more about who was doing what to what part of the system.  Offering a little insight into how things are put together behind the scenes actually does allow users to become more educated on how it works and ultimately to make better results.  You'd not be "giving away the farm" by describing a bit more about what's gone wrong, and what you're doing to fix it - and maybe, just maybe some users might even be able to think up workarounds you haven't thought of.

     

    Don't get me wrong, Adobe is more open than many big companies (try to engage a Microsoft engineer at all, for example), but things could be better.  Maybe you ought to try to be more of a little company that just happens to have big resources.

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 30, 2012 3:46 AM   in reply to PDFerguson

    Hi, any chance that Adobe might confirm whether or not today's 13.0.1 update resovles this issue?

    "The Adobe Photoshop 13.0.1 update includes many critical fixes improving security, stability and performance while also addressing a number of high priority bugs with 3D, Crop, Type, Painting, Paths, and Shapes."

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 30, 2012 9:26 AM   in reply to J.Y. Design

    i think it actually made one my files worse now the new layers are breaking so im guessing the update does have soemthing to do with bug. would be nice if adobe could provide some clarity as far this issue as it pertains to 13.0.1 and best methods for rebuilding files.

     

    Are these files totally screwed for all time and is it even safe to copy and paste layers from these files into to new files or would that infect the new files?

     
    |
    Mark as:
  • Noel Carboni
    23,496 posts
    Dec 23, 2006
    Currently Being Moderated
    Aug 30, 2012 10:03 AM   in reply to ubernaut

    I think you really need to create a new document (or at least open one that has no prior text layer corruption in it) to determine whether 13.0.1 solves this issue. 

     

    Editorially, 13.0.1 had better solve this issue.  Adobe has known about the problem for 4+ months.

     

    Additionally, Adobe needs to do something they've not done before (at least not recently):  Set the new build to be used for trial downloads.

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 30, 2012 10:06 AM   in reply to Noel Carboni

    Noel Carboni wrote:

     

    I think you really need to create a new document (or at least open one that has no prior text layer corruption in it) to determine whether 13.0.1 solves this issue.

    how you prove a negative though that's why i think only adobe can verify this issue was addressed unless someone has figured out how to induce the fault and i missed that.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 30, 2012 10:49 AM   in reply to ubernaut

    I have a file with only two text layers that developed the problem. It was easy to "fix" using PS CS5 in this instance since all I needed to do was reposition the bug-swapped text layers. I've done some editing to the layers and resaved the file since and have yet to see further misbehavior from the file. ubernaut_4 is right, we'd need to know what triggers the bug to know if a "fixed" file can ever be fully trusted. I'd also like to know if a new file can be "contaminated" by dragging text layers to it from a corrupted file.

     

    Seriously, there are many of us who would like a more detailed post-mortem for this bug.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 30, 2012 10:55 AM   in reply to BJN3

    i know this is off topic but my handle is actually supposed to be "ubernaut" its an adobe shortname i have had for years and i figured since i have been going back and forth with customer service about this since creative cloud came out and my handle got all jacked up and that some higher ups might be watching this thread i would beg for someone to please fix that. aside over…

     
    |
    Mark as:
  • Noel Carboni
    23,496 posts
    Dec 23, 2006
    Currently Being Moderated
    Aug 30, 2012 6:09 PM   in reply to ubernaut

    Adobe has said they addressed the bug.

     

    But I agree, more transparency would be good.  Adobe should not assume everyone is dumb as a post about what's going on inside their computers..

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 30, 2012 6:19 PM   in reply to Noel Carboni

    can you send a link?

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 16, 2012 3:15 PM   in reply to PDFerguson

    Hi, just wanted to add my name to the list of concerned clients who are affected by this attrocious bug.

     

    It would seem that on the day this post was made, I began working for my new employer, and commenced working on a draft wireframe/storyboard for a new high level project using PS as my tool of choice. They had purchased me that latest versions of all the software I required for my role as their newly recruited web dev. After spending a good few days working on the drafts and then taking the products to a show and tell meeting with my colleagues we identified some creases which needed ironing out of the system spec for our project, before I was to commence development with my new team.

     

    I went back to my desk and began to edit my files only to be distraught at the fact that the 3 solid days I had spent working on my first project with my new employer had been completely wasted as a result of this bug....

     

    Can you please keep us up to speed as to how the fix for this is progressing, so that other  unfortuate souls are not going to be expossed to potentially career limiting situations such as this from arrising? I do think you have a resposnisbility to do as such for your valued customers and I am certain that everybody else affected by it here would sincerely appreciate it.

     

    Regards,

     

     

    Mark

     
    |
    Mark as:
  • Noel Carboni
    23,496 posts
    Dec 23, 2006
    Currently Being Moderated
    Sep 16, 2012 3:27 PM   in reply to PS De Resistance

    They say they fixed it in 13.0.1.  Do Help - Updates...  in Photoshop to get that update.

     

    Files already corrupted are not fixed by this; but it's my understanding that it won't corrupt new files.

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 16, 2012 3:56 PM   in reply to Noel Carboni

    So actually i have found that under 13.0.1 the problem is semi resolved even for already corrupted files. Any new or edited layers now retain the attributes when even after save/reopen and typically all you lose when editing an existing corrupt layer, typically, is font, text content (which be retrieved via the layer name prior to edtiing, typically) and color. So the layer style itself is usaully intact, at least on mac, it's a pain but can usually be ignored unless you actually need to change a layer's text content. If you duplicate the layer first before editing you can avoid most of the pain since that helps you replicate the layer appearance faster and more acurately.

     

    i learned all of this becasue one of my files is so importnat that i had to continue using it all throughout the bug and even now after the fix some of those corrupted layers may remain so for all eternity but at a certain problem i will barely remember they are. Long story short, all hope is not lost for these files, at least for my problem file, as far as i can tell, up to this point.

     

    P.S. i do realize i put a ton of qualifiers on that but given i have only one sample to dervie my personal conclusions from that's what you get.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 16, 2012 4:16 PM   in reply to ubernaut

    P.S. i do realize i put a ton of qualifiers on that but given i have only one sample to dervie my personal conclusions from that's what you get.

     

    That is understandable. Qualifiers are often very useful.

     

    Thank you for reporting your tests and observations.

     

    Good luck,

     

    Hunt

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 25, 2012 10:28 PM   in reply to Bill Hunt

    I'd like to reply with this with hopes you guys have more info.

     

    I have the same issue but when I try to adjust the image size or canvas it goes ballistic. All of the text gets replaced without me actually using the Text Tool.

     

    Hope it helps. Do you have an update? It's unfortunate, I have a very large file and I am unable to sort it out as I lost my last-non corrupt file.

     

    Thanks!!

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 25, 2012 11:12 PM   in reply to Hyrule Guardian

    The 13.0.1 update should have fixed it.

     

    But your existing files are still corrupted -- you'll  have to rearrange the text layers by hand.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 26, 2012 12:13 AM   in reply to Chris Cox

    Hello Chris, can you then confirm that the text layer bug is fixed with 13.0.1? Can we once again start using Photoshop CS6 without fear of text layer corruption?

     

    Andy

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 26, 2012 3:09 AM   in reply to aconda

    All seems to be fine now - I have been using cs6 for a little while again and no problems so far

     

    Thanks - Chris

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 26, 2012 3:18 AM   in reply to CCdroid55

    Thanks, it would still be comforting to hear an official statement. Confidence level is low right now.

     
    |
    Mark as:
  • Noel Carboni
    23,496 posts
    Dec 23, 2006
    Currently Being Moderated
    Sep 26, 2012 5:20 AM   in reply to aconda

    aconda wrote:

     

    Thanks, it would still be comforting to hear an official statement. Confidence level is low right now.

     

    If not an "official statement", what do you consider Chris Cox's message in post 100 above?  Did you not notice the [staff] indication and eye-burning white background?

     

    Companies don't gift wrap admissions that they've screwed up.  You're lucky a plain-speaking engineer is even calling it a "fix" and not some marketeer spinning it as "enhanced reliability when working with text".

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 26, 2012 5:37 AM   in reply to Noel Carboni

    An official statement doesn't include the words "should have fixed it", it would normally state something in the line of

    "the problem has been resolved"... So yeah there you have it, I can't afford to screw up work files, so until I have a positive answer I can't use Photoshop CS 6 even though I've been paying for it since 3 odd months now.

     
    |
    Mark as:
  • Noel Carboni
    23,496 posts
    Dec 23, 2006
    Currently Being Moderated
    Sep 26, 2012 5:52 AM   in reply to aconda

    I'll be curious if anyone from Adobe will clarify the wording for you beyond what's already been stated.

     

    I think it's interesting this particular bug-fix, possibly one of the most egregious in the product as initially released, didn't make the list.  It doesn't even fit in any of the categories:

     

    http://blogs.adobe.com/photoshopdotcom/2012/08/photoshop-cs6-13-0-1-up date-now-available.html

     

    But hey, more power to you for asking.

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 26, 2012 8:38 AM   in reply to Noel Carboni

    @noel that's funny because it's true.

     

    @hyrule nice handle btw, because the image size typically refactors all style and sizes of text layers i would expect that would be an extremely good way to flush out any corrupt layers but under 13.0.1 you shouldnt be creating any new corrupt layers. im not sure if ive tried this yet but if you just wish to retain appearance of the layers and do not need to edit them you should be able to just rasterize the layers in question before resizing. not sure why canvas resize is having that effect probably shared code from the two functions or some thing like that.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 26, 2012 11:07 AM   in reply to aconda

    I did not fix this bug myself - so I don't personally know what exactly was wrong, how it was fixed or tested.

    So, from my viewpoint, you're going to have to live with some qualifiers.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 26, 2012 1:25 PM   in reply to Chris Cox

    Well I'm not exactly sure what "you're going to have to live with some qualifiers", but it kinda sounds like, "I have no interest in this posting and I hate my job"!

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 26, 2012 1:27 PM   in reply to aconda

    No, more like "I can't give absolutes because I didn't see it myself".

     
    |
    Mark as:
  • Noel Carboni
    23,496 posts
    Dec 23, 2006
    Currently Being Moderated
    Sep 26, 2012 2:38 PM   in reply to aconda

    aconda wrote:

     

    I can't afford to screw up work files

     

    Aconda, did you start using Photoshop CS6 for real work the day you bought the new release?  Or did you do test projects with it, and read all the forums so that you knew exactly what was wrong with it?

     

    Now you claim you won't start using the updated version again, even after someone on the inside says the problem was fixed by his co-workers until...  What?  You get some kind of personal guarantee from Adobe's CEO that says the problem is definitely fixed, and that if it happens again he'll come over to see you to fix it himself?

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 26, 2012 2:42 PM   in reply to aconda

    Easy, aconda, we're all just trying to help here.

     

    The absence of this issue in Barry Young's blog post is an oversight, this was a critical bug and we believe it has been fixed in 13.0.1.

     

    In all our testing we were unable to trigger this problem in new files after we had made the changes we believe were the root cause, so we have a high degree of confidence it has been resolved. However, there may be files created in earlier versions of Photoshop that will still exhibit text corruption, and may even appear "normal" when first opened, but that is an artifact of how text layers work in Photoshop. The fix in 13.0.1 does not attempt to repair files that had already been corrupted, which in some cases may lead to confusion about whether this has been fixed.

     

    I hope this helps, and again, we apologize for the problems this has caused.

     

    Paul

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 26, 2012 11:54 PM   in reply to Noel Carboni

    Noel, no I started using it and it corrupted some of my files which just happen to have had hundreds of text layers in them... and no I didn't test it first, why would I? Who would ever have thought that a major release would completely screw up ones work? Not me! I wasn't expecting anything like that so now I'm back with CS5. I've been using graphic products from Adobe since around 1995 and have never seen such a major hiccup as in this release.

    You don't have to be sarcastic either, I sent in files to Adobe to hopefully help with the identification of this bug! I don't expect the CEO to come over and give me a perosnal fix so don't even go there trying to mock me.

     

    If you read the statemenent that the bug "could" have been fixed then you should understand that that's not a definate "we have fixe the bug". So why should I consider a "could" would be a definate fix?? Why would I risk corruption of new projects before I know for a fact that the problem has been resolved? That would be niave.

     

    So, Noel hope that answers your questions. Yeah I wrote something yesterday that was out of order and I will apologize to Chris for that. Doesn't mean you have a right to atatck my judgement. So all is cool and I wish you a good day.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 26, 2012 11:57 PM   in reply to PDFerguson

    Paul, I was out of order with my comment to Chris and I apologize. It's no excuse but I just had a bad day in the design studio and getting frustrated that Adobe couldn't give an official OK on this problem.

     

    Kind regards

     

    Andy

     
    |
    Mark as:
  • Noel Carboni
    23,496 posts
    Dec 23, 2006
    Currently Being Moderated
    Sep 27, 2012 6:16 AM   in reply to aconda

    I suggest that the next step needs to be this:  Just start using 13.0.1. 

     

    It's said to have fixed the text layer swap corruption problem, as well as many other problems.

     

    You're apparently not going to get a better answer from Adobe, so it's up to you whether to trust their software again.  The rules aren't really completely different now, just because it had a bug.

     

    Yes, they should have stopped the release and fixed that bug before the software ever got to you, but they made a mistake.  But that doesn't mean the software will be bad forever more.

     

    13.0.1 is in every way I can see an improvement.  I haven't read one complaint on any of these forums of 13.0.1 adding corruption, while there were plenty against the software before that. 

     

    I think Adobe may have been particularly gunshy about breaking new things and so tested the 13.0.1 changes very thoroughly.  Is it bug-free?  No, but it's better, and this particular problem seems to be gone.

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 27, 2012 9:59 AM   in reply to Noel Carboni

    I didn't mean to spark such controversy over this.

     

    I also think (Forrest Gump Dixit) "it happens" and well, this time I got affected by it.

     

    I will stick with Adobe, think they are great. One small nuisance and I think too many go into a fracas over it.

     

    Regards,

     

    Marco

    http://www.webmentor.cr/

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 27, 2012 1:05 PM   in reply to Hyrule Guardian

    "Small nuisance" for you perhaps. I've only had a handful of files corrupted and dealing with that issue has cost me several productive hours. And I've seen examples of corrupted files where recovering that file alone would take several hours work. This is professional software and serious bugs like this can be very expensive. What's worse than time rebuilding artwork is missing deadlines. Few clients are sympathetic to "Photoshop corrupted your artwork".

     

    For many of us this isn't even close to the same league as nuisance bugs or even application instability issues.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 27, 2012 1:21 PM   in reply to BJN3

    Let me remind you of a few things things

     

    1) You upgraded to a software version that has been released not too long ago. A huge project like Adobe CS6, and it's make over and it's changes are projects that will have bugs. No matter what and how hard they try to minimize them. It happens every.single.time. Be this an OS upgrade, whichever. It's part of the cycle of software development. If you went in anyway by upgrading, you went in willingly at your own risk. This is why it's always prudent to wait for the FIRST patch before you upgrade. You and I didn't.

     

    2) I was affected by it as well and I have had to do the same things you did. Quid pro quo. The hours I save due to upgrading and having shortcuts that add up to HOURS when editing comps in PS are still superior to the hours I have lost rebuilding the corrupt comps.

     

    3) Where is your back up? Surely you must have it?

     

    Marco

    http://www.webmentor.cr

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 27, 2012 1:31 PM   in reply to Hyrule Guardian

    I agree with the point about using new software, but loosing or corrupting data is one of the bigest "No-No's" out there. Looking back in this thread this issue was reported during the beta, but still made it out the door - and that should have never happened


    As far as back-up's are concerned this could be a new file and you would not know when to back up as the file could already be corrupt. It also begs the question of when is it safe to use a new product? The latest release fixed some of the reported bugs - but looking through this forum there are a boatload that still need to be fixed

     

    Mike

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (1)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points