Forum Replies Created
-
In reply to: Problem with bpPicture Album
Wow. That was quick. Thanks : )
In reply to: bp-events for bp 1.1 needs testing!Fantastic. Thanks so much for the update. I was a little confused as to who was working on what or if Erwin had abandoned it… etc. This clears things up a lot. Looking forward to this plugin for sure. Should be great. I would love to help… but my PHP skills are pretty limited.
In reply to: How to requirie log in to access everythingSo you want to just redirect anyone who’s not logged in to a static homepage with only static content?
In reply to: bp-events for bp 1.1 needs testing!Any tips on getting bp-events 1.1 working with BuddyPress 1.1? Or is it simply not finished?
I installed it fine but it’s somewhat broken. For instance, nothing shows up on the event detail pages. The content area is just blank. Anyway, if it’s still in development… that’s fine. I’m just trying to figure out the status… is it’s just not done or it I didn’t install it properly.
In reply to: bp-events for bp 1.1 needs testing!Sorry. I’m confused. I can still download the plugin from erwingerrits.com but I take it that you folks have taken the plugin and updated it for BP1.1. Is that correct? If so, that would mean that the version available at erwingerrits.com is out of date. Is he no longer developing it? Also, bp-events was not included with BP1.1. Where could I go to grab it? Here?:
http://svn.ywamnetworks.com/bp-events/trunk/
Can anyone recommend a Mac SVN client?
Thank you.
In reply to: admin bar links at bottom of browser – a bug?Same here in Safari… but only while in the Forums section. Looks like the forum pages are not linking to / importing the admin-bar.css file
In reply to: Conditional tags for BuddyPressawesome!!!!!!!!!!!!!!
In reply to: Upgrading to 1.1-rc/1.1-betaOkay… I must be an idiot but I can’t even get the plugin activated. I installed a fresh WPMU 2.8.4a with a fresh database and no plugins. No problem so far. Then I placed the release candidate files (bp-activity, bp-blogs, etc.) inside wp-content/plugins/buddypress and the plugin doesn’t even show up in the admin area. Wha? I went to “Site Admin” as well and enabled plugins in the options area. No dice. Weird. It just says “No plugins to show”
In reply to: BuddyPress Privacy Component: An Update@Anointed Ha! I was doing the same thing! Trying to make Elgg look like BP. Funny. I worked on it for about a week before giving up. I couldn’t deal with the 100’s (okay, dozens) of CSS files (that are actually PHP files so you can’t use live CSS editing tools like Coda or CSSEdit for Mac… ARGH!). Plus I was finding I had to override a lot of core files to make it look and act the way I wanted… which didn’t sit well. I agree that Elgg is more advanced in terms of features… but I just didn’t want to deal with it. I also decided that although BP is newer and not as complete… it has a brighter future. My prediction. I could be wrong.
In reply to: BuddyPress Privacy Component: An Update@Jeff. That’s cool. I can just use a simple plug-in to block out groups, etc. wholesale. Like that code Burt did… just using is_user_logged_in(). It’ll do for now.
The issue is, I want to use BP as a kind of simple, lightweight “Intranet”/communication tool for our local Search & Rescue group. We’ll mostly use groups and/or bbPress to discuss fundraising, training, recent searches… etc. As well as look up members in the directory. Etc. All that stuff should be just for members. Some of it can be sensitive info. But we still need a public face for news, events and static info (faq, about, photos, etc.)
Two sites (a WordPress site for the public and a BuddyPress site for members) might make sense… but there’s overlap. All that public stuff needs to be available to members as well (pages, posts, events). So having two sites would be kind of a nightmare.
But I digress!!! As I say… I’m sure I can hack something together. Since I’m just hiding entire classes wholesale… it should be simple enough with a bit of PHP. Not sure how events will work though.
Anyway… very much looking forward to the privacy component as designed. Even thought it’s not what I thought it would be… and won’t do what I had in mind… it sounds like it’s actually a lot more impressive than that.
In reply to: Plugin to show components to registered Users onlyI imagine it might make sense to hide the activity stream too… otherwise non-registered users clicking on links in the stream would get a LOT of annoying “please register” screens.
In reply to: BuddyPress Privacy Component: An UpdateReplying to myself… I did a forum search and this should do the trick. A simple plugin to make BP components only visible to logged in users.
https://buddypress.org/forums/topic/plugin-to-show-components-to-registered-users-only#post-18381
In reply to: BuddyPress Privacy Component: An UpdateLike wordpress fan… I also need a solution that shows different components to registered vs. non-registered users. I can’t launch without it. Unless we build to separate sites… but I really don’t want to do that. The “public” (non-members) should basically only see the main blog’s posts, pages and events. Everything else needs to be hidden until you log in. I guess a bit of PHP might fake it just by hiding navigation options. In fact, there is a thread on the forums about that. I was assuming that the new privacy module would make that information moot however.
In reply to: BuddyPress Privacy Component: An Update@Anointed: It’s not that the core is “flawed”… it’s that BuddyPress is simply a plugin that sits “on top” of WordPress MU while Elgg is an integrated solution. Personally, I still prefer BuddyPress. The theming process in Elgg caused me great pain and I find the Elgg interface suffers from inconsistencies and poor usability.
In reply to: CSS help requiredThat’ll work but can result in scrollbars or cutoff images in some cases. This is not a CSS forum… there are better places to learn this stuff… but briefly… I know of four methods to clear floats:
1. Use extra HTML markup to clear your floats (<br style=”clear:both;” />). Ugly but it works every time.
2. Use :after (the positioniseverything.net method) to do the same without the added presentational markup. But it doesn’t always work.
3. Float everything. But you may unleash a positioning nightmare.
4. Use overflow hidden or auto on the parent. But you may get scrollbars or cut off content in some cases.
In reply to: CSS help requiredIn reply to: CSS help requiredLike I said, it’s a float issue. You have your entire page wrapped in the #header div (with it’s white background) and there are a number of floated children.
In reply to: CSS help requiredI just realized that of course Eric Meyer has written a lot of books on CSS. LOL. This is the one I’d recommend for a beginner.
In reply to: CSS help requiredLooking at the page quickly (without having viewed any code) it looks like you just haven’t cleared a float. When you float an element (like a div) it’s parent elements collapse unless you clear the float. CSS 101.
Do some googling, use w3schools.com as a reference site, keep on banging away at it and maybe pick up Eric Meyer’s book on CSS.
In reply to: Force positioning img in .storycontentWith the text and images living at the same level… there’s not much you can do other than force an alignment. You can’t move an image from the middle of a paragraph to the start of a paragraph. I don’t know what your site is and what kind of content it handles… but what you MIGHT consider is disabling the media buttons in the WYSIWYG editor completely (if possible) and then… if people want to upload media… have them do that via a custom field. The plugin “Custom Field Templates” is great for this. Now you have separate database entries for the content and the media. The media is now post metadata. You can then run an SQL query to grab this data separately and have total control over where it goes, how it looks, etc.
Of course… the bigger question is… how strict do you want to be? Maybe just let them be? Also… my crazy idea above could confuse or annoy uers who a) don’t get it or b) get it but want to put an image HERE damn it!
In reply to: How to: Make drop down menu from nav?Some good resources for learning CSS are w3schools.com, lynda.com, Firebug for Firefox, anything written by Eric Meyer… and if you’re on a Mac… CSSEdit from MacRabbit.
In reply to: Can find a specific colour code. Need a little help.Makes sense. When I saw the filename (theme-options.php)… I figured this was a custom generated css file that was pulling in settings from the admin side. I guess the theme needs more testing maybe? Anyway… you could add “#post-entry li blockquote {color:#000;}” anywhere and it should work. Using the BuddyPress “custom.css” file or “site-wide.css” files might make sense if you don’t plan on changing the theme and don’t want to mess with the theme files.
In reply to: Can find a specific colour code. Need a little help.I tried taking out that !important property but all his white text went bye bye. It would be nice to revisit the CSS and not use so many !important properties… but I have a feeling that would be opening the proverbial can of worms. Adding a color to #post-entry li blockquote is a quick fix for this one specific problem.
In reply to: How to: Make drop down menu from nav?Yah… always best to use unordered lists for navigation. It just makes the most sense semantically speaking. Once you have your navigation being output as nested lists… there are any number of CSS/JS solutions to hide the nested lists and turn them into drop downs. The most lightweight solution is the old tried and true suckerfish menu… which is pure CSS with just a teeny tiny bit of javascript code to make it work in IE. But since jQuery is already included in WordPress… may as well go with something a little more fancy… with a mouseout delay… etc.
In reply to: Can find a specific colour code. Need a little help.Hey Andy,
Nice looking site.
Looking at your CSS I see that the declarations have a lot of “!important” properties. Like… a ton of them! This property should be used sparingly because it tells the CSS not to cascade (the “C” in CSS). It tells the browser that this rule will override all other rules unless it is overridden by a more specific declaration. This can make styling and debugging a huge pain because you’ll try to add or edit a style and nothing will happen.
In your case… you have “color:#ffffff !important” declared for the body tag in base.css. That makes every single bit of text on the entire site white unless it is overridden by a more specific declaration. Which is exactly what’s happening here. You don’t have a declaration to override the white text for your wire content. I would highly recommend reworking the CSS so it takes advantage of cascading and doesn’t have all those !important properties. They make styling very confusing. But the quick fix is to add this line to the “#post-entry li blockquote” style in your base.css file:
color: #000;
So change this:
#post-entry li blockquote {
padding: 10px;
width: 90%;
margin: 1em 0px 0px;
background: #eee;
-moz-border-radius: 5px;
-khtml-border-radius: 5px;
-webkit-border-radius: 5px;
border-radius: 5px;
}
to this:
#post-entry li blockquote {
padding: 10px;
width: 90%;
margin: 1em 0px 0px;
background: #eee;
-moz-border-radius: 5px;
-khtml-border-radius: 5px;
-webkit-border-radius: 5px;
border-radius: 5px;
color: #000;
}
