rrjmdpa

Did “read here” and nothing applied. In my case I’m reverting back to last working version 3.* after “updating” inactivated added functions. Was working – now not – nothing changed but the “update.”

If you hadn’t flown off the handle and actually read what I wrote, the actual words say: “Worthless TO ME” which is a true representation of FACT. It is worthless to me – which by all precepts of UI is what a programmer is trying to avoid at all costs. In fact major businesses set up entire “focus groups” to obtain feedback like I just gave you. Your new “hard-coding” has squashed out your graph across the entire screen and makes it look like anything BUT a graph. I thought you’d like to have known that. If I HAD said something like “pisses me off” or “IT IS a bunch of junk” or in other ways maligned your programming skills I might better understand the bristles on the back of your neck. [That, to me, seems an “unfortunate over reaction.”

I wanted to convey what your upgrade (even if it was an accidental oversight) did to the functionality of the program I was using – it isn’t just an “annoyance” or “cosmetic preference” or a simple something to “get around to.” It actually renders your product more difficult to use (I would think to everyone on a wide screen) and in situations like I’m describing completely non-functioning–that’s what I was trying to convey. And “what the crap has happened” is a representation of the astonishment one is overwhelmed with when one walks out to get in one’s car and sees oil running down the driveway. It was working minutes before and now is un-drivable; and the only thing that happened is that the mechanic worked on it!

Regarding the programming – the code I used before came graciously, and readily, from YOU; like you had run into the request many, many times previously and had it to hand. Like you intended it to be used for just such a purpose. I see that WordPress itself, and many other plugins, use hooks like that for such a purpose. From your PREVIOUS willingness to share such code it seemed like: A – you had already vetted the value of the request and found it worthy of your time; B – you understood the value of the “hooks” that WP uses and modular programming and either already had, or intended to implement them; and, C – valued user feedback.

I did see your several warnings against doing things that would be “overwritten” when your programming was updated and broke none of them. You warned that styling was being done in a separate file which would get overwritten when updated so I left that alone like you advised. However, what seems like styling has now broken even though I followed your warnings.

In addition, I took extra care to put the functions code (again which I received from you) in a functionality plugin, also like you advised. I admit that it may have been just an assumption on my part, but I assumed that by your warnings and suggestions you fully intended to use that methodology in order to make future “upgrades” were backwards compatible.

Lastly, after what Yost did a few months back with his plugin, I’ve begun making sure to read all the so-called “enhancements” given in the change log for any upgrade BEFORE I commit them into production. I did read what was available from your descriptions and didn’t find any warnings that internal tags or programming had changed which might cause problems with previous versions. That would have been nice.

Now, it’s just my guess, but it seems TO ME that the problems I’ve reported are of such a minor nature (or oversight) that they could be readily corrected, or worked around with a few simple instructions listed in your change log; and, in the time we’ve both already spent crafting our replies probably could have already been resolved… your call.

At very least it seems that a “warning” in the change log about possible failures to those who’ve made modifications would be in order. Like I said, it seemed to be working fine for me before your “upgrade.” If I can figure out how to revert back to the previous version maybe that’s what I’ll do.

Same exact issue and browser warnings:

“This organization’s certificate has been revoked. Security certificate problems may indicate an attempt to fool you or intercept any data you send to the server.” [Not the usual “no certificate” or “removed” but REVOKED.]

Apparently it IS sneaky spyware – perhaps mandated by Facebook. Trying to see if this unacceptable update and the poorly programmed “nag” button which won’t disappear or allow you to “decline”, meant that I couldn’t now use the plugin; every page I clicked on gave a browser warning:

“This organization’s certificate has been REVOKED. Security certificate problems may indicate an attempt to fool you or intercept any data you send to the server.”

Spent a lot of time vetting this plug-in, liked it, used it for a long time, now completely worthless to me – I can’t put subscribers data or privacy in jeopardy like this. [You probably can tell this hits a nerve – having been burned twice before by Facebook and its privacy violations]

Seems like you and YOAST can’t leave well enough alone. There are a lot of people who dislike and do not support Facebook – your update page says the update was basically for Facebook functionality and apparently requires that you have us sign a completely new privacy statement!

Does not accepting your new Facebook privacy statement (which you don’t even give as an option) completely invalidate the plugin and cause it not to work?

How do you revert back to a previous version. And people of WordPress – this is becoming a real crap process – apparently we’ve got to NOT allow auto updating and cruise the forum for early adopter’s bad comments before we can safely install updates. I mean mistakes happen BUT – it seems there need to be a huge “REVERT” button next to the “install” button. Why not?

@twoelevenjay Thanks for taking the time for all the info. I’ll update as soon as I see 0.0.6 go live. I thought I had the most recent update – I only began this about 10 days ago.

And, I have to say that I’m sure I just missed something along the way but it has been gradually dawning on me very slowly, the scheme of things you outlined. I AM really GRATEFUL for the “get_post_meta” string you posted. I’ll need to try to get it to work on my installation in case I ever need it. I did read the codex on it but tried several variations without success and thought that the data must be stored in some extra file.

What I was really trying to do is be able to list all the posts for a custom post type ordered in a multi-level UL list by their value in a custom hierarchical taxonomy field. It seems so basic but I still can’t get it to work even after all this – that’s probably why I couldn’t figure out the function you gave because I really want a list spanning several posts and not just one whose ID I know.

[Honestly, the support explanations given for the whole taxonomy topic are, for me, by far the most difficult to understand and grasp. If I ever feel like I’ve got a clue how it all works – I’d volunteer to write up documentation on it. Right now I’m spending hours and hours just trying to get anything to work like I think I understand how they say it should work. <whine>I usually can figure it out eventually, it's just the agony endured till I do.</whine>]

Justin… thanks for all the info; I wish I could do the fancy movie screen capture like you did – I’d show you that the select field covered the data entry field on my computer or I probably wouldn’t have mentioned it. Perhaps it has to do with the position on the screen and/ or the order of keypress or something.

However, for me, all the click and move and click and move just seems bizarre and not something that seems remotely good UI or I would find useful either way. Still however, if I can make it NOT to cover over the interface it will be easier to hand enter the full date, probably not as easy as using a “good” UI calendar but there you are. (It’s likely that most others enter within 10 years either way; but, for me I prefer those that program the calendar UI as a user discretion pop-up and not as auto default)

Thanks for the trouble of taking the time to explain all this, obviously, I would have never in a million years figured out the backdoor approach to what should be an easy scroll process.

Ah… tag team customer support. I like it.

Justin you win the prize by revealing that your CMB2 doesn’t even have a GUI so what was I thinking? … I waded through the maze of internet posts and google hits that is most of our gateway into trying to deal with the disappointment that WordPress has supported taxonomies for many years and even now still has no basic support for it beyond creating them!

Links from all over the net go to your “old” page with the disclaimer that you’ve upgraded the program – which is what I followed and which makes all of us “uninitiated” a bit wary and watchful of getting the “old/bad” code. There were two listings with CMB2 in the title on the WP Plugin install page and my assumption was that they were both from the same team — evidently wrong.

“CMB2 admin extension” is not yours then, and it didn’t click for me that the “post editor” was still in the “admin” and therefore part of the “extension.” I deactivated that “aberrant” plugin and walla – I get nothing, even though yours is still active.

That was the culprit, but now I’ve got to figure out where it was storing all its code because I’ve already done a lot of work with it. Sorry for wasting all of our time.

Guess I’ve got to start all over. I can’t see me starting from scratch and writing a data entry program to enter custom data on every entry just because I’m using a custom taxonomy name instead of the WP basic “cat” and “tag.”

Perhaps you’ve got a recommendation for a GUI based plugin that will allow custom fields attached to taxonomies – or one more compatible with yours?

Thanks anyway.

— In fairness though, in my google travels I did see the descriptions that you’ve linked to and being full of jargon I didn’t understand many of them. Also, I did copy and paste your functions-example.php into my jedit to try and see what it did, but got two parsing errors (line 2 and line 20) warning “2:statement expected” and “20:statement expected” (I have no clue what that means) — so I thought that the code was probably the “OLD CODE” that you warned about and discarded it.

Perhaps I could add that until I see whether/how this thing works I’m just setting it up using native worpress and twentysixteen theme (yes, latest updates)

the only “programming” I’ve done has been to add a simple functions-plugin with the taxonomy and custom post type code as thus: (perhaps this is what you mean by “registration”??? Except it is not for “box/field” as you asked for) – basically got this off previous “answers” on the inet and modified it to my content. It seems to be working in every other way with adding real content.

/* ---------------------------------- *
 * Custom taxonomy - engram classes   *
 * ---------------------------------- */

// hook into the init action and call create_engram_taxonomies when it fires
add_action( 'init', 'create_engram_hierarchical_taxonomy', 0 );

function create_engram_hierarchical_taxonomy() {

// Add new taxonomy, make it hierarchical like categories
// first do the translations part for GUI

  $labels = array(
    'name' => _x( 'Engram Classes', 'taxonomy general name' ),
    'singular_name' => _x( 'Class', 'taxonomy singular name' ),
    'search_items' =>  __( 'Search Engram Classes' ),
    'all_items' => __( 'All Classes' ),
    'parent_item' => __( 'Parent Class' ),
    'parent_item_colon' => __( 'Parent Class:' ),
    'edit_item' => __( 'Edit Class' ),
    'update_item' => __( 'Update Class' ),
    'add_new_item' => __( 'Add New Class' ),
    'new_item_name' => __( 'New Class Name' ),
    'menu_name' => __( 'Engram Classes' ),
  ); 	

// Now register the taxonomy

  register_taxonomy('classes',array('post'), array(
    'hierarchical' => true,
    'labels' => $labels,
    'show_ui' => true,
    'show_admin_column' => true,
    'query_var' => true,
    'rewrite' => array( 'slug' => 'class' ),
  ));
}

/* ---------------------------------- *
 * Custom taxonomy - Periods   *
 * ---------------------------------- */

// hook into the init action and call create_period_taxonomies when it fires
add_action( 'init', 'create_period_hierarchical_taxonomy', 0 );

function create_period_hierarchical_taxonomy() {

// Add new taxonomy, make it hierarchical like categories
// first do the translations part for GUI

  $labels = array(
    'name' => _x( 'Periods', 'taxonomy general name' ),
    'singular_name' => _x( 'Period', 'taxonomy singular name' ),
    'search_items' =>  __( 'Search periods' ),
    'all_items' => __( 'All Periods' ),
    'parent_item' => __( 'Parent Period' ),
    'parent_item_colon' => __( 'Parent Period:' ),
    'edit_item' => __( 'Edit Period' ),
    'update_item' => __( 'Update Period' ),
    'add_new_item' => __( 'Add New Period' ),
    'new_item_name' => __( 'New Period Name' ),
    'menu_name' => __( 'Periods' ),
  ); 	

// Now register the taxonomy

  register_taxonomy('periods',array('post'), array(
    'hierarchical' => true,
    'labels' => $labels,
    'show_ui' => true,
    'show_admin_column' => true,
    'query_var' => true,
    'rewrite' => array( 'slug' => 'period' ),
  ));
}

/* END - ADD TAXONOMIES  */

/* ADD CUSTOM POST TYPES   */

/* -------------------------------------- *
 * Custom Post Type - Engrams             *
 * -------------------------------------- */

function custom_post_type_engrams() {

// Set UI labels for Custom Post Type
	$labels = array(
		'name'                => _x( 'Engrams', 'Post Type General Name', 'iRememberMe' ),
		'singular_name'       => _x( 'Engram', 'Post Type Singular Name', 'iRememberMe' ),
		'menu_name'           => __( 'Engrams', 'iRememberMe' ),
		'parent_item_colon'   => __( 'Parent Engram', 'iRememberMe' ),
		'all_items'           => __( 'All Engrams', 'iRememberMe' ),
		'view_item'           => __( 'View Engram', 'iRememberMe' ),
		'add_new_item'        => __( 'Add New Engram', 'iRememberMe' ),
		'add_new'             => __( 'Add New', 'iRememberMe' ),
		'edit_item'           => __( 'Edit Engram', 'iRememberMe' ),
		'update_item'         => __( 'Update Engram', 'iRememberMe' ),
		'search_items'        => __( 'Search Engram', 'iRememberMe' ),
		'not_found'           => __( 'Not Found', 'iRememberMe' ),
		'not_found_in_trash'  => __( 'Not found in Trash', 'iRememberMe' ),
	);

// Set other options for Custom Post Type

	$args = array(
		'label'               => __( 'engrams', 'iRememberMe' ),
		'description'         => __( 'Single life memories', 'iRememberMe' ),
		'labels'              => $labels,
		// Features this CPT supports in Post Editor
		'supports'            => array( 'title', 'editor', 'excerpt', 'author', 'thumbnail', 'comments', 'revisions', 'custom-fields', 'listings'),
		// You can associate this CPT with a taxonomy or custom taxonomy.
		'taxonomies'          => array( 'classes' ),
		/* A hierarchical CPT is like Pages and can have
		* Parent and child items. A non-hierarchical CPT
		* is like Posts.
		*/
		'hierarchical'        => false,
		'public'              => true,
		'show_ui'             => true,
		'show_in_menu'        => true,
		'show_in_nav_menus'   => true,
		'show_in_admin_bar'   => true,
		'menu_position'       => 5,
		'can_export'          => true,
		'has_archive'         => true,
		'exclude_from_search' => false,
		'publicly_queryable'  => true,
		'capability_type'     => 'page',
	);

	// Registering your Custom Post Type
	register_post_type( 'engrams', $args );

}

/* Hook into the 'init' action so that the function containing our post type registration is not
*    unnecessarily executed.
*/

add_action( 'init', 'custom_post_type_engrams', 0 );

/* -------------------------------------- *
 * Custom Post Type - Passages*
 * -------------------------------------- */

function custom_post_type_passages() {

// Set UI labels for Custom Post Type
	$labels = array(
		'name'                => _x( 'Passages', 'Post Type General Name', 'iRememberMe' ),
		'singular_name'       => _x( 'Passage', 'Post Type Singular Name', 'iRememberMe' ),
		'menu_name'           => __( 'Passages', 'iRememberMe' ),
		'parent_item_colon'   => __( 'Parent Passage', 'iRememberMe' ),
		'all_items'           => __( 'All Periods', 'iRememberMe' ),
		'view_item'           => __( 'View Passage', 'iRememberMe' ),
		'add_new_item'        => __( 'Add New Passage', 'iRememberMe' ),
		'add_new'             => __( 'Add New', 'iRememberMe' ),
		'edit_item'           => __( 'Edit Passage', 'iRememberMe' ),
		'update_item'         => __( 'Update Passage', 'iRememberMe' ),
		'search_items'        => __( 'Search Passage', 'iRememberMe' ),
		'not_found'           => __( 'Not Found', 'iRememberMe' ),
		'not_found_in_trash'  => __( 'Not found in Trash', 'iRememberMe' ),
	);

// Set other options for Custom Post Type

	$args = array(
		'label'               => __( 'passages', 'iRememberMe' ),
		'description'         => __( 'A particular part of someone\'s life or career in which something continues to exist or happen', 'iRememberMe' ),
		'labels'              => $labels,
		// Features this CPT supports in Post Editor
		'supports'            => array( 'title', 'editor', 'excerpt', 'author', 'thumbnail', 'comments', 'revisions', 'custom-fields', 'listings'),
		// You can associate this CPT with a taxonomy or custom taxonomy.
		'taxonomies'          => array( 'periods' ),
		/* A hierarchical CPT is like Pages and can have
		* Parent and child items. A non-hierarchical CPT
		* is like Posts.
		*/
		'hierarchical'        => false,
		'public'              => true,
		'show_ui'             => true,
		'show_in_menu'        => true,
		'show_in_nav_menus'   => true,
		'show_in_admin_bar'   => true,
		'menu_position'       => 5,
		'can_export'          => true,
		'has_archive'         => true,
		'exclude_from_search' => false,
		'publicly_queryable'  => true,
		'capability_type'     => 'page',
	);

	// Registering your Custom Post Type
	register_post_type( 'passages', $args );

}

/* Hook into the 'init' action so that the function containing our post type registration is not
*    unnecessarily executed.
*/

add_action( 'init', 'custom_post_type_passages', 0 );

/*  END - ADD CUSTOM POST TYPES  */

Justin, Michael – Really, I don’t think I know what you are asking for. I’m merely using the GUI you’ve programmed into the plugin to9 fill out boxes. I’ve created a box called “duration”. I’ve entered the title “begin” and “date began” into the name and description boxes of “field 1”. I’ve selected “text_date:Date Picker” for the field type. I MAKE SURE that the “repeatable” box is NOT checked. There is no entry in either the “options” or the “default value” boxes.

I added a “field 2” box with absolutely identical settings except named “End” and described “Date ended.”

The metabox settings in the sidebar are”
Post Types: “Engrams” and “passages” (two custom post types)
Priority: “core”
Context: “normal”
Show names: “checked” to show on left
Disable CMB2 Styles: “NOT checked”
Closed by Default: “NOT checked”

Is that what you want?

Then when I go to enter either a new “engram” or “Passage” the “Duration” box that I set up using your GUI appears like it should with both “begin” and “end” fields and their “begin” and “End” names on the left.

EXCEPT that the “begin” box has the description above the entry box (the “end” field does NOT) – inconsistency number 1;

the “begin” field has a greyed out “remove” remove box to the right (the “end” field does not – inconsistency number 2;

the “begin” area then has an extra grey horizontal line below which exists another button “Add Row” (the end field does not) – inconsistency number 3.

Also the two fields are separated by another full width horizontal line – which I guess is intended.

This also occurs if I enter a “passages” taxonomy too.

—

Perhaps this is not what you wanted – but I have written no “registration code” that I know of for a “box/field”, only used your GUI – and I thought I gave all this originally only not so succinctly.

Let me know if I’ve missed your point.

Any progress on this yet?

I think he meant that it was a lot of unnecessary work to tie developers to only using the ID – why not allow using either the ID OR the slug like we’re used to? He’s calling it “meta_name” or the visible name of the field; but that’s not exactly how it’s done is it – WP plugins use the “slug” and not the field “public name”.

NO THE PROBLEM ISN’T SOLVED!

I clearly demonstrate the problem every time I upload a Yoast enhancement – however, I do NOT have the “pro” version. Turning on a Yoast version (after 2.3.5) completely borks if ACF is active. Removing either ACF or Yoast allows the other to work; BUT, clearly the issue is with Yoast because it was the one which changed AND the forums are full of other reports claiming their plug-in stopped working after Yoast v3.x was uploaded.

I have followed the link above and installed the Extra ADDON plugin – it did NOT correct the problem.

Today, Yoast announced their new “release candidate” version 3.1_RC which was supposed to have solved the problem – BUT it hasn’t either! The issue is STILL OPEN

If you are using Yoast as an add on to a Theme (either free or purchased) you run the risk that the theme will be trying to do similar things on its own to what Yoast is trying to do and they will not be compatible. It is up to You to do your own troubleshooting when you try to add any plug-in on top of a theme that someone else has written.

That said, the latest “update” of yoast has caused many sites to break, and we are unfortunately seeing that the “team yoast” has no desire to support their “free edition” any more.

It is known that the Yoast update is no longer compatible with the advanced custom field plug-in; and there may be more. It also does not fill the sitemap completely with all posts in some installations.

Actually, you’ve described issues that make me think you’ve got more problems than with just Yoast. Check the plug-ins that you use. Deactivate them one by one and see if things improve. If it does then you’ve got an incompatibility and we’d appreciate knowing about it on this forum.

A lot of people are experiencing issues with the latest update. Sans any help from the Yoast team I’m trying to troubleshoot under what conditions the sitemaps and other plug-ins work and don’t work. Are your site maps complete and what other plugins do you use (if you’d care to share.) The new update seems to bork my sitemaps and I know it’s become incompatible with at least the Advanced Custom Fields plugin.