dreamingbear

Forgive me for waiting so long, but lots of other stuff in the line…

just reuploaded the plugin to https://test.comunitamagnificat.org/large/bp-registration-options.zip, if someone needs it. This file is the original plugin plus a diff file to apply. I have another folk that’s working on the plugin since I have no time left… will post any progress here.

About user->data->user_status, I stepped the code with a debugger and found there the infamous sixty-nine. user->user_status was nonexixtent.

The function wds_bp_registration_options_bp_before_member_header is non-existent, so no action would be performed by the filter. But the entire idea of the filters is to display a message to the unapproved user that he is, actually, unapproved. So the same message can go both on the activation and the member profile page.

I am perplexed instead on the change I made on line 18 of core.php. If I remember, without this change the plugin did not work at all, either not blocking registration or not showing the page or something similar. But on second thought the call to is_admin is there just to avoid calling the block while the dashbosrd is active.. I must look into this

the same with bp 1.6.4, wp 3.5.1, latest activity plus, theme salutation

Link to patched plugin:
https://test.comunitamagnificat.org/wp-content/uploads/bp-registration-options.zip

same problem during test upgrade

That’s it! My table was in worse shape, so I had to REPAIR … USE FRM (see MySQL docs) but in the end it worked. I was put on the right track by a comment in nav-menu.php that said

/**
 * Save posted nav menu item data.
 *
 * @since 3.0.0
 *
 * @param int $menu_id The menu ID for which to save this item. <strong>$menu_id of 0 makes a draft, orphaned menu item.</strong>
 * @param array $menu_data The unsanitized posted menu item data.
 * @return array The database IDs of the items saved
 */
function wp_save_nav_menu_items( $menu_id = 0, $menu_data = array() ) {

Browsing the bad database, I’ve seen that table wp_postmeta is broken. phpMyAdmin reports “#126 – Incorrect key file for table ‘./a3953875_wpress/wp_postmeta’; try to repair it “.
May this be part of the problem?

It’s the same. The good copy of the databasa that’ on a local machine has all nav_menu_item with status ‘publish’. The bad copy (that is, the ‘pseudo-production’ copy on the server) had all nav_menu_items with status ‘draft’. I re-saved two of the pages the nav_menu_items referred to, and now I have two new nav_menu_items with status ‘publish’ but the manu are still broken. I need to fix this, becaus I am going real production very soon…

Did you succeed in fixing this problem? I have it too. It’s strange that this behaviour appeared all by itself after some weeks during which nobody messed up with site administration.