Who considers that can do a better job, do a fork on git. Good job with the fork yourself SyamilMJ!
Actually, as Mike McAllister pointed out on one of his articles on his blog, there isn’t even a need for a CPT for portfolio items. Everything you need is already there. No need to reinvent the wheel.
The way that I saw people are using it around here is using the plugin as the main benchmarking tool to determine whether a theme is broken/not-broken without even considering the context of the errors generated by the plugin…theme check plugin is dumb
So, what you’re really saying is that people are dumb, not the plugin, correct?
Okay. So to just get this straight. The plugin is dumb because people are using it incorrectly. Is this a more correct assessment of your earlier reply?
Based on everything you said earlier, it sounds like your problems with the plugin are not based on the plugin itself but how it’s being used by people (something that the plugin has no control over).
To be honest it’s a bug of Theme Check plugin.
I don’t have a time and enthusiasm for it.
You have the time to post twice here in this thread about there being a bug but not the time to actually say what the bug is? Tell me the bug in your next reply; I’ll report it myself.
Note that the Theme Check plugin was built specifically for WordPress.org themes and base64 encoded source is not allowed there.
Saying it’s dumb because people rely on it is way over the top. That’s simply stating that the users of the theme check plugin are dumb because they use that as the be-all-end-all tool for determining whether the theme is good. It is a fantastic tool for giving a quick once over on a theme to determine if there are obvious problems, but no automated tool will ever do it all for you. Period. End of story.
If people are using Theme Check as the only check then they are the idiots. Not the plugin.