Skip to:
Content
Pages
Categories
Search
Top
Bottom

Forum Replies Created

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

  • mkgold
    Participant

    @mattkg

    Great! Very glad to hear it. Thanks for your reply.


    mkgold
    Participant

    @mattkg

    I agree that this is an important and needed functionality for groups. At the CUNY Academic Commons, we’ll probably wind up building this plugin if no one gets to it first.


    mkgold
    Participant

    @mattkg

    Hi Biegun,

    Yes, there is more than one way to skin this cat. The advantage of using MediaWiki is that it offers a more robust wiki platform than the wiki plugin you mention. MediaWiki is the software that powers Wikipedia; it can be downloaded here.


    mkgold
    Participant

    @mattkg

    http://commons.gc.cuny.edu

    WPMu + BuddyPress + BbPress + MediaWiki

    It’s an academic social network built to bring together members of the 23 campus City University of New York system


    mkgold
    Participant

    @mattkg

    I ran into a big problem with avatars: images could be uploaded, but the crop box couldn’t be adjusted (it could only be found up in the lefthand corner of the image), when you cropped anyway and went ahead the image literally bounced around the page, and the uploaded images wouldn’t show up — I’d just get a black box.

    The solution, as it turned out, was to look for plugins that might be causing the conflict. For me, the Litebox plugin for WordPress was causing the problem — deactivating it enabled everything to work just fine.


    mkgold
    Participant

    @mattkg

    Hi Everyone,

    I have solved this problem on my installation with help from a very wonderful sysadmin. Here are the two steps we took to make this work:

    – PHP safe_mode turned OFF

    – PHP able to execute the “readfile” function.

    Now that we’ve done that, things appear to be working. I hope this solution works for others.


    mkgold
    Participant

    @mattkg

    It’s a known bug, I think. Here’s a workaround: https://trac.buddypress.org/ticket/519

    Not a perfect solution, but one that works . . .


    mkgold
    Participant

    @mattkg

    Has anyone been able to find a solution to this yet?


    mkgold
    Participant

    @mattkg

    Basically, I think I’m having problems with paths — the buddypress member page isn’t accessing the css/image files for the main theme. For some reason, I’m having trouble getting my head around this.

    Here is the actual error that I’m seeing:

    Warning: include(C:xampplitehtdocs/wp-content/member-themes/buddypress-member/options.php) [function.include]: failed to open stream: No such file or directory in C:xampplitehtdocswp-contentmember-themesbuddypress-memberheader.php on line 53

    Warning: include() [function.include]: Failed opening 'C:xampplitehtdocs/wp-content/member-themes/buddypress-member/options.php' for inclusion (include_path='.;C:xampplitephppear') in C:xampplitehtdocswp-contentmember-themesbuddypress-memberheader.php on line 53

    And here is a screenshot

    I want the header to match the header on this


    mkgold
    Participant

    @mattkg

    Running into this problem today, and creating an avatars folder didn’t help. Does anyone have another solution?


    mkgold
    Participant

    @mattkg

    Just to add to the historical record: I installed BuddyPress on a working WPMU install and got a blank screen of death. It turned out that the problem had to do with the 16M limit in the php.ini file. Upping that limit solved the problem.


    mkgold
    Participant

    @mattkg

    Solved this problem with help from a friend, who did some PHP error reporting. It turns out that my PHP install has a 16M limit. Upping that limit on php.ini has given me a working version of BuddyPress. All right!!!

    So, we are finally resolved.


    mkgold
    Participant

    @mattkg

    I’m not sure how this topic was marked as resolved, because it’s not .. . . I still need help and would be grateful for any assistance that you might be able to offer. Thanks.


    mkgold
    Participant

    @mattkg

    Typo (here, not on the server). The above problem occurred with permissions set to 755.

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