Opened 12 years ago
Closed 10 years ago
#6119 closed bug (fixed)
If no Theme is selected, the custom unified .css file is not added to the downloadable archive
| Reported by: | cs94njw | Owned by: | |
|---|---|---|---|
| Priority: | blocker | Milestone: | 1.9.0 |
| Component: | [meta] ui.downloadbuilder | Version: | 1.8.5 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
If no Theme is selected, the custom unified .css file is not added to the downloadable archive.
You get the developer* subdirectory. Two .js files - core and ui, but no unified .css file.
Happy to provide more information if required.
Change History (6)
comment:1 follow-up: 3 Changed 12 years ago by
comment:2 Changed 12 years ago by
OK, I think I'm completely wrong here.
If I could delete this I would.
When I tried to integrate and use the SplitButton, it didn't seem to work. Looking at the example lists the extra .css files I need to use.
I can't find a delete button for this ticket, so please can someone do this.
comment:3 Changed 12 years ago by
Replying to rdworth:
Agree this is a bug. If no theme is selected, the custom css file should includes core css and css for each selected plugin.
Oh. Actually, you're right.
comment:4 Changed 12 years ago by
| Milestone: | TBD → 1.9 |
|---|---|
| Priority: | critical → blocker |
comment:5 Changed 11 years ago by
| Status: | new → open |
|---|
comment:6 Changed 10 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | open → closed |
This is fixed in the new download builder.
Agree this is a bug. If no theme is selected, the custom css file should includes core css and css for each selected plugin.