[Steven Zahm]

@ NetWarden

re: notes fields/rte

Sorry, unfortunately, I don’t have anything handy I can give you to replace that section of code.

re: rte_notes and rte_bio options

No those options would not affect the back end, only Form. Looking at this closer. I’m not sure I will be able to add these or even keep the other rte option with the next Form release. Why?

As mentioned Form is going thru a significant update. Primarily to support the new custom fields API built into Connections. A few other highly requested features to be included as well. Part of supporting the custom metaboxes means I rewrote Form to reuse the metaboxes coded for the admin. The benefits here is it makes Form far leaning and also not requiring updates to take advantage of any new fields that might be added to Connections or added by other extensions for Connections. So what does this have to do with the rte? There is not a way way simply turn of the rte. The only thing I can think of off the top of my head is to include a filter which can be hooked into to define if an rte is to be used or not.

[Wayne]

Well Instead of trying to convert ‘Notes’ into something else (as it seems really painful to remove RTE from it), why don’t you make a new permanent text only field called ‘Keywords’ or ‘Tags’ to your Connections plug-in. This would improve site search results.

Also whenever Connections displays a single listing it can include the Keywords/Tags in the page meta-data ‘Keywords’. This would greatly improve search results for the search engines.

[Steven Zahm]

@ NetWarden

With the new custom fields and metabox API, this could be very easily added by a dev. This isn’t something I’ll be adding to core.

As far as meta tags/keywords, I could be wrong, but I think I’ve read that search engines no longer give any weight to keywords because they were so badly abused in the early years.
https://yoast.com/meta-keywords/
https://yoast.com/focus-keyword/

Now with that said, I do not yet know if it is possible, but on my todo list is an extension the integrates with WordPress SEO. The only blocking item I can think of is that Connections does not use a CPT, so I would have to be creative in bringing in the SEO metaboxes and processing the settings when an entry is added/edited.

[Wayne]

Will custom fields and metabox API work throughout Connections (ex: the back-end) or just the Form extension? Also will these ‘custom fields’ be something that can be set-up within WordPress back end, or will each field would have to be ‘coded’ into a plug-in/extension as an add-on?

If it does work throughout and can set fields within WP back-end then adding any other fields to core is mute. However if it can’t, then adding at least one non-RTE text only text box (not necessarily a Keywords/Tags box) that can be ‘relabelled’ and used like the others should be added to core.

BTW: I assume because the custom fields and metabox API is being developed, the extra ‘Categories Group’ idea is also likely going to have to be done using this custom fields and metabox API. I’m I correct on this assumption?

[Steven Zahm]

@ NetWarden

Yes, it will work throughout Connections … one of the major reasons it is being rewritten; so it can support this new feature.

Initially, since this is just an API, it will require a dev to add much like a dev has to add custom fields to posts pages. At some point, I will be creating a point and click admin interface to add custom fields.

I suppose one could create a second categories group using this new API, but it probably would be best not to until I can add custom taxonomy support (categories is a taxonomy).

[Patricia Ford]

I am in the process of setting up Connections and also would like to customize the fields and meta-boxes on the Your Directory Entry form.

In the future when you have Form integrated with Link, I will definitely want to use that configuration to have better control over the fields presented on the user’s form. But for now I have to deal with the backend “Edit My Directory Entry” form and I would like to eliminate some metaboxes and fields that I do not need.

Can the snippet (above) to remove the Dates metabox be expanded to remove other metaboxes? Like LOGO and BIO?

What about individual fields in the Name metabox? I do not need “Title” or “Department” — is there some way I can remove those from the entry form?

Lastly, could you please elaborate on this statement you made in one of the replies above:
” I have the filters for the advanced users can hook into and change.”
Is there more information available regarding “filters for advanced user”? If so, where can I find this information?

Thank you for a fantastic plugin! I’m really looking forward to upcoming versions where Link and Form are integrated and custom fields can be added.

[Steven Zahm]

@ Patricia

I’ve been hacking away on Form 2.0 for the past few days now and it has received quite a few significant enhancements. I’m actually going to start working on front-end editing today.

I added two additional snippets. One to remove the bio metabox and another to remove the logo metabox.

The only way to remove the other fields is to add CSS to the cn-admin.css / cn-admin.min.css files to hide them.

Sorry, I do not have any more details on the filters at the moment as most are not yet implemented and the one I did, I’m really not happy with so I plan on re-working it.

Hope that helps.

And …

If you have a moment, I would truly appreciate a review as they really do make a difference. Many thanks in advance!
http://wordpress.org/support/view/plugin-reviews/connections

Attachments:

You must be logged in to view attached files.

[Author]

Posts