Meanwhile, work for YAF and MojoPortal integration coming to a ready to publish stage.

This is published because of some inpatient users =) No real dead line but it would be presumably published  already soon.

i17.fastpic.ru/big/2011/0312/ba/fea2ac68112b320b2685d00808d680ba.png

http://i17.fastpic.ru/big/2011/0312/cd/77e82c837b53b80d366a642d38f265cd.png

http://i17.fastpic.ru/big/2011/0312/cd/5d94b2a8840ecb0050d1e8acacd99fcd.png

http://i17.fastpic.ru/big/2011/0312/e4/067ebae4ab5502d4569299e929d970e4.png

http://i17.fastpic.ru/big/2011/0312/90/14e1dbd131dc4440be1ab3fb881ac190.png

http://i17.fastpic.ru/big/2011/0312/1c/d66aa4d111548b622685d12ada6d221c.png

Hi, Rick.

I can't say exactly, because it heavily depends on YAF current state too. Recent release required some integration files changes and even in the latest YAF release some unpleasant things were found.

But anyway a sort DIY kit  and HOW-TO will be published until the end of the month,

if I don't encounter any horrible bugs. Currently I'm testing latest version  on my site and I want that both communities get it as soon as possible. I'm tired to wait when it will be PA too.

It's not a piece of cake despite the fact  it's rather easy at the first glance.

Best, bob.

Basic content of  MojoPortalUrlBuilder.cs Technically it's all the required content of YAF.Mojo.dll

using System;
using System.Web;
using mojoPortal.Business;
using mojoPortal.Business.WebHelpers;
using YAF.Classes;
using YAF.Core;
using Intelligencia.UrlRewriter;

namespace YAF.Mojo
{
    public class MojoPortalUrlBuilder
        :  RewriteUrlBuilder
    {
     
        private static string _baseUrl = null;

        public override string BuildUrl(string url)
        {
            string scriptName = "";
            PageSettings currentPage = CacheHelper.GetCurrentPage();
         
            scriptName = currentPage == null ? HttpContext.Current.Request.ServerVariables["SCRIPT_NAME"] : currentPage.Url.Replace("~/", "");

            if (!Config.EnableURLRewriting)
            {
                scriptName = HttpContext.Current.Request.ServerVariables["SCRIPT_NAME"];

              
                url = url.Replace("&", "&");
                if (scriptName.Contains("install"))
                {
                    return Config.AppRoot.Replace("~", "").Trim() + scriptName;
                }

                return string.Format("{0}?pageid={1}&{2}", scriptName, currentPage.PageId, url);
            }
            else
            {
            }          
                url = url.Replace("&", "&");           

                string pageid = HttpContext.Current.Request.QueryString["tabid"];              
                return scriptName.Replace(Config.AppRoot.Trim(), "");
           
        }

    }
}
 

I've published already all that's required. it's not a problem to write a MP-YAF control and it works. I think that if someone wants to integrate it but has no skills he can  contact someone who has like Joe. I have no doubts that you can cope with the rest yourself.

Best, bob.

Hi,

I use YAF 1.9.5.6 from svn and MP 2.3.6.4. You should not encounter any problems with it. Really, I can't help with it as I don't encounter any problems with url rewriting. It has 2 YAF boards in 1 MP site and even in the case it works fine. I use it with Postgre as database but it doesn't matter.

I think you have problems with Forum.aspx.cs control.

There's a profile sync problem and you should enter display name by hand in YAF,  but nothing more. 

Really, I've posted exactly the code I use on my site. Try to move all entries from user.config to web.config.

Make sure that you've enabled it for YAF in Forum.ascx.cs control.

Page.EnableViewState = true;