yes this is because of the following reasons
in wp-favorite-posts.php
function wpfp_list_favorite_posts() is calling the template file in this manner before $content is being checked for shortcodes
if (@file_exists(TEMPLATEPATH.'/wpfp-page-template.php')):
include(TEMPLATEPATH.'/wpfp-page-template.php');
else:
include("wpfp-page-template.php");
endif;
this means that before the $content is parsed, whatever is happening in the template file is causing the favorite links to be generated ahead of the content rendering thereby circumventing the ability to place the favorites inline as a swap out for the shortcodes
looking at the template file itself, we can see it’s set up to echo it’s contents as opposed to generate a return string
<?php
echo "<div class='wpfp-span'>";
... code truncated for posting here ...
echo "</div>";
wpfp_cookie_warning();
?>
I’m sure the author could change this – I’m currently hacking away at the code to try and strip the template into rendering and layout sections so that I can include the rendering inline as opposed to ahead of all content but other things are taking my time
for pointers something along the lines of
<?php
$wpfp_echoStr = '';
$wpfp_echoStr .='<div class="wpfp-span">';
... code truncated for posting here ...
$wpfp_echoStr .= "</div>";
//if(wpfp_cookie_warning())...
//generate your warning strings and tag on to output//
//do the same for remove links etc//
$wpfp_echoStr .= '<div class="wpfp-userinteration">';
$wpfp_echoStr .= $wpfp_userinteration;
$wpfp_echoStr .= "</div>";
?>
understand that you will need to work out when and how to call $wpfp_echoStr for inclusion – I’ll report back if I get around to it
great plugin btw!