Dean Robinson

Looks like this is happening because this plugin is using a div for text entry and not a textarea.

I’ll see what I can do to get around this in the next update, until then you can disable hotkeys by commenting out (or removing) this line, around line 211:

fluencyKeys.init();

With this removed/commented out the hotkeys won’t be active.

Hi Michael,

when i click on one of them the “hide menu” item seems to pop up above these two items. the drop down menus from these items are also then disabled.

As I’m shifting the “hide menu” item to the bottom using JS, what you’re seeing usually means the JS has failed to trigger for one reason or another. It could just be a conflict with either of the plugins you mentioned, I’ll add them to to-do list.

there’s also frequent problems with the nextgen gallery but i think that’s the ngg problem

If you could provide details or any issue I may be able to solve them. In Fluency 2.1.1 I’ve fixed a few layout issues with NGG that were brought to my attention, but there are probably more.

Most “problems” with other plugins that I come across is that their admin interfaces differ too much (structure, style etc) from the core WordPress admin screens and some of my style overrides don’t play nicely.

thanks for the info, I will look into it.

The issue for the one-click plugin updater is just a CSS issue – the plugin works but has display problems when you activate it and Fluency together.

Cool, thanks, I’ll make sure I fix that up.

Fluency 2.1 does not work using the One Click Plugin Updater plugin.

Can you tell me what exactly doesn’t work? Is it that you can’t update Fluency using the One Click Plugin Updater, or is there something in the One Click Plugin Updater that doesn’t work once Fluency is activated?

Also seems to have issues with Headspace2…

A quick look at its plugin page seem to reveal that this plugin uses a lot of ‘non-standard’ style in its admin panel. My guess is that’s what causing any issues.

I will see what I can do about supporting them in the next release.

Yes, I should be able to fix those in the next update.

I don’t want to have to use fly-out hover menus. I like being able to expand a nav menu section and leave it expanded.

I think Jane said in this thread that the menu behaviour (expanding/collapsing etc) most likely wouldn’t change if the design changes.

I should have just left the exmaple flyout menu off of my mockups… ??

If anything, this ‘challenge’ will provide me both positives and negatives around Fluency which I can look to address in the future. Feedback is good ??

As long one of those options continues to be available.

The Fluency plugin will remain available, and will be updated regardless of the outcome of this challenge.

Having the sub-menus fly out to right, rather than open up downward both covers up part of the screen (maybe not a huge deal), but also breaks the ability to leave a commonly used menu left open all the time. That alone should be a deal breaker.

In defense of the flyouts, they are only there while your hovering over the menu, at which point you don’t really need to see what underneath because you should be looking at the menu. I believe the ability to leave a menu expanded is irrelevant if the menu is show on hover, but maybe that’s just me. “Deal breaker” might be a bit strong given that flyouts is how the current menu works when in ‘collapsed’ mode. My reasoning is here: https://deanjrobinson.com/wordpress/design-tweaks-28/

What would the buttons actually do? How would you display the Screen Options? You certainly wouldn’t want to slide in like the current UI, they would be very inconsistent with a button.

They would do something like this: https://www.flickr.com/photos/deanjrobinson/3101608647/ hard to demonstrate everything with a single screenshot

the flyout menus will be terrible to use from mobile devices

yes, agreed, however I doubt the current admin is particularly nice to use on a mobile device either. Theres a reason why there is a native iphone app and numerous “iphone optimised admin” plugins.

also worth saying that there is no reason that the Fluency design can’t have expand/contract style menus (like the current one) my mockups have flyouts simply because that what Fluency currently has.

Theres only so much you can knock together in a couple of hours, with additional time theres probably a bunch of things that I would/will change.

Keep the feedback rolling, keeps me thinking about ways I can possibly improve Fluency in the future.