Support » Plugin: Fluency Admin » [Plugin: Fluency Admin] Fluency 3.2 does not work with WP 3.3

Viewing 12 replies - 1 through 12 (of 12 total)
  • Agreed. It does not work right now with the 3.3 new update installation of WordPress.

    It looks like it is just a few minor tweaks in the CSS of the menu and some new css that needs to be over ridden in the newer system.

    I have a work around for those who would like one until the plugin’s author can update.

    Basically all this does is override Dean’s and WordPress’s css.

    You will want to add this into your functions.php file of your theme or if you run a network of sites (like i do) you will want to put this in a custom plugin that you can put in your plugins folder or your mu-plugins folder. Either one will will work.

    ////////////////////////////////////////////////////////////////////////////////////
    // This gives us some options for styling the admin area
    ///////////////////////////////////////////////////////////////////////////////////
    
    function custom_colors() {
     echo '<style type="text/css" media="screen, print">
                    #adminmenu li.wp-has-current-submenu .wp-menu-arrow, #adminmenu li.menu-top:hover .wp-menu-arrow, #adminmenu li.current .wp-menu-arrow, #adminmenu li.focused .wp-menu-arrow, #adminmenu li.menu-top.wp-has-submenu:hover .wp-menu-arrow div { display: none !important; }
    		.fluency-hover-menus #adminmenu .wp-submenu { -moz-box-shadow: 0px 0px 0px rgba(0,0,0,0.25) !important; -webkit-box-shadow: 0px 0px 0px rgba(0,0,0,0.25) !important; box-shadow: 0px 0px 0px rgba(0,0,0,0.25) !important; border-left: 1px solid #FFF !important;}
    </style>';
    add_action('admin_head', 'custom_colors');

    If you’ve turned off the plugin and want to work within the new css to accomplish something like the default fluency implementation, give this a try:

    //Add to functions.php or, ideally, include in a plugin.
    function like_fluency_css() {
        echo '<style>
    		    *,body {font-family: helvetica, sans-serif;}
                img#header-logo{display: none;}
    			#adminmenu div.wp-menu-image {float: left;width: 1px;height: 28px;}
    			#adminmenu .wp-menu-image a{display: none;}
    			#wp-admin-bar-wp-logo{display: none;}
    		    #adminmenuback, #adminmenuwrap {background-color: #222;border-color: #444;border-right-color: #ddd;}
    			#adminmenu li.wp-menu-separator {display: none;}
    			#adminmenu div.separator {border-color: #0e6ac8;}
    			#adminmenu a.menu-top, .folded #adminmenu li.menu-top, #adminmenu .wp-submenu .wp-submenu-head {border-top-color: #444;border-bottom-color: #000;}
    			#adminmenu a {color:#fff;}
    			#adminmenu .wp-submenu a {color:#777;}
    			#adminmenu a:hover, #adminmenu li.menu-top>a:focus, #adminmenu ul.wp-submenu a:hover {color: #fff;}
    			#adminmenu li.menu-top:hover>a, #adminmenu li.menu-top.focused>a, #adminmenu li.menu-top>a:focus {background-color: #000;text-shadow: 0 -1px 0 rgba(0, 0, 0, 0.4);}
    			#adminmenu li.wp-not-current-submenu:hover>a {border-top-color: #000;border-bottom-color: #000;}
                #adminmenu li.wp-not-current-submenu .wp-menu-arrow {border-top-color: #000;border-bottom-color: #000;background: #000;}
                #adminmenu li.wp-not-current-submenu .wp-menu-arrow div {background: #000;border-color: #000;}
    			#collapse-menu {color: rgba(255,255,255,0.3);}
    			#collapse-menu:hover {color: rgba(255,255,255,1.0);}
    			#collapse-menu:hover #collapse-button {border-color: rgba(255,255,255,0.4);background-color: #333;background-image: -moz-linear-gradient(center bottom , #333, #444);}
    			#collapse-button {border-color: rgba(255,255,255,0.2);background-color: #000;background-image: -moz-linear-gradient(center bottom , #111, #000);}
    			#adminmenu .awaiting-mod, #adminmenu .update-plugins, #sidemenu a .update-plugins, #rightnow .reallynow {background-color: #464646;box-shadow: 0 1px 0 rgba(255, 255, 255, 0.5);color: #FFFFFF;}
    			.folded #adminmenu .wp-submenu-head {border-bottom-color: #ccc;border-top-color: #ccc;}
    			.folded #adminmenu li.wp-has-current-submenu, .folded #adminmenu li.current.menu-top {border-bottom-color: #6D6D6D;border-top-color: #808080;}
    		</style>';
    }
    add_action('admin_head', 'like_fluency_css');

    I have not tried nsantillo’s solution, but that may be more like what you’re after if you’re trying to continue to use fluency until it is updated.

    Hi mmattner. You are correct what I have above is if you are still using Fluency Admin.

    I have deactivated Fluency Admin because of it’s incompatible with wp3.3. but the “Howdy, username” and the link to logout is missing. Does anyone know how to put it back?

    Thanks in advance!

    tarundeology, this is an integrated part of the new admin toolbar: http://codex.wordpress.org/Version_3.3#Highlights. Unfortunately, you’ll need to deactivate any plugin that removes the toolbar as it is now an integral part of the administration interface.

    I disabled WP Custom Admin Bar and it works.
    Thanks mmattner!

    Plugin Author Dean Robinson

    (@deanjrobinson)

    Info regarding Fluency and WordPress 3.3, and when an update might be expected can be found here

    Thanks for the info Dean.

    @ nsantillo – you’ve missed a closing } from the function custom_colors

    @aljuk And so your right! Thank you for catching that.

    Here is the revised code:

    ////////////////////////////////////////////////////////////////////////////////////
    // This gives us some options for styling the admin area
    ///////////////////////////////////////////////////////////////////////////////////
    
    function custom_colors() {
     echo '<style type="text/css" media="screen, print">
                    #adminmenu li.wp-has-current-submenu .wp-menu-arrow, #adminmenu li.menu-top:hover .wp-menu-arrow, #adminmenu li.current .wp-menu-arrow, #adminmenu li.focused .wp-menu-arrow, #adminmenu li.menu-top.wp-has-submenu:hover .wp-menu-arrow div { display: none !important; }
    		.fluency-hover-menus #adminmenu .wp-submenu { -moz-box-shadow: 0px 0px 0px rgba(0,0,0,0.25) !important; -webkit-box-shadow: 0px 0px 0px rgba(0,0,0,0.25) !important; box-shadow: 0px 0px 0px rgba(0,0,0,0.25) !important; border-left: 1px solid #FFF !important;}
    </style>'; }
    add_action('admin_head', 'custom_colors');

    great to hear that dean plan to upgrade fluency – btw one my big desire – please do not forget to support tablets – some parts were unusable on tablets, especially the “popup” windows. today’s wp should have this solved

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘[Plugin: Fluency Admin] Fluency 3.2 does not work with WP 3.3’ is closed to new replies.