[Plugin: Custom Content Type Manager] Seems to break Advanced Custom Fields plugin on frontend but n

Solved this by adding a Custom Field in the Custom Content Type Manager for the custom content type and setting the default output filter to get_post for that field.

After adding one field with this output filter all custom fields are being returned and able to be displayed.

I can then hide that field using ACF.

Interesting. I’m wary of crossing plugins like this. What exactly does ACF do that the CCTM does not? It would make for a good feature request.

Advanced Custom Fields is one of my favorite plugins. It allows you to completely customize the fields for any post type in wordpress, including creating repeating and grouped repeating field types, drag and drop galleries, etc. makes entering data a breeze for my clients. It is more advanced then Custom Content Type Manager when it comes to form fields, which isn’t the main purpose of the Custom Content Type Manager, just a nice additional feature.

Since ACF can set those fields based on any condition, including a custom post type, and since Custom Content Type Manager creates and uses the wordpress standards when creating post types they should work together without issue.

The key for solving my problem was that Custom Content Type Manager can override how custom form elements are passed, shortcode/get_post/etc (about 10 options). So setting a default dummy custom field in Custom Content Type Manager to get_post, makes it set the passing of all custom fields via get_post instead of overriding to a different type. or at least that is why i’m guessing that this workaround works in this case. ??

Hope that info helps.

Thanks for the explanation. Can you show me what your template code looks like? I’m having a hard time imagining how using the get_posts output filter can act as a workaround.