Forum Replies Created

  • Plugin works great for me out of the box. Just had to add a little css to get the edit button the way I want and voila. Perfect. thanks.

  • Got this working with maps on the front-end. elliots example code was extremely helpful:

    // vars
            var args = {
                zoom		                : 16,
                center		                : new google.maps.LatLng(0, 0),
                mapTypeId	                : google.maps.MapTypeId.ROADMAP,
                scrollwheel                 : false,
                mapTypeControl              : true,
                mapTypeControlOptions: {
                    style                   : google.maps.MapTypeControlStyle.HORIZONTAL_BAR,
                    position                : google.maps.ControlPosition.TOP_LEFT
                zoomControl                 : true,
                zoomControlOptions: {
                    style                   : google.maps.ZoomControlStyle.SMALL,
                    position                : google.maps.ControlPosition.LEFT_CENTER
    // create map
            var map = new google.maps.Map( $el[0], args);
  • This was helpful, and took me awhile to get.
    I’m doing something similar.
    I have a list of staff members as custom post type
    Each staff member makes a monthly book pick – also a custom post type called staffpicks

    ACF is running on staffpicks with a custom object field relating back to the staff member who picked it.

    When using the post object field – even though the post object field will show the title of the post in the select box (which is convenient…thanks), it’s actually saving the post ID of that related post object in the database.

    So when we run the meta query we have to use a value of post id – not the title of that post.

    Am i getting that right?

  • I second this feature request.
    Would be a nice check box in options for map /location fields.

  • Yes, thanks.
    I suspect i need to look over the maps api more closely.
    Let me do that and get back.

  • sorry for the double post. needed to notify via email.

  • i struggled with getting the map to work with the code you provided a few months ago on the git repository.

    Before i take any more time on it, can you confirm that code actually still works?

  • I’ve noticed this on a few woo themes where the gravity forms product add-on plugin was installed. I believe it was version 2.44 and 2.45. They’ve updated that 2.47 now and it works fine.

    I just replaced the plugin files over the old one and the error clears.

  • Went back to the other code you suggest:

    add_filter('acf/options_page/settings', 'os_acf_options_page_settings');
    	function os_acf_options_page_settings( $settings )	{
    		$settings['title'] = 'Theme Options';
    		$settings['pages'] = array('Header', 'Sidebar', 'Footer');
    		return $settings;

    and it works fine, but using the previous code posted with title and slugs still not working.

  • Yes, I’m seeing this too.

    When I use ‘parent’ =>’options-general.php’ with similar code to that listed abvoe, it makes the sub-page “footer” show up under the general wordpress settings menu under permalinks.

    If I use alternative parent, for example:

    	if( function_exists('acf_add_options_sub_page') )
            'title' => 'Footer',
            'parent' => 'acf-options',

    It breaks the options page altogegher. Specifically, i notice it removes the default options page as a choice in the field group rules locations.

    Here’s the entire code I’m using in a child theme functions.php file:

    add_action('init', 'os_child_theme_options');
    	function os_child_theme_options (){
    	if( function_exists('acf_set_options_page_menu') )
    	    acf_set_options_page_menu( __('Theme Options') );
    	if( function_exists('acf_set_options_page_title') )
    	    acf_set_options_page_title( __('Theme Options') );
    	if( function_exists('acf_add_options_sub_page') )
            'title' => 'Footer',
            'parent' => 'acf-options',
  • Got it working beautifully on a clean theme and child theme, even in a plugin.

    But Couldn’t get it to work on this one particular premium theme. Can’t figure it out at all.

    I do know that theme author is using an older version of your code though.
    I tried replacing his code with the new acf, and that blew it out too.

    My guess is that his code is relying on your older code.

    Either way, I think I’m going to take this up fruther with theme developer. Only problem is he’s not very responsive. Poor form.

    Anyway, thanks for your help on this. Gonna bring this one to a close.
    Pull my hair out one last time and then move on.

  • I’m going to switch from basing this on categories to a whole new custom post type. that way I can show the fields based on post type and not worry about drilling down further.

    Should eliminate this problem.

    thanks for your help and quick response.

  • I was just using an example, if I create an options page with one drop down select field called ‘postcats’ which would store the id of the category the user selects.

    The location of the field group would then be set to display only on the category id.

    But you’re saying it can’t be done that way, correct?

    I’m not seeing how a custom location rule would get something like that done, since it seems the location rules are based on already set choices, terms, cats, etc. I’m not seeing anything here that would hint otherwise.

    Im developing something as a plugin to go into sites where i want the custom fields to populate on a specific type of post category, but what one user calls that category might be different than another, hence the reason i want to give them the option to choose which category gets the custom field functionality.

    Appreciate your quick response though.

  • Good timing. I just started with a clean copy of the theme and child to see if I can recreate it. We’ll see where it goes.

  • any attempt to include acf.php in my child makes my fields workk, but eliminates the theme authors fields.

    If i leave that code out, his fields work, but not mine.

    Not sure where to go with this one.

  • Nah, still not working. Same issue still exists. Advanced fields for my taxonomy not showing up.

    Even if I pull out the call to the custom post type and taxonomy file and place all that code inside the child theme functions.php it doesn’t work.

    This is really frustrating because it works both ways, just not at the same time.

    Theme developer is on vacation too, and not offering support for some time.

    I’m not sure what I need to be calling or if I need to include acf.php in a different way.

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