Hello @mattcaldwell,
Thanks for writing in and I’m sorry you’ve been having this issue. I think there was some confusion on this initially, as the shortcode does indeed allow for portfolio categories, as well as multiple category configurations, there are just a few specifications for how it needs to be setup. First we’ll need to review our live shortcode demo pages:
http://demo.theme.co/integrity-1/shortcodes/recent-posts/
If you scroll all the way to the bottom of that page, you’ll find a list of accepted parameters for the shortcodes and a description of how to use each one of them. For our purposes, the two you’ll want to focus on are the type and category parameters. Taken directly from the page, here is how those two parameters are described:
-
type – “post” or “portfolio.”
-
category – to filter your posts by category, input the slug of your desired category; also accepts multiple category slugs separated by a comma to display posts in any of those categories, or multiple category slugs separated by a plus sign to display posts that have all of those categories.
Since the default for type is “post,” for your situation where you’re wanting to pull through a portfolio category to the frontend, you’ll want to enter “portfoliio” to ensure that it’s pulling from the correct place. Next, we’ll need to enter the category slug into the category parameter. This is one area that can trip people up sometimes as the slug is different than the category name. By default, a slug is typically an all lowercase version of your category name with dashes put in place of spaces. So if your category is “Our Works,” the slug that is generated by WordPress will likely be “our-works.” It is this “our-works” value that you would want to enter into the category parameter.
Also, as you saw from the article excerpt, we can use multiple slugs separated by a comma or a plus sign to achieve different results and filter things as you want.
Again, I want to apologize for any confusion there might have been initially as the shortcode is certainly not broken and is functioning as it always has. The core functionality of this shortcode has remained consistent from the beginning (by design for backwards compatibility), and it is simply built off of core WordPress query features, so everything should still be functioning as expected. In my personal tests, all methods of using the shortcode still function as they should.
If you do not feel that your question was adequately addressed with my response, or you have any further questions, please do not hesitate to let me know. Hopefully this will help to point you in the right direction moving forward.