“good ole 1.2” can be wiped out by a script kiddie with very little effort.
Upgrading is essential. If it wasn’t I wouldn’t say so.
Honest.
Im only using 1.2 as a news poster, 2.0 beta is for my blog, but does anyone have a solution for my problem, ignoring the security faults.
Okay 🙂
With the problem – you know where the mistake is because of what it should look like. But this is the first time we have seen it – could we have a better description of things ?
Im not sure what you mean.. This is the code Im using, if this helps
<table width="332" border="0" background="images/news/newsbg.gif" height="18">
<tr>
<td width="76%" height="14" class="main">"><span class="style1"><span class="style2"><span class="style3">
<?php the_title(); ?>
</span></span></span></td>
<td width="24%" class="main"><?php the_date(); ?> by
<?php the_author() ?> </td>
</tr>
</table>
<span class="main"><?php if ($posts) : foreach ($posts as $post) : start_wp(); ?>
</span>
<div id="content">
<div><div></div>
<div>
<span class="main">
<?php the_content(); ?>
</span></div>
<div>
<span class="main">
<?php wp_link_pages(); ?>
<?php comments_popup_link(__('Comments (0)'), __('Comments (1)'), __('Comments (%)')); ?>
</span></div>
<span class="main">
<!--
<?php trackback_rdf(); ?>
-->
<?php include(ABSPATH . 'wp-comments.php'); ?>
</span></div>
<span class="main">
<?php endforeach; else: ?>
</span>
<p class="main">
<?php _e('Sorry, no posts matched your criteria.'); ?>
<span class="main">
<?php endif; ?>
