Troubleshooting

Common problems and how to resolve them. If a problem is not covered here, check the FAQ or contact support from the WB Plugins > Profile Pro > Support tab.

The plugin will not activate, or deactivates itself

“BuddyPress Profile Pro is ineffective as it requires BuddyPress to be installed and active.” BuddyPress is not active. Install and activate BuddyPress, then activate this plugin. The plugin checks for the BuddyPress class on every load and deactivates itself if it is missing.

The plugin silently deactivates with a BP Resume Manager notice. BuddyPress Profile Pro and BP Resume Manager cannot run at the same time. If the BP_Resume_Manager class is present, this plugin deactivates itself. Deactivate BP Resume Manager, then activate BuddyPress Profile Pro again.

The settings page is blank, or there are no default groups

On first activation the plugin seeds three default groups (Education, Professional Experience, Contact Details) and their fields, but only when the group and field options are still empty. If activation ran while those options already existed, or the seeding did not complete, the Overview tab shows no groups.

Deactivate and reactivate the plugin to re-run the seeding. Because seeding only writes when the options are empty, this does not overwrite groups you have already created.

Members cannot see the extended-fields tab

The tab is shown only to the profile owner and to site administrators. A member visiting another member’s profile will not see the tab in the navigation. This is by design. Configured groups still appear in the read-only profile view based on each field’s visibility.

If the owner cannot see their own tab, confirm the plugin is active and that the profile tab name on the General tab is set. Changing the tab name changes its URL slug, so old bookmarked tab URLs stop working after a rename.

The profile search form does not appear on the members directory

Confirm that Enable profile search is checked on the Profile Search tab and that you saved the settings. Also confirm your BuddyPress members directory uses the standard BuddyPress template. The form is injected automatically above the directory tabs; if your theme replaces that template, place the [wbbpp_member_form] shortcode where you want the form instead. See Shortcodes.

Profile search returns no results

Check that the Search Mode matches the field type. For example, “contains” on a Year Dropdown may return nothing because year values are stored as plain strings and matched exactly. Try “is” instead. Search modes offered per field type are described in Profile Search Settings.

Every member shows up in every search

This usually means the field key in the search configuration does not match the stored meta key. On the Field Settings tab, expand the field and compare its Field Key and Meta Key with the search row. See Field Settings.

The Google API key will not verify

The Verify button tests the key with a live Google Places request and stores the result. It reports “not-verified” when:

• Google returns a non-200 HTTP response, or
• Google returns HTTP 200 with status: REQUEST_DENIED in the body.

Make sure the key belongs to a Google Cloud project with both the Maps JavaScript API and the Places API enabled, and that any key restrictions allow requests from your site. Re-verify after rotating the key. Place Autocomplete fields are only offered to members once the key verifies.

A shortcode profile shows the wrong member’s data

[wbbpp_show_profile] reads field values with the logged-in user’s ID. On a standalone page it reliably shows the logged-in user. On a BuddyPress profile route for a different member, the group display toggles by the viewed member but the field values still come from the logged-in user. Use the plugin’s own profile tab for viewing other members’ data. See Shortcodes.

A repeater image or file field lost its uploaded file

This was fixed in version 2.6.0: repeater image and file fields no longer lose a previously uploaded file when a row is saved without re-selecting a file. Update to 2.6.0 or later.

A custom field type throws a fatal error

When you register a field type through wbbpp_add_extra_field_types, the plugin dispatches its input by calling bprm_get_field_{type_key}_html(). If that function is not defined when a field of your type renders, PHP fatals. Define the input function before any page that renders your type. See Extending Field Types.