Support

Account

Register Login

Forum Replies Created

  • I don’t know what the chances are but I’ll mark this thread for the developer to take a look at when he has time. It seems like a bit of an edge case.

    I almost never use table layouts for repeaters as it is because the have a tendency to break on narrow screens and they cause issues with tab fields.

  • What version of ACF are you using? I’m assuming 5 because the wysiwyg field in 4 does not have the visual/text tabs.

    What other plugins do you have installed? I’ve tested in out and I’m not seeing the behavior you describe. You need to deactivate other plugins, especially anything that modifies the behavior of the editors. You may also need to try switching themes to one of the default 20XX themes to see if that clears it up.

    It’ll be easier to figure out what to do one you know where the incompatibility is.

  • If it works on a single site it will work on multisite. this is the only thing I can think of without more information. Did you follow the instructions exactly, meaning are you using get_stylesheet_directory() with a plugin that needs to be changed to plugin_dir_path().'acf/acf.php'

  • There really is not enough information provided to help.

    Is the code you posted above inside “The Loop” in the template?

  • You need to use get_field. the_field echos the content of the field

    
<?php if(get_field('publication', get_option('page_for_posts')))
		{
		 echo ' / '.get_field('publication', get_option('page_for_posts'));
         }
	?>

  • I’m not sure why this would be happening, or actually, how you might have done this. Did you delete the original field? The only reason that I can think this is happening is that you have two fields defined with the same field name/key.

  • ACF does not support user taxonomies and from what I understand the developer will not add it since WP does not really support user taxonomies.

    There has been some discussion on these forums about this and ways to get it working. Not sure if this will help you or not.

    http://support.advancedcustomfields.com/forums/topic/user-taxonomies/

    http://support.advancedcustomfields.com/forums/topic/taxonomies-not-saving-for-users/

  • Looking at the JSON code for this group, the field name of the repeater is empty. The field name cannot be empty.

    
{
            "key": "field_56437036a09b3",
            "label": "Assets",
            "name": "",  <=== MISSING FIELD NAME
            "type": "repeater",
            "instructions": "Upload downloadable assets",
            "required": 0,
            "conditional_logic": 0,
            "wrapper": {
                "width": "",
                "class": "",
                "id": ""
            },
            "min": "",
            "max": "",
            "layout": "table",
            "button_label": "Add Row",
            "sub_fields": [

  • If the URL is being added correctly to all of the data-src attributes then you’re having an issue with the script you’re using. You should look for possible javascript errors something else causing that script to fail.

    If the attributes are not being populated correctly, make sure that the field you’re using is returning a url and not something else.

  • The developer is looking into the possibility of adding this to ACF.

    Until then you can try this add on plugin for ACF5 https://github.com/Hube2/acf-reusable-field-group-field

  • Like I said above, I have flagged this thread for E to look at when he has time but I can’t say if he will or if he will comment.

    I run into the same problem with ACF pro. It has some more optimization but eventually you still run into the problem.

    The site I mentioned above uses ACF Pro and to give you an idea of the problem I was facing.

    One post type has a repeater field that lets the client add sections to a page. Each section actually represents a page of a printed publication. Each section can have up to 7 content areas. Each content area has controls that allow the client to specify the formatting of the block including padding, background, border, font color and I’m sure some things I don’t remember. So ff they add 10 sections that means they have up to 70 WYSUWYG editors plus the related settings fields for each. I created an interface using ACF Pro that was extremely easy for them to use, but I did not realize I would run into the updating problem.

    Having run into this problem I now make a special effort to think about how much data the client might try to add. If I could go back to the beginning of that project I would create a parent/child structure to the custom post type where each “Page” section was a different post. It would have been a bit more difficult for the client to use but would have avoided the problem that they now have to work around.

    This hasn’t changed my opinion of ACF, I still think it’s the best tool for the job I need to do, but I have a better handle on it’s limitations.

    What I would like to see is not using the WP update meta function and use $wpdb to build queries to insert or update all of the needed database rows in a single query. I started looking into this when I had the problem but could not figure out a safe way of bypassing or cancelling what ACF was doing. I would still like to figure something out but it’s been put on a back burner do to my current workload and other projects that I need to get done.

  • Sorry if you misunderstood, but I’m not the developer and this isn’t my forum, I’m just a guy that uses ACF a lot and helps out here on the user forum.

    I don’t really need to see your field group, but I need to understand where the disconnect we’re having is.

    Do you want these users to be able to edit the content of a post or other object that has ACF groups attached to them? Example, click on “Presentaciones” and add new or edit and existing post and change the content.

    OR

    Do you want the users to be able to click on “Custom Fields” and be able to update and modify their own field groups?

  • ACF doesn’t handle the actual upload. It calls wp_handle_upload() to manage the details.

  • I don’t understand how it’s not working. Maybe I’m confused. I added your code which added a post type and 2 user types. I went in as admin and creates some field groups and added them to your post type. Then I logged into one of the users to edit a post and the acf fields were working on that fields.

    Are you talking about allowing these users to edit the ACF field groups?

  • I’ve tried adding your code to my functions.php file, added a field group to the post type and logged in as a user of ‘Transporter’ and I could see and edit the fields in that group. I did not set any location rules on the field group.

    You’ll need to dig deeper, my test was on a site with a default WP theme and only ACF installed. Have you tried disabling other plugins and using a default theme?

  • You can’t really add another field to the Gallery, but you could add fields to attachments that could be edited when adding an image to the gallery. Then on the front end you can get these fields using the attachment ID and use them to do what you need to do there.

  • Can you attache that field group instead on putting it into the editor? You may need to put it in a .zip file. If you do that and you’re still having a problem, if you attach it I can give it a quick test and see if it’s causing an error for me.

  • @hdcms, The featured image in WP only takes an attachment ID, which point to the image object and not to a specific image size. If you want to show different size images on the front then then you’ll need to create the code that does it.

    Look at https://codex.wordpress.org/Function_Reference/the_post_thumbnail

  • Yes, you would add the code to functions.php

  • I’ll mark this for the developer to take a look at, but I can’t say that he’ll add this. Your best chance at getting this is to create a custom location rule. http://www.advancedcustomfields.com/resources/custom-location-rules/

  • The problem is that in order to use the gallery field the user has to have access to the media library. Any user type that does not have access to editing the media library will cause a JS error.

    I think this means that the user must be at least a contributor, maybe an author.

  • thanks, I’m been trying to go through some old topics when I have time to try and clean up the forums a bit. glad you got it worked out.

  • I hadn’t seen that and I didn’t dig that far. The second thread you pointed out might be the only way right now. I will mark this thread for the developer to look at if he finds time to get here. Maybe he’ll make an addition of create a hook to trigger it.

  • What is the field name of the first wysiwyg field that’s not showing the toolbar?

    Does it contain any characters other than letters, numbers and underscores?

Viewing 25 posts - 12,726 through 12,750 (of 14,460 total)
1 2 3 … 509 510 511 … 577 578 579