Thread

I’m looking for a solution to link a weblog entry to a member from a specified group.

Does anyone have an idea to make this happen within EE?

Thanks in advance!

So do you need the author to remain different from the member? Cause if not, just set-up the member as an author, even if they don’t have publishing rights, their name can be selected from the pull down menu.  If the author and member need to remain separate, then I guess the question is how frequently do you need to do this? how many members do you have? and maybe a bit more detail on what you are hoping to accomplish.

No, the member ain’t the author. It’d be a seperate field.

There are 950 members (...and counting) and we want to use it with all the new blog-items, about 10 items per day. We want to use this field to connect a blog item to a member who gave the hint to publish.

I can think of two ways off the top of my head.

(1) Assuming you already have the member name with the submission data, just create a custom field to store that data in, you can then create a quasi relationship between that data and membership information, using queries. Benefits are that its quick and easy, as well as fairly flexible. Cons are you have to trust people’s typing abilities and if names aren’t provided you’d need to look the up.

(2) Create an extension that allows member data as a field and field type for the system. Benefits are you could add a pulldown menu or multi-select menu to any weblog/section that required it as needed. Downside is its not as quick or easy to develop, but could be beneficially to the whole community 😊

I use the text field and custom queries one for a number of purposes, way past but including membership. The queries once developed aren’t that complicated, I could post a few examples.  The second option would probably still require a custom query if you wanted to display something like entries associated with a member; but would possibly streamline data entry as well as insure consistency.

Thanks for your suggestion. I hoped there was a out-of-the-box solution for this issue, but a workaround with a simple query would work for me.