I'm fine with Active Topics becoming "My Topics" but does it now work differently? I haven't downloaded the source for a few weeks, but have noticed here that there is no longer the ability to view all posts since last visit or by date range. I hope this isn't going away. It was working perfectly in previous 1.9.4 builds, where the selection range was persisting rather than having to be reset on each "Active Topics" page load.

I love the Active Topics feature. Any inside word is much appreciated.

Thanks,
Dave

Update: Oh, never mind. I see it under the "My Topics" - "Active Topics" tab. Don't know how I wasn't seeing it! Splendid. Looking forward to the next release! Thanks for the great work guys.

I didn't expect to see RC1 for a while yet. You guys are smokin' hot! Congrats to Jaben, Kamyar and everyone on the YAF Dev Team. Thank you!

-Dave

Thanks for the input, guys. I'm a "whatever works" coder, and seeing how AjaxPro works so well with Thanks I'm going to definitely explore it. But as you say, Jaben, I probably will lean toward the web service route for most client functions in the future as I've been for a few months now.

Have a good one.
-Dave

Thanks for the update, DJ. The incremental approach is really the way to go, IMO. And YAF makes upgrades a snap (98.7% of the time, anyway. )

I'm confident you'll be donning that Superman cape soon and back kicking Lex Luther's butt again.

-Dave

I wish I knew more about YAF Membership cause I don't want to give you bad info. Perhaps someone else will fill the void.

For membership YAF uses its own providers or ASPNET membership. Very cool, actually. You'll see a number of tables yaf_prov_application, yaf_prov_user, etc which pattern the ASPNET Membership data structure so YAF user data can site on top of either it or ASPNET Membership. I've always used YAF with ASPNET membership, so my yaf_prov tables are empty.

The provider sql scripts are in the /install/mssql/prov folder and executed on install/upgrade.

There's a lot of dynamic object creation in YAF, including the application name prov_application if you look at the yaf_prov_getuser stored procedure which executes yaf_prov_createapplication. If I were analyzing this I'd focus here, at the yaf_prov_CreationApplication proc, and yaf_prov_GetAllUsers procs. I'd downshift Visual Studio into debug mode and hang out in YAF.Providers.YafMEmbershipDBConnManager's GetAllUsers() and GetUser() methods to wait for some bits to come a long to see what might be missing in the underlying data. Or set a breakpoint in login.ascx.cs login1_authenticate() and let PageContext.CurrentMembership.ValidateUser() take you through the process.

G'luck!
-Dave

I don't know what the official YAF line is on upgrades from 1.9.1.2, but personally I wouldn't consider going straight from 1.9.1.2 to 1.9.4 without first satisfied with a stable 1.9.3.

Even commercial products like Community Server that cost a gazillion dollars require incremental upgrades. (They did. Don't know about the very latest version as I haven't touched it.) The primary issue is ensuring a complete database upgrade. I am assuming you have a local development server and can quickly throw up a temp database and site. If performed exclusively in a shared hosting environment, then no, not a very fun venture. But if you're installing a beta, then I am also assuming that you plan on upgrading more than once anyway.

Then again, your issue could be something else.

Do you have a web.config in the root directory? Any other site applications in co-existence?

-Dave

There are guys better versed in YAF.NET to advise you, but I do a lot of upgrades and I would certainly recommend going from 1.9.1 to a working 1.9.3, then from a working 1.9.3 to a working 1.9.4 beta.

Glad there's no DNN action.

Sorry, missed the history on this. You were using 1.9.3 and upgrading to 1.9.4? And DNN is involved?

You're getting this when logging in to YAF the first time after upgrading? Sounds like a Provider issue in the web.config, in the <Membership /> element specifically. Sorry I can't be more specific. I'd check there.

-Dave

Kamyar, you must be thinking of someone else using the word "expert." I really do appreciate your work and helping me get the final bits in place for "Thanks." I have a "Favorites" function in Sueetie with 1.9.3 that I added as a theme button in the post footer, then would use JQuery and call a WCF service. (screenshot attached.) I like your model much better. When 1.9.4 is released and I get to blog about the great new features I'll definitely make sure you get the credit for supplying the new Favorite logic. People are going to love Thanks, too. That's going to be the subject of its own post.

Exciting!

Best regards,
Dave