[Magi182]

Thanks Paul! Been out for the holidays. I appreciate your response! Lovely site, BTW. Did you have to do some tweaking to the database/BP/etc or are you basically running an out-of-the-box core installation? Looks like you’re using Groups, Extended Profiles, Friends and Activity Streams?

Any suggestions, caveats for someone beginning this process for a larger community?

[Magi182]

I was able to hack this plugin to accomplish most of what I needed:

https://wordpress.org/extend/plugins/bp-export-users/

You have to edit the array in the plugin file to use your buddypress profile fields (you can add or delete), but other than that, pretty slick.

[Magi182]

For those still looking for a solution to this, you can add the following code to the functions.php file of your active theme. The username gets replaced with the username you wish to hide. Alternatively, you could substitute the stuff in the parens of the conditional with a properly done current_user_can() statement to hide all the administrators.

`
global $current_user;
get_currentuserinfo();

if( $current_user->user_login == ‘username’ ) {
remove_action(“wp_head”,”bp_core_record_activity”);
}
`

[Magi182]

It actually needs to read:

`remove_action( ‘wp_footer’, ‘bp_core_admin_bar’, ;
remove_action( ‘admin_footer’, ‘bp_core_admin_bar’ );`

as the admin footer hook has no priority in the current versions of buddypress (1.2.

[Magi182]

Are you running any other facebook plugins concurrently? If you are, you\’ll have either pick one, or fix the plugins so you instantiate only one copy of the facebook connect, and work both plugins through that.

[Magi182]

It could be any number of things — out of memory can be hard to track down the actual cause. Transaction log could be full, might be low on disk space, the system might be running out of RAM trying to execute the transaction… Sometimes out of memory is a symptom of an underlying problem — this is the short list.

[Magi182]

Not sure I understand… Maybe you could explain your idea a bit more? What exactly is getting aggregated and why?

[Magi182]

actually, you can hit either one and it should work as Activate site wide

[Magi182]

@Maythil Sorry, I guess the first thing I need to do is better explain this in the readme.txt!

You’ll need to chose some posts to feature in the slideshow. Each post’s edit page has a new meta window: JQuery Slideshow. You’ll need to activate the posts you want to be shown in the slideshow by:

1. Editing the post(s) you want in the slideshow

2. going to the RH side of the edit window in the JQuery Slideshow Widget box

3. choosing “show this post” from the pulldown

That will make that post available to the slideshow. The widget will attempt to grab any images that are part of the post body and show them as the big slideshow image. Alternatively, you can set a special slideshow image by uploading an image to the media library, and setting a custom field for the post called (without quotes) “jqss_image” where the value is the complete URL of the image.

The general idea is something similar to whats in the UL corner of http://abc.go.com/

[Magi182]

well, private messaging is still not working on the site, so here’s the download link:

http://www.asomatic.net/plugins/wp-jquery-slideshow.zip

I’d appreciate all feedback. You can mail to me or reply on the plugin thread.

Thanks again, I really appreciate your time.

[Magi182]

@Enlightenmental1

The plugin works mostly off the post and media library architecture. The database interaction is principally adding entries to wp_postmeta. It saves the post as a slideshow post by a boolean _jqss_is_showing, and, if desired you can add a special slideshow image with a meta field called jqss_image to contain the URL of the image. If you are lazy like me, you can just insert an image in the body of a post, and the plugin will sniff that out (hopefully) and use it as the slideshow image.

It saves widget options in wp_options. Pretty standard stuff I would guess.

@Hyrxx

My intention was that the widget would appear on the main page of the site, where the admin would select pages from the main blog to feature. I am working on a few CSS themes to make the presentation a little snazzier. A regular blog could use it in any sidebar. I guess that I could hook it into TinyMCE so you could put a slideshow of posts in a post, but that might get ugly if the person accidentally slideshow-selected the post that had the slideshow in it.

[Magi182]

OK. XMLRPC is enabled for local calls. I had to put a loopback in the server’s hosts file as this isn’t a live domain yet. It’s always something blindingly easy – once you figure it out.

Yet… posting to the forums didn’t actually work until I reset the linking account’s password a couple of times.

[Magi182]

Heh. After weeping tears of blood trying to integrate bbPress, buddypress and wpmu, after several installs, multiple reads of Trent’s tutorial page, I began to suspect XML-RPC problems and jumped back on the forums, found this thread and installed Burt Adsit’s lovely little plugin and am rewarded with:

-32300 >> transport error – could not open socket: -1080553356

Thanks Burt. You rock. Now to figure out how to permit XML-RPC calls locally.

[Magi182]

[Magi182]

And… if you make these changes to the BP core files, don’t forget to save them when updating BP.

Oh, and BTW, upgrading to the paid godaddy hosting will most likely fix the ad code injection issue you’re having; but I would concur with the negative comments about godaddy — paid or not — as a host for a buddypress project. You’ll keep running into problems trying to do more advanced stuff on their servers. That’s just not the market that they’re serving.

[Magi182]

I haven’t tested this, but you should probably be able to edit

/wp-content/themes/buddypress-home/style.css

delete the @import directive that is there and instead add:

@import url(css/base.css);

@import url(css/custom.css);

This might hose some of the functionality added by loader.php, but should be the easiest place to make the change.

[Magi182]

See the other thread on this, but your host is injecting ad code into the loader.php that pulls the stylesheet.

view source on:

http://illdesigned.com/user/barrymadden/wp-content/themes/buddypress-home/css/loader.php

</iframe></noscript></object></layer></span></div></table></body></html><!-- adsok -->

<script language='javascript' src='https://a12.alphagodaddy.com/hosting_ads/gd01.js'></script>

[Magi182]

as near as I can tell,

/wp-content/themes/buddypress-home/css/loader.php

is not pulling the stylesheet properly. I would guess that the problem is coming from your host, as they are trying to inject an iframe into that page upon execution.

</iframe></noscript></object></layer></span></div></table></body></html><!-- adsok -->

<script language='javascript' src='https://a12.alphagodaddy.com/hosting_ads/gd01.js'></script>

[Magi182]

You’re probably having a problem with your css rule not being “strong enough” to override whatever styling is assigned to the links in the first place.

If you have a wrapper div for your blog, try something like

html body div a { font-family: “Comic Sans”; };