BuddyPress.org

@footybible – you can try replacing line 368 in wp-login.php with the code I put in the pastebin (above).

However, I don’t know if this catches everything (give it a quick try!). There’s a lot of code / javascript going on in there, so fingers need to be crossed that this simple fix will do the trick.

@govpatel – you are using the wrong @mention for Matt – you need to use the username rather than the displayed name. I know, it’s really un-user friendly!

@matt have you tried this Theme My Login plugin as it will redirect to login page on your own theme

It isn’t a BuddyPress site though, is it?

Support for themes such as that need to go to the relevant theme writer really. This site supports the BuddyPress plugin for WP/WPMS

For anyone having this issue with Topic creation in forums please read and follow the steps I outline in this comment:

https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/forums-not-working-error-when-creating-topic/#post-69618

If this does not solve the issue for you then post a fresh topic outlining your situation with relevant details of setup.

This thread deemed closed.

@jabberjazz
Jane to answer the question from the other thread; yes the support forums are of use, as can be seen by the number of issues raised and solutions provided, of course not all issues are that easy to get to the root of, especially without a lot of detailed info and steps to hopefully reproduce the issue on a local dev install.

I have had this issue before and oddly just a second ago, what causes it ? Can’t tell you for sure, my install was pretty clean no plugins to speak of , forums had been installed, one test group forum activated, create topic -> failure , re-install forums using existing installation , still no joy, create a new group with forum, create a topic -> success ?? something to do with that original group I set up was out of sequence ?

Checking my DB shows that the forum name and id doesn’t exist for the group forum acting up only the default id and group forum recently created are seen.

Soooo I go back to the troublesome group as the admin I go to the admin tab of the group I select ‘Group Settings’ I am shown the initial screen one sees after creating a group and the ‘Enable Discussion Forum’ checkbox. I – unnecessarily – uncheck and check again that box and then select save at bottom of screen – tab back to my DB and yep forum group now is entered!

Attempt to create new topic – success!

So can you give the above procedure a try and report back to us whether it worked or not.

And I hope this changes your opinion on whether there is a help to be found on this support forum

@Travel-Junkie: great job man! I know you’ve been working on this for a LONG time, so I’m glad you’re able to release it

Sure.. check out this plugin from @nuprn1:

https://buddypress.org/community/groups/buddypress-block-activity-stream-types/

Simply add the “joined_group” action to the Block Activity Types textbox in the plugin settings!

Had you ever previously installed BuddyPress or attempted a BuddyPress forum installation on this site / database before now?

Are all the forums broken, or do, for example, newly-created groups’ forums work ok?

Is your WordPress set up as a multisite? (this used to be called WPMU. If you don’t understand this question, the answer’s no)

Are the bbPress tables in your database? For example, wp_bb_forums, wp_bb_meta, wp_bb_posts and so on?

Hmm. Looks like the plugin is active at the moment (I see a javascript include). I also see a lot of other plugins; if you’ve got a test server I suggest disabling all the plugins other than BuddyPress and seeing if it works. I suspect this is likely due to a conflict.

Another idea is, when you previously ran the BP Template Pack, did you restore your theme’s files to defaults? e.g. removed the BuddyPress stuff it added. Also, as far as I’m aware, you can disable the BP Template Pack — it’s a once-off thing.

@travel-junkie Sounds great!

I really can’t wait to get to work with the CV component, the site I am working on now will benefit dramatically!

Keep me posted on how you’re getting on or any test versions etc.

Cheers!

Hej Ikey,

as you have heavily customised this area of the site – redirecting to login if not a member in the members directory – I suspect the problem is in your customisation / redirect logic, and not a BuddyPress bug.

You’d need to post a lot more information for someone to assist on this – all of your re-direct logic / function would be a start (use pastebin.com and include a link in your thread).

Then, keep your fingers crossed that someone wants dive in to heavily customised code and look around to help

Cheers,
Roger

Hi,

You can check this plugin which I recently develop to provide ACL BuddyPress Extended Profiles:

https://wordpress.org/extend/plugins/buddypress-xprofiles-acl/

Hope you find it useful.

Regards,
NetTantra

@mikey3D

Yes, sorry – I only checked a multi-word post title.

You are correct, categories and tag page titles are behaving differently in default BuddyPress vs. default WordPress install

The function that builds the title in BuddyPress is bp_page_title(). In WordPress it’s wp_title()

The WP function is doing a lot more work with the category and tag slug, taking the name slug it’s been passed (with the hyphens inserted) and looking up the correct (non-hyphenated) title to insert.

OK, two things I suggest:

1. Report this, and suggest that the bp_page_title() function should behave the same as wp_title() for categories, tags, etc. This would be the sensible way for the function to behave IMO. @hnla – is adding this to the trac, the correct way to raise this a possible fix?

2. For a quick fix, code your own title function, and replace the call to bp_page_title() in your header.php with a call to your own function

The function may look a little daunting, but should be reasonably straightforward with a bit of judicious copying and pasting from the existing BP and WP functions.

Cheers, Roger

Oops! That last bit didn’t post correctly. Enclose the first and last lines in < brackets.

files wp-config.php
order allow,deny
deny from all
/files

@TedMann

This is what I’ve added to .htaccess to block bots:

