|
|
Rank: Advanced Member
Joined: 5/19/2007
Posts: 70
Location: Plymouth
|
So Jaben, We are about to test this beast out, thanks for ALL the hard work team of developers. That being said, if we green light it on our site, can we move this to production and still be able to upgrade to the release? Or will we be stuck on the beta if we go live? Thanks, Don Don Alcombright Thrash Magazine - Check out my forum!"thrash harder!"
|
|
|
Rank: Advanced Member
Joined: 9/25/2004
Posts: 40
|
Yes, thank you! Seriously. Such clean integration with membership/role/profile from such a nice forum system is exactly, precisely what I've needed for a long time.
|
|
|
Rank: YAF Head Dude
Joined: 10/10/2004
Posts: 2,949
Location: Honolulu, HI
|
Don_Thrash wrote:So Jaben,
We are about to test this beast out, thanks for ALL the hard work team of developers.
That being said, if we green light it on our site, can we move this to production and still be able to upgrade to the release? Or will we be stuck on the beta if we go live?
Thanks,
Don Well, my only concern is that there are still issues being ironed out. Granted, they are not show-stoppers, but I just want to be forthright. But, there will be no problem upgrading from BETA to Release, of course. "When you are grateful, fear disappears and abundance appears”." 
|
|
|
Rank: YAF Forumling
Joined: 5/15/2008
Posts: 7
|
Where can I find documentation on integrating it with ASP Membership? I want to run YAF outside of DNN but using the same membership. I can't find any docs on ASP.NET Membership. Thanks!
|
|
|
Rank: YAF Forumling
Joined: 6/6/2008
Posts: 2
Location: UK
|
I cant say thank enough!
Finally it works cleanly with asp.net providers, thank you!!!
The only thing id ask: is can you provide more detailed update logs (eg: which projects / files have been updated), as im currently manually having to compare files (not fun!).
Especially in regards to any changes to the "YAF.Classes.Data" or "YAF.classes.Providers" projects and any database changes, as ive rewritten the database schema to tie in with an existing project im integrating with (basically just refactored it to tie in with our database naming convensions).
Thanks again!
|
|
|
Rank: YAF Forumling
Joined: 6/6/2008
Posts: 2
Location: UK
|
PS: Any chance of hosting it on a SVN server eg: CodePlex, as then i could use Client diff tools for update comparisons?
Thanks, again!
|
|
|
Rank: Advanced Member
Joined: 9/25/2004
Posts: 40
|
Actually, Sourceforge has SVN. I've done modifications to fix Medium Trust and target 3.5, and I'm using Tortoise to work with the YAF repository. They're even pretty good at logging their commit.
|
|
|
Rank: YAF Developer
Joined: 7/12/2005
Posts: 1,219
Location: on Dock Street
|
Quote:I've done modifications to fix Medium Trust Interesting, anything you can share with the community? As i'd like to know the problems with Medium trust.  "It's a case of RTFM.. the only problem being we don't have a manual!" When I post FP:Mek in a topic, I'm leaving my footprint there so I can track it once I get into coding/supporting. (Yes I stole this off Ederon  )
|
|
|
Rank: Advanced Member
Joined: 9/25/2004
Posts: 40
|
Sure, there were two issues, iirc. Both are very simple to fix. 1. PMList's View property used a TypeConverter that did things not allowed in Medium, like the way it uses reflection. PMView's only purpose was to indicate the mode, with almost all of its work being simply converting from string and serializing itself. It did't really *do* anything other than say "I'm Inbox mode". So I changed PMView to an enum. Code:
public enum PMView
{
Inbox = 0,
Outbox,
Archive
}
That way the code using PMView didn't need to change much. They could still test with "View == PMView.Inbox", and the markup in cp_pm.ascx (View="Inbox"  didn't need to change either. I had to refactor the FromQueryString and ToQueryStrinParam methods. I made them part of the PMList class instead. I completely removed PMViewTypeConverter since it wasn't needed anymore, and removed the associated attribute from PMList.View . Regression tests showed no problems from this change. 2. YAF.Classes.Utils.SendMailThread.SendMailThreaded() wanted to assign HttpContext.Current, and that throws a security exception in Medium. I oouldn't figure out why HttpContext.Current was needed, since the method will be running outside of any httpcontext anyway, so I removed the assignment and changed the test for null to test against _appContext instead (not even sure that SendMailThread needs _appContext, but I left it). So far no problems with this-- mails re going out. I'd be happy to crank out a patch file in Tortoise for merging if you'd like. The other changes are just referencing the 3.5 assemblies and the 3.5 AjaxControlToolkit assembly. I just needed to get YAF working well with VS 2008 and 3.5 .
|
|
|
Rank: YAF Developer
Joined: 8/7/2006
Posts: 68
Location: Boston, MA
|
If you'd like to email me the changed files (or create a patch) for the PM-related changes I'd be happy to integrate those for you.
Edit: I've integrated wesclyburn's PM-related changes.
|
|
|
Rank: Member
Joined: 11/7/2007
Posts: 15
Location: UK
|
hi all
well i have not tested new release yet but i'm using old release and i have some very small seo suggestions. So that before releasing it will be more seo friendly (like vBulletin )
if you people like i'll send it here
thanks
Good Luck
|
|
|
Rank: YAF Forumling
Joined: 6/11/2008
Posts: 1
Location: Ha noi
|
when i setup forum. I found a error. It message is  could you tell me how to fix this error.
|
|
|
Rank: YAF Head Dude
Joined: 10/10/2004
Posts: 2,949
Location: Honolulu, HI
|
Just refresh and it will fix. I'll update the code to reflect this minor bug fix on a new installation. "When you are grateful, fear disappears and abundance appears”."
|
|
|
Rank: YAF Forumling
Joined: 5/13/2008
Posts: 8
|
How straight forward is it to upgrade from the 1.9.3 alpha to the new beta? The install.txt only shows options for upgrading from 1.9.1.x and below, or new installations. Has the DB changed at all from the alpha?
|
|
|
Rank: YAF Forumling
Joined: 5/13/2008
Posts: 8
|
I ran the the beta install to upgrade a database that the 1.9.3 alpha installed on it. The installation procedure said it completed successfully, but redirected me to the forum homepage where I received the following error:
Server Error in '/YetAnotherForum.NET-beta' Application.
Cannot insert the value NULL into column 'UserID', table 'YAF-playground.dbo.yaf_UserGroup'; column does not allow nulls. INSERT fails.
The statement has been terminated.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Cannot insert the value NULL into column 'UserID', table 'YAF-playground.dbo.yaf_UserGroup'; column does not allow nulls. INSERT fails.
The statement has been terminated.
Source Error:
Line 106: this.Controls.AddAt( 0, _header );
Line 107:
Line 108: this.Controls.Add( forumControl );
Line 109:
Line 110: // add the footer control after the page...
|
|
|
| Users browsing this topic |
|
Guest
|