Where does it go? Does this module require you to create a custom “favorites” page for the member so they can view their favorites, or could I simply allow them to view their favorites on their public profile page which I created using the User module?

This is all definately possible!

You can pull the user’s Favorites with the Favorites Entries Tag

hmm… this may make more sense if I actually bought it and used it, but:

If a member id number is provided in the url, then that member’s public favorites are shown.

That seems like it wouldn’t really be public? The member_id would have to be in the URL which I could be mistaken, but that’s only shown when the user is logged in, so how for example, if you and I were members of the same site, how would I view your favorites? My member_id will be different than yours thus I wouldn’t be able to view your favorites because they’re tied to a different member_id.

Doesn’t seem like I could just throw the favorites list anywhere then really? I would HAVE to go in the member profile template that I created since that page would have the member_id in the URL?

I’m probably just confused

Correct… if you, for example, wanted to display the Favorites on the member’s profile, it’s possible (with the combonation of the User Module) because the User ID is in the URL.

If you really wanted to go crazy, you could whip up a member list just for clicking to view that persons favorites…
Although, I’m not sure why you’d want to do that per say.

The Favorites module does several things....

You can view which entries are your Favorites.
You can view others Favorites
When you’re looking at a weblog entry, you can view how many, and who added it to their Favorites.

That’s just the basics… there’s more

It’s neat because you can use it in all different kinds of applications/concepts…

A neat idea might be using it as an itinerary. Each weblog entry could be an event, dated to the event date… then members can add it to their itinerary… so they can then view what they have on the go.

Is there anything in particular you want it to do?

Pie Man - 12 March 2008 08:39 PM

If you really wanted to go crazy, you could whip up a member list just for clicking to view that persons favorites…
Although, I’m not sure why you’d want to do that per say.

The Favorites module does several things....

You can view which entries are your Favorites.
You can view others Favorites
When you’re looking at a weblog entry, you can view how many, and who added it to their Favorites.

I’m understanding a little better now. Still a little fuzzy on if favorites are public or private though? Or can you make them one or the other? Can the current logged in member be the only one to view their favorites? The docs read: “If a member id number is provided in the url, then that member’s public favorites are shown.” If I’m reading it right, that seems contradicting? If a member id is provided in the URL then that members PUBLIC favorites are shown. I’m reading it as if the current logged in user’s member id is in the URL, they could view their own favorites based on the member id in the URL, but how would everyone else view those favorites since everyone else will have a different member id with potentially a different set of favorites (or none at all). I’m just not following on how the logged in member’s id needs to be in the URL to view their favorites and they could also view other’s favorites...since their member id is different than everyone else? I’m probably not making any sense on that… I think I’m confusing myself here.

I really don’t foresee ever needing to whip up a member list just for clicking to view others’ favorites. Just trying to get a grasp on how this works. On one hand you said you’re sure why I’d need a list which people could view other people’s favorites, but then in the “...does several things” list, you said “You can view others Favorites.” But then, a member id has to be in the URL to view the “public” favorites so that would indicate to me that they are not actually “public” since a member id has to be in the URL? One member isn’t going to know another members id (unless they guess it) so with the member id having to be in the URL, that indicates that only the logged in user can view his/her favorites but they cannot view anyone else’s favorites as the member id in the URL would be wrong?

Sorry I’m talking in circles here… this is just confusing.

Pie Man - 12 March 2008 08:39 PM

Is there anything in particular you want it to do?

I have a couple sites that it had crossed my mind to use it on. I have a CSS gallery built with EE where I could allow people to favorite their favorite designs and then keep track of them in their profile page or own favorites page. The most recent thing I thought about using it for was a golf website I’m developing that would allow people to favorite courses that they liked so they could quickly find information about them in the future (without searching).

deronsizemore - 13 March 2008 05:53 AM