# IF THE UA STARTS WITH THESE
RewriteCond %{HTTP_USER_AGENT} ^(aesop_com_spiderman|alexibot|backweb|bandit|batchftp|bigfoot) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(black.?hole|blackwidow|blowfish|botalot|buddy|builtbottough|bullseye) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(cheesebot|cherrypicker|chinaclaw|collector|copier|copyrightcheck) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(cosmos|crescent|curl|custo|da|diibot|disco|dittospyder|dragonfly) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(drip|easydl|ebingbong|ecatch|eirgrabber|emailcollector|emailsiphon) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(emailwolf|erocrawler|exabot|eyenetie|filehound|flashget|flunky) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(frontpage|getright|getweb|go.?zilla|go-ahead-got-it|gotit|grabnet) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(grafula|harvest|hloader|hmview|httplib|httrack|humanlinks|ilsebot) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(infonavirobot|infotekies|intelliseek|interget|iria|jennybot|jetcar) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(joc|justview|jyxobot|kenjin|keyword|larbin|leechftp|lexibot|lftp|libweb) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(likse|linkscan|linkwalker|lnspiderguy|lwp|magnet|mag-net|markwatch) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(mata.?hari|memo|microsoft.?url|midown.?tool|miixpc|mirror|missigua) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(mister.?pix|moget|mozilla.?newt|nameprotect|navroad|backdoorbot|nearsite) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(net.?vampire|netants|netcraft|netmechanic|netspider|nextgensearchbot) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(attach|nicerspro|nimblecrawler|npbot|octopus|offline.?explorer) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(offline.?navigator|openfind|outfoxbot|pagegrabber|papa|pavuk) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(pcbrowser|php.?version.?tracker|pockey|propowerbot|prowebwalker) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(psbot|pump|queryn|recorder|realdownload|reaper|reget|true_robot) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(repomonkey|rma|internetseer|sitesnagger|siphon|slysearch|smartdownload) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(snake|snapbot|snoopy|sogou|spacebison|spankbot|spanner|sqworm|superbot) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(superhttp|surfbot|asterias|suzuran|szukacz|takeout|teleport) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(telesoft|the.?intraformant|thenomad|tighttwatbot|titan|urldispatcher) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(turingos|turnitinbot|urly.?warning|vacuum|vci|voideye|whacker) [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^(libwww-perl|widow|wisenutbot|wwwoffle|xaldon|xenu|zeus|zyborg|anonymouse) [NC,OR]
# STARTS WITH WEB
RewriteCond %{HTTP_USER_AGENT} ^web(zip|emaile|enhancer|fetch|go.?is|auto|bandit|clip|copier|master|reaper|sauger|site.?quester|whack) [NC,OR]
# ANYWHERE IN UA — GREEDY REGEX
RewriteCond %{HTTP_USER_AGENT} ^.*(craftbot|download|extract|stripper|sucker|ninja|clshttp|webspider|leacher|collector|grabber|webpictures).*$ [NC]
# ISSUE 403 / SERVE ERRORDOCUMENT
RewriteRule . – [F,L]

To help block spam registrations, add the following to .htaccess, then create a simple GOAWAY type html page and upload to your root directory:

# BEGIN ANTISPAMBLOG REGISTRATION
RewriteEngine On
RewriteCond %{REQUEST_METHOD} POST
RewriteCond %{REQUEST_URI} .wp-signup.php*
RewriteCond %{HTTP_REFERER} !.yoursitehere.com. [OR]
RewriteCond %{HTTP_USER_AGENT} ^$
RewriteRule (.*) http://yoursitehere.com/yourgoawaypage.html [R=301,L]

Add the following to .htaccess to deny access to wp-config.php to anyone who doesn’t have your ftp details:

order allow,deny
deny from all

Instead of example.com/register or example.com/sign-up, use something like example.com/unb2x-2010 for your register page. If you were a spammer, would that look like an inviting url to hack?

Hope this helps

@pcwriter, you rock. Going to try all of these. Few quick q’s:
1. With the list of bad blocks, you added all these to your HT access file? Is there any downside to having such a lengthy htaccess? Could you anonymize yours and post it?

2. What does “Added “deny from all” in .htaccess for wp-config.php” mean?

3. When you say you changed “register slug to something unrecognizable,” what sort of thing did you use? Garbledygook, or just something like “/whats-up”

Looks like Javascript problems. I’d be checking the CSS id’s and class names (in the theme HTML code) to make sure they are what they should be in order to work with BP.

.You could also try my plugin (he says with shameless self-promoting grin).

See this post for the latest beta version: https://buddypress.org/community/groups/add-all-nav-links-to-bp-adminbar/forum/topic/updated-the-beta/
Here are the user configuration options available in the admin panel under “Settings” > “BP-WP-Navbar”
– Hide or display the main theme navigation
– Hide or display the site name in your new adminbar
– Hide or display the Login and Signup links in the adminbar
– Hide or display the “Visit Random” menu
– Select whether to display top-level WordPress pages horizontally or in a dropdown menu
– Define the label for the dropdown in WordPress 2.x
– If you’re running WP3.x, the plugin will fetch whatever custom menu labels you assign and display them in the admin bar along with all child pages in dropdowns
– Define the label for the Buddypress directory dropdown (default = “Community”)
– Define the font, font-weight and font-style for all menu items
– Define ALL colors: navbar background, main and sub menu item backgrounds, border, text and hover colors too
– Set the overall width of the navbar and of sub-menus
– Set the height of all menu items
– Adjust margins where required
– Reposition your fancy new custom navbar anywhere you like, relative to your theme so it scrolls with your pages

If you add categories to your custom menus in WP3.x, the plugin will pick them up and display them in whichever menus they are assigned to. Give it a whirl.