Skip to content
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

Must override at least one static content file or custom theme static content won't deploy #3754

Closed
dnadle opened this issue Mar 14, 2016 · 25 comments
Labels
Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development

Comments

@dnadle
Copy link

dnadle commented Mar 14, 2016

Steps to reproduce

  1. I created a custom theme with Magento/blank as parent, to override a template.
  2. I did not override any static content. (nothing in the theme's web folder).
  3. I ran bin/magento setup:static-content:deploy

Expected result

The static content requests would fall back to load from the Magento/blank theme.

Actual result

All of the static content links in pub/static/theme 404'd.

Workaround

I added a logo file to theme/web/images and reran setup:static-content:deploy. This time all the files were generated in pub/static.

@zanilee
Copy link
Contributor

zanilee commented Apr 20, 2016

Hi, @dnadle!

Thank you for reporting this issue.
Internal ticket MAGETWO-52102

@mazhalai mazhalai added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Apr 20, 2016
@MomotenkoNatalia MomotenkoNatalia added PS and removed CS labels Apr 28, 2016
@MomotenkoNatalia MomotenkoNatalia removed their assignment Apr 28, 2016
@piotrekkaminski
Copy link
Contributor

The issue is currently in progress.

@Krapulat
Copy link

Same problem in Magento 2.1.

@tarnagas
Copy link

Same problem in Magento 2.0.7

okorshenko pushed a commit that referenced this issue Jul 6, 2016
…out overriding at least one static content file #3754
@vkorotun vkorotun removed the PS label Aug 4, 2016
@wert2all
Copy link
Contributor

Fixed

@pinkdigital
Copy link

This is still an issue in 2.1. Without an image in theme/web/image it ignores the theme.

@keyurshah
Copy link

had this same issue in 2.1. took a while to figure out until I saw the workaround.

@OLTC-fperrin
Copy link

Still an issue in 2.0.9. I had to create an empty test.js file in app/design/adminhtml/[Package]/[Theme]/web for the theme to deploy

@fxdegroot
Copy link

Why is this closed ? Still an issue in CE 2.1.1

@MarekKarmelski
Copy link

Confirm! Still bug in CE 2.1.2

@shahankitb997
Copy link

Yes. I face same issue in Magento 2 CE Version 2.1.2. What is solution?

@mrkhoa99
Copy link
Contributor

mrkhoa99 commented Dec 2, 2016

When creating a new custom theme, if we don't have any assets files under web folder, your theme may be ignored when executing deploy command.

@jurgisl
Copy link

jurgisl commented Jan 6, 2017

Still a bug in CE 2.1.3.

@Nguyen-Cong-Anh
Copy link

still a bug CE 2.1.4

@dersam
Copy link

dersam commented Mar 9, 2017

This issue still exists in 2.1.5.

@lfolco
Copy link
Contributor

lfolco commented Mar 28, 2017

Please reopen this!

@pguedesbr
Copy link

Issue still exists.
I've had to create a dummy static file (dummy.js) so the child theme wouldn't be ignored by setup:static-content:deploy command

@DnDDeployer
Copy link

Still exist in 2.1.6

@JoJuhasz
Copy link

I confirm still present in 2.1.6.
Ok workaround is quite simple, but still an issue :)

@charmeleon-zz
Copy link

Still an issue in 2.1.7... that's two days of my life I won't get back :(

@erfanimani
Copy link
Contributor

Yeah, same issue on 2.1.7..

@rouralberto
Copy link

Please reopen this, is still an existing issue.

@Igloczek
Copy link
Contributor

It will be released with 2.2.0 unless someone will create a backport for 2.1.x.

@Anshu-Mishra
Copy link

Anshu-Mishra commented Aug 19, 2017

I have experienced this issue in 2.1.8 as well.

hostep pushed a commit to hostep/magento2 that referenced this issue Sep 2, 2017
…ic content won't deploy without overriding at least one static content file magento#3754

(cherry picked from commit 6a9744d)
@magento-team
Copy link
Contributor

Internal ticket to track issue progress: MAGETWO-72253

@magento-team magento-team added 2.1.x Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development labels Sep 6, 2017
magento-engcom-team pushed a commit that referenced this issue Feb 14, 2019
[pangolin] Remove composer.json from dev/tests/acceptance (2.2-develop)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development
Projects
None yet
Development

No branches or pull requests