Search and Top Navigation
#6119 closed bug (fixed)
Opened September 28, 2010 04:06PM UTC
Closed October 04, 2012 10:42PM UTC
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.
Attachments (0)
Change History (6)
Changed September 28, 2010 04:09PM UTC by comment:1
Changed September 28, 2010 04:14PM UTC by comment:2
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.
Changed September 28, 2010 04:16PM UTC by comment:3
Replying to [comment:1 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.
Changed October 19, 2010 04:04PM UTC by comment:4
milestone: | TBD → 1.9 |
---|---|
priority: | critical → blocker |
Changed February 27, 2012 11:36AM UTC by comment:5
status: | new → open |
---|
Changed October 04, 2012 10:42PM UTC by comment:6
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.