Check your field names for words that are reserved by WP. For example “name”. Basically any argument name used in WP_Query can cause this. Although I think ACF deals with most of them you may have found one that snuck through.
The problem with adding a potentially long prefix (the options page slug) to an option_name value is that by default option_name in WP is limited to 64 characters.
This might not be a problem in a lot of cases, but when added to the way that repeater fields, or nested repeaters are stored it can become a problem that I’ve actually run into when building custom plugins and themes using ACF, and that’s without including a prefix for the options page name.
You don’t. All options field names must be unique because they are saved in the “wp_options” table. The field name becomes the “option_name” value.
Basically you need to duplicate the field group and then manually modify the field names of all the fields for each options page
I have created an options page adder that includes a field group duplicator to do this automatically that I’d like input on if you care to try it.
So what I’m getting is, you have unlimited use of ACF Pro but when you include it into a premium theme, you can not include the license (obviously) and people will need to buy their own license in order to get updates? Is that correct?
I think it works.
That I’m not sure about. I suppose it’s partly to do with what will be used by the most people. I like the add-on system because helps keep the core plugin lighter. I honestly don’t like using plugins that try to cram everything possible in because they start to get bloated. While I use things like the repeater field on almost every site I build, I’ve only needed to allow the selection of menus on 1 of the many sites I’ve built.
Yes, it is, you just need to use correct value for “parent” More information here: http://www.advancedcustomfields.com/resources/acf_add_options_sub_page/
For example: if the CTP slug is “my-post-type” the the value of parent would be “edit.php?post_type=my-post-type”
Or if I might plug my add on 🙂 https://github.com/Hube2/acf-options-page-adder
There is currently an add on in the WP repo for this, just updated to work on V5.
Both are possible, you just need to specify the correct parent
Below appearance set the parent = themes.php
or you can use my add-on plugin that lets you add options pages through an admin interface: https://github.com/Hube2/acf-options-page-adder
I’m currently looking for feedback on a new version that also duplicates field groups for use on multiple options pages: https://github.com/Hube2/acf-options-page-adder/tree/Fieldset-Duplicator
Try the get_current_screen() function. http://codex.wordpress.org/Function_Reference/get_current_screen. Not sure that’s the answer, but it may be a place to start.
If any are interested, I’ve finished adding field group duplicators to my options page adder plugin. I would be interested in any feedback or bug reports before I merge it with the master repo. The duplicator basically does all the work of renaming all the fields and other necessary changes so that you can use the same field group multiple times and all of them will be automatically updated if there are changes in your master copy of the group.
If you’re interested, I’ve finished adding field group duplicators to my options page plugin. I would be interested in any feedback or bug reports before I merge it with the master repo. The duplicator basically does all the work of renaming all the fields and other necessary changes so that you can use the same field group multiple times and all of them will be automatically updated if there are changes in your master copy of the group.
I know this is not a help right now, but I see the same issues with the way other ML plugins work.
I am in the process of building a multisite plugin that works completely different to the way the standard WP multisite setup works. My idea is that you edit a single page that can appear on multiple sites and that you can specify alternate content to appear on each of those sites. One editor == multiple pages with different content. My plan is to also create a “Multilingual” addon. My idea will require the use of sub-domains for creating each language site and will not support a sub-folder structure for languages.
But, I am building this plugin using ACF to build it and it takes into account all the things that ACF does specifically. Since I’m using ACF to do the building it will always need to be up to day with what ACF is doing.
I also plan on it being extremely focused, I’m not going to be building in any extra fluff. The reason is that I’m building my plugin to be an aid in developing sites and assume that it will be used mostly by developers that can handle adding what they need. Just the backbone that makes the whole multisite thing work.
Like I said, not much help today. But I too do nothings without using ACF to do it and the fact that most of the other plugins available to not work and play well with ACF is a huge issue for me.
If you can get to the page by typing in the URL then the developer that built the site has hidden the menu I do this all the time to prevent clients that don’t know what they’re doing from massing about with the field groups I’ve set up.
Like I said, there are several ways that hiding the menu can be accomplished. One is with code in your theme’s functions.php file.
Another way is to install an advanced permissions plugin. You may be listed as an admin but you many not have all the permissions of an admin and you wouldn’t be able to see the settings for the permissions plugin to find this out.
If you really need access to it you should probably contact the developer that built the site and ask them how they’ve hidden it.
Thanks E, actually it answers most of them. As a heavy user of ACF, there is little that I do that I don’t turn to ACF for a solution. I’m currently working on a plugin that I eventually see being a premium plugin and I have been debating whether or not I should think of including ACF or just stating that it’s required and pointing to your site where they can get it.
As a developer, I’m never usually happy with bundled plugins because they are difficult to update. A recent and serious security issue with one premium plugin in particular made me question the idea of bundling plugins even more.
I’ve got some time to think about it so I’ll probably let the idea stew in my head for a while longer before I decide.
I don’t have a lot of experience with different multilingual plugins. I do know form a bit of working with WPML and digging into things that it has problems with causing a site to be extremely slow with many languages. I also ran into problem recently with crons failing due to PHP errors.
Do a search of your theme template for hooking into the admin menu. Something like:
Then look at any functions that are hooked.
This may be a pain, but you can usually get to the ACF page by entering the URL directly in the location bar:
If you can’t access it that way then the permissions needed to access the page have been changed for your user type. Maybe there is a plugin installed that adds controls for who can access what.
The custom fields menu item can be hidden. This can be done in several ways and it is done in the code of the site.
There is the ACF filter, explained here: http://www.advancedcustomfields.com/resources/how-to-hide-acf-menu-from-clients/
There are also other ways that the menu can be disabled or hidden. This is generally done so that clients do not have access to mess about with things they probably shouldn’t be messing with.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!
© 2022 Advanced Custom Fields.