Support

Account

Forum Replies Created

  • Also noticing this behavior. Seems counter to what it should do (or at least two what I’d expect it to do), which is for the default alignment to honor the value of the specified align property.

    When set to full, blocks seem to not be displaying as full. I still have to click the full icon – which means I also have to leave that icon visible.

    Ideally I’d be able to set the default alignment to full and also disable the icon bar.

  • Just adding the QueryMonitor debug output for reference (see attached). Happy to share additional details if helpful.

  • I am experiencing the same issue after upgrading from 5.7.10 to 5.8.0.

    Like the original author of this post, I use flexible layout fields, cloning other field groups in for each layout option.

  • Yes, please do what Delicious Brains does for WP Migrate DB Pro. Allow us to set a constant in the wp-config file. See:

    https://deliciousbrains.com/wp-migrate-db-pro/doc/activating-license/

  • +1 to being able to choose rgb or hex for output

  • +1 for being able to just set a config constant for the license key.

    I have a shell script that uses wp cli to setup (or tear down) my development environments quickly and efficiently. ACF is one of the standard plugins I include in that process. WP Migrate DB Pro as well. DelicousBrains allows you to simply define a constant in the config file for the plugin license key. This allows me to easily add that constant via wp cli when creating the environment.

    https://deliciousbrains.com/wp-migrate-db-pro/doc/activating-license/

    Needing to manually add the key for ACF is a step that would be nice to eliminate.

  • I’m not sure if this is THE solution. I’d absolutely love to NOT have to manually update the Taxonomy, but have ACF handle it – like it seems it should do? Totally may be user error for why it’s not.

    I’m manually saving the taxonomy using wp_set_object_terms(). In this case the user is restricted to selecting a single term. The solution would look a bit different if multiple terms were allowed.

    
    function acf_post_save_tribute( $post_id ) {
    	
    	// bail early if not a tribute
    	if( get_post_type($post_id) !== 'tribute' ) {
    		return;
    	}
    
    	// bail early if wordpress admin
    	if( is_admin() ) {
    		return;
    	}
    	
    	// get step
    	$trib_step = get_field('trib_step', $post_id);
    	
    	// create/update the post title if this is a new post or if the user has edited step 1
    	if ( $trib_step <= 1 ) {
    		$args = array(
    			'ID' 		 => $post_id,
    			'post_title' => $_POST['acf']['field_558884854c6ce'] . ' ' . $_POST['acf']['field_558884974c6cf'],
    		);
    		wp_update_post($args);	
    		
    		// manually update the state taxonomy field
    		$the_term_obj = get_term($_POST['acf']['field_5591b6e43e1b7'], 'trib_state');
    		$the_term_slug = $the_term_obj->slug;
    		wp_set_object_terms($post_id, $the_term_slug, 'trib_state');
    	}
    
    	// redirect new tributes to step 2 and pass along the proper ID
    	if ($trib_step < 1) {
    		$redirect = get_tribute_editor_url(2,$post_id);
    		wp_redirect($redirect);
    		exit;		
    	}
    
    }
    
  • Narrowing it down here…

    The problem is in the use of acf/save_post.

    Quick overview: I have a multi-step process setup for creating a tribute (custom post type). First form creates the post (a custom post type). Next forms are for adding additional meta data. To get users to step 2, I am using the acf/save_post action to redirect them (back to the editor) after the post is created. However, using this action is preventing the custom taxonomy (states) from saving. It saves the text fields just fine.

    function get_tribute_editor_url($trib_step=false,$trib_id=false) {
    	
    	$url = site_url() . '/edit-tribute/';
    	
    	if ($trib_step && $trib_id) {
    		$url .= "?trib_step=$trib_step&trib_id=$trib_id";	
    	}
    	
    	return $url;
    }
    
    function acf_post_save_tribute( $post_id ) {
    	
    	// bail early if not a tribute
    	if( get_post_type($post_id) !== 'tribute' ) {
    		return;
    	}
    	
    	// get step
    	$trib_step = get_field('trib_step', $post_id);
    	
    	// create/update the post title if this is a new post or if the user has edited step 1
    	if ( $trib_step <= 1 ) {
    		$args = array(
    			'ID' 		 => $post_id,
    			'post_title' => $_POST['acf']['field_558884854c6ce'] . ' ' . $_POST['acf']['field_558884974c6cf'],
    		);
    		wp_update_post($args);
    	}
    
    	// redirect	new tributes to step 2 and pass along the proper ID
    	if ($trib_step < 1) {
    		$redirect = get_tribute_editor_url(2,$post_id);
    		wp_redirect($redirect);
    		exit;		
    	}
    }
    add_action( 'acf/save_post', 'acf_post_save_tribute', 20);
    
  • Wondering if it’s a problem with the taxonomy not being registered at the time the post is saved? Seems that everything should be registered at that stage – looking into that today.

    The taxonomy field is set to load/save with the actual taxonomy.

  • I’d like to disable select2-search on all select menus. Specifically on front-end forms, but also fine if disabled in the admin area as well.

    In my case the menus are fairly short and there’s just no need for search. I could potentially just hide it with CSS, but it seems that disabling it from appearing at all would be the better route.

Viewing 10 posts - 1 through 10 (of 10 total)

We use cookies to offer you a better browsing experience, analyze site traffic and personalize content. Read about how we use cookies and how you can control them in our Cookie Policy. If you continue to use this site, you consent to our use of cookies.