Well he did not request the price, so it’s something unfair if you ask me.
I know what it falls back on, but that makes the whole cpt into plugin useless. I really think custom post types should be kept inside the theme and not in a plugin. I think the concept is a waste of time if tgere is no way to display the taxonomy properly using a plugin.
One thing that i wonder is what can you do is with displaying custom post types and make tge display stay from a theme to another. So… you can include shortcodes into the plugin, you can also include a page template, but what can you do with the taxonomy page? The whole purpose is to make content reusable outside the theme it originated from, but how do you display a tax that the theme does not have a template coded for, excluding the two options described above.
Just a quick heads up. On localhost, with windows and wamp, i wanted to check it out, but it’s full of errors and does not work.
I think custom post type is good to keep in the theme otherwise it will take more time for buyers to import demo content. For example for portfolio – buyer need to install portfolio plugin and import demo content for portfolio posts and same for other post types like testimonials, team members, sliders, FAQs etc. – this is time consuming for buyers. We (all authors) have different (or unique) design for all post types in each theme and for this we have to make each post types plugin for each theme – this is time consuming for authors.
Totally agreed. Post types should be kept inside.
@carlhancock – well explained.
Thanks guys for your feedback on my not on topic questions.
@kaptinlin – i have no idea if your English skills are not good enough, and was not intended, but what you said there is offensive. So everybody who talked about the changes here has no relevance. It’s time that YOU came and made everything right. This sounds really rude, and i really feed offended.
So nothing easy or that you have done before. If you use the post types, how do they order the slides?