Using Confluence server 6.2.3. I have a user who tells me nothing happens when clicking on the "dot dot dot" menu in the upper right of a Confluence page. He's trying to look at the version history for a page. He tried/says:
I wonder if there's something in his environment, but don't know where to start.
I also can't find a keyboard shortcut for that menu. There is not one listed on the lists of keyboard shortcuts I've found. Is there one available? There are shortcuts for all the links right next to it!
(What is the real, true name of that menu anyway? I can't find it anywhere in the documentation.)
Thanks in advance for any ideas.
Hello Michelle,
Thanks for reaching out to the Community for the strange behavior of the meatball menu not being interactable. Firstly, from your notes, you mentioned you’re currently running Confluence 6.2. This version of Confluence is currently end of life and we ask you to plan to upgrade to a minimum of Confluence 6.7 or higher. Further information about our currently supported versions may be found at Atlassian Support End of Life Policy.
With that out of the way, we need to figure out what's happening with your user's session. We would be interested to know the following;
We look forward to hearing back to help find the cause of this odd behavior.
Regards,
Stephen Sifers
Thank you so much for your reply. I have shared this with my user for more investigation. He is pretty busy right now so it may take several days to respond. I will circle back.
(And yes, there is a plan in place for moving forward into a more current version. This is outside my control but I am looking forward to it!)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Okay, my user sent me some very helpful info including a video and I think I know what the problem is, but I don't know quite enough about CSS to fix it.
On a few of our spaces, we have a custom search box and help links panel that "floats" in the upper right of the screen just below the "save" "watch" and "share" icons. Here my user is mousing directly over the tools meatballs, and there's no pointy hand:
When he mouses directly *above* the meatballs, he does get a pointy hand:
My user isn't seeing this behavior in spaces that have no floating help panel. I was able to replicate his observations.
Here's the CSS that manages the appearance / position of the panel, which was created by the previous wiki admin. There is a little CSS in the site stylesheet which displays the labels at the very top of the screen, I can supply that if needed. I welcome any suggestions or tweaks that can bump the custom search / help panel out of the way of the menu button. I'm still a rank beginner with CSS.
Our users rely heavily on the search panel which searches only that specific space, so removing it altogether isn't an option.
/* style for the Livesearch widget */ div.search-macro.search-macro-medium div.search-macro-query {width: 210px;} /* style for IE */ div#NavLiveSearchWrapper {position: absolute; top: 2.5em; right: 0em; width: 20em;} /* style for non-IE */ @media screen and (-webkit-min-device-pixel-ratio:0) { div#NavLiveSearchWrapper {position: absolute; top: 2.5em; right: 2em; width: 20em;}} /* prevent page elements from overlapping the assistance panels */ h1#title-text {margin-right: 320px;} /* style for the help links */ div.helplinks {width: 200px;} /* style for IE */ div#helplinks {position: absolute; top: 6.25em; right: 10.5em; width: 20em;} /* style for non-IE */ @media screen and (-webkit-min-device-pixel-ratio:0) { div#helplinks {position: absolute; top: 6.25em; right: 10.5em; width: 20em; background-color: #ffffff; text-align: right;}} /* prevent page elements from overlapping the assistance panels */ h1#title-text {margin-right: 320px;}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Michelle,
Thanks for reporting back and confirming there is a customization that may be impacting the meatball menu. My suggestion moving forward would be to plan an upgrade and test within a staging instance and from there troubleshoot the customization. The reason I would suggest this is your version is currently end of life and a new version of Confluence are readily available, these new versions may not function the same with your customization and it would be best to resolve your issues on a later version to avoid conflicts during an upgrade in the future.
Here are additional resources to help with setting up a staging instance and upgrade;
Regards,
Stephen Sifers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Further update, I was able to adjust the CSS to move the search box down far enough to not interfere with clicking the button.
Thanks again Stephen and when our wiki admins upgrade us I will make a point to check for correct operation in the dev environment.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.