Skip to:
Content
Pages
Categories
Search
Top
Bottom

Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)

  • beeeerock
    Participant

    @beeeerock

    I’m having the same issue… latest ‘mainstream’ versions of everything. I haven’t created a child theme – just trying out the BuddyPress Default to see if it will server my purposes. My header was configured in Photoshop to be exactly the 1250×133 pixels. In Chrome, I’m seeing what looks like the start of a vertical tiling of the header image… just a few pixels worth, but it looks pretty dumb. Firefox seems OK… don’t care what IE does with it… 😉

    Did you find a solution to the problem, or is this something in the way Chrome renders the page that can’t be fixed without an unreasonable amount of effort? When I viewed you link it looks like you’ve got it solved…


    beeeerock
    Participant

    @beeeerock

    Have a look here: http://commonsinabox.org/

    That site does a good job of explaining what their plug-in does. However, your summary is pretty much what I did. I would note that the sites created could use P2 or pretty much any theme you want as you have per-site control of themes, plug-ins etc. To a casual user, the subsites just look like pages of the main site…

    If you have a place you can try this, I suggest you do just that. I found that my in-house Beta program pretty much became a production site overnight as the users found it very useful and without too many bugs!


    beeeerock
    Participant

    @beeeerock

    I wish I could show you the site, but it’s behind security for internal use only!

    I too had trouble getting my head around the problem. What I really wanted was a blog that everyone could use in all workgroups, but filter by workgroup. And based on credentials, some users would never see some groups postings. However, I don’t think WordPress is really set up for that… at least I never managed to find a way to do it, or a plug-in that would do it for me!

    After beating my head against that wall, I eventually did what someone had suggested – build a Commons in a Box site and test it.

    It looks more complicated than it is. My primitive understanding is like this:

    – Commons in a Box (CBox) requires a Multi-Site installation of WordPress (easy to do)
    – When first installed, CBox gives you the base site that everyone in your group would use. The Infinity theme it uses by default is fine for my purposes but I think you can configure other themes if you want.
    – CBox automagically creates subsites on demand. I created a subsite for each general workgroup I wanted to keep separate blogs for.
    – Users can be given access to any or all of the subsites, with different privileges on each.
    – Subsites can use pretty much whatever theme you want. I use P2 for the features you already know about.

    You can set up groups, which seems to do about what I did manually… that confused me at first because I thought groups would give me different functionality… it didn’t, so my recommendation would be to leave that part alone, or let it create all the subsites. Mixing manual creation with Groups creation was confusing for me and didn’t add anything of use!

    You probably don’t want the forums activated either, unless you need to add that function in addition to the top posting P2 blog! I felt the forum would just spread information around too much, making it difficult to find what you want.

    I strongly suggest you set up a sandbox and give Multi-Site and CBox a try… 🙂


    beeeerock
    Participant

    @beeeerock

    @tsinclair1982 beyond the typical titling and header adjustments, there doesn’t seem to be much control over things like the number of columns, header images etc.

    It took me a while to get my head around how to get the multiple blogs going. I don’t think the model I described in my first post is fully possible… however, using Multi-site and Commons in a Box I was able to create subsites for each of my workgroups… my main CBox parent site uses the ‘stock’ theme (Infinity) which allows much more flexibility. I use it as the jump point to the subsites. The subsites run P2 of course.

    P2 is a great start… the glimpse of what it can do is tempting and it’s unfortunate that it doesn’t seem to have enough of a following to advance the development it deserves. There are some plug-ins specific to P2 that are worth a look, but I haven’t found a way to do everything I’d like… yet. I’m a perpetual optimist and hope that someone with coding skills will write more.


    beeeerock
    Participant

    @beeeerock

    I went to Commons in a Box, which is a giant plug-in for WordPress that includes BuddyPress (and many other plug-ins) and allows me to create a multi-site installation with a blog/site for each workgroup I wanted to integrate. Now that the new release of BuddyPress seems to work with most themes that weren’t designed to be specifically BuddyPress-compatible, P2 Theme just seems to work.

    The only issue I have now is that the new P2 Theme seems to have broken the P2-Check-In plugin as I can no longer see the “I’m Here” button on the header. Otherwise, I’ve got most of what I needed working via Multi-Site and Commons in a Box.


    beeeerock
    Participant

    @beeeerock

    Wow, that’s a quick turnaround! Thanks Paul! 🙂


    beeeerock
    Participant

    @beeeerock

    There wasn’t a php log file there, so I edited php.ini and started the logging.

    Here is the output of interest… with ‘domain’ substituted for actual domain:

    [09-Apr-2013 15:26:58] PHP Fatal error: Cannot redeclare bp_login_redirect() (previously declared in /var/www/domain.net/wordpress/wp-content/plugins/buddypress-login-redirect/bp-login-redirect.php:10) in /var/www/domain.net/wordpress/wp-content/plugins/buddypress/bp-core/bp-core-dependency.php on line 235

    Odd… the time stamp looks to be UTC but other messages in the log are local time… but obviously not the problem!

    I moved the buddypress-login-redirect plug-in directory out of the WordPress install and the site is again visible. However, the function that plug-in provided is obviously gone now. I assume this is something the plug-in author will have to fix to live along side of BuddyPress, not the other way around?

Viewing 7 replies - 1 through 7 (of 7 total)
Skip to toolbar