Please allow more css customisation

  • Resolved steve-pheriche

    (@steve-pheriche)


    7 years, 9 months ago

    Hi, my client has rejected your plugin because we cannot match the fonts to their branding.
    I can style most things you’ve created but due to the prevalence in your CSS of !important declarations. I’m reduced to increasing specificity of selector to override a background or a border radius. But some items simply will not syle. Fonts for instance.

    So, I’ve had to fork your plugin to eradicate the very hard-set styles and fonts.

    If you could put a method of adding pluggables to these, whether by the use of WP filters, or by adding a conditional which checks the active theme for a /gdpr-cookie-compliance child that would help a lot. As it is I’m off into the fork wilderness.

Viewing 7 replies - 1 through 7 (of 7 total)
  • michaelw90

    (@michaelw90)

    7 years, 9 months ago

    I second this, you’ve already specified the font-family in the main container, there’s no need to specify deeper.. Or better yet, don’t import it at all, it will fit sites much better, as the plugin will use the theme font branding.

    mjca

    (@mjca)

    7 years, 9 months ago

    Hi,

    Thank you for this plugin which is very good. But yes, it would be nice to have something else for the Floating Button “change the settings”. It is not nice on my website and this mention is mandatory. I would have prefered a text which sticks at the bottom of the page, sober and more discreet. For this reason I don’t choose this plugin, too bad because for the rest, my favorite!

    Thanks anyway.

    Marianne

    • This reply was modified 7 years, 9 months ago by mjca.
    Thread Starter steve-pheriche

    (@steve-pheriche)

    7 years, 9 months ago

    What I’ve done is de-queue the CSS. My CSS file is named gdpr-cookie-fork.css and I put it the functions.php in a child theme for my client. Like this …

    /*** overwrite the cookie law CSS **/
function cookie_GDPR_style_fixes(){
  wp_dequeue_script('moove_gdpr_frontend');
  wp_enqueue_style( 'moove_gdpr_frontend', get_stylesheet_directory_uri().'/gdpr-cookie-fork.css' );
}
add_action('wp_enqueue_scripts', 'cookie_GDPR_style_fixes', 100);
    sixtyseven

    (@sixtyseven)

    7 years, 9 months ago

    Nice idea, Steve. Maybe the author will check for moove_gdpr_frontend.css in the theme dir before enqueuing his own css. I think the webfonts are a bit too much.

    One setting is probably missing: Putting the notification bar at the top of page instead of bottom. I realized that by this css bit:

    #moove_gdpr_cookie_info_bar {
    top: 0;
    bottom: auto !important;
    border-top: none !important;
}

    Others than that: Pretty useful plugin!

    Mathe, Klara M.

    (@veralinn)

    7 years, 8 months ago

    Same font issue here. Texts in some languages don’t display well with Nunito. It’s a serious problem when we have special fonts in the text. We would appreciate if you could loose all those css lines with !important on font-family.

    It is about “best practices” also. Those lines give a negative light to your company’s image.

    Best regards,
    Klara

    Plugin Author Moove Agency

    (@mooveagency)

    7 years, 7 months ago

    Hello,

    Thanks for using our plugin and for your comments!

    We plan to include these features in the future releases of the plugin.

    We’ll keep you updated.

    Plugin Author Moove Agency

    (@mooveagency)

    7 years, 6 months ago

    Hi there,

    Thanks for your comments. Please update the plugin to the latest version and you’ll be able to define custom font family or inherit from your WordPress theme.
    If you override the font, the Nunito font will not be loaded, you have to ensure the selected font is included by your theme.
    Another improvement is the !important tags are removed from the stylesheet.

    I hope this works.

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Please allow more css customisation’ is closed to new replies.