gadgeteffect

Ok, maybe you can help me some more. I am trying to use

<?php query_posts('pagename=example'); ?>

That is to pull the page content that I mentioned. I didn’t know what all pages were called posts too in PHP. So that first loop I can pull, but I don’t know how to end the loop and start the second loop without either going in to infinite loops.

My code is now this

<?php
/*
Template Name: example
*/
?>

<?php get_header(); ?>

	<div id="content">

               <?php include('picturearea.php') ?>

               <?php query_posts('pagename=example'); ?>

             <h1><?php the_title(); ?></h1>

             <div id="entry">

             <?php the_content(); ?>

             </div>

             <?php query_posts("category_name=example"); ?>

             <?php while (have_posts()) : the_post(); ?>

               	<h1><?php the_title(); ?></h1>

				<div id="entry">

					<?php the_content(); ?>

                </div>

                	<?php endwhile; ?>

						<div id="navigation">
			<div id="alignleft"><?php next_posts_link('&laquo; Previous Entries') ?></div>
			<div id="alignright"><?php previous_posts_link('Next Entries &raquo;') ?></div>
				</div>

  </div> <!-- content -->

		<h2 class="center">Not Found</h2>
		<p class="center">Sorry, but you are looking for something that isn't here.</p>

<?php get_footer(); ?>

Think you could help me with starting and stopping each loop successfully?

Could you at least tell me what the loop is for posting to a new page through the page creator?

I figured it out!

<?php query_posts(“category_name=janky”); ?>
<?php while (have_posts()) : the_post(); ?>

All I had to do was that!

Woops, I was wrong! I need to put the file in the root wordpress folder for it to actually find it. When it does find it though, I start running in to a slew of php errors because the page isn’t in the original theme folder. How can I keep it in the theme folder by doing “/about.php”>About” instead of something like this “/wp-content/themes/exampletheme/about.php”>About“? That would look tacky in the URL.