Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #1223426

    Hello.

    Is it possible to use a remove function?

    Like: add_theme_support(‘avia_template_builder_custom_css’);
    to
    remove_theme_support(‘avia_template_builder_custom_css’);

    I’d like to remove the Quick CSS, as we’re a lot of designers and developers, and sometimes people use the quick css, so for our custom plugins etc. it can be tricky to find the changes.

    One thing is to remove it and the CSS will still be there, but just hiding on future pages will prevent it.

    #1223438

    i often remove the import demo options for non admins. Because importing a demo removes all other content and settings.
    If you like to completely obfuscate the options styling try this.
    those who know where to find aren’t hampered to use it anyway. But on exidentily usage maybe this is helpful:

    function admin_head_mod() {
    if(!is_admin()){ 
    echo '<style type="text/css">
    	#avia_options_page .goto_styling, 
    	#avia_options_page #avia_styling { 
    		display: none !important
    	}
    </style>';
    }
    }
    add_action('admin_head', 'admin_head_mod');
    #1223603

    Hi,

    Thanks for sharing @guenni007. Are you ok with hiding the box @tekniskakari?

    Best regards,
    Rikard

    #1223639

    you can do that for quick css only – it has an own ID so :
    If your developers have all admin right – you might want to have it globaly

    function admin_head_mod() {
    echo '<style type="text/css">
    	#avia_quick_css { 
    		display: none !important
    	}
    </style>';
    }
    add_action('admin_head', 'admin_head_mod');
    #1223651

    Hi,


    @Guenni007
    Thanks for your help! :)

    Best regards,
    Yigit

    #1224004

    That worked perfectly. Thanks for answers :)

Viewing 6 posts - 1 through 6 (of 6 total)
  • The topic ‘add_theme_support > remove_theme_support?’ is closed to new replies.