I’m understanding a little better now. Still a little fuzzy on if favorites are public or private though? Or can you make them one or the other? Can the current logged in member be the only one to view their favorites? The docs read: “If a member id number is provided in the url, then that member’s public favorites are shown.” If I’m reading it right, that seems contradicting? If a member id is provided in the URL then that members PUBLIC favorites are shown. I’m reading it as if the current logged in user’s member id is in the URL, they could view their own favorites based on the member id in the URL, but how would everyone else view those favorites since everyone else will have a different member id with potentially a different set of favorites (or none at all). I’m just not following on how the logged in member’s id needs to be in the URL to view their favorites and they could also view other’s favorites...since their member id is different than everyone else? I’m probably not making any sense on that… I think I’m confusing myself here.

What it’s saying is that if you access the template with the Favorite:Entries code, it will show your OWN favorites. If a Member ID segment is included in the URL, then it will show for that specific person. I thought there was a way to make it private (in the sense that if someone added a Member ID to the URL it would still ONLY show THEIR OWN, but it does not seem to be available yet… I will submit as a feature request in the meantime.

deronsizemore - 13 March 2008 05:53 AM

I really don’t foresee ever needing to whip up a member list just for clicking to view others’ favorites. Just trying to get a grasp on how this works. On one hand you said you’re sure why I’d need a list which people could view other people’s favorites, but then in the “...does several things” list, you said “You can view others Favorites.” But then, a member id has to be in the URL to view the “public” favorites so that would indicate to me that they are not actually “public” since a member id has to be in the URL? One member isn’t going to know another members id (unless they guess it) so with the member id having to be in the URL, that indicates that only the logged in user can view his/her favorites but they cannot view anyone else’s favorites as the member id in the URL would be wrong?

Sorry I’m talking in circles here… this is just confusing.

Haha… it’s early in the morning!
It’s not that you should or need to link to other person’s favorites… but the option is there. In this case, if you decided to display their favorites on their member profile for the public to see.... it’s possible. If you want to go all out and make a directory of member names that can be clicked, and it will show their favorites… it’s possible. So yes, you can view other member’s favorites. Those are two of the simplest ways.

deronsizemore - 13 March 2008 05:53 AM

I have a couple sites that it had crossed my mind to use it on. I have a CSS gallery built with EE where I could allow people to favorite their favorite designs and then keep track of them in their profile page or own favorites page. The most recent thing I thought about using it for was a golf website I’m developing that would allow people to favorite courses that they liked so they could quickly find information about them in the future (without searching).

This is all definately possible.

Pie Man - 13 March 2008 06:40 AM

What it’s saying is that if you access the template with the Favorite:Entries code, it will show your OWN favorites. If a Member ID segment is included in the URL, then it will show for that specific person. I thought there was a way to make it private (in the sense that if someone added a Member ID to the URL it would still ONLY show THEIR OWN, but it does not seem to be available yet… I will submit as a feature request in the meantime.

Ok, I see now. I’m not sure if a feature request would be needed?  In my case anyway, I’m using the User module for the front end member stuff. I’ve got a profile page set up using user:stats and I’ve encased the user:stats inside of an “if logged_in” conditional so that only the member logged in can view their profile. If someone else tried to view the favorites (assuming I placed them on that same member profile template with user:stats) they essentially would be private for only the logged in member regardless of what was in the URL, correct?

Pie Man - 13 March 2008 06:40 AM

Haha… it’s early in the morning!
It’s not that you should or need to link to other person’s favorites… but the option is there. In this case, if you decided to display their favorites on their member profile for the public to see.... it’s possible. If you want to go all out and make a directory of member names that can be clicked, and it will show their favorites… it’s possible. So yes, you can view other member’s favorites. Those are two of the simplest ways.

Have you seen any type of consistent situation when people have needed to use the favorites module and have a need to link to other member’s favorites? I guess maybe if you have a weblog and then you have the “favorite it” link and then maybe below that you could have a link that says “see others who have this as a favorite” to where maybe that link takes you to a page with a list of member names of people who have saved the article as a favorite (and each one of their names would be click able so you could click their name and view the other things they’ve favorited). I don’t think I’d need this functionality, but just throwing this out there. Would this be one instance of maybe when you’d need to display a list of members so others could view their favorites? What other ways have you seen?

Pie Man - 13 March 2008 06:40 AM

This is all definately possible.

Ok cool, thanks. I may go forward with using this then.. at least on my golf site.

deronsizemore - 13 March 2008 10:35 AM

Ok, I see now. I’m not sure if a feature request would be needed?  In my case anyway, I’m using the User module for the front end member stuff. I’ve got a profile page set up using user:stats and I’ve encased the user:stats inside of an “if logged_in” conditional so that only the member logged in can view their profile. If someone else tried to view the favorites (assuming I placed them on that same member profile template with user:stats) they essentially would be private for only the logged in member regardless of what was in the URL, correct?

The if logged_in conditional applies to anyone logged in, not just the owner of those favorites… so in theory, if you place the Favorites:Entries loop on a profile page (with the User:Stats), then anyone viewing that profile will see that persons favorites… this might be what you’re after… maybe not, but that’s the way it currently works. That’s why I’ve submitted a feature request to have some sort of parameter or something, so that you can restrict it so that each member can only view their own…

deronsizemore - 13 March 2008 10:35 AM

Have you seen any type of consistent situation when people have needed to use the favorites module and have a need to link to other member’s favorites? I guess maybe if you have a weblog and then you have the “favorite it” link and then maybe below that you could have a link that says “see others who have this as a favorite” to where maybe that link takes you to a page with a list of member names of people who have saved the article as a favorite (and each one of their names would be click able so you could click their name and view the other things they’ve favorited). I don’t think I’d need this functionality, but just throwing this out there. Would this be one instance of maybe when you’d need to display a list of members so others could view their favorites? What other ways have you seen?

In regards to viewing another persons favorites in a public manner, I haven’t seen any other use for this than what I’ve mentioned above… where you’d list it in a profile. I’d imagine there’s other uses out there though. The idea you mentioned would work too…

It also brings me to another feature of Favorites: Favorites Shared Tag Documentation
It basically allows you to display “Those who liked this entry also liked....” and will show other entries that others have commonly favorited (in addition to and in coorelation to the entry you’re viewing)

Pie Man - 13 March 2008 10:54 AM

The if logged_in conditional applies to anyone logged in, not just the owner of those favorites… so in theory, if you place the Favorites:Entries loop on a profile page (with the User:Stats), then anyone viewing that profile will see that persons favorites… this might be what you’re after… maybe not, but that’s the way it currently works. That’s why I’ve submitted a feature request to have some sort of parameter or something, so that you can restrict it so that each member can only view their own…

Actually, you’re right and I was confused again. I’m using the {if logged in} on a totally different section of the site. On my profile page, so that only the current logged in member can view his/her profile, I’m using the is_mine tags. Yes a feature where only the logged in member could view their favorites would be great then! 

Pie Man - 13 March 2008 10:54 AM

It also brings me to another feature of Favorites: Favorites Shared Tag Documentation
It basically allows you to display “Those who liked this entry also liked....” and will show other entries that others have commonly favorited (in addition to and in coorelation to the entry you’re viewing)

Now that’s cool! I could definitely use that for my golf site on the courses section… “those that liked this course, also like:”

So, correct me if I’m wrong here… in a sense, if one member favorites an entry, that members favorites page is technically viewable by anyone (logged in or logged out) as long as they know that user’s member id? In theory, the user’s favorites page is for all intents and purposes hidden from everyone else because everyone else would need to manually type a member id into the URL (which they probably don’t know anyway)?

Oooooh, just saw this as I’m looking through the Favorites docs:

Append the word “private” as a segment, and the entry will be added to the user’s favorites list, but will not display on their public favorites list.

{exp:weblog:entries}
{title}
<a href="{path='site/favorite_add'}{entry_id}/private">Make this entry a private favorite</a>
{/exp:weblog:entries}

So looks like I could just use that, and anything that is saved as a favorite by a member will be private so regardless of what’s in the URL, the favorites won’t show?

Awww man… that rings a bell too.... I hope Mitchell doesn’t see this… I haven’t been reading my Docs again!! 

Quick! hide me!