[#16508] - [4.0] Tweak to CSS imports for templates
- Fixed in Code Base
- 25 Jun 2017
- Medium
- Build: 4.0-dev
- # 16508
- Diff
- C-Lodder:template
- Failure continuous-integration/drone/pr the build failed Details
- Success continuous-integration/travis-ci/pr The Travis CI build passed Details
- Failure continuous-integration/appveyor/pr AppVeyor build failed Details
User tests: Successful: Unsuccessful:
Summary of Changes
Import the user.css and language specific CSS in the same way as Protostar.
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Administration Templates (admin) Front End Templates (site) |
@andrepereiradasilva - yeah that's fine. If the other PR works, I'll fix this one with the necessary fix ;)
| Labels |
Added:
?
|
||
I would go with custom.css file name as it is a more common name when you have a template from a club.
@laoneo we currently use user.css and there is no benefit in making a change
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/16508.
I think the reason for user.css was somehow related to TinyMCE which uses custom.css. But I don't remember it exactly.
Ok, custom.css just makes more sense to me. Not an issue at all.
| Milestone |
Added: |
||
| Milestone |
Added: |
||
@andrepereiradasilva @wilsonge Updated to reflect the changes from J3.x and conflicts fixed.
Complicts again in component.php
All the templates I know of use custom.css
| Status | Pending | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-06-25 10:56:04 |
| Closed_By | ⇒ | wilsonge |
@C-Lodder i think the language specific will not work. see #16513