Moss field editing permission control solution (2)-add management link

Source: Internet
Author: User
This series Article I haven't finished it all the time. Some friends are very interested in Moss field permission control and decided to continue writing.
You can read the previous articles:
Codeart wss3.0 (MOSS) Field editing permission control solution (V1.0)
Codeart wss3.0 (MOSS) Field editing permission control solution implementation-Summary
Implementation of the moss field editing permission control solution (1)-management page development and configuration information persistence

In the previous article, we discussed how to save the field editing permission configuration information of a list by serializing and saving data to the list. Of course, this is not the only method, for example, it can be kept in the database.
(Since Moss development, databases are Rarely touched, and list is used for list implementation .)

After the configuration page is developed, we need to combine it with moss perfectly-add a link to this function on the Management page of the list:

This feature is implemented by feature.
The development of feature is not the focus of this series. There are many articles in the garden. Using feature, almost all Moss functions can be extended,
For example, you can manage menus (website operations, website settings, list settings, and list management), deploy eventhandler (also called eventuploer), deploy webpart, and deploy workflows...
For more information, see the SDK.
The following two files are required to add the "field permission settings" management link:
Feature. xml < Feature ID = "E5441FAC-1D99-4ecc-98AA-D76D5BBDCDE9"
Title = "$ Resources: codeart, fieldright_feature_title ;"
Description = "$ Resources: codeart, fieldright_feature_des ;"
Scope = "Site"
Hidden = "False"
Defaultresourcefile = "Codeart"
Xmlns = "Http://schemas.microsoft.com/sharepoint"  
>
< Elementmanifests >
< Elementmanifest Location = "Elements. xml" />
</ Elementmanifests >
</ Feature >

Elements. xml <? XML version = "1.0" encoding = "UTF-8" ?>
< Elements Xmlns = "Http://schemas.microsoft.com/sharepoint" >
< Customaction
ID = "Codeart. fieldvalueeditcontrol"
Groupid = "Generalsettings"
Location = "Microsoft. Sharepoint. listedit"
Sequence = "106"
Title = "$ Resources: codeart, fieldrightsetting ;" >
< Urlaction URL = "~ Site/_ layouts/codeart/fieldeditcontrol. aspx? Listid = {listid }" />
</ Customaction >
</ Elements >

Feature. xml declares the feature ID, name, range (farm, site collection, Web ).
Elements. XML uses a customaction element to add management links. The location attribute indicates that the menu is added to the List settings page, and the groupid attribute specifies that the menu is added to the general setting group.
Urlaction specifies the link page address. Note that ~ The site character ,~ The site is the path of the current web. {Listid} is automatically replaced with the guid of the current list when the system presents the link.
You can use this GUID to obtain the list currently managed: Splist list=Spcontext. Current. Web. Lists [NewGUID (request. querystring ["Listid"])];

For more information about customaction, see WSS feature: customaction to add a site management menu.

The latest version solves previous bugs and adds the edit permission control function to the group:
Http://files.cnblogs.com/jianyi0115/CodeArt_FieldRightSolution.zip

All articles in this series:
Codeart wss3.0 (MOSS) Field editing permission control solution (V1.0)
Codeart wss3.0 (MOSS) Field editing permission control solution implementation-Summary
Implementation of the moss field editing permission control solution (1)-management page development and configuration information persistence
WSS page customization series (2) --- customizing the form pages of a single list
WSS page customization series (3) --- rewrite the form storage Logic
Moss field editing permission control solution (4)-packaging Solution

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.