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

jsTree jquery plugin refers to style.css instead of style.min.css #3170

Closed
keithbentrup opened this issue Jan 27, 2016 · 7 comments
Closed
Labels
Area: Frontend bug report Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release triage wanted

Comments

@keithbentrup
Copy link
Contributor

When deploying with minified js and css, jsTree still refers to the unminified version of its stylesheet in its javascript. However, the minified version is not deployed to pub/static. This can be probably be resolved by configuring the correct minified style url for jsTree which does exist in pub/static.

See the failing url in the javascript console of the screenshot included below.

image

If I change the url to reference style.min.css, I see the expected icons next to the folder names in the UI.

image

@vrann vrann added the PS label Mar 8, 2016
@vrann
Copy link
Contributor

vrann commented Mar 8, 2016

@keithbentrup Thanks for reporting, this looks like a bug in configuration.

@pivulic
Copy link
Contributor

pivulic commented Mar 9, 2016

@stevenvdp
Copy link
Contributor

We also have this issue.
Any progress @vrann ?

@vincentwinkel
Copy link

One year and half after, still not fixed...

@magento-engcom-team magento-engcom-team added bug report Area: Frontend Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed labels Sep 11, 2017
@magento-engcom-team magento-engcom-team added Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed 2.1.x Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release labels Nov 16, 2017
@magento-engcom-team
Copy link
Contributor

@keithbentrup, thank you for your report.
We've created internal ticket(s) MAGETWO-84017 to track progress on the issue.

@magento-engcom-team
Copy link
Contributor

Hi @keithbentrup

This ticket has been marked as "Triage Wanted" due to low user involvement over time. Over the next 2 weeks we are looking for additional community feedback to decide if it should be archived or not. More information on this is available on the GitHub wiki.

Thank you for collaboration.

@magento-engcom-team
Copy link
Contributor

@keithbentrup thank you for your report.

Unfortunately, we are archiving this ticket now as it did not get much attention from both Magento Community and Core developers for an extended period. This is done in an effort to create a quality, community-driven backlog which will allow us to allocate the required attention more easily.

You may learn more about this initiative following this link.

Please feel free to comment or reopen the ticket if you think it should be reviewed once more. Thank you for collaboration.

magento-engcom-team pushed a commit that referenced this issue Sep 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Frontend bug report Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release triage wanted
Projects
None yet
Development

No branches or pull requests

9 participants