[@windhamdavid Participant 16 years, 7 months ago]

@Boone ~ Big thank U.. I tested the .diff this morning and let’s just say.. it’s much much less ‘hacky’ than what I had going on!

[@windhamdavid Participant 16 years, 7 months ago]

r-a-y – r-a-y ~ is da man. hi five!

[@windhamdavid Participant 16 years, 7 months ago]

nvrmnd… i see you got it, didn’t refresh my browser… but I have you know.. I was investigating

[@windhamdavid Participant 16 years, 7 months ago]

try ../wp-admin/admin.php?page=bp-component-setup and save the settings again? it’s right on ‘takeoff’ ~ bp-core-catchuri.php #20 ~ bp_core_set_uri_globals() $current_component ~ all the urls depend on it and it looks like it fails if the root_blog is not the current_blog ID? sitewide activation? Not running BP on the root? I don’t know.. do you have a any other unique configuration going on?

[@windhamdavid Participant 16 years, 7 months ago]

they provide you with an RSS feed for your posts and comments on any syndicated content (my feed)… just like wordpress ~ so if you want to pull a feed, just use any common feed parsing plugin to pull your RSS into your Buddypress install. I like to use feedwordpress. Or if you don’t want to duplicate the feed as posts, you can use the built in SimplePie functions in wordpress to display your RSS feed as a widget, like the widget here that pulls in rss from another site.

[@windhamdavid Participant 16 years, 7 months ago]

than the admin bar is controlled by lines #17-35 in adminbar.css. The width is set to appear 100% of what is available, and in the case of the default theme – the body is set to 960px and max of 1250px. if your child theme also has the #bp-default css ID for <body> than lines #25-32 of adminbar.css also apply. trial and error is the way to go.

[@windhamdavid Participant 16 years, 7 months ago]

so to answer your question. You can build a service just like amplify with MU and BP, but it will take a lot of custom development and considerable amounts of effort in scaling and database management strategies. It’s running on dedicated hardware and Amplify.com is owned by Clipmarks LLC (Forbes). It is likely a Automattic VIP project. It is very well executed and would take some top notch developers to come close to duplicating anything similar.

[@windhamdavid Participant 16 years, 7 months ago]

scratch that.. they’re already running BP, I just set up a text account and I noticed ~ /wp-admin/admin.php?page=bp-xprofile.php they did a lot of editing of core files though. clog-signup.php etc..

[@windhamdavid Participant 16 years, 7 months ago]

there’s a lot of custom development in amplify. When you say adapt it to BP, do you mean you want to run a similar application that is also running BP or you’re involved with Amplify and want to integrate bp into it?

[@windhamdavid Participant 16 years, 7 months ago]

I’m with @stwc on this one .. get off my lawn. “nature of the beast” is b/c folks choose to make it that way. @stwc is right U is for Universal and by following some easy w3c recommendations and guidelines we might make some sense of this internet thing. @arnonel ~ my best advice would be to shorten your own domains in the way that you set up the permalinks options or create .htaccess redirects for the urls for any links you want to shorten the url on ~ if you still insist try Shorty and/or Alex King’s Twitter Tools now supports a shortener …but let me warn you that if you use a plugin and/or shorty and it becomes unsupported then essentially, you’ll have broken links everywhere on the web, which is likely the reason that @stwc called it a cancer since you’ll be polluting the web with dead links. I’ve experience this personally with a site that had over ten years of articles. The owners of the site decided to install a shortener, it became unsupported and essentially they left the web with thousands of dead links in retweets, share-this, facebook links. etc.. with no way for me to clean them up, and as a result they also lost organic search results. As URL shortening services become obsolete (which they will), this is exactly what is going to happen.. cancerous shortened dead urls everywhere.

[@windhamdavid Participant 16 years, 7 months ago]

do you have buddypress enabled as a sitewide plugin? the registration is a function of wpmu and the register slug is a function of buddypress. If you have blogs that don’t have buddypress installed as a plugin, they will not redirect the user to the BP_REGISTER_SLUG

[@windhamdavid Participant 16 years, 7 months ago]

.. and remember that anytime you ‘hack’ the core, you’ll eventually need to keep up with those edits for when it comes time to upgrade since many of those filenames are going to be changing in the upcoming 3.0 release.

[@windhamdavid Participant 16 years, 7 months ago]

I just noticed I failed to read you entire question there. Correct, they will target wp-signup.php and you can modify this file name too, if you wish. It is a bit involved though and may I suggest this article if you would like detailed information about how to do so ~ http://wpmu.tripawds.com/2009/12/12/the-ongoing-fight-against-spam-blogs/

keep in mind those instructions are for MU 2.8.6 and if you decide to edit wp-signup.php ~ don’t forget to change it in these places ~ wp-signup.php, wp-login.php,wpmu-settings.php and bp-core/bp-core-templatetags.php

[@windhamdavid Participant 16 years, 7 months ago]

