Hi, I understand your pain. I spent several weeks unpicking the mess Inverse made of the mifration from 6.5 to 8.3 as far as customisation was concerned. They basically made it impossible to use previously customised captive portal profiles in 8.3 without major rewrites of the HTML code (particularly the use of graphics sprites inside buttons but that is another story).
You would be better off using a new ‘settings’ file and adding that into the styles.scss file in the scss folder. If you include your new settings file immediately after the existing one then you can override any of the previous settings without having to change the original files:- @import "settings/settings.core"; @import "settings.global"; @import "settings.colors"; @import "settings.packetfence"; // This is our custom colours file that defines the colours we want to use for each type of portal. @import "settings.Custom"; // This puts the previous custom colours into the relevant PF colour variables. @import "settings.FXPLUS"; // We uncomment this line to completely change the colour scheme for another company // @import "settings.CPLUS"; The order of the files can basically be used to override the settings./variable defined in earlier ‘settings’ files. As far as button background colours are concerned you have override the following variables:- // Primary button $pf-color-primary: $Buttonbackgroundcolour; $pf-color-primary-touch: $Buttonbackgroundcolourwhenpressed; $pf-color-primary-disabled: $Buttonbackgrouncolourwhenbuttondisabled; // Secondary button $pf-color-secondary: $Buttonbackgroundcolour; $pf-color-secondary-touch: $Buttonbackgroundcolourwhenpressed; $pf-color-secondary-disabled: $Buttonbackgrouncolourwhenbuttondisabled; // Tertiary button $pf-color-tertiary: $Buttonbackgroundcolour; $pf-color-tertiary-touch: $Buttonbackgroundcolourwhenpressed; $pf-color-tertiary-disabled: $Buttonbackgrouncolourwhenbuttondisabled; Also might be a good idea to use the ‘grunt dev’ option instead of ‘grunt dist’ while developing this as the resultant ‘styles.css’ file is then uncompressed and readable. Have fun. Andrew From: Mullo . via PacketFence-users <[email protected]> Sent: 16 April 2019 05:44 To: [email protected] Cc: Mullo . <[email protected]> Subject: [PacketFence-users] PF Color Scheme Hello, Hoping someone could shed some light on changing color schemes. Packetfence version: 8.3.0 I’m attempting to change the color of the background for the buttons presented via the ‘content-with-choice.html’ page. I’ve edited the ‘_settings.colors.scss’ to reflect the correct color codes in ‘Secondary button’ section and run ‘grunt dist’ to publish, which completes successfully. It seems as those the changes made to the ‘_settings.colors.scss’ are not being bought into the generated styles.css after running grunt. Is there something I’m missing in this process? I’ve even changed the color directly in the generated style.css to see if it would be reflected on the portal but continues to be the default blue. Any help would be appreciated. Thanks, Steven Andrew Torry Senior Infrastructure Engineer Tel: 01326 370760 Email: [email protected] [cid:[email protected]] [Falmouth Exeter Plus] [cid:[email protected]] [Twitter] <https://twitter.com/falmouthexeter> [Facebook] <https://www.facebook.com/falmouthexeter> [Instagram] <https://www.instagram.com/falmouthexeterplus/> [YouTube] <https://www.youtube.com/channel/UC5-Jq4vTOhWgYoJJDYrZHWw> [cid:[email protected]] [Falmouth University] Falmouth Exeter Plus is an exempt charity established by Falmouth University and the University of Exeter to deliver their shared Higher Education services in Cornwall.
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
