I noticed in MSDN forums, many of them are struggling with creation of sub-sites using webservice in sharepoint.
I take a look on that, Because they are all try to use CreatSite method in Admin webservice. But that will help only on creating SiteCollections.
Then how we can create a susite? It’s very easy if you are look in to Meetings webservice. This will have a CreateWorkspace method.
URL for Meetings webservice: ~site/_vti_bin/meetings.asmx
CreateWorkspace([Site Title],[Site Template],[LCID],[TimeZone Information]);
MeetingWebService.Meetings WMService = new MeetingWebService.Meetings(); MeetingWebService.TimeZoneInf tz = new MeetingWebService.TimeZoneInf(); XmlNode xnode= WMService.CreateWorkspace(“sitename”, “STS#0”, 1033, tz);
:) Cheers guys
March 5, 2010 at 11:52 AM
any idea what might be going wrong?
November 15, 2015 at 4:41 AM
Great advice, but I think that your rnmmcoeedation of adding the URL of the applicable site is very difficult for Site Owners to maintain. If you are creating a special group for Project Managers, as in your example, it’s probably to give them extra permissions in select areas of one or more sites (i.e., a few lists or libraries), not a whole site. I definitely think that the About Me section should be filled in when you create a special security group with a description of the basic intentions for the group (for example: Use this group to identify Project Managers who will be able to assign tasks and view PM-only libraries). However, I think it’s really hard to expect site owners to remember to add the URL of each and every list that the group has been assigned to especially if the group is used on multiple sites. Fortunately, in SharePoint 2010, even without a third party tool, you actually CAN look at the group in one place and see what it has access to. If you are in the Group, select Settings > View Group Permissions and you will be able to see where this group has access all across the entire site collection. It’s a pretty handy feature and is probably a bit more realistic than relying on site owners to remember to keep that About Me area up to date with each list and library. I’m a big, big fan of third party tools to help with permission management, but this is one area that SharePoint 2010 can handle on its own.