datdesignguy

Thanks for clearing that up.

Where did you put the function definition for echo_page_description_mp()? In functions.php?

and you’re calling the function at the top of the archive-events.php template with a hard-coded $page_id?

Hi there,

It looks like you’re going to need to add some definitions to your theme’s stylesheet.

The markup for your gallery uses the DL and DT tags. For this to work, you’re going to need to add a rule like:

dl.gallery-item {
    width: auto;
    display: block;
    float: left;
    margin-right: 1.5em;
}

this should allow you to have 3 images per line with approx 21px right margin.

Try adding the above css to your theme and see what happens ??

I believe we’ll need some more information about how you’ve set this up before anyone can help you.

You’ve got an archive template for your custom post-type. Would that be an archive-{custom-post-type}.php file that is picked up by the WordPress Template hierarchy, or is it a Page template that you’ve created? A

Please let us know so we can help you ??

ahhh, yes, I actually had this problem just yesterday when working on a custom home page template. NEVER forget the loops! gj Jarret

I figured out what the “problem” was. Me. LOL.

Guys, when you’re attempting to override the default arguments for wp_nav_menu… make sure you’ve assigned a menu to the theme location before you try and test out your code!

*facepalm*

Jarret, thanks for convincing me to take another long, hard look at the codex. If it weren’t for your suggestion, I probably would’ve sat stumped for another couple hours. No kidding. GAH! lol

No dice ?? Still doesn’t have any effect.

You will probably want to move the call to the_content(); so that it is situated between get_header(); and get_sidebar();

Hi styletheology,

The problem is with your template code itself. You are forgetting to call the_content(). If you add a call to the_content(); into your template you should see the content of your page. Simple fix ??

Hope this helps,

-Greg J

Where are you adding this code? If it were successfully being added to any of the stylesheets associated with your theme, I’d be able to see it in Google Chrome’s Element Inspector, but I cannot.

Nah, don’t do that.

You want to add the code: background: transparent;
to the end of the second one, before the closing bracket: }

does that make sense?

Try doing that and see if it works, or you can completely replace the two that you showed above with this single statement:

#wrapper {
margin:auto;
padding: 0 20px;
width: 940px;
background: transparent;
}

If your style.css doesn’t container #wrapper, then you can just add the rule I described above.

If you copied the original stylesheet from the parent theme it will be on line #147.

Hope this helps,

-greg

You’ll want to set:

#wrapper { background: transparent; }

in your theme’s style.css file (hope you’re using a child theme!)

Could you post a link to the site you’re working on as an example. By default the twenty-ten theme does not have a background-color set on it.

When you say transparent, do you mean that you want the main content column to have a background color, but you would prefer the sidebar show-through to the page background?

I hope that made sense.

-Greg

brisus,

Do you have a list of the files you have modified in the core theme?

Provided that you know what files you have modified, you can make a list, and copy those files into a child-theme folder (make sure to include the style.css file along with these.

If you do not have a list of the files you have modified somewhere on hand, an alternative is finding an unmodified copy of your theme’s current version on your hard-drive, and looking at the last modified timestamp for all of the files, and comparing that with your local copy’s last modified date… Make a list of the files that do not have matching timestamps, and then copy those to a child-theme directory along with your style.css file from the parent theme. ( This is how I did it in a past project after learning what a child-theme was for the first time. )

Next open up the child-theme’s style.css and add the template tag that points to your parent theme as directed on the Codex Child Themes page.

Upload the child-theme and activate.

Make a backup copy of your current parent theme!

Finally, upgrade the theme.

I would definitely advise you do this on a development server or test site first, that way if you miss a file, the design goofs up, or you get the WSOD, you’re not affecting the client’s live website.

I hope this helps!

-greg

Can you explain what’s happening when you attempt to update?

Do you get a specific error? If so, it will be helpful for you to paste that information here ??