Skip to:
Content

Opened 10 years ago

Closed 5 years ago

Last modified 5 years ago

#278 closed enhancement (duplicate)

Different xprofile fields output format.

Reported by: Jehy Owned by: djpaul
Milestone: Priority: major
Severity: normal Version:
Component: Extended Profile Keywords:
Cc: djpaul, vpundir@…

Description

It would be very nice if, when creating the field, I could choose link (or HTML) format for it:

  • email (mailto: link)
  • website (http link)
  • plain text (NI SEARCH)
  • skype
  • ICQ

etc. I mean - not only temlates for editing fileds, but also templates for showing them on the profile page.
You know - it looks really stupid when you click "web site" field in user profile, and go to the search page, trying to view all users with that web site value...

Change History (12)

#1 @apeatling
10 years ago

  • Milestone changed from Extended Profiles 1.0 to Extended Profiles 1.1

#2 @(none)
10 years ago

  • Milestone Extended Profiles 1.1 deleted

Milestone Extended Profiles 1.1 deleted

#3 @DJPaul
10 years ago

This is in the BP roadmap for v1.4.

#4 @johnjamesjacoby
9 years ago

  • Milestone set to Future Release

#5 @djpaul
9 years ago

  • Cc djpaul added
  • Owner set to djpaul
  • Status changed from new to assigned

There is a plugin out which lets you do this sort of thing, but ties up with some changes I want to make so I'm taking it.

#6 @DJPaul
9 years ago

  • Component set to XProfile

#7 @sooskriszta
6 years ago

  • Cc vpundir@… added
  • Severity set to normal

#8 @sooskriszta
5 years ago

  • Milestone Future Release deleted
  • Resolution set to duplicate
  • Status changed from assigned to closed

#9 @johnjamesjacoby
5 years ago

Thanks for cleaning this up.

As a general note, our workflow is to leave ticket-closing and milestone-changing to the core team; otherwise the project runs the risk of having tickets get lost in the shuffle.

If you're closing one ticket in favor of the other, we typically keep the older ticket and close the newer one, and drop comments on both tickets with both ticket numbers, to connect them together. This case seems fine, because your other ticket is more specific, but this ticket has ideas that one doesn't, so it may be premature to close it.

If you believe a ticket is worth closing, definitely drop a comment stating so, but please do not close them yourself or change/remove the milestone. Conversely, if a core team member asks for your help, leave a note in your comment stating so, so the rest of the team has the additional context.

Thank you!

Last edited 5 years ago by johnjamesjacoby (previous) (diff)

#10 follow-up: @sooskriszta
5 years ago

Got it.

#11 in reply to: ↑ 10 @johnjamesjacoby
5 years ago

Replying to sooskriszta:

Got it.

I knew you would. Since you spend a lot of time in Trac, it would be great to have your help cleaning things up (if you're interested.) Basically closing duplicates, connecting them together with comments, identifying issues that are already resolved, features already built, etc...

If this sounds fun, and you have questions as you go, ping any of is in #buddypress-dev on IRC, and anyone in the core team will be happy to help you out.

#12 @sooskriszta
5 years ago

Sure thing, will do.

Note: See TracTickets for help on using tickets.