BuddyPress.org

Issue solved.

It was a function at child theme filtering one of the xprofile fields.

Thanks a lot for your concern.

https://buddypress.org/support/topic/how-to-allow-users-to-edit-profile-fields-from-their-buddypress-profile-page/

https://buddypress.org/support/topic/multiple-profile-group-fields-in-registration/#post-111943

the basic php filter code was share with me, needed for this. Now i’m investigating how to put a ‘Rich Text’ checkbox on the fields editor.

Feel free to help over here
https://wordpress.org/support/topic/how-to-add-textarea-field-to-buddypress-xprofile-custom-fields-type

thx!

thank you very much!

your solution is slightly different from this other one, which helps me learn.
https://wordpress.org/support/topic/how-to-add-textarea-field-to-buddypress-xprofile-custom-fields-type?replies=5#post-8009134

thx!

note, i also edited the .po file, and generated a new .mo from that

you can download my zip here:
https://www.dropbox.com/s/nx0ox3weg5khlpi/buddypress-xprofile-custom-fields-type-JW-TEXTAREA.zip?dl=0

i noticed modernizr.js mentions ‘textarea’. Not sure what it’s doing, but i don’t think this is the cause:
‘ var c = a.html5 || {},
d = /^<|^(?:button|map|select|textarea|object|iframe|option|optgroup)$/i,
e = /^(?:a|b|code|div|fieldset|h1|h2|h3|h4|h5|h6|i|label|li|ol|p|q|span|strong|style|table|tbody|td|th|tr|ul)$/i,
f, g = “_html5shiv”,
h = 0,
i = {},
j;
(function() {
try {
var a = b.createElement(“a”);
a.innerHTML = “<xyz></xyz>”, f = “hidden” in a, j = a.childNodes.length == 1 || function() {
b.createElement(“a”);
var a = b.createDocumentFragment();
return typeof a.cloneNode == “undefined” || typeof a.createDocumentFragment == “undefined” || typeof a.createElement == “undefined”
}()
} catch (c) {
f = !0, j = !0
}’

hmm, ok, taking a different approach. i’m inspecting donmik’s files in ‘buddypress-xprofile-custom-fields-type’. Hope that’s ok, donmik!

i found ‘datepicker’ in:

bp-xprofile-custom-fields-type.php
classes\Bxcft_Field_Type_Datepicker.php
lang\buddypress-xprofile-custom-fields-type.pot
lang\en_US.mo
lang\en_US.po

(ignoring the non-english files for the moment).

i simply duplicated all the ‘datepicker’ code-chunks in these files, and replaced ‘datepicker’ with ‘textarea’.

also duplicated the file ‘classes\Bxcft_Field_Type_Datepicker.php’, renamed it ‘Bxcft_Field_Type_Textarea.php’, and removed any date-specific code i found there.

and so on and so forth.

then i zipped it, uploaded to wordpress, activate, and added my new Textarea field to a form.

i actually got no errors, and actually got a text field on my registration form!

unfortunately, it’s only a one-line textbox, not a multiline textarea.

hrm. In inspector, the displayed field is:

<input type="string">

so something in donmik’s code, or BP, or WP, is causing this to render as an <input> rather than <textarea>

….

thx for that! css will be our quick-and-dirty fallback. But not a long-term solution.

it would be cool to develop a proper control. i’m guessing this is part of the recipe for displaying on the user-profile page:

bp_profile_field_data()

but would be awesome if someone can share the full recipe to develop a custom field.

i’m looking here for clues-

Profile Fields Loop

and also searching the buddypress install for ‘multiselectbox’– just to see how that one gets handled 🙂

thx!

hi, thx for reply.

enter in user registration form, and display in user front-end profile.

want to be able to use it like any other field in “user fields” editor.

thx!

Solved.

It’s this plugin:

Introducing Conditional Profile Fields for BuddyPress plugin

really appreciate the awesome developer who built this!

not this one. Unfortunately doesn’t work on WP 4.4.2
https://wordpress.org/plugins/buddypress-conditional-profile-field/

Still working on this, I discovered something while debugging:

1) If I set my priority to 1​ like so:

add_action('bp_core_activated_user', array( $this, 'setup_registration_metadata'), 1 );

then in my setup_registration_metadata() function I use add_user_meta() to capture the first_name & last_name values at that point in time. Thankfully it makes an entry in the usermeta table with the expected value from get_user_meta($user_id, 'first_name', true)

2) Unfortunately, something else apparently is hooked afterwards (possibly a method from the “Enable BuddyPress to WordPress profile syncing”, which then overrides any value I had set for those fields so that in the end the WordPress fields are now incorrect or wiped.

It seems apparent to me that the “Enable BuddyPress to WordPress profile syncing” option is the culprit, but would that be a bug that the setting is grabbing the wrong values because even if I don’t hook into bp_core_activated_user the meta values that were successfully stored at registration are then wiped during activation? For example:

• first_name becomes the username
• last_name is cleared completely

Setting the priority to 20 the results show that by that point the originally stored meta_value(s) have already been wiped.

<?php do_action( 'bp_before_profile_loop_content' ); ?>

<?php if ( bp_has_profile() ) : ?>
	<ul class="accordion">
	<?php while ( bp_profile_groups() ) : bp_the_profile_group(); ?>

		<?php if ( bp_profile_group_has_fields() ) : ?>

			<?php do_action( 'bp_before_profile_field_content' ); ?>

				<li>
				  <h5 class="accordion-title <?php bp_the_profile_group_slug(); ?>"><?php bp_the_profile_group_name(); ?><span class="accordion-icon"></span></h5>
				  <div class="accordion-content">
						<dl class="dl-horizontal">

							<?php  while ( bp_profile_fields() ) : bp_the_profile_field(); ?> 

								<?php if ( bp_field_has_data() ) : ?>

									<dt><?php bp_the_profile_field_name(); ?></dt>
									<dd><?php bp_the_profile_field_value(); ?></dd>

								<?php endif; ?>

								<?php do_action( 'bp_profile_field_item' ); ?>

							<?php endwhile; ?>
						</dl>

				  </div>
				</li>
			<?php do_action( 'bp_after_profile_field_content' ); ?>

		<?php endif; ?>

	<?php endwhile; ?>
	</ul>
	<?php do_action( 'bp_profile_field_buttons' ); ?>

<?php endif; ?>

<?php do_action( 'bp_after_profile_loop_content' ); ?>