Archive for the ‘ProPhoto Bug Fixes’ Category

BugFix: headlines on post pages

Tuesday, April 8th, 2008

So, I screwed up the css a bit by not pulling out one line of code and putting it in the easy edits on the top of your Stylesheet (style.css). The result is, unless you’ve already hunted it down, when you click on your single post pages, you probably get the default blue instead of your nice branded color, like you can see below.

I’m guessing that Holly, since her blog is called “All Things Pink,” didn’t mean to have big blue headlines on her single post pages. Sorry Holly, and the rest of you. You can see if you have the same problem by clicking on one of your post titles.

Luckily, as usual, the fix is very easy. Just open up “Stylesheet (style.css) from within your “Theme Editor”, and scroll down to line 400. There you will see the missing code on the third line down:

#comments h3 {
margin: 0 0 15px 0;
font-size: 19px;
color: #3333CC;
}

Change the line that says “color: #3333CC;” to the six-digit color of your choosing and save your changes.

My bad, my bad. Carry on.

Bugfix: Biopic only shows on home page

Tuesday, April 1st, 2008

There’s a little bug in the ProPhoto template files that you may want to take a moment to fix. Basically, your bio picture shows up on your blog’s main page, but if you scroll down to the bottom of the page and click “Older Posts”, the bio picture disappears on other pages.

Props to Petra for pointing this out to me. The fix is pretty easy. Just open up your “Theme Editor” (under “Presentation” in WP 2.3 and earlier, or under “Design” in WP 2.5) and click to edit the file called “bio.php.”

Then, look for this line/chunk:

<!-- path to filename of bio pic --> <img src="wp-content/themes/prophoto/images/biopic.jpg" width="215" height="312" id="biopic" />

And change it to:

<!-- path to filename of bio pic --> <img src="<?php bloginfo('template_directory') ?>/images/biopic.jpg" width="215" height="312" id="biopic" />

Save your changes and you should be good to go!

Bugfix: Bold and Italic styles not working

Thursday, March 27th, 2008

Shannon pointed out to me the other day that when you use the bold or italics from within the visual editor, they weren’t showing up as such when viewed in the blog.

To fix it, open up “Design” (”Presentation” if you’re on WP 2.3.3 or earlier) –> “Theme Editor” and open up the “Stylesheet” (style.css). Then, scroll down to the very bottom, and add a new line by pressing return. Then paste in these lines.

strong {
font-weight:700;
}
em {
font-style: italic;
}

Click to update the file, and you should be fine.

Bugfix: picture max-width issue in WP 2.5

Thursday, March 20th, 2008

If you’ve already upgraded to WordPress 2.5, you may have noticed a problem inserting pictures into your posts: WordPress keeps shrinking them, even if you click on the “insert full size” button

Well, after a little digging, I found out why this is happening. WordPress 2.5 has a new bug i mean feature that makes the default max-width of pictures 500px.

Luckily, the fix is pretty easy. All we have to do is edit a ProPhoto template file to communicate to WP 2.5 that we want to have a different max width. To do so. Go to the “Design” tab in your WP Admin area, and click on “Theme Editor.” Then, select the file called “Theme Functions (functions.php)”. Scroll all the way to the bottom and press return/enter to add a new line and paste in this:

<?php $content_width = 900 ?>

NOTE: It is extremely important that you copy ONLY the code shown above, and not any extra spaces after the last “>” character.  If you leave any extra spaces, it will break your blog.  When you paste in this line, go to the very end of the file and press delete until you are positive there are not extra spaces.

Click “Update File” and you’re good to go.

If you’ve got WordPress 2.5 and you’re not having this issue, you probably downloaded ProPhoto after I added this line to the download file, so you’re all set. But, if you’re still using 2.3.3, when you eventually do upgrade to 2.5, you’ll need to perform this fix. Unless, that is, WordPress decides to remove this silly feature in 2.5.1.

If you want to read the WordPress support thread about this, click here.