Add another linkblog widget into whatever container you want it in (and on whatever blog you want it on), depending on your version of course.

You mean inlcude another _linkblog.php? I am running 0.9

This is off the top of my head as I haven't used a 0.9.x version for a loooooooooooooooong time ( you *really* need to upgrade huh? :| ... mind you, I'm pretty sure that we've been telling you that for ages as well :| )

If you crack open linkblog.php there should be some var like $linkblog = ##;

If there is then you can have two linkblogs with something like :

<?php
$linkblog = ##; // id of fist linkblog
include dirname(__FILE__).'/linkblog.php';

......

$linkblog = ##; // id of second linkblog
include dirname(__FILE__).'/linkblog.php';
?>

That goes in whatever file is the equivalent of /skins/skin/index.main.php ( if my ancient memory serves me right it's _main.php ).

¥

Thanx! Works great! Is it posible to sort the entries by date and no alphabetically?

Ok, I'll answer it myself:

in _linkblog.php search for this:

// Load the linkblog blog:
	$LinkblogList = & new ItemList( $linkblog, array(), '', '', '', $linkblog_cat, $linkblog_catsel, '', 'ASC', 'category title', '', '', '', '', '', '', '', '', $linkblog_limit, 'posts', $timestamp_min, $timestamp_max );

and replace it with this:

	// Load the linkblog blog:
	$LinkblogList = & new ItemList( $linkblog, array(), '', '', '', $linkblog_cat, $linkblog_catsel, '', 'DESC', 'issue_date', '', '', '', '', '', '', '', '', $linkblog_limit, 'posts', $timestamp_min, $timestamp_max );

MarcDK wrote:

Ok, I'll answer it myself:

Seriously, upgrade ;)

¥

Unless you're asking about upgrading from 0.* there is absolutely no reason to have active threads about obsolete versions.

Sorry friend, but I'm going to lock this and any other threads that talk about actively using 0.* as your blog engine.

By the way, I'm pretty sure in another thread we learned that upgrading to 1.10.* then upgrading to 2.4.2 is the wrong way to go. Something about the upgrader becoming smarter over time so that issues that might befall the upgrade to 1.10.* won't happen if you go straight to the 2.4.2 release.