when you activate Buddypress, you enable this function

function bp_get_signup_page() {

global $bp; if ( bp_has_custom_signup_page() )

$page = $bp->root_domain . '/' . BP_REGISTER_SLUG;

else

$page = $bp->root_domain . '/wp-signup.php';</p>

return apply_filters( 'bp_get_signup_page', $page );

}

which redirects your wp-signup.php page to your BP_REGISTER_SLUG.

in order to change that url slug ~ modify your register slug in your wp-config.php by adding this line.

define( 'BP_REGISTER_SLUG', 'whatever_you_want_to_call_it_no_spaces_or_weird_characters' );

above the line. /* That’s all, stop editing! Happy blogging. */

[@windhamdavid Participant 16 years, 7 months ago]

All in all, here’s my approach that I use on MU/BP sites ~

1) modify the register/register.php wp-signup.php hardcoded default text and url slugs.

2) enable xprofile and require additional fields upon registration.

2) use a captcha ~ i’m fond of ReCatcha

3) make sure you and check the NO setting under “Allow blog administrators to add new users to their blog via the Users->Add New page. ” in wp-admin/wpmu-options.php “Admin > Site Options”

4) I ban or limit the registration domains (also in Admin > Site Options) so that the commonly used spammer domains are blocked from registration and then I add an email contact for owners of these addresses to manually request registration. I hide the email address from bots with HiveLogic EnKoder

5) I then firewall off entire blocks of IP’s from my servers from commonly used spammer IP ranges you can find at sources like spamhaus.org .. and considering that these are one language sites, the need for access for the IP blocks on the pan asia network or eastern europe are unlikely. If you have a multilingual site, this might cause issues to very few users. Cpanel, Plesk, BSD, etc have tools to do this.. if you’re on a shared server, ask your hosting provider if they can do it for you, and they may be likely doing it already.

6) I also recommend using Askimet.

[@windhamdavid Participant 16 years, 7 months ago]

let’s continue this thread over here ~ https://buddypress.org/forums/topic/how-to-control-spam-registration/page/2

and did you try that recommendation regarding bbpress?

[@windhamdavid Participant 16 years, 7 months ago]

~ also might want to make sure and check the NO setting under “Allow blog administrators to add new users to their blog via the Users->Add New page. ” in wp-admin/wpmu-options.php “Admin > Site Options”

[@windhamdavid Participant 16 years, 7 months ago]

I don’t quite understand these spam posts since I’ve run ten to twelve mu sites for several (4+) years with no splog/smap exploits (knock on wood) and some of them are outdated installs with very little protection. If buddypress is in fact, the culprit, perhaps it’s related to the registration in bbpress if you have forums installed? @micheal ~ perhaps you should try removing register.php from the buddypress/forums/bbpress/ ~ and/or buddypress/forums/bbpress/templates/kakumei/register.php to see what happens…

I just tested on a local install with no conflicts and thanks for investigating.

[@windhamdavid Participant 16 years, 7 months ago]

you might try this ~ How to Install WordPress MU on IIS 7 on Windows 2008 Server, and I know there used to be quite a bit of rewrite mods for IIS 6 and there is plenty of information available to get in running in the MU forums

[@windhamdavid Participant 16 years, 7 months ago]

very nice tip!

[@windhamdavid Participant 16 years, 7 months ago]

and may i suggest these peachy tools ~

Debug

Configure_Error_Log

Save_queries_for_analysis

[@windhamdavid Participant 16 years, 7 months ago]

OSX, Terminal, Textmate, Navicat , Changes, CSSedit, Safari (webkit), Transmit/CyberDuck, Quicksilver, http://github.com/ciaran/projectplus, http://github.com/fspeirs/changes-tmbundle

~ and if I absolutely must crank up bill’s operating system for it’s devil spawn browser child “Explorer” ~ than it’s Notepad ++ Firefox /Firebug and WinSCP

I know I don’t know as much as I can and in doing so, I know enough.

Read the Readme.txt and don’t hack the core.

[@windhamdavid Participant 16 years, 7 months ago]

i’m unaware of a variable as i don’t believe there is a distinction b/t a registered user and an un-activated user in wpmu_create_user() but you might investigate bp-core-activation.php and wp-includes/wpmu-functions.php (ms-fuctions.php for 3.0-alpha for wpmu_create_user() & wpmu_activate_signup() to see if you can hook in there.

[@windhamdavid Participant 16 years, 7 months ago]

@tyler ~ I’ve now built two similar ‘medical related’ sites where the privacy was of utmost concern and I used my code from above beautifully. You could drop the plugin and the secondary install and just use that for any pages you want to keep private from both unregistered users and spiders/robots.

[@windhamdavid Participant 16 years, 7 months ago]

with the $is_root_component empty ~ it’s also failing to allow login with the redirect pointed to site_url( BP_REGISTER_SLUG ) ~ So that is not a viable solution for bp_lockdown()