Thanks for coming to InDesignSecrets.com, the world's #1 resource for all things InDesign!

When an “Update” Isn’t an Update

A few people I know—well actually it was me—got confused when they looked at their Adobe Creative Cloud desktop manager and saw that the listing for InDesign as well as the other Creative Cloud 2014 applications were listed as “Updates.”

Here InCopy CC 2014 will be installed separately from my version of InCopy CC. But Extension Manager CC will be updated.

Here InCopy CC 2014 will be installed separately from my version of InCopy CC.
But Extension Manager CC will be updated.

The label “Update” is wrong. Notice the category at top called New Versions. This means that as I am installing Illustrator CC (2014), it will NOT overwrite my copy of Illustrator CC. I will be able to have both versions installed in my Applications folder. Similarly InCopy CC (2014) will not overwrite my version of InCopy CC.

This is vital for InDesign users, as documents created in CC (2014) must be saved as IDML so that InDesign CC can open them. So if I have a student who is using CC and sends me a file to change, I need to open it in CC or save it down as IDML if I open it in CC (2014).

Bottom Line:

Don’t panic at the “Update” button. It’s an “Install“.

Tags
Related Articles
Comments

8 Comments on “When an “Update” Isn’t an Update

  1. Well done Adobe for finding a way to make simplified version labelling complex. You may as well have called this upgrade CS8 and the previous CS7. How are we better off with this idiocy?

    If settings migration fails for you like it did me, then just manually copy over relevant prefs. You may lose several hours of productivity to this badly structured upgrade.

    Make sure to turn off usage sending info via your online user settings – as if the system wasn’t already invading your privacy enough…

      • yeah, so far ID has a button and PS just asks if you wanna keep your workspace. Im OK with it, though I agree with Stupid (heh) that the naming conventions changing so much is super silly.

  2. Not a great idea having it say update
    “Your bad Adobe”
    My co worker thinking it was just an update installed it and went back to work, next thing I can’t open the files she has created.
    Had to go through her jobs and save em back down to CC.
    Our other office has not upgraded to new version yet as well.

  3. And I thought the whole point of Adobe CC was we wouldn’t have to worry about all these different version issues anymore. What a pain!

  4. Quote: “And I thought the whole point of Adobe CC was we wouldn’t have to worry about all these different version issues anymore. What a pain!”

    That’d be NIMBY come to software development. Software enhancements that add something new to a saved file of necessity mean new file format versions. We can’t get around that.

    The “whole point of Adobe CC” wasn’t to get us away from versions. It’s move most improvements out quickly rather than hold them back for a major revision every 18-months. Changes that don’t affect document file formats can come out ASAP (i.e. improvements to ePub export). With this yearly naming scheme, it looks like the ID saved document changes will be coming out roughly yearly.

    Since I am a one-man shop, I migrated to 2014 as soon as it came out. With teams, there may be a bit of delay and confusion, but keep in mind that a subscription plan makes it far easier to keep everyone using the same version. With the old buy-to-use scheme, one department might upgrade quickly while another might take months to persuade their boss to agree to an upgrade. That was bad news.

  5. Of course the whole point of Adobe CC is INDEED that you don’t have to worry about updates – just like you don’t have to worry about updates with any of the apps on your phone. Adobe has never, and will never have their act together. What a joke.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>