Jump to content
  • entries
    78
  • comments
    135
  • views
    2,218

Forums on Sharepoint

TheScarfedOne

Entry posted by TheScarfedOne

20,684 views

 Share

OK - so Sharepoint has Forums (well, discussion boards as they call them) built in. However, not really as full featured as I would like - or as you would see elsewhere on the Internet.

 

So... came across this a while back from Codeplex. Problem... not strictly WSS3/MOSS 2007 compatible. Fair dooooos - thought would leave it alone a bit.

 

Most other things on our system are sorted now, so I went back to it. This is what it looks like (attached), and also a link to it...

 

7d1243008171-forums-sharepoint-forums_final.jpg

 

http://www.codeplex.com/spforums

 

==========================================

 

Ok - getting this to work on WSS3/MOSS 2007 is a bit of fun. To save you looking through the discussion on codeplex - here is how to get it working. :troll:

 

1. Download and install the AJAX Enabler Kit solution from RL-Soft. This saves you loads of time - and also means you can use loads of other AJAX webparts on your sites.

 

Link: http://www.rl-soft.com/en/downloads/sc/RLSoft.SharePoint.Features.AjaxEnabler.rar

 

You will need to install and deploy the solution. In the download is a script to do this for you. From your Sharepoint Central Admin Site, you can then activate the solution. A guide is attached - even though this applies to the Contact Us webpart solution they also have (handy too!) - the first bit deals with the AJAX enabler.

 

Link: http://www.rl-soft.com/en/downloads/d/ContactUs_Documentation.pdf

 

2. Download the SPForums solution from Codeplex and run the .msi on your system.

 

Link: http://spforums.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=53

 

You will then need to go to C:\Program Files\WPPackager\. In there you will find a {string} folder containing the .cab, .xml and some other bits.

 

3. You then need to deploy the web part package. Open a command prompt and run the following command from the

C:\Program Files\WPPackager\{14aa60ab-2b6b-4254-b45e-0ef7b8b2a201} folder:

 

Copy the code below, and paste into a new text document in the same folder. Rename it as deploy.bat

 

stsadm.exe -o addwppack -filename "SharePointForums-1.2.0.0_Bil Simser.cab" -globalinstall -force

 

4. Add the following to the .master page for your websites, just before the </BODY> tag:

 

<script>
function ProcessOwsForm(ctl, argument) 
{ 
if (frm.fPreviewMode) 
{ 
var LcantSaveText = "This form cannot be saved when previewing this page."; 
window.alert(LcantSaveText); 
return; 
} 
if (frm.FValidate(true)) 
{ 
frm.FPostProcess(); 
var theForm = document.forms['aspnetForm'];
__doPostBack2(ctl, argument); 
} 
}
function __doPostBack2(eventTarget, eventArgument) 
{
theForm.__EVENTTARGET.value = eventTarget;
theForm.__EVENTARGUMENT.value = eventArgument;
theForm.submit();
}
</script>

 

5. Add the webpart to a page as you would usually - and job done.

 

Enjoy!

Edited by TheScarfedOne

 Share

4 Comments

Recommended Comments

EduTech

EduTech 7,792

Posted

I can also confirm this works perfect :) much easier this way. and took minutes to install and nothing can get broken.

 

Looks much better than the normal "discussion boards"

Swarve

Swarve 0

Posted (edited)

That's awesome - I've been banging my head up against a wall trying to get this installed for the last couple of days. Just one problem - when I attempt to add the web part, I get the error "Unable to add selected web part(s). Sharepoint Forums 1.2.0.0: The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT:0x80131040).

 

Any idea what this means and how I can resolve it?

 

Thanks in advance,

 

Swarve

Edited by Swarve
Swarve

Swarve 0

Posted

Finally got it working after removing all instances of Sharepoint Forums, then continuing from step 2 above - don't know what happened, but it seemed to work in the end. Thanks for posting this solution, it's been invaluable!

 

Swarve

TheScarfedOne

TheScarfedOne 2,161

Posted

Ah - if you had a previous version of the solution on your environment - you would end up with an assembly version mis-match to what is registered as safe in your web.config. Remember - that your web.config reflects the internal unique identifier in the assembly dll. This does change between versions.

 

With a copy of the webpart already on a page - you would therefore get this error as the webpart on the page (old version) would not match the assembly.

 

Glad you are all sorted - sorry I didnt see the problem sooner to save you some head scratching.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...