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.
Please, guys, give us possibility to turn off russian localization on settings screen!
Russian localization right now wrong. Men, which made this localization, don't understand WordPress terms at all. I was near to broke my head, when try to use your beautiful plugin with this frightful localization!
You must log in to submit a review. You can also log in or register using the form near the top of this page.