dauidus

As of now, I have this. Figured its always easier to solve a problem when we have something to start with. ??

global $wpdb;
		    $post_type = $pt;
		    $query = "
		        SELECT DISTINCT($wpdb->postmeta.meta_key)
		        FROM $wpdb->posts
		        LEFT JOIN $wpdb->postmeta
		        ON $wpdb->posts.ID = $wpdb->postmeta.post_id
		        WHERE $wpdb->posts.post_type = '%s'
		        AND $wpdb->postmeta.meta_key != ''
		        AND $wpdb->postmeta.meta_key NOT RegExp '(^[_0-9].+$)'
		        AND $wpdb->postmeta.meta_key NOT RegExp '(^[0-9]+$)'
		    ";
		    $meta_keys = $wpdb->get_col($wpdb->prepare($query, $post_type)); // get array of all meta_keys that don't start with _ or a number and have a value saved in the database

		    // as of now, this only checks for custom fields with a saved value

                    if ( $meta_keys ) {  // if our post type has any custom fields...

                             foreach ( $meta_keys as $key => $value ) { 

					if ( substr( $value, 0, 5 ) == "wpcf-" ) { // if from Types Plugin
						$name = str_replace("wpcf-", "", $value); // all this gets rid of wpcf and hyphens in the label
						$check = str_replace("-", " ", $name);
						$label = $check . ' &nbsp; <em>types</em>';
					}
					else if ( CFS()->get( $value ) ) { // if from CFS Plugin (not working)
						$field = get_field_object($value);
						$label = $field['name'] . ' &nbsp; <em>cfs</em>';
					}
					else { // if from ACF Plugin (as of now, this detects everything thats not from Types)
						$check = str_replace("_", " ", $value);
						$label = $check . ' &nbsp; <em>acf</em>';
					}

Then, I’m using $label to output the pretty name of the field and which plugin created it. Trouble is, all CFS-created fields are being detected as ACF. I’m planning to add more checks later, to determine if the field is hard-coded or a number of other options. But, if I can’t get this to work with CFS/ACF, then I’m just wasting time.

Thanks!
-D

mrickan,

Thanks for the kind words.

I have been working on support for ACF for the past month or so. The farther I dive into it, the trickier it is to have custom fields fully working with my plugin. But, it is possible and I am looking to release a paid version of this plugin to support custom fields and other features. I’m also looking to support the Types plugin and Custom Field Suite, among a few others.

May I ask why you use Custom Field Suite and not any other custom field manager? Is there a certain feature in it you would like to see supported? Does it do something the other plugins don’t?

I’m also looking to incorporate an API in a pro version of this plugin. That way, it can be easily extendable through add-on plugins. But, I’m not quite there, yet.

I am available to do customizations for this plugin now, if that’s something you’re interested in. For custom work, please inquire through my website at https://www.dauid.us/contact.

Cheers,
-D

Wely,

I have integrated this already into the next major version of this plugin. It will be released when all new features have been finished.

Thanks for the kind words. ??

-D

I’m working to integrate custom fields support, but due to the many ways custom fields are created and handled in WordPress, this will most likely be a paid solution.

Switching between tabs via JS is an awesome feature request! I’ll look into how to implement this (or, if I can the way this plugin is currently written). Great stuff there!

You’ll be hearing back from me at some point. ??

-D

Thanks, bkno!

Actually, I’m looking to release a new version soon that looks even more like native WordPress. I’ve also cleaned up the settings pages quite a bit to hide input boxes that aren’t being used.

I’m planning to have it available on the repo in the coming weeks – the update will coincide with a premium plugin I’m launching meant to work alongside it.

I’m taking suggestions for features to add to this one, and I’m all ears!

Cheers!
-D

Li-An,

The current version of this plugin does have known issues with custom taxonomies (they present themselves when settings have already been added, then a taxonomy is added or removed from the site). This is being addressed in the development version.

Look for new things to drop sometime soon-ish!

??

ehm01,

Sounds like you’re looking for one of these (both are simple changes to theme code):
https://www.findurlaptop.com/tech/2014/12/26/post-excerpt-in-twenty-fifteen-wordpress-theme/
https://johngirdwood.com/2014/12/27/show-excerpt-snippets-on-blog-for-wordpress-twenty-fifteen-theme/

So, as long as your content writers use the excerpt area, you should be good to go. You’ll need to go back and fix each past post individually, unless you wanna deal with code/database tables.

As this issue doesn’t really pertain to my plugin, I’m marking as resolved.

-D

ehm01,

As I understand it, the Read More tag can be replaced by the use of excerpts. This plugin already supports excerpt requirements. Perhaps you could modify your theme to use automatic excerpts, based on a specific content length.

I’m looking to keep this plugin as lean as possible, with only the core requirements that 90% of sites might use. For anything else, I’m considering developing some paid add-ons that add extra functionality. I will add your request to my list of possible add-ons.

-D

We’re looking to add some features to this plugin, and your request seems to be creating interest. Could you provide some screenshots of what you need, and provide a little more information about how you use radio buttons for taxonomies? Are you using a plugin to do this? Or can you provide a function your using so we may assess your situation?

If its something obvious that we can do, we’ll add this feature in the next major release.

Thanks!

-D

Well, a bit more than a month has passed. Good news is, we’re getting closer to v3.0, with many added features and better performance. Not so good news is, custom fields functionality will not be baked into the free version of this plugin. But, it is coming.

Thanks for the feature request!

-D

Your feedback has been heard, and we are adding “administrator bypass” functionality in the next major release. Version 3.0 will be a complete reworking of the plugin, with many other new features.

Thanks for the positive review, and keep the feature requests coming!

-D

Radio buttons are not supported, as it isn’t a standard option in WP. The only quick solution I know of would just be to use my plugin to set an exact requirement of 1 item in your taxonomy. It would work exactly as your radio buttons, but would provide a nice visual feedback for the user, as well.

-D

Ha! No worries! ??

-D

Li-An,

Could you provide a bit more detail into the problem you’re having with this plugin? Perhaps you’re maxing out on the limit of taxonomies I’ve set to check for (5). Or, maybe you’re using 2 different plugins to create those fields?

Please be detailed with your bug reports… otherwise, I have little to go on and can’t replicate your problem.

-D

X-Raym,

Due to the many ways custom fields are added by plugins, this will prove to be a challenge to code. I am looking to introduce such a feature later in this plugin’s development cycle, but it will probably be a paid solution. Which plugin do you currently use, so I may begin to look at how to implement this?

Thanks,
-D