[@takeo Participant 17 years ago]

But you didn’t answer the question. How do you find out what version you’re running?

That said… why not just update to 1.0 anyway?

[@takeo Participant 17 years ago]

try adding left: 0;

[@takeo Participant 17 years ago]

@Timschmi

As stated above, a blog is typically more personal… written by one person. A Wiki is the opposite. The whole point of a Wiki is group collaboration… group being the key word. So within an organization, you may have a Management group, an IT group, a Training group… etc… and they would all have their own documentation to manage and collaborate on. So to me… Wiki’s within a group just make sense. Right now, the only thing you can share within a BuddyPress group is chat on the wire. But within an organization (for instance)… groups have much greater needs that that.

In case you couldn’t tell… I’m hoping to use BP someday as an Intranet… which to me means social networking + collaboration and document sharing. BP 1.0 has the social networking aspect nailed right now. It’s VERY nice. So sweet. I just hope it takes off and developers start getting on board to extend it.

p.s. I like the Elgg approach of having Wiki’s and Files within groups but also allowing you to browse *ALL* Wikis and Files on the site… so you don’t have to get to them from the group.

[@takeo Participant 17 years, 1 month ago]

If group pages were group-editable… this would be extremely useful for people who’d like to use BuddyPress as an Intranet / collaboration tool. Buddypress is great but it’s mostly just about community… not sharing files, content, photos, collaborating, etc. Now that 1.0 is out though… I’m sure a lot of this will be coming in time… either via plug-ins or new core development.

[@takeo Participant 17 years, 1 month ago]

Could you just add <?php wp_list_pages(); ?> to the header.php file?

https://codex.wordpress.org/wp_list_pages

[@takeo Participant 17 years, 1 month ago]

I have to admit… the name “Wire” confused me too… as I’m sure it will just about everyone the first time. It’s a difficult function to label though.

[@takeo Participant 17 years, 1 month ago]

Yes… I’ve posted this elsewhere (so please excuse me if I sound like a broken record) but it would be great if groups could share different kinds of content… photos (coming this fall?) videos, files and wiki’s (aka group-editable page/post).

Maybe once we are able to share blog posts in groups (as Andy mentions above)… wiki functionality could be wedged into groups simply by installing WordPress Wiki. Create a blog post, make it wiki-enabled and then share it with the group? Just a thought. Not sure if that would work or not.

[@takeo Participant 17 years, 1 month ago]

Try this to make the site always 800px wide in ALL browsers:

in core.css

1) remove the min-width from #main (so it will always be 100% of it’s parent)

2) remove min-width and max-width from body (since you want a fixed width and IE6 doesn’t understand min/max)

3) add “width: 800px;” (or whatever you want) to body (so the entire site will always be this wide)

in admin-bar.css

1) remove “left: 0;” from #wp-admin-bar (so this absolutely positioned element will center itself within the body)

The theme will be a little cramped at 800px… but this should work. Again, if this is just an IE6 issue, I use conditional comments to accomplish what you want (I’m still not 100% sure I understand what you’re trying to achieve).

[@takeo Participant 17 years, 1 month ago]

Internet Explorer 6 does not understand min/max width… it only understands width. So if you set min/max to the same… IE6 will just make the <div> 100% wide (assuming it’s not floated). You need to remove min/max and just put in a width. Your options are fixed width in all browsers or 100% fluid in all browsers (no min/max). Or you could use conditional comments to feed IE6 a different set of width declarations.

Bottom line (if I’m recalling the code correctly) is that you have to make #main narrower if you want the profile page to fit within 800px. You can either define a set width in pixels or just remove all width declarations and let #main default to 100% of the width of it’s parent.

[@takeo Participant 17 years, 1 month ago]

@Kunal17 – Ah yes… I’m always looking for the simplest “low tech” approach… but guess I didn’t really think that one through.

[@takeo Participant 17 years, 1 month ago]

Well… you can still make WordPress pages of course and have them show up in the Pages widget… but I’m guessing you want the pages to be associated with a specific blog/profile?

[@takeo Participant 17 years, 1 month ago]

http://www.w3schools.com/ is a great resource as is http://www.lynda.com and of course the documentation available on this site https://codex.buddypress.org/

[@takeo Participant 17 years, 1 month ago]

One option for GA and bookmarking would simply be to add the required javascript code directly to your templates. The GA code just gets pasted before the body tag closes. I’ve alway thought it was a bit of overkill to have a plug-in just to add a few lines of JS. For the bookmarking feature… addthis.com is pretty popular and easy to use. Same deal… just paste the JS where you want it in the templates. It might not be ideal… but it’ll work.

[@takeo Participant 17 years, 1 month ago]

@Maythil – If you’re on a Mac… download a copy of CSS Edit:

http://macrabbit.com/cssedit/

This editor makes it ridiculously simple to “reverse engineer” CSS code. In the “x-ray” mode you can click any element on the screen and it tells you what the container is (along with all of it’s parent elements). You can also bring up an “inspector” that will show you all CSS declarations that are affecting that element. And you can even modify the CSS and see the changes as you type the code. I’m not sure if there is anything similar for PC… but there must be.

I actually took a quick look myself using CSS Edit and the difference between profile pages and other pages seems to be that profile pages have two left sidebars with a fixed width of 138px (#optionsbar and #userbar) while the other pages have a single right sidebar (#sidebar) without any width defined (i.e. 100%). Meanwhile, #main is used on all pages and has a min-width of 680px. So unless you change some CSS code… the profile pages will always be at least 956px wide.

How did you change the CSS? One thing to bear in mind is that the default theme is fluid. It has min and max widths set. It sounds like you want a fixed width of 800px all the time (no bigger, no smaller… regardless of window size). So… did you remove the min/max on the body and change it to 800? Did you remove the min-width on #main and change it to… let’s say… 560px (allowing 120px each for those two sidebars in the profile)?

Anyway… as mentioned above… this is not a bug and has nothing to do with BuddyPress development. It’s just CSS 101. But I feel you pain. Hopefully the above is some help.

p.s. Did you look at Elgg during your evaluation? It has some features I need that BP currently lacks… but BP is clearly much superior otherwise.

[@takeo Participant 17 years, 1 month ago]

Would the galleries feature be just for photos… or could it also work for documents and/or video? I’m guessing it’s just a photo sharing feature? Which would be awesome!!!

Document sharing would be great too tho’ (and/or a wiki). All in due time I suppose eh? Appreciate the amazing work done so far. Nothing else comes close to BP in terms of usability / interface / etc.

[@takeo Participant 17 years, 1 month ago]

@Lifemore – Thanks for the link. That’s the same guy who makes the eCommerce theme right? I was aware of that Wiki for WP but haven’t tried it with BP. I’ll have to try it out. I’m not super keen on Elgg (it looks really good feature-wise… but just not quote as polished and user-friendly… and perhaps a little more tricky to theme). And the idea of trying to mash up a dozen plugins with Drupal makes me nauseous. LOL

@Nicola – Good stuff!!!

[@takeo Participant 17 years, 1 month ago]

IRC is the protocol (Internet Relay Chat). Freenode is the network (I presume). I haven’t used IRC in years (decades?) but it shouldn’t take long to figure out with a little googling.

[@takeo Participant 17 years, 1 month ago]

@Timschmi

That is so great! Will you be making the plugin available to the community at large? It’s not that tightly integrated (you have to essentially leave BuddyPress and come back)… but it’s better than nothing!

Perhaps integrated Wiki’s will arrive in a future version of BuddyPress (Please BP team). I would envision them appearing within Groups. So group would navigation be “Home, Forum, Wire, Wikis, Members”.