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

Can't disable JS Bundling in adminhtml while keeping it enabled on frontend #6638

Closed
hostep opened this issue Sep 16, 2016 · 3 comments
Closed
Labels
Area: Frontend bug report Component: Developer Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed

Comments

@hostep
Copy link
Contributor

hostep commented Sep 16, 2016

Preconditions

  1. Magento CE 2.1.0

Steps to reproduce

  1. Disable JS Bundling in the 'Default Config' scope
  2. Enable JS Bundling in either a Website or StoreView scope
  3. Deploy the static assets

Expected result

Bundled js files should not be used in the adminhtml

Actual result

Bundled js files are still being used in the adminhtml
You just can't disable bundling in adminhtml when it is enabled in a lower scope.

@tkacheva
Copy link

@hostep I'm struggling to understand steps you are following.
Scope selector that switches magento scopes influence Magento Storefront only. there is no possibility to switch off JavaScript Bundling only for Admin Panel.

What you are looking for is a functionality that magento doesn't support.
Feature Requests and Improvements should now be submitted to the new Magento 2 Feature Requests and Improvements forum (see details here).

@hostep
Copy link
Contributor Author

hostep commented Oct 27, 2016

Sorry for the late reply, I was away on holiday.

Anyway, @tkacheva, you are incorrect.

Traditionally in Magento (1 and 2) you can define configuration settings for the adminhtml by configuring them in the Default Config scope and override them for the frontend in lower scopes (website or storeview).

For example: we always set the Default Config locale to en_US while configuring the different storeviews to different locale's like nl_NL, fr_FR, de_DE, es_ES, en_US, ...
Which makes the adminhtml locale en_US and the frontend storeviews different locale's. So this use case obviously should work and has always worked traditionally (merging JS files in M1 as another example worked perfectly fine like this).

So @tkacheva: please reopen, tnx! :)

@hostep
Copy link
Contributor Author

hostep commented Nov 17, 2016

I still believe this has been incorrectly closed.
@tkacheva or @veloraven: can you please review this?
The issue is a minor one, but it is still a bug, so I think this should be reopened.

Thanks!

@ghost ghost added the Component: Developer label Jan 10, 2019
@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Jan 10, 2019
magento-engcom-team pushed a commit that referenced this issue Feb 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Frontend bug report Component: Developer Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed
Projects
None yet
Development

No branches or pull requests

4 participants