[Steven Zahm]

@ Jon

Ahhh, you know what. I wasn’t paying close enough attention to the version numbers you gave me. I seem to recall making a tweak to that logic so the birthday field [not table] would be removed / overwrote or something; I can’t remember. There may have been other smallish tweaks elsewhere too so this wouldn’t happen. So your change makes sense… Wait, you did say you tried 0.7.9. OK, well, I’m lost.

Anyway great to hear you have it sorted!

[Steven Zahm]

@ Cathy

I’m sorry, but I don’t understand. The widget will list all categories regardless is a parent category is clicked. Could you provide more detail?

[Steven Zahm]

@ Sean

If you’re having display issues [the way things look] take a look at this FAQ and this QuickTip.

Let me know if that helps.

[Steven Zahm]

@ nickyker

Great to hear and many thanks for the review!

[Steven Zahm]

@ Jonathan

Use this shortcode on the page:

[connections category=X enable_search='false' enable_category_select='false' enable_pagination='false']

X would equal the category to limit the results.

Will that work?

[Steven Zahm]

@ katherine

All you need to do is a the label option the function, like so:

$entry->getCategoryBlock( array( 'label' => 'Certifications' ) );

If you have other options set, you’ll have to be careful on how you add the label option to the function.

Hope that helps.

[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.

[Steven Zahm]

@ dgalassi

Yeah, that would hide it to all users. My assumption was if you’re an admin you would just use the Manage page to update their entry since they have access to it. The important bit was to hide it from the subscribers; right? Any way what you did accomplish the same, so it should work too.

[Steven Zahm]

@ Tell

Sorry, but there is no way to manage subscriptions with Connections so it sounds like it will not be a good for for your needs. Other users use member plugin to manage subscriptions, but that would still require manual management of the entry with Connections for delisting cancellations. If you decide to go this route; you would need Link to allow the user to submit and maintain their own entry. As for flagging updated entries; there is nothing built in to do this.

I hope that thoroughly answers you’re questions.

[Steven Zahm]

@ Lora

Sure, except for the PDF part; sort of. You could add easily add a link to anything in either the bio or notes fields. You could even add a link to the PDF by adding a link in the links data.

For search, you’ll need one of the premium templates. cMap is the most popular if that helps.

I hope that thoroughly answers your questions.

[Author]

Posts