Adobe ColdFusion Backward Licensing

With the recent ColdFusion 2016 release we’ve had a few inquiries as to our backward licensing policies.  We can license one version back for certain types of volume licenses.  Below are the relevant links and contact information to help you navigate the licensing for ColdFusion 11 if needed.

 

FAQ for ColdFusion:

https://helpx.adobe.com/coldfusion/standard/faq.html

 

Backward License Policy:

http://wwwimages.adobe.com/content/dam/Adobe/en/volume-licensing/pdfs/pv_esd_customer_faq.pdf

 

We will update our sales contact information on the web site and update this blog, but for now feel free to contact Kishore@adobe.com if you want to be directed to a ColdFusion sales resource to assist with further information.

 

18 thoughts on “Adobe ColdFusion Backward Licensing

  1. Looking for the same answer that Brian is… Does this mean there’s no way for us to use CF11 now for a single Standard License? Even to upgrade our developer license that we’ve been, you know, developing on?

  2. No, a single license can be backward licensed if it is purchased through our volume programs. If it is purchased from the online shopping cart it wouldn’t qualify. Please feel free to email us if you need to discuss the possible scenarios.

  3. @Mehdi, per the FAQ unfortunately CF 10 is not covered under the backward licensing. It allows only 1 version back:

    Q. Can I order more than 1 version back?
    A. Not at this time. Adobe is currently offering one version back only.

    Is there a particular issue preventing you from migrating to CF 11 or 2016? I’d like to understand. Thanks.

  4. Probably should let people go back to the oldest version that is still under core support. It’s not our issue, but I do know we wouldn’t run a bunch of different versions of CF for the same app. Maybe they take a similar line of thought, and don’t have the upgrade budget to do all their systems?

  5. Hi Adobe,

    Why would any customer want to downgrade a CF2016 license to CF11? Well:

    As you know, CF2016 shipped with a performance optimization that causes silent data corruption and messy-to-debug behavior.

    The Release Notes mention -Dcoldfusion.udf.reuseTagInstances=false as the workaround for a few specific cases.

    As you know, the Release Notes do not describe the optimization in detail. Nor does the Release Notes warn that the risk affects much more than the few cases listed. I have found/reported more cases myself. Others will just stumble into additional cases, not realizing what all the cases have in common: CF2016 is re-using “tag instances” (Adobe, you really should blog about what exactly this means).

    What the Release Notes do indicate, however, is that CF2016 knowingly shipped w/ an optimization that it shouldn’t have.

    CF2016 should’ve had a public beta. Any CF customer would have a legitimate reason for not wanting to upgrade to CF2016 until some issues like this are fixed.

    Thanks!,
    -Aaron

  6. We’re on CF10, using CF11 on development for some new applications. If we want a CF11 license, are we able to get upgrade pricing when we purchase through the volume program? We’re a small company, so that makes a huge difference.

  7. Still looking for an answer to #8

    “We’re on CF10, using CF11 on development for some new applications. If we want a CF11 license, are we able to get upgrade pricing when we purchase through the volume program? We’re a small company, so that makes a huge difference.”

  8. Just make sure you buy any upgrade through the USA store if in the UK or AU.. otherwise you’re being raped blind with the upgrade cost.(extra 40% for downloading from the same download server)

  9. So why are you saying they tack on 40%? Is that the dollar exchange or are you saying they add on 40% in USD for the ownership clause you mentioned in a previous post?

Leave a Reply

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