Thanks r-a-y for the link. I’ll know to search in Trac from now on.
As the error is with the bundled bbPress 1, I’m guessing the next thing to do is exclude BackPress from my repo/push. It seems this might be a way for me to get through the WP Engine syntax gatekeeping.
Could I bother someone to let me know if simply deleting the BackPress folder is the legit way to handle this-assuming that I’m using a separate, late model install of bbPress.
Note: the issue is present in the previous version of BuddyPress too, so it’s not a matter of using 2.5 locally, for now. In fact the bug is reportedly not being addressed (“wont fix”), so there’s no fix in sight.
I’d say you’ve got an interesting problem here though, as anyone pushing to WP Engine is going to have the same issue as I am, and some won’t know where to turn for help. It’s a bit of a hassle for WP Engine to field support calls too, I imagine.
I believe you can simply delete /bp-forums/bbpress/ and you should be good to go.
However, I understand that this is annoying for WP Engine as you might have to do this manually each time BuddyPress has an update.
An alternative is to pull the development version of the codebase (SVN or Git) from buddypress.trac.buddypress.org. Then, you can checkout the current maintenance branch (currently 2.4, but will be 2.5).
The development version does not include the older version of bbPress; we only include the older version when bundling it for a release.
Hopefully that helps somewhat.
Thanks r-a-y! That’s super helpful. Much appreciated!
Onwards…
Running the dev build means you’re not getting the optimised CSS / JS files.
If you’re able to deploy with a SVN checkout instead of Git, you could use svn co https://plugins.svn.wordpress.org/buddypress/tags/xxx/ --ignore-externals which will not include the bbPress folder from the checkout.
