Fixed :D

Aye its just no fun at the moment and the following is just off the top of my head; There is a cookcomputing dll version conflict if your using the latest version of YAF and MojoPortal; I recompiled MojoPortal using the same versions as YAF.
You need the YAF.Mojo.Dll which provides the URLBuilder for YAF in MojoBuilder (this is what you were looking at in the SVN), it needs to be compiled.
You then need to create a .ascx user control file with using the MojoPortal Module Control to inherit from, and have the <YAF:Forum> tag within that control; or like Bbobb says on the other thread use a .aspx and link the masterpages.
You have to integrate the web.configs.
Follow the same steps for placing YAF within MojoPortal as you would a subfolder i.e. app.config or user.config (if you included the app.config ones in there) settings.

I'm putting in some work to try and help people along with MojoPortal integration; however I am not finished and not sure when I'll have the time to put it together.

All depends on whether you are "distributing the code". I.e. if you are doing this for a client, you have to pass on the full GPL rights to them as well.

If you are purely coding for your own project, then you don't as your not giving it to anyone.

If your site is heavily integrated with YAF and makes use of its methods then the GPLs copyleft will cover your existing site code.

If its pretty much seperate and let say just uses the Forum control in one of its pages and makes use of teh same membership; it doesnt.

It's supposed to create entries in the YAF_Users table; thats the synch working. Without it YAF has no users. What YAF no longer does is use this table for Authentication, so the passwords will be blank in the YAF_user table; in other words it users the provider for that.
The user provider key gives YAF the synch between itself and the Membership provider.
As for why it doesn't have a providerkey I'm unsure and unfamiliar with the Umbraco Membership provider; check to see what datatype Umbraco is using for its providerkey. You can then adjust this in our app.config I believe and then check.

Yeah we really need a way of updating and disabling JQuery for both YAF and DNA through the web.config.

Try using


In the code behind of your MasterPage, see if that helps. I can't remember what other changes I made to get round this problem.

I think this successfully disables the Jquery for both YAF and DNA. The problem I then had was there no quick hack to get around DNA inclusion of the Jquery UI.

Change AspNetHostingPermissionLevel.Medium to .High i think.
Its been mentioned before somewhere I believe but i am solely going of memory.

not seen any issues when i've been developing on 2008 with YAF

Actually I stand corrected; someone fixed that one. Kudos to them.

Lo mate.

Bet you a beer that its when a user posts and upgrades to the next rank. The upgrade routine doesn't pass the boardID or take it into account to get the next rank; they then have a rank thats not linked to that board.

Let me know as this is gonna cause me a migraine when I finally get my multiboard installation running.

Dev's check in fixes to either their own code; or from the list on the bugtracker. Bug tracker gives an indication as to the progress (show stoppers and criticals) as to where we are with the release.

Release does not happy until Jaben is ready to put his name to it, as is his right as Project Manager and that requires his time. Not a question of Devs stepping up to take on more responsibility; though stepping up to take a couple more pathces would be nice