[@johnjamesjacoby Keymaster 15 years, 2 months ago]

Using @import in combination with linked CSS causes CSS load order issues, as the HTTP requests are not completed in sequence.

I would suggest researching and using the WordPress API wp_enqueue_style() to better avoid the fouc.

[@johnjamesjacoby Keymaster 15 years, 2 months ago]

Working on all of it. There’s a topic somewhere here that lists what’s broken. One thing at a time.

[@johnjamesjacoby Keymaster 15 years, 2 months ago]

Let’s move this into the codex, and unstick it.

[@johnjamesjacoby Keymaster 15 years, 2 months ago]

Updated. Feel free to adjust as needed.

[@johnjamesjacoby Keymaster 15 years, 2 months ago]

Added some additional checks that are in bbPress 2.0 RC 4. Thanks for the heads up.

[@johnjamesjacoby Keymaster 15 years, 2 months ago]

Easiest thing to do is check out the phpDoc in the code itself.

https://buddypress.trac.wordpress.org/browser/trunk/bp-core/bp-core-component.php#L6

Basically it requires a few basic parameters to identify the component, and calls the parent class function to put them into action.

[@johnjamesjacoby Keymaster 15 years, 3 months ago]

@foxly – Any chance you kind folks can test the plugins with menu issues against this patch?

https://buddypress.trac.wordpress.org/attachment/ticket/3454/3454.patch

[@johnjamesjacoby Keymaster 15 years, 3 months ago]

@foxly Awesome stuff

[@johnjamesjacoby Keymaster 15 years, 3 months ago]

That is weird. Someone want to double check the files in the Trac zip.

[@johnjamesjacoby Keymaster 15 years, 3 months ago]

* Search is fixed.
* Forum pagination is fixed

[@johnjamesjacoby Keymaster 15 years, 3 months ago]

JavaScript caching or an error in your theme or another plugin. Check the solutions in the topic linked above.

[@johnjamesjacoby Keymaster 15 years, 3 months ago]

All these little odds and ends are good to know about. Search is a known issue, but I hadn’t noticed tags not working. If you all notice any other oddities, note them here.

[@johnjamesjacoby Keymaster 15 years, 4 months ago]

Since this got the bump, I’ll add:

Soon.

[@johnjamesjacoby Keymaster 15 years, 4 months ago]

@stevieg – Could be a memory issue. You should be disabling all plugins before doing a core WP update.

[@johnjamesjacoby Keymaster 15 years, 4 months ago]

No, you don’t. There won’t be one.

The issues everyone are having are not with BP. They are with plugins or themes that had the same issue BP did (outdated jQuery) or are issues with browser cache. I personally confirmed this on 5 user sites in the past 2 days, and BP has been woking perfectly.

[@johnjamesjacoby Keymaster 15 years, 4 months ago]

Updates are cron’ed. You should be able to force check with the button in your updates screen.

[@johnjamesjacoby Keymaster 15 years, 4 months ago]

Cheers

[@johnjamesjacoby Keymaster 15 years, 4 months ago]

Browser probably cached it, yeah. We have some cache-busting built into BuddyPress 1.3, so future versions won’t have this problem.

[@johnjamesjacoby Keymaster 15 years, 4 months ago]

@valuser – The migration to 1.3 will be just as easy, but we are making a few under-the-hood changes that still need to be tested for backwards compatibility.

[@johnjamesjacoby Keymaster 15 years, 4 months ago]

I just tested BuddyPress 1.2.9 on WordPress 3.1 and WordPress 3.2 and everything was perfect.

* OS
* Browser(s)
* WP Version
* Try clearing cache?

[@johnjamesjacoby Keymaster 15 years, 4 months ago]

@webby101 – You are safe to update to WordPress 3.1.4. When WordPress 3.2 drops, we are going to release an update to BuddyPress 1.2 to fix a few compatibility issues.

You should also update all sites on your network on your own. Normal users should not be updating your site for you.

[@johnjamesjacoby Keymaster 15 years, 4 months ago]

@markaduffy – There was a bbPress plugin on the stand-alone side of things at one point, but I believe it hasn’t been updated in some time. I have a thought about how to do this in bbPress 2.0, but it would most likely not be persistent, and rather based off the last time a user visited the site.

[@johnjamesjacoby Keymaster 15 years, 5 months ago]

-1 having a hook manager in core.

There is no shortage of actions and filters that can be used, and there’s no way to add functionality to a website without writing some kind of code to do it. If someone wants a hook manager, they’d have better luck using Pods or some other library purpose built for it.

[@johnjamesjacoby Keymaster 15 years, 5 months ago]

Looks neat. You should get it into WP Extend and leverage the BP support forums.

If you want to do that, let me know and we can make it happen.

[@johnjamesjacoby Keymaster 15 years, 5 months ago]

@svenl77 – Happy to have your team on board. Something as easy as moving the `get_sidebar()` calls into the footer makes sense to me. Would seem an easy patch and reduce some duplication.

I’m opposed to hosting anything anywhere else (github) for the simple fact it further fragments development. We have Trac, and we have BuddyPress.org. Unless there’s a coup d’état and mutiny abounds us, no sense in moving that code somewhere else and possibly losing out on the eyes that are already here.

Now if you want to setup your own git repo, and chip away at something until you’re comfortable with the end result, and then provide an SVN diff to put back into core, obviously something like that is fine.