I have a requirement that I need to add a extra tab in SiteManager->Administration->Users
This tab will have functionality of Users only but with more advanced filters, this is because HotFix/Version Upgrade of Kentico can update the default and code functionality of Kentico, so we don't want to update its basic functionality
So it's a risk if we change core Advanced Search functionality therefore we need to have a new page/webpart with our needed requirement.
Any help is appreciated, we have been looking on it from a while, didn't found any solution for the same.
In version 7 I would do it this way:
Create your new search page by copying the existing one along with its underlying controls (to ensure upgrade won't break your changes)
Make your customizations
Navigate to CMS Site manager -> Development -> Modules -> Users -> Edit User -> User interface
Add UI Element e.g. "Advanced search"
set Target URL to your page
set Element is custom to true
Related
When I view the properties (F4) of my MVC 4 project I cannot see the typical properties for setting up windows authentication. I believe they used to show, but now they don't. If I start a new MVC project these properties exist. How can I make them available again?
OK, so I will try to answer my own question....
An MVC project has two properties sheets. One can be seen by right-clicking the project and selecting the context menu item 'Properties'. This property sheet is big and grey and takes up the window normally used for viewing code. I will call this 'SheetA'.
Another property sheet is seen when selecting the project in the solution, then strike the F4 key on the keyboard. This is a typical property sheet - looks like a thin spreadsheet with a white background and cells with grey borders, typically a tab near the solution explorer. I will call this 'SheetB'.
Looking at 'SheetA', if the user navigates to the tab on the left called 'Web' and selects server 'IIS Express', then the option to define Anonymous Authentication is visible on 'SheetB'.
If a user instead selects 'External Host' on 'SheetA', then Anonymous Authentication is no longer visible on 'SheetB'.
This is probably because the authentication is now part of the server configuration not the local environment.
I dislike the idea that choices affect the visibility of properties. I would rather it affect the enabled property of the properties so at least I know I am not going crazy - "I saw the entry right here a while ago and now its gone!!!"
Displaying the default right-click context menu is pretty straightforward and fairly well documented here and elsewhere on the web.
I based one largely off of Andreas Johansson's framework
How to show system menu of a file in C#
http://windows-tech.info/19/e5ad8751fc63816b.php).
My app provides a simple explorer-like view to display some custom attributes (thanks Windows for getting rid of IColumn). The right click context menu works great.
However, I'm now finding myself really wanting the right-drag context menu (Copy here, Move here, Create shortcuts here, cancel, plus any additional add on handlers like TSVN).
I assumed that there would be an additional flag I could add to QueryContextMenu uFlags, but alas I don't see one. Is there an alternative to QueryContextMenu to extract the menu items that are relevant to the right-drag menus?
I'm working on a project a tool to track holidays and there are some parts of this application (report administration), the role "user" should not see. So far that works without problems, but somehow the representation of the parts that a "user" should not see look terrible:
The permission who should see something on the page is controlled in the Web.sitemap
<siteMapNode title="Vacation" roles="Administrator,Location Business Leader,Business Leader,Department Leader" description="All employees with vacation" url="~/EmployeeView/UserVacationGrid.aspx" />
If someone had the same problem and, could you give me some good tips or a solution how to fix this I would really appreciate it!
The problem is that whatever you are hiding (either client side or server side) is not encapsulating all of the controls associated. So for example, if you were using an ASP.NET menu, then you could hide a menu option server side with the following code:
switch (UserRole) {
case "Administrator":
Menu1.Items.Item(0).Enabled = false;
break;
}
These controls will make sure to collapse all the associated HTML with that option. If however you are using your own controls, or hiding things client side you need to make sure to hide the entire container (i.e. <div>) containing the control. A good way to do this is with jQuery:
$("#divVacationControl").hide();
Your best bet at figuring out which controls in IE8 are not being hidden and leaving that undesirable look is to use the IE developer toolbar. You can access it via F12 button, or Tools -> Developer Tools It can also be downloaded from here: http://www.microsoft.com/en-us/download/details.aspx?id=18359
Once open use the 'Select Element by Click' function to inspect the non-hidden elements and inspect the DOM. You can then find the culprit not being hidden and check your logic.
The last method if it only happen in a certain browser is to set its compatibility mode. Not saying this is the best way but it's an option. You can read how to do this in a blog post of mine below; just use IE7 or whatever worked for you. I would not recommend this approach as a long term solution unless this is a corporate intranet app that you have total control over the environment.
Specifying Document Compatibility Modes for ASP.NET Intranet Sites using IE8
I have an existing Outlook Add-In that was developed for a client for Outlook 2003/2007. One of the requirements was that the add-in would disable the default New email button on the toolbar. I was able to do this by accessing the CommandBars object of the Explorer windows.
They are now looking at migrating the tool to Outlook 2010. Obviously the CommandBars object is no longer available, and I have not been able to find anything regarding programmatically disabling any of the built-in buttons on the ribbon.
Is it possible to programmatically change the state of any of the built-in buttons?
Any suggestions here would be appreciated
If group policy is an option, the "right" way to do this in Outlook 2010 is via group policy settings. From Technet:
"Verify that you have the necessary security permissions for the GPO: either Edit settings or Edit settings, delete, and modify security. For more information about permissions that are needed to manage Group Policy, see “Delegating administration of Group Policy” in the Group Policy Planning and Deployment Guide (http://go.microsoft.com/fwlink/?LinkId=182208).
In Group Policy Object Editor console, expand User Configuration, expand Administrative Templates, and then expand the application for which you want to disable commands (for example, double-click Microsoft Excel 2010).
Click Disable items in User Interface, click Predefined, double-click Disable commands, click Enabled, select the commands that you want to disable, and then click OK."
Full documentation here: http://technet.microsoft.com/en-us/library/cc179143.aspx#section3
Good luck!
I would like to know if there is a way to prompt the user when activating/deactivating a feature within SharePoint.
The background behind this is that I have a SharePoint solution that deploys several configuration files that are modified by the user when deployed to the site. I would like to either allow the user to decide whether or not to overwrite the files when activating or deactivating a feature.
Thanks guys!
Do you need this to work on ANY feature that is activated in your site, or just on features that are developed by you? If this is the latter case, you can add an event handler (SPFeatureReceiver) to your feature and catch the feature activated event.
EDIT: As per #Muhimbi's comment I finally understood the question - you want to allow user edit some properties and only then to activate the feature. In this case, I would suggest to define the feature as "hidden", so it does not show up in "web features" and "site features" list. Then create a custom page for "administration" of this feature, which would allow the user to override the settings in question etc. Then, register this administration page with SharePoint (again, deployed as a feature, these two features may be stapled together). Quote a good article about it can be found here: http://www.tonstegeman.com/Blog/Lists/Posts/Post.aspx?ID=13
EDIT2: found a similar article here on SO: SharePoint Feature Activation Form
One of the responses gives a good point - "The problem is, you don't always know where your feature activation code is going to run. If you turn on the feature using stsadm, it will execute in stsadm.exe, not the web process."