Types on its own is fine for what it does, except that it really doesn't have any advantages over any other similar utilities and leaves some interface elegance to be desired. I don't like its interface or the fields it creates on post edit screens, and the choices for those fields is limited. The repeater fields are particularly horrendous. Props for including a repeater field in the free version, though.
However, you will be enticed within the plugin to buy their Toolset suite, promising sophisticated site-building without code. I have used Types and other Toolset components on several sites. Where I have used Types alone, I wish I had used ACF. On the sites where I've used other Toolset components, I wish I hadn't at all. I have wasted a lot of time and energy because I used Toolset, going back to fix sites that broke down the road or too close to launch/soon after launch when bewildering behavior or bugs were discovered.
Views does require coding for lots of features, such as conditionals, and the shortcodes in which you have to do that coding are really messy.
Each component has its little bugs that get introduced with updates and later resolved (sometimes), but some of these are huge and have cost me lots of wasted time developing workarounds, redoing configurations that were lost because of a bug or unexpected behavior, or rebuilding in a way to remove the plugin. For example: the Modules plugin will overwrite components during import even when you specifically instruct it not to in the import options.
Updates for components, Types included, have broken my sites because of sloppy coding (on their part). For example: a Views update injected new elements onto the page, even though those elements were only relevant to a feature I had specifically disabled. I had to add a filter to remove this code after discovering the bug.
The Layouts plugin just does not behave in a usable manner regarding assignment to content. Setting a layout as a "default" doesn't work for existing content unless you specifically tell it to update existing, in which case it changes ALL posts of that type, even if they were assigned to other Layouts, and when you are modifying some default setting for OTHER post types, it will overwrite all your existing settings for the first type. It's a mess. I've had to reassign every Page to its custom Layout because I wanted another Layout to be the new default, or because I made a Layout the default for a new post type and it overwrote all my Page settings.
Access doesn't do what I thought it did based on its description, and I ended up using the free Members plugin and a little code to do exactly what I wanted with regards to limiting front-end access to posts and displaying content conditionally.
I could go on. I have 16 support requests in their paid support forum. A few of them were resolved satisfactorily. I have used Types and Views on a few sites, and the Toolset suite to build one full site (with 3 multisite sub-sites). I will not be using them on any projects in the future.
Tried to install types, because Sydney Theme recommends it. Activating the plugin leads to this error:
Fatal error: 'break' not in the 'loop' or 'switch' context inin the backend!
Types has now become an essential part of every wordpress site I build.
Hated Visual Composer. Loved Types.
I just found this plugin today. It is an incredible work that has saved me a ton of time for my client. The user interface is great for developers or a semi-savvy client. I have had no issues so far accessing the data from within my own custom plugins or themes either. Great work guys!
I have installed this plugin because Sydney theme wanted it. Having activated it, I discovered that my site turned into one white page.
Perhaps it was partly my fault, server might've been misconfigured or something else but I didn't have a clue what to do. All my attempts to fix it have failed completely. So I just deleted the folder with plugin and regained my site back. It's a pity because Sydney seemed to be quite a decent theme.
I am using Types on a few sites and it is great for creating custom post types and taxonomies. You can add custom fields in groups easily and make them appear conditionally in a number of useful ways. It really comes into its own when combined with their other, paid for plugins: Views, Layouts and CRED.
Toolset has improved my development speed and capability. It has enabled me to do what I could not have done without it. When I have pushed the limits of what I could do with Toolset, their support staff has been exceptional in helping me overcome my challenges. A great tool well supported.
Great to add taxonomies and custom post types without coding. You can create your own views or use the extras they offer. Easy to setup and easy to use.
Saves a lot of coding time. User Friendly. Fast and loaded with features. THanks
Types and its related suite of plugins provide a very comprehensive and robust set of tools that allows a user to "avoid" programming.
However, for our project, we can across a fatal deal-breaker: When custom fields are created by Types, the names start with a prefix of "wpcf-" and then the remainder of the field name uses hyphens instead of underscores. Nor, does Types allow us to edit the names of the custom fields once they are created.
For example, one of our custom field names was "wpcf-shortcode-name" instead of "wpcf_shortcode_name".
Why does this matter? If you stay completely within the Types environment and avoid all programming, it does not - Then, 5 stars.
However, for our website we have a 500+ line PHP function that we use. And, PHP does not allow hyphens to be used in a variable name - such as the name of a custom field. Thus, I cannot programatically access any of the custom fields created by Types.
I suppose that I could use some type of CamelCase, but then I still have the "wpcf-" prefix to deal with. Our research indicates that there is a "hack" that allows the end-user to modify or even eliminate the prefix. But, I shouldn't need to hack it in the first place.
I consider this to be a serious oversight by the Types developers. I hope they will correct this issue in the future. Until then, 1 star.
You must log in to submit a review. You can also log in or register using the form near the top of this page.