occupant

Great to see this is cleared up. I’d also recommend adding the echo to your real-world example on your documentation page.

So this: <?php echo types_render_field("field-name", array("arg1"=>"val1","arg2"=>"val2")); ?>

instead of this: <?php types_render_field("field-name", array("arg1"=>"val1","arg2"=>"val2")); ?>

I added it (my issue was the prefix), but I can see how someone might not. There’s never a danger in being too clear.

I have the same issue (and I saw it posted last week as well). According to the API, that’s correct. My guess is it’s busted.

Embedding is a poor way to implement this imho – you can’t customize the layout as easily or trust others to get it right. I guess it’s a way to try to sell Views. I’m sure I could get it to work with Views, but I’m not going to buy a module to ‘add’ functionality that supposedly exists. I assume Views is similar to Drupal Views (which would make it worth the price).

It’s disappointing – this is sorely needed in WordPress.