ghaib

I tried, I’m getting this error:

syntax error, unexpected T_LNUMBER

I think it’s because I also include the comment code <?php comments_popup_link('0', '1 ', '% '); ?> right after the title (in a div).

Any ways of fixing this? (I’m not a php wiz ?? )

Thanks!

@alchymyth I applied your code, it seems to be working.

In essence, what I want is the title (h2) to be included in the same <div> as the content, usually it’s:

<h2>Test title</h2>
<div class="content">The content</div>

What I’d like to achieve is something like this:

<div class="content">
<h2>Test title</h2>
The content</div>

While your code works, what if I want to wrap the title in additional divs, and have it be a link as well?

Well, the theme is coded like any other WP theme.

Thanks, it worked!

Haven’t debug it, don’t really know how to do that.

Running it in half-only mode doesn’t solve anything, it still generates new pages, meaning the plugin is useless.

That’s just disgusting that someone would do that.

#19 is set up correctly, and I tried it on half-on mode, but it still generates a new cached file for every new visitor.

If they reload the page, the cached one seems to be served, but for everyone new, a new cached page is generated — which means the plugin is pretty useless if there’s a sudden spike in traffic (e.g. from Digg).

Does anyone know any good alternative WP cache plugins?

@donncha: I have, and it’s set up correctly )to the correct path), but still appears to generate a dynamic and static page on each reload.

I’m having the exact same problem.

bump

bump

@t31os_

Yep, that’s exactly what I mean. I solved it partially by doing this:

<?php the_content(''); ?>

And then this, in a separate div:

<a href="<?php the_permalink(); ?>">Read more</a>

However, a new problem emerges: the “Read more” button will always be present, linking to the post, whether <!--more--> is specified in the post or not.

@jrav001: Thanks for the tip, it works, however, it always displays the “Read more” button, even if read more isn’t used in the post.

Same problem here