Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8008559
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 4, 20262026-06-04T18:10:29+00:00 2026-06-04T18:10:29+00:00

After updating to EmberJS 0.9.8.1 I now get two warnings: WARNING: Computed properties will

  • 0

After updating to EmberJS 0.9.8.1 I now get two warnings:

WARNING: Computed properties will soon be cacheable by default. To enable this
in your app, set `ENV.CP_DEFAULT_CACHEABLE = true`. 

And:

WARNING: The way that the {{view}} helper affects templates is about to change.
...SNIP...  by setting `ENV.VIEW_PRESERVES_CONTEXT = true`.

This may seem like a stupid question, but how do I set these ENV variables? I’ve tried setting them a few different ways, and none make the WARNING message go away, and nothing in my App breaks either. Does that mean I’m in the clear? Or does it mean I’m not setting the ENV variables correctly?

  1. window.ENV does not exist, so literally doing ‘ENV.CP_DEFAULT_CACHEABLE = true’ doesn’t work
  2. Ember.ENV exists, but is an empty object, and has no Ember.ENV.set method. So I tried doing Ember.ENV.CP_DEFAULT_CACHEABLE = true. Is this the correct way to set an ENV? It, however has no effect on Ember.CP_DEFAULT_CACHEABLE, so that doesn’t seem right.
  3. Ember.CP_DEFAULT_CACHEABLE exists, so I’ve tried doing Ember.CP_DEFAULT_CACHEABLE = true, but this has no effect on Ember.ENV.CP_DEFAULT_CACHEABLE.
  4. I’ve also tried doing Ember.set(‘CP_DEFAULT_CACHEABLE’, true).

Which (if any) of these is the right way to respond to these warnings? Do they not just do away when you set things based on their pleas? The warnings should probably document this better, or provide feedback that you set them.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-04T18:10:30+00:00Added an answer on June 4, 2026 at 6:10 pm

    You have to make sure that the ENV variable is set, before Ember.js is loaded (defined in ember-metal/lib/core.js), see http://jsfiddle.net/pangratz666/jweyf/:

    <!doctype html>
    <body>
        <script type="text/javascript" >
            ENV = {
                CP_DEFAULT_CACHEABLE: true,
                VIEW_PRESERVES_CONTEXT: true
            };
        </script>
        <script src="http://code.jquery.com/jquery-1.7.2.js"></script>
        <script src="https://github.com/downloads/emberjs/ember.js/ember-0.9.8.1.js"></script>
        ...
    </body>
    

    ​

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

ORIGINAL MESSAGE (now outdated): After running python setup.py install I get the following: Warning:
After updating my ADT plugin to version 17 I'm getting a warning massage saying
After updating to WHM/cPanel 11.30.0, PHPMailer mails are now being rejected by exim. This
I get a strange PHP error after updating my php version to 5.4.0-3. I
after updating my grails app's security plugins, i get the following error when deploying
After updating to the latest (and now deprecated, sniff...) update of Apple's JDK, Eclipse
After updating to rubygems 1.5.0, I get this error message when trying to run
Is it possible to get the number of affected rows, after updating data? Here
After updating to Wordpress 3.2.1 my photo gallery plugin, Photo Galleria , has now
When executing SubmitChanges to the DataContext after updating a couple properties with a LINQ

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.