After recent update of types on site with a many to many relationship, on the the custom post field is behaving strangely.
Relationship: Place - PlaceArticle - Article (3 posts types to make the many to many relationship happen)
I have a Custom Field Group with a checkbox post field ("Promoted on Home page")
This Custom field group is use in both the Place and Article Post types.
Used to work well before Toolset Types 3.0
The issue: If you add a new relationship between a place and article, the Promoted Checkbox turns unselected and you can no longer select it.
I believe this bug came with the upgrade of Types.
I cannot migrate the existing many to many relations yet as there is at this day no ways to automate that.
Yes that is right. Running the migration tool fixes that. But I cannot run it yet as we have many to many relations going on and are not ready to migrate those yet.
I can give you access to a test site with that issue if you want. Very easy to test. Editing a "Place" and you will see that check box post types do not work. I have tried on multiple checkbox and it is the same issue.
I tried to reproduce this on a clean test site with the previous plugin versions and then upgrading to the new ones, but I couldn't.
There may be some detail in your set-up I'm missing, so, yes, let me take a look at your site to see what's involved.
What, specifically, is stopping you from running the migration? Your existing M2M relationship (which is actually two one-2-M relationships) will be migrated to the same, two one-2-M relationships, rather than a full M2M relationship, but should continue to work. If you are actively developing the site and want to update Forms and Views to take advantage of the actual M2M relationships then, yes, I see why. We are working on a script to automate converting the pseudo-M2M relationships into actual M2M relationships.
OK, it is a checkboxes field, not a checkbox field, that's the key distinction.
We have a lot of issues around checkboxes fields, which need a complete re-factoring.
I reproduced this on a clean install and am reporting this particular issue to add it to the list and to keep up the momentum for the required changes.
It is the same issue with both cheboxes field and checkbox field.
In the page example given above there is also a checkbox field and it has the same issue.
I'm just reviewing my escalated queue to check I haven't missed anything, but it looks like I overlooked this, which should have been fixed by a Types update shortly after my last update.
Could you let me know if you still see the problem with the current Types version?
