Magento2: Static content not generated, only generated file is requirejs-config.js

[Cristy94]

Preconditions (*)

1. PHP Version 7.1
2. Magento CE 2.3.0
3. Installed on a shared server, only have cPanel access, no shell

Steps to reproduce (*)

1. Fresh installation of Magento 2.3.0
2. Installation is successful, but when I access the frontend no CSS is loaded:

Expected result (*)

1. I expect the store to properly load CSS, which is requested (but missing) from the static folder.

Actual result (*)

1. Only HTML is loaded, the only file generated in pub/static/Magento/luma/locale is requirejs-config.js
   

I have tried to somehow trigger the static content generation as explained here, but it didn't seem to do anything.

I also tried reinstalling the store from scratch, same result. I don't think there is a permissions issue as the requirejs-config file can be copied there, so there are write permissions.

[magento-engcom-team]

Hi @Cristy94. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• [ ] Summary of the issue
• [ ] Information on your environment
• [ ] Steps to reproduce
• [ ] Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@Cristy94 do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• [ ] yes
• [ ] no

[magento-engcom-team]

Hi @engcom-backlog-nazar. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!
  

• [ ] 5. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• _Next steps are available in case you are a member of Community Maintainers._

• [ ] 6. Add label Issue: Confirmed once verification is complete.

• [ ] 7. Make sure that automatic system confirms that report has been added to the backlog.

[ghost]

Hi @Cristy94 thank you for you report,
The GitHub issue tracker is intended for Magento Core technical issues only.
Please refer to the Community Forums or the Magento Stack Exchange site for advice or general discussion about this issue.

[Cristy94]

How is this not a core issue? A fresh installation does not work while the installer passes all checks and says installation was successful. Why does it say everything is ok if it is clearly not?

[ghost]

@Cristy94 But why many people can install without this errors ?

[Cristy94]

@engcom-backlog-nazar That's how bugs work, right? It's like saying, if 2 planes crash but 998 are fine, then there is no problem, as the majority are fine.

It's clearly an issue when a locale is used, there are many people having this issue (just first results from some google searches):
https://magento.stackexchange.com/questions/219268/setupstatic-contentdeploy-issue-with-locale
https://stackoverflow.com/questions/34040496/magento-2-not-loading-css-and-javascript/45114847
https://magento.stackexchange.com/questions/212514/refused-to-apply-style-because-its-mime-type-text-html-is-not-a-supported-s
https://community.magento.com/t5/Magento-2-x-Technical-Issues/Refused-to-apply-style-quot-because-its-MIME-type-text-html-is/td-p/86721/page/2

There were also a few blog posts about it, but can't find them at the moment.

I understand there might be some server specifications issues, but the biggest question is why it only generates some files (the requirejs file, it can create the required folders etc) and why it says it's working as expected when it is not.

I don't think the mentality of "the platform is fine because it works for most users" is the way to go for such a big product.

[ghost]

@Cristy94 ok i agree with you , but how we can reproduce this ? without reproduce issue we cannot create a PR

[Cristy94]

I can 100% reproduce it on my environment.

@magento-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

[magento-engcom-team]

Hi @Cristy94. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @Cristy94, here is your Magento instance.
Admin access: https://i-21201-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[Cristy94]

I tried to reproduce it in your Environment, but:

1) When I installed Magento 2 in my case, I selected at installation time the ro_RO locale.
2) When I changed the locale in your environment to ro_RO, the frontend store language (text) was still in English (language doesn't seem to change).

Yet all text on the store is in English (after flushing cache).

[gitxsun]

I have exact same issue. Already wasted one whole days , then saw this post. My dev is using PHP 7.1 . but my testing production server is using PHP 7.2. I suspect that it is a PHP 7.2 and Magento 2.3 bug.

[Cristy94]

I have PHP 7.1 on my servver and have this issue, so not sure it is related to the PHP version. Do you also have have your shop in a locale different than the default one (en_US) ?

[Cristy94]

I have fixed my issue by switching from Magento to WooCommerce, the installation was infinitely more pleasant and hassle free and importing the products from Magento to WooCommerce was quick.

I won't recommend anyone Magento, it's just an old platform with bad support.

[arslanfarooq]

I have the same issue. Wasted whole day on it, did fresh install twice. Then came to this from another report that was closed.

If this is your way of nudging people to go for premium version of Magento, it won't work in the long term. You guys will lose.

[kmv]

Sometime it is a hosting settings issue - its try to find "static" folder directly in magento root but not in pub/
To fix it try to make symbol link in magento root directory
$ ln -s pub/static static

[Nader-GenKO]

have the same exact issue, first use of Magento. searching for a solution without luck.

[angelascone]

Magento CE 2.3.1, PHP 7.2, shared hosting. I replicated the same issue today. In developer mode only one requirejs-config.js was deployed after requesting the homepage. After dozen minutes of useless searching I made "a big job" to get the Apache log from the provider :).
I found:
_*/pub/static/.htaccess: Option MultiViews not allowed here, referer: *_
I commented out line (10) Options -MultiViews in the file /pub/static/.htaccess and then the static contents have been correctly deployed.
Of course, better way is to allow multiviews overriding within .htaccess files by default but it doesn't have to be always possible on hosting servers.
Hope it helps anyone.

[antoinekociuba]

Hi there, if some people are still in trouble with that issue, simply remove or switch _dev/static/sign_ setting, from _core_config_data_ table, to 0.

It did the trick on my side.

Check https://github.com/magento/magento2/issues/7869 for more details.