Forum Replies Created
-
there’s more to it than that, W3Total Cache is a full featured and complex plugin – on the plus side it is extremely powerful and on the down side, you can break your site or make it slower if you don’t know what you’re doing
> What settings should be set then..?
it really depends. for example, are you using vps? or shared hosting? etc.
there are lots of tutorials floating around but most are out of date, this one is probably the most recent and complete:
http://code.tutsplus.com/series/configuring-w3-total-cache–cms-656
Any caching plugin will ignore (or should ignore) logged in users and not present them a cached version.
The only way to get around this is to use fragment caching which is when you take parts of the web page which do not change, even if the user is logged in and cache them and present these cached versions to the user. For example, sidebar content.
W3Total Cache does support fragment caching but it is a premium feature and you have to buy it at a price of $95, I think but don’t quote me on that 🙂
https://www.w3-edge.com/weblog/2013/09/w3-total-cache-pro/
The good news is that you do have several open sourced and free options for fragment caching. There are several out there is you just google, including one by rarst.
The fact that caching isn’t really helpful for buddypress sites – since the whole point is to have a social site where people login and interact means that a HUGE amount of priority from a development point of view should be going towards optimization and performance.
We’ve seen some improvements but there’s a long ways to go yet to even come close to wringing out the most. Buddypress is hampered by a large legacy code base with some fundamental structural decisions made early on which still have repercussions today and the desire of the developers to have backward compatibility.
But you can always speak up and add another vote to let the dev team know what your priorities are as a user and community member.
@ hnla Thanks Hugo. The “legacy” term is misleading but I don’t want to get bogged down in that.
I realize that there are older components, features, etc. that are being accommodated because the development team (rightly, I might add) wants to maintain backward compatibility with existing or older versions of buddypress that have been deployed and on which people depend on.
I’m wondering if there is a safe way to excise these to have a leaner version of BuddyPress when running a fresh install which doesn’t need to accommodate any older ‘baggage’.
Hope I’m being clear 🙂
Hi Paul, thanks for the message. The “official” stance is that HHVM will be officially supported in the upcoming wordpress 4.0 – although as you say, as of 3.9 it runs without a hitch.
I think it is obvious that HHVM is an important variable in wordpress and will become even more important in the future.
@mercime thank you but that is a configuration of VVV with HHVM. Unless I’m missing something, it doesn’t answer my original question.
a couple of things:
- here’s the codex page for customizing the permalink for members or any other component like it:
https://buddypress.org/2009/05/customizable-slugs-in-buddypress/ - while it may not be buddypress’s fault if there was a conflict with a plugin (cubepoints), I would suggest considering moving from cubepoints to myCRED which has a newer code base, support and extensive documentation (mycred.me)
maybe someone else can chime in on the activity update ‘bug’ that you mentioned
I’ll let Matt have the last word (jump to 9:13):
http://wordpress.tv/2014/04/05/matt-mullenweg-wordpress-future/
Hi Hugo, my bad, should have given the link: https://codex.buddypress.org/getting-started/improving-performance/ at the bottom of page
but I see you, or maybe another mod? has already removed the link to this thread
does anyone know if Fredrick Townes has said anything about adding functionality to W3 total cache for buddypress? all I found was this 4 year old comment
Maximize WordPress and BuddyPress Performance With W3 Total Cache
this is so strange! the codex leads here but no one has any useful information
:/
@sooskriszta totally agree with you on your 3 (relatively) objective tests – this is why I suggested 2 key features that need to be improved in buddypress *immediately*:
1) spam fighting
2) fragment cachingFirst, 99.9% of buddypress communities have to deal with spam and it is mission critical (who wants a website overrun with spam? users leave, google rank drops, etc.). How many forum threads are opened again and again about people asking for help dealing with spam? how many different methods need to be cobbled together? it just makes sense to take the best practices and build them into the core.
Second, performance is an issue that is more and more important not only because speed is a do or die issue (there is ample evidence of a direct link between a website’s speed and its success in converting and in pageview counts)
with buddypress, regular caching plugins simply do not work, we need fragment caching, and we need it YESTERDAY!
there is already a tentative step in the right direction with rarst’s fragment cache plugin but this should be developed into a full solution and built into core.
everyone will benefit from improvements in caching and it will make a MASSIVE impact on the overall quality and success of buddypress as a platform
/drops mic
@mercime fantastic! this is a far far better presentation than I could have ever imagined! 🙂
kudos and THANK YOU !!
pls remove spam comment above and delete spam account @saeed-mahmoood
thanks
Glad you found my suggestions helpful. re mobile, any good theme would give you that functionality so make sure to test them at different resolution sizes and check total kb size (how bulky the theme is) also.
also, check out: https://wordpress.org/plugins/buddymobile/
@mercime any update on the survey results? 3 weeks ago you mentioned it would be released ‘next week’
thanks
Rick, glad that we’re clearing up some confusion. To confirm, yes, messaging is totally different than posts. Please read the codex links provided. Also, if you really want to take buddypress for a test drive, set up a development site either on a live site or right on your own computer using http://www.instantwp.com/ and then add some “fake” users and messages, and data using this plugin: https://wordpress.org/plugins/bp-default-data/
And then jump in there and click around like crazy, edit, message, post, and see what happens! this is the best way to really check things out without doing any damage to your own site. Nothing compares to getting your hands dirty and mucking about (in a safe test environment).
This way you can really understand what messaging is, what private messaging is, broadcasting from admin to all members, etc. You can also add/remove plugins and check out their functionality, all in the comfort of your own computer’s hard drive or a test environment set up at a test domain/host that you control/own.
Also, keep in mind that buddypress has many features but you do not have to enable them! for example, there is a feature for groups. But you don’t have to enable it! you can add a forum (using bbPress) but you don’t have to! you can have private messaging so members can send private messages to each other… but, you guessed it, you don’t have to enable this feature. Also, another powerful feature is that you can give members of your site the ability to start their own blogs! this is called “multisite” but you can choose to enable this or not. Same goes for “friend connections” feature… etc.
My suggestion is to start with a very simple starting point and then as your community grows, add features that they require or need. It is a far too common mistake for new buddypress users to just turn everything on at the start.
If you don’t want to restrict your membership in any way or to collect money online from them then you don’t need anything else other than buddypress and wordpress. But look through the membership plugin links I provided to familiarize yourself with them and their features just in case. A few are completely free and still have tonnes of features.
Finally, keep in mind that spam registrations do happen. There are many guides and tools to mitigate spam membership registrations. Here’s a good start:
Google is your friend for more info on spam fighting.
oops, looks like I linked to the wrong url for the broadcast message plugin (from admin to all members)
:/
this is the right plugin:
https://wordpress.org/plugins/mass-messaging-in-buddypress/I’ll add this to clarify further, a person can join your website but with a membership plugin you can have several tiers which would act as a filter to designate what they can and can’t do or see on the site.
So for example, a regular member can read the blog. A ‘premium’ or ‘conference’ member can read the blog, write comments, read the conference specific blog posts, private message other conference members, etc.
Some membership plugins are quite powerful and granular… if you need that sort of thing.
ok, let me see if I understand you — if not, correct me 🙂
1) you have a website at: http://www.betterpresenting.com/
2) you have created another separate website at http://www.summitcommunity.org/ where you want to install buddypress and create a community website for a conferenceok I think before we even get to the ‘messaging’ or ‘post’ issue, we have to clarify something.
As of now, http://www.summitcommunity.org/ forwards to http://www.betterpresenting.com/community/
Buddypress automagically works seamlessly with your existing theme so it looks good… this wasn’t always the case so thank the developers who added this feature just a few months ago! moving on from minor digression…
So it looks like you don’t have two separate sites but your domain at summitcommunity.org is 301 redirecting to http://www.betterpresenting.com/community/ and this is where you have installed buddypress.
Is that correct?
If this is correct, then we can move on to the other question you posed.
I went back and read you original post that you referenced above:
https://buddypress.org/support/topic/installing-bp-into-a-portion-of-a-site/In that message you write:
“If I understand correctly (a reach at best), posts become messages. But I post at betterpresenting.com about a great many things, not just ones that would be for the conference community.”
Posts do not become messages. Posts and messages are separate things. ok?
A post is well, a blog post. I’m sure you know what that is.
A message is an internal message sent from one member to another (if you have enabled this feature of buddypress – you don’t necessarily have to! or from admin to members)
https://codex.buddypress.org/buddypress-components-and-features/messages/
https://codex.buddypress.org/component/private-messages/Also, admin can send a ‘broadcast’ message to all members with this plugin:
Hope that clarifies words and definitions so we have a standard vocabulary with which to communicate!
Now, if I understand the rest of your original message accurately, what you’re saying is that you run a website and have an annual conference and would like to know how buddypress can help you with both. And you want to make sure there is a way to keep the conference ‘stuff’ separate from the other regular website ‘stuff’.
To solve this, you don’t need subdomains or extra installs of wordpress or any of that. Here’s what I would do:
I would install buddypress as a plugin in your existing wordpress blog (the ‘main’ site). Then I would use the buddypress features to run your annual conference by also enabling a membership plugin.
Using the membership plugin you can post ‘conference’ related material and pages which ONLY THE MEMBERS SEE and interact with. To someone who just comes to your site, all they see is your regular blog/site… until or if they ‘login’ and have paid or are accepted as ‘conference’ participants.
People who are members of the conference (aka buddypress + membership powered) site can see and interact with both the conference portion of your site as well as the regular part of the site.
If I have hit the nail on the head and accurately understood your needs, here are some reference material:
http://chrislema.com/comparing-wordpress-membership-plugins/
If not, let me know!
Hi Rick, I think you need to clarify exactly what you’re trying to do. What you write is very confusing and may have lead to your and others’ frustration in attempting to help you:
“But our main site has an active blog and I don’t know how to separate posts that are intended to be read by the entire world and shown across the entire site from messages that are intended to go just to the Summit community.”
Are we talking about messaging? as in private and internal messaging between members and between admin and members? or are we talking about blog posts that are read by all or some parts of the community?
If you want to restrict blog posts to just members, this is extremely easy and there are many plugins that handle this.
https://wordpress.org/plugins/private-community-for-bp-lite/
as well as s2member and other ‘membership’ plugins which work with buddypress to create tiers to separate content (pages, posts) so that you have control over who sees or reads what.
So please clarify EXACTLY what you are trying to accomplish and hopefully the community here can help you.
@chefbt you can also change the ‘buddypress’ slug to something else, like ‘community’ so that the URL structure is:
http://example.com/community/members
this is what this website’s configuration does, like so:
https://buddypress.org/community/members/chefbt/
for more, scroll down to slugs part here:
@chefbt my time to shine (even though I’m not a coder!)
to put profiles in the root — http://example.org/username/ add the code snippet below to your wp-content/plugins/bp-custom.php file:
define ( ‘BP_ENABLE_ROOT_PROFILES’, true );
yay! hope that fixes it for you. In the future, google is your friend. So is the codex where this came from:
because of its nature (membership site where content differs depending on being logged in vs. logged out content) the best caching solution for buddypress is partial page caching (aka fragment cache), something that sort of exists and sorta doesn’t.
my suggestion is to take the BP survey and to add your voice for it so the developers know there is real demand:
more info:
http://chrislema.com/high-performance-wordpress-membership-site/Fragment caching in WordPress to optimize site speed for logged-in users
https://bitbucket.org/Rarst/fragment-cache
https://wordpress.org/plugins/fragmentcache/@henrywright-1 Thanks Henry, I’m familiar with the usual steps you outline. Just curious if removing comments and blank lines would make a significant difference 🙂
umm… is this a stupid question?
- here’s the codex page for customizing the permalink for members or any other component like it:
