I just had a look at the Knowledge Network team blog. It seems like they have released a build last week. Completely missed out on it. Have not tried it out, but it does seem to be cool. Head over to the Knowledge Network Team Blog if you want to know more about it.
Please visit the CNN-IBN site and light an e-candle for the Mumbai Victims. For every candle lit – CNN-IBN channel is giving 1 Rupee to the victims. Thank you for you time and efforts.
I am working with some custom area templates, and was interested to know if anyone has found any workaround for some bugs. I did not find anything on the ms knowledge base and was unable to locate any information on google.
1. Area Templates do not consider the hidden attribute while showing in the list of templates. When you set an area to let you choose which template to use when creating subareas, all the templates available are presented in that list. Even if you have set the Hidden=”True” (which is the default) in the webtempsps file, it displays all the templates. Is there any fix so that it only displays the templates which we want to appear in that list?
2. Multiple configurations in an area template gets ignored. If you have multiple configurations in the onet.xml for your area templates, on creation, it always seem to use the default configuration. Even if you choose the second configuration ( after adding them to your webtemp file ), it creates the area with the default configuration.
Has anyone found a solution to these problems? Or any workaround? The site ones work fine. Just the area ones are all affected by this. I am running SPS 2003 with SP2. I am still trying to find some workaround if there is any for these problems, and will post here if I found any. Please leave a comment if you have found any workaround.
I ran across this problem today when I tried to run stsadm and kept on getting an error saying that it is unable to connect to the configuration database. I was able to go thru the site and the central admin pages successfully, but this problem was happening only when accessing via stsadm.
You need to give you current logged user access to the SharePoint databases. I found a very nice explaination about this problem on Mitch Milam’s site. Thanks Mitch.