Skip to:
Content
Pages
Categories
Search
Top
Bottom

Forum Replies Created

Viewing 20 replies - 1 through 20 (of 20 total)
  • Sorry, it get posted twice. [edited]

    Andy, we’ve had a discussion on IRC long time ago about this ticket https://trac.buddypress.org/ticket/257

    And it’s stuck with this WordPress bug https://core.trac.wordpress.org/ticket/8662

    Could you push the core devs up there to take a look and commit the patch? It’s a tiny bug, and it doesn’t affect standard WP installations, but it does to BP, and it’s bugging us who live ahead GMT and use our local time as the blog’s time.

    @burtadsit

    Another alternative instead of separating WPMU & bbpress capabilities: you can assign specific user meta for each users. Say, the meta value is an array containing all forum ID that specific user belongs to. Of course you need to write some hack to the bbPress side as well. That way you can share both public & private forums in a single bbpress install.

    Just an idea. I haven’t look into the code too :-)

    usually I search the whole wordpress directory for the string do_action or apply_filters, then look for the best place to hook my functions to.

    I’ve successfully setting up mercury mail. But can’t remember how. There’s are alternatives software in windows. Try hmailserver. So easy to configure.

    With regard to the title: “Feature that MUST be included in next version for me..”

    I’m in need of event listing. And if we look at how Facebook manage their event list, I think a pseudo-blog would also be a good base to build on. A “blog” that is open to any member to post and comment. The blog post is the event description. The blog custom field can hold specific informations: venue, RSVP, speaker, etc. The category system, tagging, etc. All is perfect, I think. Then we exclude/hide it someway so it’s not considered someone’s blog–to differentiate it with the real blogs.

    Anyway, we’re all used to develop WordPress into anything we need aren’t we? 😆

    @nicolagreco I think it looks like the same with the earlier version facebook status (without the status comment system)

    In the previous revisions, buddypress hold each profile page as blogs. It’s not blog, it’s profile page but use the database structure like a blog. I came here in the end part of that stage of BP. I’m not sure the whole structure behind it.

    bp-status? Never heard about this. But isn’t BuddyPress wire has the same function as status?

    Speaking about personal blog for each user, I think we had gone through this before. Every signed up user once got his/her default profile page in subdomain that acts like a blog. Then Andy made some modifications and threw then away.

    @burtadsit

    Howdy, Burt. Yes, it’s me, :-)

    @dkbuddy

    Just create it. I think you also need to enable the apache mod_rewrite module, CMIIW.

    In your case without a dns name server, you need to add new lines in your hosts file whenever you add new blogs in subdomain.

    @burtadsit

    Thank you for sharing, Burt. I need this. :-)

    @dkbuddy:

    I suggest you reinstall your WPMU, install it in a domain, not subdirectory.

    Before installing, you need to prepare a domain and a directory to be used as the document root of the domain.

    1. Map your domain to the local IP in the hosts file.

    For example:

    127.0.0.1    mysite.dev
    127.0.0.1 blog1.mysite.dev

    2. Then you need to configure virtual host in your XAMPP installation. This way, XAMPP will use a specific directory to be used as the document root. Edit your apache configuration file. Usually it’s located inside your XAMPP installation (/opt/lampp). Add mysite.dev and use your WPMU installation directory as the docroot for mysite.dev

    3. Restart your Apache, and make sure XAMPP display the content of your WPMU directory when you visit mysite.dev in via your browser. When it’s OK, you can start installing WPMU.

    Bingo! that was the problem. Thanks…


    Huda Toriq
    Member

    @hudatoriq

    Anybody using hostgator or ever heard some problems using WPMU on their shared hosting? I’m interested with their baby hosting package, unlimited space & bandwith. But the inodes limit of 250,000 is worrying me.

    What a great news :).

    Can’t wait until the update.

    That’s a good idea. Perhaps not fully open. Instead, let us confirm & permit some other buddypress site to allow their users participate in ours, creating a network of social networks.

    Will the home base database remain empty all the time and in future development? I plan to use the username.example.com as the default blog for each user, like the normal WPMU does, instead of using it as the home base. The social networking stuff will reside under the main domain. It will avoid confusing of having the blog & the user profile in the same level. I’ll examine budypress theme and look for some way to integrate it to the ‘home’ theme.

    All I concern about now is, will it create conflict? I don’t really understand what those empty database are used for.

    @ron_r

    Are you using

    username.example.com/profile or

    example.com/profile/username for the URL structure?

    Anybody is working with the latter one?

    @ron_r. Do you mean you’re using the same theme to handle the main domain & the profile?

    @vegavaughn

    /andy/home

    /andy/blogs

    /andy/profile

    This URL structure dedicates all subdirectories of the main site for usernames. We can’t use them for other purposes.

    @gogoplata

    That means each user can only have a single blog.

    Same idea here https://buddypress.org/forums/topic.php?id=25#post-92 , where Andy linked to this topic :).

    I think we need to discuss more about it.

    We can handle such URL like http://domain.com/andypeatling/home or http://domain.com/user/andypeatling simply by customizing the home theme. Instead of using another theme for the home base, let the home theme handle it.

    I hope the other components have enough flexibility to be used in such way.

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