AHHH... Simple Fix. (I hope)
Just add the following code to your wp-config.php file
define( 'PODS_SHORTCODE_ALLOW_SUB_SHORTCODES', true );
And everything "should" work out okay.
A shortcode within a Pods template is technically a "nested shortcode" and it won't work by default. This is why we need to specifically tell the WordPress site that we are enabling nested shortcodes so the Pods template understands how to parse the difference between Pods Shortcodes & Magic Tags from regular WordPress shortcodes... and such.
Side note: If you are using a single shortcode to show Pods on the frontend and you don't want to enable the full nested shortcodes with the above line of code in your wp-config.php file, you can also convert your Pods shortcode to something like this:
In the first example, this would be a Pods shortcode being used on a regular WordPress page:
[pods name="book_pod" template="book_template" limit="5"]
If we want to convert this one to allow for THIS instance of the Pod display (because the book_template has nested shortcodes), we can modify that Pods shortcode to look like this:
[pods name="book_pod" template="book_template" limit="5" shortcodes="1"]
But for the most part, it will just be easier adding the full wp-config.php modification.
.
