[@windhamdavid Participant 16 years, 7 months ago]

nice analysis ~ I’m also duplicating those errors with the core_redirect pointed to wp-login.php I’d bet Jeff has a good handle on this and I sent a request to help him test the upcoming release. I don’t have a copy of his old release to adapt or modify (if anyone could point me to, or send me the old copy, that might help).. but the hack i put up previously has worked like a charm for me making some pages private while leaving others public without having to expand this into a full on plugin with user options. I simply call that custom header for any pages I want to keep private.

[@windhamdavid Participant 16 years, 7 months ago]

I also edited this line

bp_core_redirect( site_url( 'wp-login.php' ) );

to

bp_core_redirect( site_url( BP_REGISTER_SLUG ) );

[@windhamdavid Participant 16 years, 7 months ago]

Correction on my part!! No Fail for bp_lockdown(). It Works perfectly fine in 3.0 alpha and MU 2.9.1.1 @Andrew_s1 ~ make sure you have registration enabled as that’s what’s causing your loop.

[@windhamdavid Participant 16 years, 7 months ago]

I also just tested bp_lockdown() with MU 2.9.1.1 and 1.2 ~ same fail as 3.0-alpha regardless of if I clear cookies or cache. I think andrew_s1 has it right.

[@windhamdavid Participant 16 years, 7 months ago]

<?php if(!is_user_logged_in()){

nocache_headers();

header("HTTP/1.1 302 Moved Temporarily");

header('Location: ' . get_settings('siteurl') . '/wp-signup.php?redirect_to=' . urlencode($_SERVER['REQUEST_URI']));

header("Status: 302 Moved Temporarily");

exit();

} ?>

this quick hack (in the top of header.php) will only registered and logged in users can view. As for using it with version 1.2 default theme ~ I would suggest making a custom header for any of the buddypress elements you want to keep private and keep the rest public. At least until privacy functions are available as a plugin or in core.

[@windhamdavid Participant 16 years, 7 months ago]

I know this! .. forward thinking and I’ve found very few errors, 1.2 supports 3.0-alpha much better than is to be expected with very little errors, notices or conflicts on depreciated functions.

[@windhamdavid Participant 16 years, 7 months ago]

it’s not working for me 3.0-alpha/bp trunk ~ I had a very simple solution to accomplish this eons ago (pre privacy plug) and I’ll look at it again this afternoon in combo with your lockdown code.

[@windhamdavid Participant 16 years, 8 months ago]

I highly agree on a benefit the community ~ i’d love to say that I could set aside some time to help you with benchmarking, but I’m afraid I’d be a bit out of my comfort zone and strapped to other projects, which unfortunately don’t require the scalability. But I’m sure someone of similar interest will come along to help with testing and compiling it though… if not me in a couple months.

[@windhamdavid Participant 16 years, 8 months ago]

Wow, that’s a really impressive setup you got going at http://kodingen.com. Thank you for posting this ~ I wouldn’t know where to start with hiphop yet, but I registered and noticed that the activation email is missing a backslash. I had read this statement from @rasmus and figured it’s performance gains and high scaleability would also depend on a series of other configurations like memcached and sql optimization. But something like this could prove to be as Rasmus puts it, escape from ‘framework soup’. Although wordpress.com seems to be running top notch on top of Nginx, but I’m sure they got all kinds of hardware and configuration tweaks going on.. // all the same thanks for for the experimenting and good luck with it.

[@windhamdavid Participant 16 years, 8 months ago]

@mrmaz scratch that ~ bp-links is functioning perfectly from trunk, as I just discovered I had overwritten another plug with the wrong file dir name.

[@windhamdavid Participant 16 years, 8 months ago]

you might try this. https://buddypress.org/forums/topic/registration-link-redirects-to-home-page

[@windhamdavid Participant 16 years, 8 months ago]

No problem, I’m glad it helped. i can always replicate errors that come from NOT following directions since I almost never follow them.

[@windhamdavid Participant 16 years, 8 months ago]

Oembed makes sense for core and my trunk version of bp-links is prompting an upgrade to 0.3.1 in the plugins admin.

[@windhamdavid Participant 16 years, 8 months ago]

Very Nice work Hempsworth, maybe now you’ll get requests for a dislike button.

[@windhamdavid Participant 16 years, 8 months ago]

voted

[@windhamdavid Participant 16 years, 8 months ago]

