Forum Replies Created
Does anyone know if Mystique for BP works with the new 1.5?
hmm, the ‘edit’ link on my previous reply 404′s?
anyway, just saw that that link is dead. Not sure where it came from, but the name of the plugin is “Remove BuddyPress AdminBar”.
There is a ‘hide admin bar for logged out users’ option. But I want the bar on regular BP sites, I just did not want it on a domain-mapped site that is totally separate (though running on the same WP multisite installation).
http://blog.netweblogic.com/php/wordpress-php/remove-admin-bar-plugin/ did the trick for me.
It worked,but leaves a blank space on top of the page and the CSS is still being called in the source.
Is there a way to remove the admin.css call for just this theme (or better remove the bar and the css for all non-admin users).
Did you try deleting wp-signup.php?
And have you made sure that all spam users have been ‘spammed’ so they cannot just simply add/open new spam users/blogs?
Hi Andrea. Yes, that 1st part is quite easy with BP
the 2nd part is tougher though, as far as I know:
“- the opportunity to manually approve/delete sign-ups based on their answer, at least blocking the unapproved from appearing in blog lists, sidewide activity etc, basically making it 100% private (only vsible for admins) until approved.”
I don’t think anybody can stop you from posting a file on your server with domains and IP’s which you advise to be blocked… I actually think it would be a good idea to have this info centralized, an Akismet for sign-ups if you please, would save a lot of effort.
Just checked wp-ban’s stats and 4 IP’s were blocked over 1000 times. Though it does not stop splogs, it serves as a good example that sharing info might help, especially if the signup page can check a database of known sploggers or words in blog titles.
A nice feature would be (plugin request!) to have:
- an extra field on signup. Skip all the usless and annoying captcha’s, just a simple question: “why you want a blog?” or more specifically: “what are you going tor write about?”
- the opportunity to manually approve/delete sign-ups based on their answer, at least blocking the unapproved from appearing in blog lists, sidewide activity etc, basically making it 100% private (only vsible for admins) until approved.
Before you ask: I cannot make this, but I will be happy to test if some more skilled person can!
ehmm, please refrain from opening new posts which basically links to an other post which links to another post
Not that I do not agree with your request, but by annoying people who might be able to help out, you steer focus away from the problem.
Anyway, does feedwordpress not work?
Rewriting the slug works for me. @andy, would it be possible to have the slug name not in wp-config, but as an option under BP options? Or even as a required step when activating/installing BP? That way, everybody will create their own slug and all should be happier to use BP
yes and no
You probably could use one of the “members only” plugins and adapt them. I do not use them myself, but know they can be used to hide content. You can use it in the loop or maybe for other templates as well to hide more?
Just quickly, like the homepage layout, well done! Any tips on using the template pack or is it easy to use?
@cyndy: I totally agree with you, Capthca’s are ony good for creating jobs in Asian countries and a useless hurdle to users. I second (third?) stwc and Andrea though: once changing the defaults, splogger change from several times daily to once a month….
Don’t forget to delete or rename (or empty if you want to avoid loads of entries in your error log) the wp-signup.php file, as that is what most sploggers come in on. Though I am pretty sure that now BP works on WP, some new methods need to be found soon on both sides of the fence
That looks like what everybody needed
Great, the zip is filled with loads of .tmp, .svn, _MacOSX files though (346 files in 187 folders!). Andy/whoever made it, maybe it should be repackaged?
Also, the instructions on http://codex.buddypress.org/how-to-guides/wordpress-to-buddypress-theme/ are a bit confusing; if somebody got it working, maybe they can edit the documentation with some example codes?
Thanks Modemlooper. Is not also possible (anymore?) to just rename widget.php to home.php and add it to the BP theme?
Saves creating a page, setting it as home page etc (but I guess makes it harder to edit).
Not quite sure yet how the new template structure works, have some reading to do!
I meant that there is no home.php template file as there was before, with some nice standard widget areas, making it easier to have a hmepage/landing page or whatever you want to call it.
But it is no big deal.
Ah, I just got a message from Modemlooper, as he already did something, thanks ML
I used it on bicipedia.com, will likely not work on 1.2, but have not tried yet.
Yep, like it too (and the 6 minutes set up ).
Just installed 1.2 on a fresh install and works nice so far. But I noticed that the new standard theme does not have a home theme (like the buddypress.org) as was included before?
Will there be one later? It keeps me from switching my live BP site to 1.2 at the moment.
Cheers and thanks for the hard work in geting 1.2 out.
>(oo bad construct there – computers aren’t people. yet.)
Hmm, careful or you will hurt Lenny’s feelings. (No, Andrea was joking, Lenny, really!).
ehmm, anyway, thanks for the tip about the hosts file; it seems useful for testing. But how would the wildcards and internal references to the site url (if any?) work? Could I set up any blogs?
hmmm, just tried to visit the factastic page (I had tried it over a year ago but did not like it much then), but Avast Av won’t let me, as the website serves Trojans and quite agressively at that (6 attempts from some Java trojan!). Not Good.
The other plugin mentioned (which I also had tried), is not existing anymore (site gives a 500 error).
That’s why I wa sthinking that a dedicated subblog my do the trick just as fine, just need a nice workable layout
Thanks for the quick reply Andy. Sorry, forgot to mention, that yes, I will be offering user blogs (the ‘network’ setting on new WP?).
What would you recommend in ths case, for a cleanest possible install with less chance of failure when upgrading to WP3.0 when released?
Not sure what happened, could be a server problem as the 2 files do not show as expected, but maybe you uploaded the files to your site root (which is invisible through the browser) and not too the /public-html or /www folder (where your visible files live)?
Currently the BP upgrade instructions mention this as step 3:
“Upgrading with the Plugin Updater
1. BACK UP your existing install including the database.
2. Itâ€™s very important to first de-activate any plugins that require BuddyPress to run before updating BuddyPress.
3. De-activate the BuddyPress plugin.”
This might need to be changed then? I actually would not know to what as I never managed to have a straight update without white-screens and other problems as described above, but maybe that was because of following the instructions?
@DJ PAul & Jeff.
DJ Paul: Agree that a user should be able to choose whether he wants PM from strangers or only from friends.
Jeff, not sure if this is what you mean, but does the Privacy Component allow you to define this setting as just described? Do you have any update about whether your work might be added to core or if it is considered a plugin?
Hi DJ Paul.
as far as I can see, nobody is complaining that the sky is falling, that would be a quite silly thing to do. Well I guess technically it is, but at least the earth is stopping it from doing so
Just pointing out an inaccuracy in thinking, I am sure that this is allowed without immediately posting PHP to fix it?
Back on topic; the question should also be: how could this spammer get access to all the usernames automatically? Of course everybody is listed, but somehow the were harvested and added to the pm list.
- Anyway, I think a very good start is that you can only message your friends. Thought that this would be already ths case, that is why I wondered how we could get spammed?
- Additionally: a maximum of PM’s per user per x amount of time (seems that 1/minute should be enough, + 50 per day. of course this should be optional and configurable with error notification (site options or plugin?)
- Maybe a maximum mailbox size, which included sent messages. So that at least spammers have to clean out their sent box before being able to send new messages.
- Also a maximum of adressees per PM, else the other 2 are useless
- maybe a minimum age of user (meaning time since registration), before he can send out PM at all?
Of course, any of these can be worked around, but at least it might slow spam down, at least from strangers..