View Issue Details

IDProjectCategoryView StatusLast Update
0005767Simple:Pressthemes - generalpublic2018-06-09 21:04
ReporterYellow SwordfishAssigned To 
PrioritynormalSeverityN/AReproducibilityhave not tried
Status newResolutionopen 
Product Version5.7.3 
Target VersionFuture ReleaseFixed in Version 
Summary0005767: Develop method for the supply of plugin CSS within themes
DescriptionThe way we currently supply plugin CSS is not good. We currently have two methods:
  1. The original method employed by the first default theme was simply to supply a CSS file with the plugin, loaded separately. The downside, of course, is that this method is unable to take advantage of the overlay settings so components often do not fit within the overall style. On the plus side, CSS was only loaded if the plugin was in use.
  2. The alternative method - developed for Unified and used in both Reboot and BareBones - is to create CSS files within the theme for each plugin (with an extension of 'spcss') that is compiled into the final theme CSS file. On the plus side, plugin styling can now take advantage of overlay settings. The downside is that the files are included in the final CSS ruleset regardless of whether they are active or not.

With the development of Phoenix and the use of the LESS pre-processor, neither of these approaches really suffice and an alternate method is required - one that also takes into account whether a plugin is active or not.
On the plus side, as only Unified, Reboot and BareBones are going to be available for V6, front-end CSS for all plugins could now be removed as redundant as they should al employ the old 'spcss' inclusion method.
The difficult part is now to create a methodology that
  1. Allows us to build and use a plugin specific LESS file
  2. Incorporate that file only when the plugin is active

Probably a new registered theme capability is the starting point for this.
TagsNo tags attached.
change_log_textDevelop method for the supply of plugin CSS within themes
typenew feature


Yellow Swordfish

Yellow Swordfish

2017-03-11 13:53

administrator   ~0019310

See the Admin Bar display code for reference
Yellow Swordfish

Yellow Swordfish

2017-03-25 09:31

administrator   ~0019360

Not sure how this got to marked as test! Accident somewhere
Yellow Swordfish

Yellow Swordfish

2017-08-25 08:48

administrator   ~0019602

Moved to 6.0 as out of scope for what is now 5.8

Issue History

Date Modified Username Field Change
2017-03-04 12:20 Yellow Swordfish New Issue
2017-03-04 12:20 Yellow Swordfish Assigned To => Yellow Swordfish
2017-03-04 12:21 Yellow Swordfish Status new => assigned
2017-03-04 12:21 Yellow Swordfish change_log_text => Develop method for the supply of plugin CSS within themes
2017-03-11 13:53 Yellow Swordfish Status assigned => testing
2017-03-11 13:53 Yellow Swordfish Note Added: 0019310
2017-03-20 00:33 Mr Papa Target Version 6.0 => 5.7.4
2017-03-20 00:34 Mr Papa Product Version 6.0 => 5.7.4
2017-03-20 00:34 Mr Papa Target Version 5.7.4 => 6.0
2017-03-20 00:38 Mr Papa Product Version 5.7.4 => 5.7.3
2017-03-25 09:31 Yellow Swordfish Status testing => assigned
2017-03-25 09:31 Yellow Swordfish Note Added: 0019360
2017-07-11 01:58 Mr Papa Target Version 6.0 => 5.8
2017-08-25 08:48 Yellow Swordfish Target Version 5.8 => 6.0
2017-08-25 08:48 Yellow Swordfish Note Added: 0019602
2017-12-23 16:33 Mr Papa Target Version 6.0 => Future Release
2018-06-09 21:04 Mr Papa Assigned To Yellow Swordfish =>
2018-06-09 21:04 Mr Papa Status assigned => new