Any of you who continue this thread any further are simply staring the ‘gift horse in the mouth’ so to speak.

~ spam in a problem for every company, be it IBM, Google or WordPress. These companies spend millions combatting it and it’s a problem for almost any CMS, or site that has UGC. If you can’t install Askimet, and/or a couple other preventative measures on your site, then you should hire someone who knows what their doing or you have a compromised(hacked) site where once again, you should hire someone who knows what they’re doing.

while not naming names ~ I have watched ‘your’ post on this forum and you’ve offered very little contribution and quite a bit of negativity. That doesn’t bode well for an open source community who provides you a product free of charge. Perhaps providing some meaningful feedback about your experiences will help the community develop better solutions instead of glaring accusations and harsh criticism? In fact your post in this community are very much like spam for the very same reason. At this point, you’ve pretty much hit an all time low since your accusing developers, many of whom work for free, of turning a blind eye towards the issue of spam. If you’re unhappy with website, may i suggest move on to another piece of software that is magically immune to spam robots, where you’ll most positively be a great asset, not only to them, but also with your absence here on the Buddypress Forums.

[@windhamdavid Participant 16 years, 8 months ago]

i’m getting a strange error on wp trunk & bp trunk ~ screenshot

I have multi site enabled, revisions from this morning… upon clicking ‘like’, seems to be an endless spinning.gif and then my default apache page is called into a frame of sorts upon hovering over any href’d link on the default apache page.

[@windhamdavid Participant 16 years, 8 months ago]

I would dbl check it.. did you comment out the line in the core file or deactivate buddypress and then reactivate after you edited? I let it persist for long time until I took a look at that function, Also, do you have your home url set as an IP and not a domain or perhaps another of the compatibility functions? I’m unable to duplicate this error under a number of server conditions. If none of these are responsible, then Yes.. please file a ticket so it’ll get attended to.

[@windhamdavid Participant 16 years, 8 months ago]

dailynewarker: I checked on it this morning and I remember it happening on my local server, but not on a remote. So I scoured through bp-core-signup.php and found what i believe may be your issue with registration.

In an effort to support backwards compatibility, this line checks to see if you still have old bp-themes in wp-content.

if ( file_exists( WP_CONTENT_DIR . '/bp-themes' ) )

return false;

If the directory exist’, then the function bp_core_screen_signup() is rendered false and redirected to the home_url via bp_core_redirect( $bp->root_domain );

First try removing the old ‘bp-themes’ directory from wp-content, or you may remove/comment out lines 17+18 of bp-core-signup.php. It’s just a little step in the upgrade process of forgetting to remove the old bp-themes directory but I hope this solves your issue.

[@windhamdavid Participant 16 years, 8 months ago]

I’ll try to get an answer for you on this from a dev, (ie.. bump this back to the top and repost in IRC since I’m a fan of wp-tables-reloaded) but my halfway educated ‘guess’ is that it’s to assure that BP loaded first for plugins dependent on it’s functions.

[@windhamdavid Participant 16 years, 8 months ago]

this doesn’t sound good. I would disable all registrations immediately, clean out all of the users whom have been added, delete all of your wp and bp files and reinstall to make sure that you don’t have any modified files. And you might examine the db tables closely to see if they need may need repair.

[@windhamdavid Participant 16 years, 8 months ago]

[19-Feb-2010 07:15:53] WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ’12:15:53 – date_created ) / 60 ) / vote_total ) WHERE popularity <= 16777214 AND’ at line 1 for query UPDATE wp_bp_links SET popularity = FLOOR( FLOOR( ( 2010-02-19 12:15:53 – date_created ) / 60 ) / vote_total ) WHERE popularity <= 16777214 AND vote_total >= 1 made by do_action_ref_array, call_user_func_array, bp_links_recalculate_popularity_for_all, BP_Links_Link->popularity_recalculate_all

[@windhamdavid Participant 16 years, 8 months ago]

nice work! ~ complete integration, the javascript for the edit fields, the votes, the options including custom theme and the rich media embed.

[@windhamdavid Participant 16 years, 8 months ago]

bp + wp trunk ~ “Plugin could not be activated because it generated 1 characters of unexpected output” ~ nothing in my php_error.log

[@windhamdavid Participant 16 years, 8 months ago]

I successfully tested on a local install and your site and had no apparent issues ~ best of luck on the continued development.