[@egerrits Participant 17 years, 2 months ago]

This is a fast world, Simon… I found out it was easier for me to go back a version and retrace my modifications for next version rather than trying to figure out why the style sheets weren’t loading any more… I almost have it back to the .55 functionality I had before. Lost a week, but hey, version .55 is just around the corner, and it will have fully functioning group events!

[@egerrits Participant 17 years, 2 months ago]

0.54 will work with latest trunk, so will future versions… I went back to .54 and re-traced my steps to 0.55… all is peachy

[@egerrits Participant 17 years, 2 months ago]

Next version of my Bp-Events plugin will do just that: take the date off of date XProfile field, and make a birthday out of it (yearly recurring Event). It will also “replace” the XProfile field with the Birthday version through a filter/hook. Anniversaries could be the same thing.

[@egerrits Participant 17 years, 2 months ago]

That did the trick!

Thanks!

[@egerrits Participant 17 years, 2 months ago]

Seems to me “report this item” is the exact opposite of “Add to Favourites”… The buttons would show up at the same spots (group home, blog post, wire post, photos, user’s profile etc), the handling code would be the same except in Report case a notification gets sent to the administrator and in Favourite’s case it gets added to the user’s favourites.

That being said, Report This SHOULD be in the core…

[@egerrits Participant 17 years, 2 months ago]

@sgrunt

No, that functions *outputs* the image, I need its source.

[@egerrits Participant 17 years, 2 months ago]

OK, the above code works *sometimes*… but not other times… hmm…

[@egerrits Participant 17 years, 2 months ago]

I got it using this:

$avatar_file = get_usermeta( $bp->loggedin_user->id, “bp_core_avatar_v1” );

$url = $bp->root_domain . ‘/’ . $avatar_file;

but is there a more elegant way?

[@egerrits Participant 17 years, 2 months ago]

If you look in the groups-templatetags.php file under function bp_groups_header_tabs() you can see them defined there. The actions (where the links are going) are headed to the template index & loop files in member templates. The code that sorts out what the loop gets (has_groups(), the_group() etc) is at the top of the templatetags.php file under BP_Groups_Template.

[@egerrits Participant 17 years, 2 months ago]

Yeah, I know what you mean… and it seems just so pushy to *bump* your own post!

Anyhoo, the other thread was here:

https://buddypress.org/forums/topic.php?id=1499

[@egerrits Participant 17 years, 2 months ago]

I posted a suggestion about writing such a plugin a just last week, got no takers… Might revisit if there is interest.

[@egerrits Participant 17 years, 2 months ago]

After banging my head against the wall for an hour or so I found out that, unfortunately, it is impossible to obtain a user’s facebook login and password and use it to update the user:

Re: Terms of Service rule 2.A.9.vi

[apps cannot] request, collect, solicit or otherwise obtain access to usernames, passwords or other authentication credentials from any Facebook Users, or to proxy authentication credentials for any Facebook Users for the purposes of automating logins to the Facebook Site;

In order for this to work, the user would have to go to a Facebook login screen every time a status is updated, which is a pain-in-the-you-know-what.

Facebook’s out, and you can blame that on Facebook!

[@egerrits Participant 17 years, 2 months ago]

I think I will keep the helper as is, basic and functional, but add some more functions like getting the user’s tweets, friends etc. and write a more fully fledged twitter plugin that uses the helper and will add the automatic tweets as well as user’s tweets widgets and site wide tweets, friends’ tweets, what have you. More like the helper is the database layer and the new plugin is the interface layer, for those of you who do software development.

I was also wondering if I should redo the eg-twitter plugin as a “eg-social” plugin and just store and have functions for all social networks, such as twitter, facebook, flickr etc. for other plugins to use…

[@egerrits Participant 17 years, 2 months ago]

It is a helper plugin. It just stores the user’s credentials centrally and provides a function for other plugins to tweet(status) to the user’s account. The plugin in itself will not post anything. My Events plugin uses this functionality to post a tweet about event creation.

I will add some options to maybe automatically tweet the activity feed if the user wants.

UPDATE: Come to think of it, why don’t I add some options to automatically tweet: blog posts, new group creations, profile updates, etc. as a series of check boxes on the twitter settings… hmmm… now you’ve got me going…

[@egerrits Participant 17 years, 2 months ago]

Looks like it’s a float problem.

Make sure the members list div is on “float:left” and the sidebar div is “float:left” as well. Then you have to make sure that the total width of the divs (INCLUDING MARGINS) is less than the total with of the page. So if you’re working with percentages, make the total width 99% or so (say, members div = 59% sidebar is 30%). If you’re working with absolutes, make the total width 5 or 10px less than the page width. Be careful of the margins as they are OUTSIDE of the div widths and if they add up to more than the page’s width, your floats will not work.

Also make sure at the end of the two divs you put a <div class=”clear”></div> to clear up the floating for the footer.

[@egerrits Participant 17 years, 2 months ago]

I had a problem with ownerships on some directories, and I’m on a shared host, so I couldn’t change them with unix commands. What I ended up doing is install a third party “File Manager” onto my server and used that to change ownerships. (I actually installed Joomla with the File Manager plugin). You just have to find a file manager that allows change of ownerships on directories. You could also email the server hosting company’s technical support and ask them to change ownerships on directories. if they’re nice, they will do it.

[@egerrits Participant 17 years, 2 months ago]

Simon, I’d think you would have learned by now

Last week I moved my websites over to a new server running PHP5 (old one was on PHP4) and eventhough the switch over went smoothly, there are a few nagging issues with SSL certificates and registered softwares that do not like being moved from one server to another… My appologies for this inconvenience to everyone.

[@egerrits Participant 17 years, 2 months ago]

For those interested: version 0.54 of bp-events is now available from my website at http://www.erwingerrits.com/?page_id=799

As usual, read the website or ReadMe file for what’s included (and what’s not!)

[@egerrits Participant 17 years, 3 months ago]

I wonder if I should make a small addition to my events plugin to be able to set up a simple birthday field onto the profile page… should be possible. I’m going to go noodle with this.

[@egerrits Participant 17 years, 3 months ago]

Well there you go

[@egerrits Participant 17 years, 3 months ago]

First, read this webpage:

https://codex.wordpress.org/Plugin_API#Actions

That’ll explain the basics of hooks and filters. If you want to know which hooks are in BuddyPress, scan through the source code and look for do_action() functions as well as apply_filter() functions, those are your hooks, and you can “hook” into them using the functions add_action() and add_filter() respectively. I don’t think there’s too much documentation around for BuddyPress hooks, so it’s best to look into the file/function you want to extend and find your hooks.

[@egerrits Participant 17 years, 3 months ago]

There is currently an open ticket for this problem on the trac site… Andy’s working on it!

[@egerrits Participant 17 years, 3 months ago]

@burkie,

make sure you have the latest trunk version of buddypress (or at least 1164 I believe) installed, particularly bp-core-templatetags.php.

[@egerrits Participant 17 years, 3 months ago]

You’re so helpful

[@egerrits Participant 17 years, 3 months ago]

Yes, that is the way it should be. I’ll be changed in the next version.