I have been doing research, and I havent found a way to remove the WHOLE site actions menu for "non-content editors" in sharepoint. I have researched this:
<SharePoint:SPSecurityTrimmedControl ID="SPSecurityTrimmedControl2" runat="server" PermissionsString="ManageSubwebs">
but this only hides certain links in the site actions menu, what if I want to hide the whole thing so you cant even see 'site actions' in the upper left hand corner of the page for certain users. The content editors should be able to see this menu, but non-content editors should not be able to see this menu at all.
Try changing PermissionsString to "ManageWeb"... it will hide for all users who doesn't have ManageWeb role... How are you going to categorize "certain users" in your question, if it is by role, you can quickly have a look at msdn
i know its a bit of a cheat way round, but i used this from codeplex... you can sepecify what users see it through groups http://spribbonvisibility.codeplex.com/
the only issue is it does remove the users name from top right, and leaves no menu there...
Related
I want to implement scrolling to a particular section on click in Liferay, but I have no idea how to add functionalities in Liferay.
I have created a page using multiple fragments and in the top of the page I have headers of the sections and on click of a header the page should be scrolled to that particular section.
Attached page screenshot link below for reference
The easiest way to scroll to some place on the page is to place an anchor there, e.g. with <a name="scrollTarget"/>. In your navigation, you'll just link to this by Scroll to Target and you're set.
Of course, this can be done a lot fancier, with an animated scroll etc, but the basic start is this. There's nothing Liferay-specific hidden here - pick any of the more fancy methods, create fragments with the proper markup, and make sure they're used on your page.
My Home page with all the webparts has a number in brackets after the webpart title.
How can I remove this?
Ok, I found a solution.
Stay at the page that you can see "XXX [Number]"
Click the "Page" button at the top-left corner
Click the "Edit Properties" button
Click the text(possibly blue) "Open Web Part Page in maintenance view"
Check the duplicate web parts you want to remove and click the "delete" button above.
(If you are NOT sure which are the web parts you want to keep, please delete them all and re-add the web parts you need. Otherwise, you might end up with some white space on the web part page.)
The number gets added because you have multiple web parts configured with the same title. You need some change on the webpart's title to make the [2] disappear.
Alternatively, you might want to hide the webpart's title. Edit your webpart, expand the "Appearance" section, and select the option "None" on the "Chrome type" dropdown.
This was driving me nuts too. Follow the steps here for the steps to delete it through the webpart maintenance page:
http://www.spdeveloper.co.in/tipsntricks/pages/opening-webpart-maintenance-page.aspx
Add a space after the title, this way you can use the same title for multiple webparts.
Of course you should delete the "extra" duplicate web parts using the same title if they aren't visible on the page. But it's not unusual to want the same title showing for different web parts. In that scenario, a simple fix is to add a space after the title in the Appearance section of the duplicate web part's properties. If there are multiple web parts with the same title, just add more spaces. SP will treat the titles as unique.
I have created a webpage using Backbone.js and Marionette.js that mostly consists of a bootstrap accordion view that displays a list of items when the accordion header is clicked. Each item can also be clicked, which will show a hidden div of detailed information that pertains to that particular item.
I would like to make this site accessible to people who might not be using a mouse (Maybe they're visually impaired and using a screen reader? Maybe they just don't like clicking things? Either way.) I'm thinking that this would mean being able to press the Tab key to get to the accordion, pressing Space or Enter to open the accordion, Tabbing down (or down arrow key?) through the list items, and then using Space or Enter to show the selected item's hidden div.
I'm finding it difficult to find information on how to add a feature like this, since searches like "How to make an accessible website that can be used without a mouse" mostly turns up blogs on what a developer should do to add accessibility to a page, and not much on how to do it.
Currently, the page doesn't really respond to any keyboard buttons. Any tips or resources you could share would be extremely appreciated. I've been fiddling with ARIA role tags, but I'm either not doing it right or it's not the answer here.
You have to use tabindex
https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement.tabIndex
Screen readers automatically read whatever element is the activeElement
It's currently impossible for a user to tell if clicking on something will load something in their current page or take them to a new page. I feel that this is why many sites use hoverable dropdown menus, so that they don't have to click anything. This can be messy, though, if you don't intentionally hover over something and forms the habit of hovering over things and expecting a result.
There should be a standard way to identify links as external or internal. Maybe a little hover effect or symbol used in the link?
Is there anything like this, and if not, should there be?
I believe by "internal" you mean that the link does some javascript thing, and does not load a new page.
I think an effective way to indicate an immediate action is by using a button style, rather than a standard looking link. A blue underlined link somehow seems much more likely to jump to a new page than something that looks like a button.
Give the button an appropriate label and/or symbol that indicates an instant action. For example, a button that expands a section open might use a little triangle that rotates as the expanding happens.
You can also establish a consistent style for "internal" actions, use a particular color or style for links that don't take the user to a new page. Sometimes I use blue for normal links and a shade of purple for internal ones.
In general, I find it isn't that important to specify. If a user sees a link or button that like it will get them what they want, they will click it. It is up to you as the designer of the website to decide if the most appropriate action is a new page, or an action on the current page. Unless the user is going to lose some work they have done, going to a new page shouldn't be a problem. If it really took the user by surprise, they can always go back. In my experience, users don't worry about it either way.
**Hello..
i am creating English To Gujarati Dictionary WinForm Application.
I need to set a system wide hook to the right click context menu on for text selection.
it means when this application is running,and if user selects word from any program and right click on it gujarati meaning of that word should be displayed as menu item.
How to do this?
or any other options like Registery Programming,shell extentions etc...?
i have to do this,even if you say its not possible.
so please help me.**
Hooking the mouse activity is the easy part. See SetWindowsHookEx, and lots of questions regarding hooking in SO. This way, you can tell when the mouse is right-clicked.
Getting the selected text is the harder part. See WindowFromPoint, for starters. You'd have to recognize the control, and if appropriate get the selected text from it. This will not always be possible using simple Win32 functions, if the control is complex.
Adding the translation to the right-click menu is probably the impossible part. Adding stuff to explorer context menu is not a problem, because explorer provides that possibility. But various applications will have various right-click menus, without a way to extend them. They might not even use Win32 for the menus, for whatever reason. A better option, IMO, would be one of the following:
Forget about changing the right-click menu. Open a window next to the point of selection with whatever content you want, and let the application show its own right-click menu.
If the user right-clicks while, say, pressing shift, show your own right-click menu, and don't pass the message to the application. So the user will see only one menu, which is yours. The user must of course be aware of this combination.