Hey Kanishk, thanks for your suggestion.
I added it to the roadmap (low priority) and will post an update on this discussion as soon as I have more info about it 🙂
Hi Kanishk,
Just want to update you on that. I wrote to wpthemedetector.com immediately after my last comment to find out more about how they sniff information but no reply from them.
I have noticed though that if I try to access the style.css on on graphicflip that the Beans header informations are removed. That would not be done on Beans side so I suspect that you have the Cloudflare minify CSS option enabled. I suggest you try to disable it and let Beans minify your CSS (won't minify style.css since it is only use to declare the theme) it and try to run the detector again.
Let me know,
I have turned off Cloudflare minify CSS option now. wpthemedetector was still not able to identify the theme after that. Will check again after some time in case the cache was not yet refreshed.
Apologies for jumping on this, but I noticed something strange. I've also been having issues with getting my child theme to identify itself to strangers 😛 But it's gotten a little weird.
I used the Chrome extension WPSniffer while browsing this forum, and it did show tm-beans correctly.
But when I clicked on tm-beans it did not end up at getbeans.io. Instead ti threw me toward some themeforest template from 2014?