Support

Account

Forum Replies Created

  • Just following up on this. Was wondering if @elliot as a response.

  • Sorry it somehow righted itself. No isses.

  • I know this is an old thread but getting the same issue. Just migrated to MediaTemple and getting:

    Automatic update is unavailable for this plugin.

  • So actually PB had an amazing API for building out widgets of all kinds. If you download their so widgets plugin it has a bunch of additional ones and then in their developer docs they go through the process of making your own bunch of custom widgets.

    So my workflow is now ACF for page and post type additional fields as well as my custom admin panel. And then Page Builder plus my own custom widgets for layout.

  • Here is the answer

    <?php
    add_filter('acf/settings/save_json', 'my_acf_json_save_point');
    
    function my_acf_json_save_point( $path ) {
    
    	// update path
    	$path = dirname( __FILE__ ) . '/acf-json';
    
    	// return
    	return $path;
    
    }
    
    add_filter('acf/settings/load_json', 'my_acf_json_load_point');
    
    function my_acf_json_load_point( $paths ) {
    
    	// remove original path (optional)
    	unset($paths[0]);
    
    	// append path
    	$paths[] = dirname( __FILE__ ) . '/acf-json';
    
    	// return
    	return $paths;
    
    }
  • I haven’t come close to getting this to work either. ACF is the best for fields, and PB is the best in terms of creating layouts. Building a layout builder using ACF alone, while straightforward, yields an adequate UI at best.

    From what I understand, you can create a field, and then assign it to a particular registered widget. Then when you add that widget to a widget area, or Page Builder, the ACF fields should appear. I find they do in some cases.

    So the workflow for getting ACF and PB to work together would be to register a new widget type for every block element. Icon box, testimonials, etc… Create an ACF field group for each widget type and assign the group to the previously registered widget above.

    In your theme, display the widget content using get_field within the Widget’s callback.

    I would love to see just one working example of this.

  • Massive plus 1 on this. ACF Pro is able to replace horrible page builders but this issue makes it pretty rough to hand off to the client.

  • Sorry to resurrect this one. Seems I have come across this issue myself. So I have cleaned out all revisions and queried the db for the repeater field I am using:

    Here are the results

    79 30 page_blocks
    1997 3876 page_blocks 2
    2222 3882 page_blocks 3
    3311 3927 page_blocks 6
    5228 4002 page_blocks 1

    Each is a page in the site. So the process is:

    Change the field type in the ACF editor to Flexible Content

    Then specifically how do I figure out what serialized array to enter into each page?

  • Steps to reproduce

    1. Add multiple wysiwyg fields to a post type via ACF
    2. Edit post
    3. Put some content into the main content field
    4. Click on full screen mode in one of the custom wysiwyg fields
    5. Put some different content in full screen mode (in the custom wysiwyg)
    6. Click on full screen mode button again to go back to normal mode
    7. Behold the custom wysiwyg content you just added replace the main content field
  • I can definitely confirm this as well. Fill screen mode editing causes the content to shoot into the main content area instead of the custom field you are currently editing.

  • Solved it. Here is how:

    $myrows = $wpdb->get_results( "SELECT * FROM wp_postmeta WHERE meta_key = 'manufacturers' AND meta_value LIKE '%$manufacturer_id%'" );
    	
    foreach($myrows as $row){
      $retailer_ids[] = $row->post_id;
    }
    

    Then run a WP_query with the post ids

    $args = array(
      'post_type' => 'where',
      'post__in' => $retailer_ids
    );
    $retailers_query = new WP_Query($args);

    The only reason I can see this having issues is if one of the serialized pointers is the same as a manufacturer ID. But there are ways to start them high so this workaround should be good for now.

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