Hi Ioannis
Just a little update. We have gone back to the drawing board and we are discussing the best way to implement this. As far as I understand, the main problems are:
1. The wpv-post-body shortcode without attributes behaves differently depending whether it is used on a normal View (it renders the Template assigned to the current post, if any, or the actual post content) or a WordPress Archve (it renders the Templateassigned to that archive loop but in the first post, if any, or the actual post content). This should be normalized
2. There is no reliable way to make the wpv-post-body shortcode render the particular Template assigned to the current post. The method used on normal Views (omitting the view_template attribute) does not work on WordPress Archives.
We are currently discussing whether we should include an option view_template="$parent" or whether it's better that the wpv-post-body shortcode without attributes always tries to display the particular Template assigned to the current post. This is not so trivial, since it would overwrite the Template assigned to archive loops on WordPress Archives, but in case you want to use that Template to all your archive loop inside a WordPress Archive, you can always set the view_template attribute to use it.
So it's still an open issue. Sorry for the inconvenience this might be causing you, and we would love to hear your feedback on what you would expect on each case. We understand that by now there is some inconsistency and unreliable behavior happening here and we would like to get this right.
Regards,
Juan de Paco