Support » Plugin: BulletProof Security » [Plugin: BulletProof Security] Commenting Error on Buddpress Forum

  • Resolved sweetmelody

    (@sweetmelody)


    Once a comment is posted to a (Buddypress) forum topic, the following error message displays:

    Forbidden
    
    You don't have permission to access /groups/vegetarian-helpdesk/forum/topic/TEST/ on this server.
    
    Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

    The error can be removed by turning on the Default Mode.

    Please help, thank you!

    http://wordpress.org/extend/plugins/bulletproof-security/

Viewing 15 replies - 16 through 30 (of 48 total)
  • Okay, will work on the corrupted issue after the security shield is back on line.

    I have just deleted the .htaccess_old, in order to create a new .htaccess from within BPS, do I need to to click both ‘create default.htaccess File’ and ‘create secure.htaccess File’?

    Plugin Author AITpro

    (@aitpro)

    I click both buttons just so i don’t make a mistake. That choice is entirely up to you, but it is better to safe then sorry.

    No good, reinstalled BP and the problem remains. 🙁

    forum post

    Switched to default BP theme and deactivated GC but the situation ain’t improving too.

    Plugin Author AITpro

    (@aitpro)

    Ok well i guess this is going to remain an unsolved mystery of where that coding glitch/bug is coming from so you will just have to comment out the BPS security filter so that it no longer blocks this malformed query string. 😉

    I wonder if something like this is happening – any individual forums created prior to BuddyPress 1.6.1 will still use the old query string coding? they only way that would be possible is if the old forum links, etc are stored in your database and not processed from the BuddyPress coding itself. Very unlikely, but i cannot think of anything else besides maybe some sort of caching or Cloud issue where the old files or data is being cached or stored.

    Tried to reply to an old forum post but same error, sigh…

    Not going to include the filter as it’s risky, hope BP1.6.2 comes early and solves the problem.

    Many thanks.

    Plugin Author AITpro

    (@aitpro)

    The coding issue has been solved in BuddyPress 1.6.1. I have personally verified this on a testing website. I have followed up with several people who were experiencing this problem with older BuddyPress versions and all of them have confirmed that installing BuddyPress 1.6.1 has solved this old issue. So maybe installing BuddyPress 1.6.2 will solve this issue on your site or maybe whatever problem is occurring on your website will continue to happen even after installing BuddyPress 1.6.2.

    I should have mentioned trying to Debug the code. You can try these things below and maybe it will point out/pinpoint the problem area on your website.

    Add these 3 Constants to your wp-config.php file.

    // turns WP Debug on
    define('WP_DEBUG', true);
    // logs errors to the wp error log
    define('WP_DEBUG_LOG', true);
    // will display any errors in your browser
    define('WP_DEBUG_DISPLAY', true);

    You would also want to check your website’s php error log for any errors.

    You would also want to check your Server logs for any errors.

    Also i don’t think you tried this recommendation i made.
    Create a new WordPress Installation (new website) under your Hosting Account and install BuddyPress 1.6.1 and test everything.

    Managed to open ‘Error Logs’ and found some suspicious errors (though incapable to manage them):

    WordPress database error Multiple primary key defined for query ALTER TABLE wp_bb_term_relationships ADD PRIMARY KEY (object_id, term_taxonomy_id) made by require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), do_action('template_redirect'), call_user_func_array, bp_template_redirect, do_action('bp_template_redirect'), call_user_func_array, bp_screens, do_action('bp_screens'), call_user_func_array, groups_screen_group_forum, bp_forums_get_topic_id_from_slug, do_action('bbpress_init'), call_user_func_array, bp_forums_load_bbpress, bp_bb_dbDelta
    
    Duplicate key name 'term_id_taxonomy' for query ALTER TABLE wp_bb_term_taxonomy ADD UNIQUE KEY term_id_taxonomy (term_id, taxonomy) made by require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), do_action('template_redirect'), call_user_func_array, bp_template_redirect, do_action('bp_template_redirect'), call_user_func_array, bp_screens, do_action('bp_screens'), call_user_func_array, groups_screen_group_forum, bp_forums_get_topic_id_from_slug, do_action('bbpress_init'), call_user_func_array, bp_forums_load_bbpress, bp_bb_dbDelta
    
    PHP Fatal error:  Call to undefined function  bp_current_user_can() in wp-content/plugins/buddypress/bp-core/bp-core-template.php on line 728
    
    PHP Fatal error:  Call to undefined function wp-content/plugins/buddypress/bp-core/bp-core-template.php on line 728
    
    PHP Parse error:  syntax error, unexpected $end in wp-content/plugins/buddypress/bp-members/bp-members-functions.php on line 1296
    
    PHP Warning:  array_key_exists() [<a href='function.array-key-exists'>function.array-key-exists</a>]: The first argument should be either a string or an integer in wp-includes/cache.php on line 537
    
    PHP Warning:  array_key_exists() [<a href='function.array-key-exists'>function.array-key-exists</a>]: The first argument should be either a string or an integer in wp-includes/cache.php on line 537

    1. Are the above data enough for troubleshooting? Do I still need to add the 3 constants to wp-config.php? If yes, where should I open the error logs?
    2. Yes, I didn’t create a new WP installation and install the latest BP for a test as I’m having zero skill in this. However, I have other WP sites with BP1.6.1 plus BPS installed (under the same webhost) and have no forum commenting problem.

    Plugin Author AITpro

    (@aitpro)

    ok what this looks like to me is that the upgrade to BuddyPress 1.6.1 did not install all the files successfully. I do not know if you can manually replace the BuddyPress plugin files, but that is what i would try to do.

    Make a Backup of the BuddyPress plugin folder, then download the BuddyPress plugin to your computer and manually upload it to your website.

    Yes, I did download the BP1.6.1 plugin files and replace the old ones. Let me try to search for other replacement method then. Thanks.

    Plugin Author AITpro

    (@aitpro)

    Since i am not a BuddyPress expert then you should contact the BuddyPress folks about what the correct/best procedure is to replace/reinstall BuddyPress. Also check the BuddyPress Forum as this may already be documented there.

    Checked with GC support and was told that the above was the correct way to reinstall BP. Hence, created another thread in BP forum to seek further help but haven’t received any reply yet.

    Meanwhile, is it wrong to click ‘replace all’ in Filezilla while transferring the new files to the site? Thank you.

    Plugin Author AITpro

    (@aitpro)

    Yep you could be waiting a very long time to hear anything from a BuddyPress forum post (a month or more) because BuddyPress is now over 1.2 Million downloads. You will find an answer much quicker by doing Google searches until you find the answer you are looking for.

    If you have made a backup of your files and you want to overwrite the existing files then yes “replace all” is probably what you want to use to overwrite files.

    But I have nothing to search since it’s the correct way to reinstall BP. Help…

    Just found this and it looks very close to the solution by doing some tricks with permalink setting > http://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/forum-replies-causing-403-forbidden-error-to-occur-1/ . Kindly guide me on this as I can’t get a plain picture of the steps required. Thank you very much!

Viewing 15 replies - 16 through 30 (of 48 total)
  • The topic ‘[Plugin: BulletProof Security] Commenting Error on Buddpress Forum’ is closed to new replies.