Types 1.2.1 with Bug Fixes

   Amir

Announcements

March 22, 2013
21

A quick update before you’re off for the weekend. We’ve updated Types to 1.2.1, fixing a number of bugs that were recently caused.

Here is the bugfix list from the changelog:

  • Fixed compatibility with ACF, Events Calendar and a number of other plugins due to removed actions
  • Fixed a problem with WooCommerce Extensions, due to too late initialization
  • Fixed translations
  • Fixed a problem with types_child_posts function on updates
  • Fixed a problem with Types API for field render
  • Fixed a problem with conditional fields and wpv_condition
  • Fixed a bug with repeating fields in translated content
  • Fixed a problem with many-to-many relationship
  • Fixed a bug with fields inserted into the wrong WYSIWYG field

This update should cover everything for Types 1.2 and we’re moving forward with new features.

You should see this update in your WordPress admin. To download manually, get Types from your toolset.com account.

The next Types release, in about 2 weeks, will include support for usermeta field. This means that you’ll be able to add fields to user profiles. I’ll write a lot more about it when it’s ready.

Again, thank you for reporting those issues and working with us to resolve them.

Have a great weekend!

 

Comments 21 Responses

  1. “The next Types release, in about 2 weeks, will include support for usermeta field.”
    Oh, dear. My dream is coming true! 😀

    I hope this also means CRED will automatically accommodate this feature as well? Possible scenarios are defining usermets fields with Types, then using CRED to register users, edit profiles etc.

    Right?

  2. Thank you for the update ! Great job, as usual.
    Any release date for Views ? (when it will be done, I suppose…)
    Chris

  4. Adding user data fields to Toolset is huge. Make it such a more valuable plugin. Can’t wait for it.

    Here’s a question, will we be able to create a parent/child-like link between posts and users? That would open up so many possibilities; assigning a work order post to someone or sending a private message. Any hope of that?

    Keep of the amazing work. Best WP plugin by far.

    • Are you looking for more than making users the authors of posts? This is how WordPress normally associates posts with users. If you need more than this, can you describe for what and how you would envision this working?

      • Amir

        It might be worth looking at my current support request:
        https://toolset.com/forums/topic/cred-create-and-insert-parent-member-id-shortcode/

        If it was possible to make a parent child link between a post and a user, it would avoid me having to introduce a work-a-round whereby I am creating a “member” post to achieve this. I have a 1 to 1 relationship between member and user (plus dumping a few extra fields in the member record.

        It would make things so much simpler to define the user as a parent instead of member (which I am struggling with!)

        Tony

        • Yes, we’re planning to add simple post_id and user_id fields to Types. I’m not 100% sure to which Types version it will go, but we’ll get there soon.

    • I can think of 2 specific use cases that would be helpful for sites I’ve created.

      1) I create a ‘work-ticket’ custom post (and am the post author), but then I can link it to another user to “assign” that work order to him.
      2) Similarly, I create a private message custom post and link it to another user.

      Then I can create a view that filters by posts ‘assigned’ to user logged in so they would get their private message or work ticket.

      Ultimately, I want to be able to create a post and have it go to a specific person only. If there is a better way to accomplish this, please let me know.

  5. I’m excited – I need this now!!! lol!
    Can you confirm if this would also work with CRED – that way we could use CRED to register users and let them edit their profiles?
    If so this would be fantastic!

    thanks!

    • It will take us about 2-3 weeks, after Types 1.3 release, to also include User fields in CRED. We know that this is in high demand, but we first have to complete everything in Types. Then, we add similar support to CRED.

      The typical application for this is user registration forms that include different user fields, like images, preferences, etc.

      • Thanks Amir! At least we know its coming and can plan for it in our projects – Keep up the GREAT work!

  6. well there is still the nested shortcode problem….
    doesnt work with the free verison of types.
    it only works if you have views and cred with it.

  7. Can you give us any update on the next release of Types with user meta fields? I am eagerly looking forward to that, and two weeks has come and gone. Any news would be appreciated.

    • Types 1.3, with usermeta fields support will be ready in about a week. Usermeta support is not the only thing going into this release!

      • That’s great. I really appreciate the work you all put into adding more features into ToolSet. Best plugin I have bought by far. To mirror Brent, will View be supporting user data as well? (Fingers crossed).

        • Yes. Since Views displays all fields from Types plugin, it will include support for usermeta fields as soon as Types 1.3 is out. We’re almost there.

      • Any updates for us on the release date for Types 1.3? I don’t mean to be a pest and definitely want it done right instead of fast, but I am eagerly waiting this new release.

        • Sure thing. It’s always fun to brag about what we have nearly ready 🙂

          Types 1.3 is going into QA on Monday. It’s all ready with usermeta support, CSS customization for custom fields, a bunch of little fixes and improvements. We should have a major release for Types, Views, CRED and CRED Commerce – all next week.