Title: CPT-onomies: Using Custom Post Types as Taxonomies Author: wpconcierges Published: January 31, 2012 Last modified: October 15, 2019 --- Search plugins ![](https://s.w.org/plugins/geopattern-icon/cpt-onomies_f2f2f2.svg) # cpt-onomies By [wpconcierges](https://profiles.wordpress.org/wpconcierges/) * [Details](https://wordpress.org/plugins/cpt-onomies/#description) * [Reviews](https://wordpress.org/plugins/cpt-onomies/#reviews) * [Development](https://wordpress.org/plugins/cpt-onomies/#developers) [Support](https://wordpress.org/support/plugin/cpt-onomies/) ## Description This plugin has been closed as of October 29, 2021 and is not available for download. Reason: Security Issue. ## Reviews ![](https://secure.gravatar.com/avatar/cd8effb9b0376b29f9584b3c10445740c65d8b9fd1cc8f48269709c47753dd2a? s=60&d=retro&r=g) ### 󠀁[Doesn’t work](https://wordpress.org/support/topic/doesnt-work-2216/)󠁿 [la_ri_za](https://profiles.wordpress.org/la_ri_za/) August 12, 2019 Stopped working with wp 5.2.2. Cannot loop custom post types by term. Very poor documentation. ![](https://secure.gravatar.com/avatar/d51bc14972d77776918fdc9024929106b31b7e9d3baa814be4205880863bd9ed? s=60&d=retro&r=g) ### 󠀁[great plugin, now broken](https://wordpress.org/support/topic/great-plugin-now-broken/)󠁿 [zota](https://profiles.wordpress.org/zota/) April 1, 2019 4 replies This plugin has been the best way to do what it does for several years, and I rely on it for the structure of a couple of sites. It does not deserve a one-star review for it’s functionality. The problem is that the current version does not function. When freshly installed, the current plugin version cannot be activated due to a fatal error. But when updating an active copy of the plugin, it white screens the front and back end of the site. To get it back, the plugin folder must be renamed or removed from the server. That’s unfortunate, but it happens. Everyone makes mistakes. What matters it how they’re handled. The new maintainers of this plugin broke the last update by leaving out a required file. As someone in the support forums pointed out, it can be easily fixed by simply adding this small file back in. But the maintainers themselves have not responded. And have not updated the plugin with this very minor fix. As of the time I write this, it’s been nearly a week since the put a site-killing update in the repository, and they’ve just… left it there. The thing that’s kind of a last straw is that the new code that broke everything is for monetization. Which is fine. People gotta get paid. But I’d expect a developer to be especially careful about updating parts of the code that get them paid, since they require literal buy-in from users. Maybe run a few tests? Keep an eye on the support forums? Make sure the thing that asks the greatest degree of trust isn’t the thing blowing everything up? No? If this is how they handle the monetization code, it makes me think this the actual functional parts of this plugin don’t have much of a future. So while I still like this plugin (when it works), I have to give it 1 star as a warning. ![](https://secure.gravatar.com/avatar/c9b156485b26ddb50502202047804eab4b2b4881799641288280d846e64d85ab? s=60&d=retro&r=g) ### 󠀁[Used to be great, now best avoided](https://wordpress.org/support/topic/used-to-be-great-now-best-avoided/)󠁿 [Matt Lowe](https://profiles.wordpress.org/squelch/) April 1, 2019 It’s a shame I have to write this review. This plugin was, once upon a time, fantastic. When Rachel Cherry had the time to maintain it, it was solid as a rock and worked like a dream. But she went on to find she had dwindling availability, and then the cracks started to show. Eventually she passed it on to its new owners and nothing has really improved. Now every site I have this plugin installed on is broken because the developers FORGOT TO BUNDLE A REQUIRED FILE, and we’ve been waiting for over 5 days for them to package it. This is entry level stuff. And keeping us waiting for 5 days is just plain lazy. It’s now time to say goodbye to this plugin, I will no longer be using it in any future projects, I will not be supporting it in any existing projects, I will not be recommending it to anyone — in fact I will be strongly recommending they avoid it — and I will be looking to replace it in any internal projects we might have used it in. I now have the fun job of going back through every project to see whether they are negatively affected. I only awarded that second star because only a few years ago this plugin was so good. ![](https://secure.gravatar.com/avatar/3602d361ee8147cb765a2c0e2031340e9b9e3c6d392b9b31e8e1de3736e2b92c? s=60&d=retro&r=g) ### 󠀁[NOT WORKING ON NEW WORDPRESS VERSION](https://wordpress.org/support/topic/not-working-on-new-wordpress-version/)󠁿 [stemua](https://profiles.wordpress.org/stemua/) March 24, 2018 NOT WORKING ON NEW WORDPRESS VERSION ![](https://secure.gravatar.com/avatar/cf69ef6155fa671d325c1ff87511ce86520ddb11768171560f1e08ef077f4d7d? s=60&d=retro&r=g) ### 󠀁[better logic than other CPTs compilers](https://wordpress.org/support/topic/better-logic-than-other-cpts-compilers/)󠁿 [Anonymous User 14293447](https://profiles.wordpress.org/anonymized-14293447/) August 10, 2017 It wasn’t useful in my case because my CPTs are already assigned to their parent CPT, but I understood it is very functional and well supported. I had some layout issues and crashes in my backend, but I guess it’s my theme’s fault. ![](https://secure.gravatar.com/avatar/9b55b3873e09c2c36aab1d99cd479aa898709d9cf4a20276d13cceb1293bf366? s=60&d=retro&r=g) ### 󠀁[Outstanding plugin](https://wordpress.org/support/topic/outstanding-plugin-99/)󠁿 [notanothercliche](https://profiles.wordpress.org/notanothercliche/) July 10, 2017 Incredibly useful plugin for more advanced sites. Thank you!! [ Read all 57 reviews ](https://wordpress.org/support/plugin/cpt-onomies/reviews/) ## Contributors & Developers “CPT-onomies: Using Custom Post Types as Taxonomies” is open source software. The following people have contributed to this plugin. Contributors * [ wpconcierges ](https://profiles.wordpress.org/wpconcierges/) * [ HYPEStudio ](https://profiles.wordpress.org/hypestudio/) * [ Dejan Markovic ](https://profiles.wordpress.org/dejanmarkovic/) * [ Freemius ](https://profiles.wordpress.org/freemius/) * [ nytogroup ](https://profiles.wordpress.org/nytogroup/) [Translate “CPT-onomies: Using Custom Post Types as Taxonomies” into your language.](https://translate.wordpress.org/projects/wp-plugins/cpt-onomies) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/cpt-onomies/), check out the [SVN repository](https://plugins.svn.wordpress.org/cpt-onomies/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/cpt-onomies/) by [RSS](https://plugins.trac.wordpress.org/log/cpt-onomies/?limit=100&mode=stop_on_copy&format=rss). ## Meta * Version **1.4.0** * Last updated **7 years ago** * Active installations **N/A** * WordPress version ** 3.1 or higher ** * Tested up to **5.1.0** * [Advanced View](https://wordpress.org/plugins/cpt-onomies/advanced/)