Forum Replies Created
-
In reply to: tiny usability improvement on group admin page
I thought that too actually… and I still have to think about it when I see that checkbox. Good call. Create a ticket.
In reply to: First experiments and I already need help 🙁p.s. FYI… I did once successfully change a WPMU+BP URL. So it is possible. But I was the only user and the site had basically no content and no user blogs. Unfortunately… I did not document all of the DB and wp-config changes I had to make to make this work. But it wasn’t all that bad. I think I had to change the URL in maybe half a dozen places. I used the search function in PHPMyAdmin to sniff out the old URLs.
In reply to: First experiments and I already need help 🙁@Xevo: Where is “maintenance mode”. Is that a plugin? Also… that would only work if you have a new domain of course (i.e. if you don’t already have an old site up at that domain which you plan on replacing)
@Andrea_r: Ya… when I suggested just switching the domain I was assuming that the only user would be the developer… that you’d just use the remote server for development, testing and content population. If you have a bunch of users in there (esp. if they are active) and then change the domain… lots of things would break after the switch… every single member profile link for starters.
I guess as far as the DB goes… it boils down to what content you need to migrate. If you migrate the whole DB from one URL to another… lots of stuff will go boom. But if you do a fresh install on the live URL and only export/import the tables with page/post content… you’d be pretty safe. Would be nice I suppose if some uber geek wrote some migration scripts. Ultimately… the easiest thing is… if you have a new site on a new domain… just develop/test/populate with it in maintenance mode.
In reply to: WPMU or Buddy Press is really slowI have an inexpensive dedicated box at http://iweb.com/ with… I think 2 GB of RAM and a 3GHz Athlon CPU… and even without eAccelerator installed or zlib enabled at the moment… BP+WPMU screams. So… as they say… YMMV.
In reply to: BuddyPress for dummies bookSo true though. Not to diminish Lisa’s effort however. It’s a ton of work to write a book and it doesn’t pay well at all. It’s mostly a labour of love. But we’re the hardcore BP geeks here. I’m sure that the book will be quite useful to the average ‘joe’ and will sell well. And once the first version of a book is written… it’s not nearly as much work to update it for newer versions of the software.
There is a config file setting that will allow you to run BP on all of your user blogs… so you could run BuddyPress on as many sub-domains as you wish. I have no idea how you might run one instance on multiple fully qualified domains however. That doesn’t sound possible to me. But I’m no networking guy.
define ( 'BP_ENABLE_MULTIBLOG', true );https://codex.buddypress.org/how-to-guides/changing-internal-configuration-settings/
In reply to: First experiments and I already need help 🙁It’s tricky. I agree. I might register a subdomain for staging (say dev.mydomain.com) and get everything good to go there. I would not use a folder on production. BuddyPress isn’t happy living in a folder and I think it would be more of a pain to go live. If you use a subdomain, switch the domain over to http://www.mydomain.com when you’re ready to go live. But things will have to be changed in the DB (mostly in the wp_sitemeta table but also in a few other tables I think) and in the wp-config file.
But I’m no networking genius. So don’t listen to me!!! I’m mostly a designer / html guy. Maybe others have better ideas of how to manage development.
In reply to: First experiments and I already need help 🙁Ya… you don’t want to do that. You local config file will be different of course and there are a number of domain references in the DB (not thousands mind you… but more than one or two). Also, WPMU creates the config file for you upon install and you mess things up if you swap it with another.
A config file would never be kept in a repo I don’t think.
To answer your last question, it is easy to move things to other folders but everything will break :o)
Why would you ever want to mirror all those core files anyway? The only place you would be doing your own development would be within the theme.
In reply to: No admin bar in r2638?Ha! I do believe I just found a WPMU bug. The default RSS widget was misbehaving causing my HTML to stop rendering before the admin bar code (which is at the bottom of the HTML).
In reply to: BuddyPress for dummies bookWell it takes about 6 months to a year to write a book. I think this book started sometime last summer. Basically, BuddyPress has been changing faster than you can write a book. There may be a 1.2 book in the works from another publisher that I was in contact with.
In reply to: Member only access to BuddyPressYup. I’m using Burt’s tiny bit of plugin code and it does the trick.
In reply to: adding content to the 1.2 default theme homepage@Andy. Yup. It makes sense to me now that I’ve figured it out. After your instructions didn’t work as expected, I went back to basics and read the codex page about “Reading Settings” and under the “Front Page” bullet near the bottom of the page it says “If you would like to create a static home page template file, do not name it home.php”. Ding ding ding! Light bulb. So I put two and two together and finally figured it out.
https://codex.wordpress.org/Settings_Reading_SubPanel
Glad I’m not crazy after all. Sorry. I know my additions to this post were very confusing and probably a little frustrating. And thanks again Andy! Although your instructions didn’t work quite as expected because I had that home.php file, at least I knew I was on the right track! You’re a lifesaver.
In reply to: adding content to the 1.2 default theme homepageAndy’s instructions didn’t work because I still had a template named home.php for my homepage and it was taking over control of my posts page even when I had manually assigned it to my custom “Blog” page and template.
If anyone cares (LOL)… here’s the solution to having a separate front page and posts page that can both use a full paginated result set from the database.
1. Make a template for your homepage with a filename OTHER than “home.php” or “index.php”. I used “homepage.php”.
2. At the top of this file add
<?php /* Template Name: Home */ ?>3. Make a WordPress Page called “Home” and assign it to the template you just made (i.e. “Home”).
4. Make a WordPress Page called “Blog” and leave it assigned to the default template (which will be index.php).
5. In the Reading Settings switch to static mode and set the Front Page to “Home” and the Posts Page to “Blog”.
Thanks for the help guys. That was a mind bender. Just seemed easier (from a development point of view) when home.php and index.php defaulted to “/” and “/blog/”
Now I think I need a drink. LOL :o)
In reply to: adding content to the 1.2 default theme homepageI did do exactly what Andy said and both domain.com and domain.com/blog end up using home.php. Still looking for a solution I’m afraid.
In reply to: adding content to the 1.2 default theme homepageJust to make sure I’m being clear… I’m not trying to make domain.com/blog/ my homepage. I’m trying to make domain.com my homepage and domain.com/blog/ another page which shows a paginated result of all posts.
Greatly appreciate all the help so far. Hoping I can get this working one way or another.
In reply to: adding content to the 1.2 default theme homepageFollowed the above to the letter. That makes /blog/ work of course but the page does not use the assigned custom template (blog.php). It uses index.php or home.php.
In reply to: [1.2] Child Theme Best PracticesI believe the only file required for a child is style.css. If it’s literally just one line of CSS… I’d probably put it in that file. So for instance:
/*
Theme Name: My Child Theme
Template: bp-default
Tags: buddypress
*/
/* Parent styles */
@import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/adminbar.css );
@import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/default.css );
/* Custom styles */
body {background: #cf0;}In reply to: adding content to the 1.2 default theme homepage@Andy: In previous trunk versions I was able to use both a home.php template (/) and an index.php template (/blog/) but now I get a 404 when I go to /blog/.
Explanation: My theme is set up so home.php uses a custom query to show all posts tagged with the most recently added tag in a custom taxonomy (i.e. taxonomy “issues”, tag “Winter 2010 Issue”) while index.php is a normal WordPress homepage loop returning a paginated result set of all posts by date. This doesn’t work anymore since /blog/ (index.php) returns a 404.
In reply to: adding content to the 1.2 default theme homepageActually… I take that back. My solution above does not work because the posts will not be paginated. I also tried this within my “Archives” custom template:
<?php query_posts('posts_per_page=5'); ?>
<?php if ( have_posts() ) : ?>
<?php next_posts_link() ?>
<?php previous_posts_link() ?>
<?php while ( have_posts() ) : the_post(); ?>
<!-- Posts Loop Here -->
<?php endwhile; ?>
<?php endif; ?>Same problem. Posts don’t paginate. Maybe because they are on a regular page instead of the homepage. This just worked before. I could go to / (home.php) and /blog/ (index.php). Argh.
In reply to: adding content to the 1.2 default theme homepage@MrMaz: BuddyPress does use home.php if it exists in your child theme. It just can’t seem to use BOTH index.php (for /blog/) and home.php (for /). It used to be able to use both.
@Mike: Thanks. All that does however is create a link to /blog/. What I needed was for /blog/ to use index.php.
In the meantime I’ve actually solved this quite simply. Forget all the homepage settings stuff. All I did was create a page called “Blog” and assigned a custom template to that page. In that template, instead of using the normal index.php loop… i.e.:
<?php if ( have_posts() ) : while ( have_posts() ) : the_post(); ?>which would return posts based on the slug (so it only returns the page that you’re on if you’re on a regular “Page”)… I used this (to return all posts in the DB):
<?php $postslist = get_posts('order=DESC');
foreach ($postslist as $post) :
setup_postdata($post); ?>
<!-- Posts Loop Here -->
<?php endforeach; ?>In reply to: adding content to the 1.2 default theme homepage@Everyone: Thank you so much for the replies but I’m not sure the issue is being understood. The issue is the template hierarchy not working as it should. Without changing anything in your reading settings home.php should be used for the homepage and index.php should be used for the /blog/ slug. That no longer works.
@Mike: I was trying to change the slug since /blog/ no longer works. It worked before. / used home.php and /blog/ used index.php and both had functioning loops that returned posts.
@MrMaz: That works to change the homepage but the template hierarchy seems broken (see above). I can set up the homepage to manually use a page with home.php assigned as it’s template and then I can actually link to /blog/ and it WILL use index.php (yay)… but the only posts the loop returns i.e… if ( have_posts() ) : while ( have_posts() ) : the_post(); is the page you’re on since (I’m guessing) /blog/ is not longer considered a home page.
Perhaps I need to have TWO custom queries? That may be the solution. Use my custom query for the homepage (however that is set and using either home.php or index.php… all irrelevant)… and then a custom template assigned to whatever page I want (maybe a page called Archives) that uses a custom query to return all posts from the database (i.e. so the loop results won’t be based on the slug… but on your custom query). Seems like a few hoops to go though. Worked fine before simply by using the WordPress template heirarchy and / and /blog/. As long as I can get it working though… it’s all good.
@foralien: It’s a root install.
In reply to: adding content to the 1.2 default theme homepageYa that doesn’t work. I get a “bloggyblog” page of course… but it’s just a page using single.php. And if I assign index.php to it as a custom template the loop doesn’t work. Which I don’t quite understand. It’s the standard WordPress loop.
In reply to: adding content to the 1.2 default theme homepageYah… SSH command line stuff is a dream. LOL. Especially for someone who is a designer first and a coder second :o)
So you mean create a WordPress “Page” called blog (and make sure it’s slug is ‘blog’)? I had tried using my index.php file as a template that I assigned to a page… but the loop didn’t work.
It is weird tho’. In pervious versions of BuddyPress… you could go to /blog/
In reply to: adding content to the 1.2 default theme homepageI just tried changing BP_HOME_BLOG_SLUG to something other than the default (duh) and not only does
mydomain.com/bloggyblog/not work, but when I view a post the url is stillmydomain.com/blog/2010/02/04/hello-world/as opposed tomydomain.com/bloggyblog/2010/02/04/hello-world/However, when I did a test and changed a different slug, that worked. I was able to change “activity” to “stream” for instance. Perhaps it’s a bug?In reply to: adding content to the 1.2 default theme homepageI tried adding
define( "BP_HOME_BLOG_SLUG", 'blog' );to my wp-config file and when I visit /blog/ in my browser I still get a “Page Not Found” and the index.php template is not being used. I’m at a loss. I have my reading settings set to “Your latest posts”.Up until the most recent trunk, the homepage of my site used home.php (with my custom query) and /blog/ used index.php (with the standard loop).
