BuddyPress.org

Hopefully we can get it into BP 1.3, but I’m not doing a patch until @johnjamesjacoby merges the 1.2 branch with trunk

@johnjamesjacoby ok I checkedout trunk which on reflection was not what I intended as that is bleeding edge soon to be tagged 1.3 isn’t it? On a side note there installed that for fun and it breaks straightaway with an undeclared function bp_page_title() which isn’t a new function! It’s been a while since I used Subversion […]

So there seems to be an underlying error, but browsers happily ignore it..? Doesn’t sound good, really, so hopefully @johnjamesjacoby or another developer can take a look at it.

Hmm… @johnjamesjacoby; I did as you suggested, then disabled all BP plugins and BP, deleted the BP files, and copied the new ones in. The readme.txt is still code by the way, starting with; <?php define ( 'BP_XPROFILE_DB_VERSION', '1870' ); /* Define the slug for the component */ if ( !defined( 'BP_XPROFILE_SLUG' ) ) etc., etc.…

Hi @johnjamesjacoby. Yawn… a nice sunny Sunday morning, so I thought, “Why not?” Copied the files into the right folder, ran my local test installation and got; Warning: require(BP_PLUGIN_DIR/bp-xprofile/bp-xprofile-admin.php) : failed to open stream: No such file or directory in C:xampplitehtdocswp-contentpluginsbuddypressbp-core.php on line 8…[Read more]

@lincme, sorry, forgot, you will need to add
locate_template( array( 'sidebar.php' ), true )
just above get_footer() in that file.

@johnjamesjacoby, @apeatling are there any plans to add proper code back to the forums here, it’s been way too long now…

Thanks @johnjamesjacoby

@arunbasillal good share. That’s what I’d do to make home page “future-proof” for BP 1.2 series – all bets are off for BP 1.3 🙂

Agreed – @johnjamesjacoby – I just did this to a second site and took less than 3 minutes to get it working.

1. Install plugin (https://wordpress.org/extend/plugins/syntaxhighlighter/)
2. Insert add_filter statements around line 112 of the syntaxhighlighter.php file in the plugin directory

Easy!

sweet! i also dropped viper a note in that wp support thread over to here.

yo @johnjamesjacoby – add it to the site too 😛

@johnjamesjacoby said: because no one is testing the branch and no one is reporting back how various fixes have affected them.

I really dropped off on the bug hunts and running sites off of trunk (2 locals and a live). Since 1.2.x hit – my focus shifted onto contract work and building out plugins for such. […]

@johnjamesjacoby sorry, my mistake, just looked in trac & the ticket has only been there a week, thought it was there longer. It was mentioned here on the forums a lot longer & I did notice it on the WP3 RC builds, my fault for not diving into trac & adding the ticket sooner.

@johnjamesjacoby pointless argument but the activity on front page error was known for weeks before WP3.0 was released. I know the hassles of point releases but thought easy solutions like those posted in trac would have warranted one by now if you want to keep all of us encouraged to keep WP up to date for […]

@johnjamesjacoby : it fixed it !
thanks A LOT.

And before this turns into a total roast or disagreement session (which I don’t think it will, but I want to prevent the slightest chance of that), I want @johnjamesjacoby and @apeatling to know how grateful I am for all the work that you’ve done. The amounts of time, effort, sweat, and thankless work that yall have both […]

@johnjamesjacoby what you say is true and is useful for members of the BuddyPress community to learn from, but, again: The main issue in this thread is around communication, project leadership and where BuddyPress goes from here. Not how to contribute; that’s a side issue, albeit an important one. Go and read @jeffsayre or @hnla ‘s earlier posts […]

@johnjamesjacoby see, that reply of yours right there, that could’ve been a blogpost 🙂 I for one wouldn’t know where to start finding out all about your extra influx of clients, assignments, WordCamp involvement and WordPress work. Even if you are a transparent character on the world wide web, I only have time to check up […]

I would agree with @hnla. I accept all that @apeatling and @johnjamesjacoby are up to. The pace is absolutely no issue. The problem is that the BP dev community is langiushing. We need to accept that this is the current state. I’ll make this an open plea to Andy and John, et all to work with us to […]