Andy Giesler

Thanks so much for the quick reply. Great call. I found a search filter in pre_get_posts that listed everything but the pages. I’m using a child theme, so I just unhooked their function and hooked my own that includes pages, and the results appear.

…and now I see why they omitted pages in the first place, since the ugly page builder shortcodes appear in the search results snippet. This must be a problem for any site with a page builder. We’ll figure out what to do from here.

Thanks again for the help.

Good point, thanks. I should have thought for a minute before just appending my code to nims’ code. ??

If your CSS hides the meta information on the home page, then to hide the meta information on a page that shows an individual post you should just need to add the CSS that I listed above.

Your final CSS would be:

.entry-author-link { display: none; }
.entry-permalink { display: none; }
.entry-date { display: none; }
.entry-meta { display: none; }

You might want to try your questions at the official PinBoard theme forum at OneDesigns. It appears to be a fairly active forum.

One simple way to do this (without having to create a child theme) is to hide these values by adding custom CSS. You can add the CSS at Appearance > Theme Options > Layout > Custom CSS.

The date/author meta information for individual posts has a class of “entry-meta”, so this CSS will hide it:

.entry-meta { display: none; }

As I’m using pinboard, the meta information doesn’t appear on the home page, so I can’t give you specific CSS for that. But if you view the page source you should find a class being applied to the meta information on the home page. You could try suppressing it in a similar way.

.[class name goes here] { display: none; }

This could have unintended consequences of hiding information on other pages, so as with any custom CSS be sure to test it thoroughly.

Best of luck.

Andy

I’m liking this theme a lot so far, but I do wish there were more documentation. Maybe this will help:

1. My solution was to upload a header image that’s 750 x 48 pixels. That’s the size the header wants it to be. Unfortunately, the size is hard-coded in the HTML. Here’s how the header image HTML looks:

<img width="750" height="48" alt="[alt text goes here]" src="[url goes here]">

The fact that JLDV’s image widened to 1500 instead of the 750 I’m seeing might be related to the Retina Header Image option being set (Appearance > Theme Settings). Retina images are normally double the size of standard images in both dimensions.

2. If I understand correctly, you just want to delete the contents of the Welcome page. To do that, from the Admin menu go to Pages > Edit page, then remove the text of the page and click Publish.

3. The theme’s page on OneDesign.com briefly discusses this under “Adding posts to the slider”. You need to mark each post as Sticky by editing the post, editing the Visibility section on the right, and checking “Stick this post to the front page.” I’m not using the slider myself, but I played with it in testing and if I remember correctly it only shows up for some of the home page templates. You can change the home page template via Edit page > Page attributes > Template.

Best of luck.

Andy

I had the same problem and eventually worked out that the cache folder has to be in the site’s root directory.

On one site this meant creating it in the root of the WordPress directory:

[webroot]/[wordpress]/cache

and on another site it meant creating it in the site’s root:

[webroot]/cache

It seems to depend on whether WordPress is configured to take over the entire site. Even so, I didn’t find it an intuitive place for the cache folder.

Before figuring that out, I saw the wp-content/cache recommendation in several places, so assumed I was doing something else wrong. Maybe it’s a difference under WordPress 3? Creating wp-content/cache, even with 777 permissions, made no difference.

In any case, elsewhere I’m submitting requests to include the “mkdir /cache” step in the installation instructions.

Apparently it took a little longer than 30 minutes for my feed(s) to refresh. It’s working now. So never mind. ??

Thanks for creating this plugin.