New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

can't deploy: Resource invalid: source New file does not have the original extension #1200

Open
lcx opened this Issue Mar 22, 2017 · 10 comments

Comments

Projects
None yet
4 participants
@lcx

lcx commented Mar 22, 2017

when trying to deploy I get this error for some pages.
This seems to have happened after upgrading locomotive, currently running git commit cf4855f

  persisting stylesheets/application.css [failed]
    Resource invalid: source New file does not have the original extension

I'm not sure what locomotive is trying to tell me with this error.
If I remove the page and redeploy from scratch, everything is ok again.

@lcx

This comment has been minimized.

Show comment
Hide comment
@lcx

lcx Mar 22, 2017

to solve this issue one could do following:

wagon delete demo theme_assets

which deletes all assets, after that deploy again and it works without having to delete the whole site.

lcx commented Mar 22, 2017

to solve this issue one could do following:

wagon delete demo theme_assets

which deletes all assets, after that deploy again and it works without having to delete the whole site.

@did

This comment has been minimized.

Show comment
Hide comment
@did

did Mar 23, 2017

Member

hi @lcx, solved by this commit: 0866e9f. Please install the 3.3.0.rc2 version.

Member

did commented Mar 23, 2017

hi @lcx, solved by this commit: 0866e9f. Please install the 3.3.0.rc2 version.

@did did closed this Mar 23, 2017

@did did added the issue label Apr 3, 2017

@DonKoko

This comment has been minimized.

Show comment
Hide comment
@DonKoko

DonKoko Apr 4, 2017

I am reporting this as the issue still persists with me. I tried on a few different websites and on each one of them it happens, on a kind or random basis, meaning that a different file faces the issue. Most of the times js.
One one website i deleted all assets from the engine using the wagon delete and when i redeployed the issue is even bigger. My CSS is broken and this is what I get in the browser console:

[Error] Did not parse stylesheet at 'https://whale-engine.s3-eu-west-1.amazonaws.com/sites/5774da8e38abae03201d27ea/theme/stylesheets/plugins/font-awesome/css/font-awesome.css?1491327397' because non CSS MIME types are not allowed in strict mode.
[Error] Did not parse stylesheet at 'https://whale-engine.s3-eu-west-1.amazonaws.com/sites/5774da8e38abae03201d27ea/theme/stylesheets/plugins/bootstrap/css/bootstrap.min.css?1491327397' because non CSS MIME types are not allowed in strict mode.

DonKoko commented Apr 4, 2017

I am reporting this as the issue still persists with me. I tried on a few different websites and on each one of them it happens, on a kind or random basis, meaning that a different file faces the issue. Most of the times js.
One one website i deleted all assets from the engine using the wagon delete and when i redeployed the issue is even bigger. My CSS is broken and this is what I get in the browser console:

[Error] Did not parse stylesheet at 'https://whale-engine.s3-eu-west-1.amazonaws.com/sites/5774da8e38abae03201d27ea/theme/stylesheets/plugins/font-awesome/css/font-awesome.css?1491327397' because non CSS MIME types are not allowed in strict mode.
[Error] Did not parse stylesheet at 'https://whale-engine.s3-eu-west-1.amazonaws.com/sites/5774da8e38abae03201d27ea/theme/stylesheets/plugins/bootstrap/css/bootstrap.min.css?1491327397' because non CSS MIME types are not allowed in strict mode.
@lcx

This comment has been minimized.

Show comment
Hide comment
@lcx

lcx Apr 7, 2017

@DonKoko did you upgrade to 3.3.0.rc2? Was just about to do that but if you still have the same issue I will rather wait with the update.

lcx commented Apr 7, 2017

@DonKoko did you upgrade to 3.3.0.rc2? Was just about to do that but if you still have the same issue I will rather wait with the update.

@did

This comment has been minimized.

Show comment
Hide comment
@did

did Apr 7, 2017

Member

@lcx right, my patch was unfortunately solving one side of the issue.

Member

did commented Apr 7, 2017

@lcx right, my patch was unfortunately solving one side of the issue.

@did did reopened this Apr 7, 2017

@DonKoko

This comment has been minimized.

Show comment
Hide comment
@DonKoko

DonKoko Apr 7, 2017

@lcx I did, and as Did said we found some other issues so did is working on fixing it.

DonKoko commented Apr 7, 2017

@lcx I did, and as Did said we found some other issues so did is working on fixing it.

@lcx

This comment has been minimized.

Show comment
Hide comment
@lcx

lcx Apr 7, 2017

just a quick update, deleted the assets pushed an now seeing these issues:

Warning: Unable to compress and minify it, error: Invalid CSS after "": expected selector, was "25%,75%"

now I'm doomed. need to deploy new page today.
deleting the site and recreating doesn't solve the issue. Wondering if I should roll back a locomotive version or wait for a fix.

lcx commented Apr 7, 2017

just a quick update, deleted the assets pushed an now seeing these issues:

Warning: Unable to compress and minify it, error: Invalid CSS after "": expected selector, was "25%,75%"

now I'm doomed. need to deploy new page today.
deleting the site and recreating doesn't solve the issue. Wondering if I should roll back a locomotive version or wait for a fix.

@DonKoko

This comment has been minimized.

Show comment
Hide comment
@DonKoko

DonKoko Apr 7, 2017

DonKoko commented Apr 7, 2017

@lcx

This comment has been minimized.

Show comment
Hide comment
@lcx

lcx Apr 7, 2017

Na, I'm more the self hosted guy. Just rented half a rack and bought my own server, I know, crazy.
I do have backups, should not be an issue. Problem is that I have somewhere around 20 Sites on that locomotive.
I will see if I can "abuse" my testserver which has an older version and deploy this one page over there or if the customer can wait a couple of days.

lcx commented Apr 7, 2017

Na, I'm more the self hosted guy. Just rented half a rack and bought my own server, I know, crazy.
I do have backups, should not be an issue. Problem is that I have somewhere around 20 Sites on that locomotive.
I will see if I can "abuse" my testserver which has an older version and deploy this one page over there or if the customer can wait a couple of days.

did added a commit that referenced this issue Apr 10, 2017

don't rely on the mime magic carrierwave method to detect the content…
… type of an uploaded file (too false positive cases) #1200 1207
@manuchap

This comment has been minimized.

Show comment
Hide comment
@manuchap

manuchap Apr 12, 2017

Contributor

A quick workaround that worked for me (on amazonS3) was to upload the files manually from the s3 managment console and then select the javascript folder and click on more->make public

Contributor

manuchap commented Apr 12, 2017

A quick workaround that worked for me (on amazonS3) was to upload the files manually from the s3 managment console and then select the javascript folder and click on more->make public

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment