Steven Zahm@ Mitch
Right, 0.8 is where I branched off to develop this API. The version will bump when I merge this feature branch into the main dev branch. Software Version Control mumbo jumbo…
Any way…
Installing it and the demo plugin, at this point, only shows [eye candy] the “officially” supported custom fields the API can create. There isn’t actually a way to save the fields [working on it, more below] or show them in a template yet. Actually not sure how I’ll even show the data in a template yet. I’m guessing I’ll just dump the custom fields if they exists after the core fields. Any finer control would require making PHP changes to the template. I’m thinking this would be a great fit for Connections qT…
I started working the meta API. Thats the how the data for the custom fields will be saved and retrieved at the code level, nothing a user will have to worry about. I thought a good tactic would be to mimic the way WP does it … boy, was that a rabbit hole I shouldn’t have gone down. Wasted 6/7 hours. I should’ve just gone ahead and done what I was going to do as I’d have a good chunk of it down by now.