Databases
StackOverflow2013
Postsdbo
PORake aborted! Invalid CSS after " filter: progid": expected ";", was ":DXImageTransfo..."
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORake aborted! Invalid CSS after " filter: progid": expected ";", was ":DXImageTransfo..."
    primarykey
    data
    text
    <p>When I do <code>git push heroku master</code> I get......</p> <pre><code>mkdir -p /tmp/build_klvg6evbve3x/public/assets mkdir -p /tmp/build_klvg6evbve3x/public/assets (in /tmp/build_klvg6evbve3x) mkdir -p /tmp/build_klvg6evbve3x/public/assets mkdir -p /tmp/build_klvg6evbve3x/public/assets mkdir -p /tmp/build_klvg6evbve3x/public/assets mkdir -p /tmp/build_klvg6evbve3x/public/assets mkdir -p /tmp/build_klvg6evbve3x/public/assets mkdir -p /tmp/build_klvg6evbve3x/public/assets rake aborted! Invalid CSS after " filter: progid": expected ";", was ":DXImageTransfo..." (in /tmp/build_klvg6evbve3x/app/assets/stylesheets/application.css) ............. Precompiling assets failed, enabling runtime asset compilation Injecting rails31_enable_runtime_asset_compilation Please see this article for troubleshooting help: http://devcenter.heroku.com/articles/rails31_heroku_cedar#troubleshooting -----&gt; Rails plugin injection Injecting rails_log_stdout Injecting rails3_serve_static_assets -----&gt; Discovering process types Procfile declares types -&gt; web Default types for Ruby/Rails -&gt; console, rake, worker -----&gt; Compiled slug size is 39.4MB -----&gt; Launching... !Heroku push rejected due to an unrecognized error. !We've been notified, see http://support.heroku.com if the problem persists. </code></pre> <p>then to....</p> <pre><code>To git@heroku.com:testapp.git ! [remote rejected] master -&gt; master (pre-receive hook declined) error: failed to push some refs to 'git@heroku.com:testapp.git' </code></pre> <p>I Don't have anything in my application.css that is <code>":DXImageTransfo..."</code> so I'm not sure whats happening.</p> <p>Now this is an issue because using Twitter Bootstrap and Simple_form, my forms are messed up and I think this is the reason why. Anyway to fix this? What's going on here?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USLearningRoR
    1. USLearningRoR
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORake aborted! Invalid CSS after " filter: progid": expected ";", was ":DXImageTransfo..."
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIf you do a find in all files you will find this text. application.css is a bit misleading since Rails will compile all styles into application.css
      singulars
      1. PORake aborted! Invalid CSS after " filter: progid": expected ";", was ":DXImageTransfo..."
      1. USAMIT
    2. CO@Amit Thanks for the information. I will look into it.
      singulars
      1. PORake aborted! Invalid CSS after " filter: progid": expected ";", was ":DXImageTransfo..."
      1. USLearningRoR
    3. COi was getting similar errors with the lines like `filter:;` and i deleted those to solve it :(!
      singulars
      1. PORake aborted! Invalid CSS after " filter: progid": expected ";", was ":DXImageTransfo..."
      1. USHungryCoder
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload