ALPHA SOFTWARE: NOT FOR PRODUCTION FORUMS

UPDATED 2/6:

Fixed bug with EncodeString in Membership when there is a salt.

Fixed major bug with password resetting SQL in Membership.

Fixed bug with rehasing answers in Membership when changing a password.

Fixed bugs associated with "salt" setting in Membership and it's inconsistant handling.

Fixed bugs with membership password encoding not actually encoding anything.

Fixed bugs with membership not encrypting passwords.

Removed email templates directory. Moved email templates into language for localization.

Also added HTML support to template emails and send mail code in YAF.

Improved Unicode email handling in mail sending code.

Dramatically improved Send Mail Thread queue system so there won't be sending of duplicate emails anymore.

Moved almost all email sending into the Send Mail Thread so the forum feels faster and performs better.

Fixed bugs related to deleting users in admin.

Fixed and improve display of Access Masks in admin.

Running "Lost Password" for a user who is not approved will now resend the verification email to them.

Added confirmations to Approve All/Delete All in Administrator.

Added "recommended" web.config file for NEW installations of v1.9.3 which is setup to use SHA1 password hashing and salts. (ONLY use on new installs.)

Update install.txt to reflect changes.

Fixed/Improved Search SQL to exclude deleted topics and search guest usernames.

Improved Membership Upgrade code from v1.9.1.x and below to do much more error checking.

Other misc bug fixes.

UPDATED 1/27:

Fixed constraint.sql issue.

Fixed "Allow Quick Answer" issue.

Updated "Rules" code added "Show Registration Rules" option.

Added BBCode processing caching.

Fixed issue with "Require User Login"

Fixed issue related to & in Verification emails.

Fixed issues related to response not ending after redirect.

UPDATED 1/26:

Fixed major security flaws.

Made contact buttons CSS and added skype button.

AJAXified collapsible stuff.

Tons of bug fixes and coding changes throughout.

Special thanks to Ederon on this release -- he did a TON!

Here it is folks!

A release of YAF that supports Memberships, Roles and Profiles. Now, I cannot say this software is ready for production. In fact, I'm sure it a bit buggy. That's why it's I'm asking for your help in making this software production-ready.

For testing by tech-savvy

Given the huge task of handing bugs and features for this software, I kindly request that only the more-techy of you attempt to install this pre-release version. I won't be providing installation help as this is not a standard community release.

Release Goal

The goal of this release is to get issues worked out. It is not to get into "why didn't X feature get put in". We aren't looking to add more feature right now -- just trying to get the current new features stable. Then we will free to add new features. Now I'm not saying I don't want to hear suggestions -- but just understand the situation.

Lanuages

All languages need to be updated to the latest in english.xml. Help with this is appreciated.

Development Team

Thanks to MJHufford, MicScoTho and WTilton for their contributions. Special thanks to Mek and Ederon who pull a lot of weight on this release! I couldn't do it without your help guys! :cheesy:

Contributing to YAF

How can you support YAF, you ask? Just help a bit. Test the software and post bugs. Answer a few questions on this forum for other, less knowledgeable, YAF admins. If you really want to go crazy, write a little documentation in the wiki...

Notes

v1.9.3 will upgrade from v1.9.1.x and below fine. I don't suggest you do it until you feel the software it ready.

Bug Reports

http://forum.yetanotherforum.net/yaf_topics32_v193-Issues.aspx 

DNN

Sorry to say, DNN support was not a goal for this ALPHA release. That's not to say you cannot get it working with this release. If you do play around with it, please report back your findings.

Compiling

YAF v1.9.3.2 doesn't requires Web Application Project to compile! In fact, most of the main source is dynamic compilation.

BIN: Includes the compiled forum and forum page files without the source.

SRC: Includes the compiled forum and forum page files with full source.

YAF-v1.9.3.3-ALPHA-SRC.zip 

YAF-v1.9.3.3-ALPHA-BIN.zip 

EDIT: damn lot of changes, I won't do the changelog... :cheesy: for anyone who wants to get a picture, I suggest looking at SVN changelog, but you'll have to list through lot of lines.

[img]http://imaj.at/image/28547[/img]

Thanks for reporting, there should have been

dbo.sysobjects

sys.sysobjects

EDIT: Jaben updated zips in first post, they include this fix already.

we try the last version what you made.But some problems have settled in sql types.. I want to setup system MSSQL2000.but forums has SQL inde image ntext like SQL server 2005 so ı couldnt setup what can ı do

Soryy Bad English 😞 :)

http://forum.yetanotherforum.net/yaf_postst5110_Installation-problem.aspx 

I can't wait to test it 🙂 .. (tonight I will..) thank you all of YAF stuff!

I'm also putting the finishing touches to my latest project's RCs, hopefully by end of this weekend. This would allow me to spare some hours to try out the alpha version.

It would be a good idea to suggest which part of the forum you want us to pay a closer attention to. I won't be using the asp.net membership as it doesn't fit to my requirements, yet.

I have a site that currently uses the default normal AspMemebership provider, and I Wanted to integrate yaf into my site. Now do I have to redo my application to use the YAF provider? Or can I change the provider YAF uses with minimal code.

Why did you guys decide to go to the Asp membership route if you were just going to create your own provider anyway. I guess I don't understand what was gained.

Thanks for all your hard work, I got it installed and it looks great.

Hi Jaben,

Dynamic Compilation (Web Site model?) has many security challenges in particular in Web Hosting environments. For instance I won't be able to sign the assembly if I need to for security reasons.

I would like to ask you in strongest term if you have chosen the "web site" model for your project to offer us the "Web Application Project" model too. Converting "web site" projects back to "Web Application Project" model is virtually impossible for the hard work is involved.

The web site model conversion is that hard that I'm going to add some funtionality to my tool to ease this process since many people want to go back to the old model which it worked so well.

I had the same issue with .NetBlogEngine project and I also raised the same concerns with them. I'm hoping they would do something about it in 1.3 version.

Cheers

There is YAF provider, which is default. But as of nature of providers, you can replace it with your own provider (be it default ASPNET one or any other) and it all works without single change in the code.

@CSharpHeaven - is it really so hard to turn it into web application project? I'll be doing it myself for my production forum and from my experience, it's not a hard work.

Hi Ederon,

Let say I was happy to change the entire project from Web Site to Web Application Project. Since I don't own the project there are many things out of my control. For every update I have to do the same repetitive work. It means I have to find out which pages had been updated before applying the same changes to them again. I doubt it you would want to take the responsibility to keep a list of the pages you modify all the time, do you?

This is not just about the hard work, the web site model that even Microsoft admitted was a big mistake is not a nice model at all. Even though DotNetBlogEngine is not owned by me but I found it ridiculous to deploy it with actual code behind files. I'm talking about the principals.

Microsoft keeps blaming the developers for not writing security conscious codes then again they come up with a horrible deployment model like that.

One of the other issues is that most web applications written in web site model have no namespaces. This is the part which takes most of the hard work for conversion. For every web page there is you have to modify two pages to insert the namespaces. You can create layers using namespaces and avoid duplicate types but in web site model you can't do that because everything is on the root.

Think of the implications that brings when you want to integrate YAF with your own web site. The first thing you would notice is that there are two _Default types.

Anyways, I can only try to cross my points in here the final decision is yours.

BTW, I had a e-news letter from GoDaddy and they officially listed YAF to their application offerings. :cheesy:

Cheers