Timeline for CSS\JS Aggregation "Shuts down" Firebug indication
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 21, 2019 at 12:01 | history | edited | avpaderno♦ |
edited tags
|
|
| Aug 29, 2015 at 23:52 | vote | accept | CommunityBot | moved from User.Id=16289 by developer User.Id=45784 | |
| Feb 9, 2015 at 11:23 | history | edited | user16289 | CC BY-SA 3.0 |
added 25 characters in body
|
| Feb 9, 2015 at 2:35 | answer | added | Patrick Ryan | timeline score: 2 | |
| Feb 9, 2015 at 2:06 | comment | added | user16289 | Well, I prefer only one environment... Is there really no easy way to edit the CSS without clearing cache after any small change and without aggregation? | |
| Feb 9, 2015 at 1:55 | comment | added | Neograph734 | There is no way to achieve readable CSS after aggregation. It is compressesed and combined. So if you want to have both, human readable CSS and aggregation, you will need to have 2 sites. Can be on a subdomain, offline or whatever. | |
| Feb 9, 2015 at 1:52 | comment | added | user16289 | Can you elaborate? Are you talking about Offline and Online environments? If yes, I'm sorry to say it's not good for me because I definitely aspire to do everything online. | |
| Feb 9, 2015 at 1:49 | comment | added | Neograph734 | Best practice is to have two environments. One tot development and testing and another one for production. If you enable aggregation on production, you can still read the CSS in development environment. | |
| Feb 9, 2015 at 1:41 | history | asked | user16289 | CC BY-SA 3.0 |