Jon Bourne

The changes you’ll need to make should be in wp-includes/template-functions-post.php. Look for function get_the_content.

It has everything to do with what you want. You are interested in the <!--more--> tag. This is what breaks the post so that only an excerpt is shown on the home page.

Weird. Everything looks correct. I even looked up the function in comment-functions.php. I copied your code directly and it worked perfectly for me. I was using my own custom theme, though, and not Qwilm. Try it on the default theme and see if it works.

Please list your domain and subdomain.

It isn’t clear to me what you are trying to do. Create a file? Well, yes, of course that’s possible.

Try explaining what you would like the end result to be.

Create a file called functions.php in your template directory. WordPress will load any functions you define there, and you can then use them anywhere in your template.

Read this whole page

The methods I described in my two posts above are contingent on installing the two blogs on the same database. What you suggest becomes very complicated very quickly if they are not installed using the same database.

I think this can be marked as resolved.

If all you’re wanting to do is have the same users on all your blogs, install your WP installations on the same DB as I explained above. Then, in wp-settings.php, search for $wpdb->users and $wpdb->usermeta. Replace the $table_prefix variable with the table prefix of the users table prefix of the blog with your users. It will probably be wp_ unless you changed it in your initial installation.

I don’t bother with anything less than IE 6.

Also, try the FF IE tab extension for testing IE’s rendering within FF. Very handy.

You could always design your own, or pay to have one designed for you. And you can get all the help you need right here on this forum.

If you post your e-mail address, I would be happy to contact you privately and discuss developing the theme for you.

Yeah, that’s precisely what the DB table prefix is for.

During the DB configuration part of installation, specify the DB connection information for your current WP installation’s database. Then, change the field labeled table prefix or database prefix (can’t remember exactly what it’s called) to something other than the default “wp_” which is probably already being used by your existing WordPress install.

This will install the new WP installation’s tables into the same DB with a different prefix before the table name, ie. newprefix_posts instead of wp_posts.

I designed the Web site for the Fairbanks Daily News-Miner using WordPress. I ran into the same problem at the beginning, but the fix was pretty easy.

I created a PHP script that reads a directory of XML files and loads the filenames into an array. Then, I check for certain cases to sort the array.

You can set up file naming conventions, as I have done, to allow for certain stories to be given precedence over others. For instance, our top four stories are slugged (labeled) TONE, TTWO, TTHREE, and TFOUR. These slugs are then converted to the filenames of the files that are exported from our internal news management system.

Then, I loop over the array of filenames and process each file individually and insert it into the WP database using the $wpdb class, sleep()ing for one second between each post so that the reverse-chronological default sorting of WordPress will take effect correctly.

Hope this helps,

[sig moderated]

I’ve never used XML-RPC. Honestly, I don’t really even know what it is.

I just pulled the posts out directly from the database with customized SQL queries–without using the WP API.