U4-63 - APIs to deprecate

Created by Shannon Deminick 20 Jun 2012, 15:48:25 Updated by Shannon Deminick 21 Jun 2017, 07:57:25

Relates to: U4-7

Relates to: U4-44

Relates to: U4-45

  • Log API
  • Remove ‘legacy’ project -> was a seperate dl in 4.1 ! (pretty sure)
  • ITree - Rewrite any existing trees in the core using it

Comments

Lee Kelleher 21 Jun 2012, 15:25:50

Re: Member API - before any one considers deprecating it completely, I would suggest they try using a Membership Provider exclusively to access Member data. It is extremely painful to work with Member profiles.


Jeroen Breuer 24 Jun 2012, 20:16:27

I agree with Lee. I still use the old member API, because it's easier to use and works better with multiple member types.


Dan Booth 26 Jun 2012, 20:09:30

Yeah, the deprecated member API is much easier to work with than creating your own (which you still have the option to do). Perhaps find a more efficient way of storing properties, though, to improve performance?


Richard Soeteman 28 Jun 2012, 07:57:52

+1 for Lee's comment so much easier than profiles and you can set the text ;-)


Lee Kelleher 28 Jun 2012, 08:55:48

Actually, I'm thinking that the Member API should be un-depreciated (appreciated? reinstated?), as there is no way the Membership Provider can fulfil the "real world" requirements of multiple member-types and property-fields.


Dan Booth 28 Jun 2012, 12:00:34

I'd vote for un-deprecating (reinstating) it, too.


Jeroen Breuer 28 Jun 2012, 12:05:53

Me too


Shannon Deminick 21 Mar 2013, 20:59:55

yeah i agree, I don't think we should obsolete the members api... we should actually un-obsolete it!

Using the .Net Membership API is good for when you simply want to deal with the results/etc... of the Membership API like logging in, etc... or maybe creating a user on the front-end registration. But really the Umbraco Membership API is used to manipulate data in our database, just like content. The .Net Membership shouldn't be used for that. Once we create a new members API using PetaPoco (assuming that we are doing this), then sure we can obsolete the old members api.


Asbjørn Riis-Knudsen 21 Mar 2013, 22:50:18

Yes, please create a new Member API to fit with the rest of the new API. I thought that was the plan for 6.1 all along, but apparently not...


Shannon Deminick 21 Mar 2013, 22:52:04

It'll get done, we're just lacking the time atm


Asbjørn Riis-Knudsen 21 Mar 2013, 22:53:15

No hurry - just as long as you don't remove the old API in the meantime ;)


Shannon Deminick 21 Mar 2013, 22:55:53

That's the opposite of what I just did... I 'un-obsoleted' the old api so that it's not marked as obsolete. Before many of the methods said 'use the membership apis instead' but that is nearly impossible for some of the member data stuff.


Jeroen Breuer 10 Jun 2013, 23:44:48

Just assigned this to Shannon because we talked about what to obsolete during the retreat.


Shannon Deminick 21 Jun 2017, 07:57:25

Closing issue due to inactivity - see blog post for details https://umbraco.com/blog/issue-tracker-cleanup/


Priority: Task - Pri 1

Type: Task

State: Closed

Assignee: Shannon Deminick

Difficulty: Easy

Category: Architecture

Backwards Compatible: False

Fix Submitted:

Affected versions: 4.5.2

Due in version:

Sprint:

Story Points:

Cycle: