Issue: Field group limited to 20 entries

• James

• January 7, 2014 at 2:45 am

I need to build out a list of states as individual field groups. Everything was going swimmingly until I hit 25 and updated. For some reason the last five entries were gone. I added three more and hit update… back to 20…

http://i.imgur.com/rL4l8WV.png

I’ve set my max_input_vars to 3000, though it didn’t fix the issue.

These happen to be repeater fields — could that be the issue?

Are field groups limited to 20 entries? If so, how do I bump that up… I need at least 50…

Any help is appreciated, thanks 🙂

• Will

• January 7, 2014 at 8:53 am

Wordpress limits to 30 by default. See the source here:
https://core.trac.wordpress.org/browser/tags/3.8/src/wp-admin/includes/template.php#L556

add_filter( 'postmeta_form_limit' , 'customfield_limit_increase' );
function customfield_limit_increase( $limit ) {
    $limit = 60;
    return $limit;
}

in your functions.php should set you up.

• Elliot

• January 7, 2014 at 4:11 pm

Hi @James

There is no limit for saving fields in a field group.
Each time you save, all fields are updated and this requires PHP memory, vars, database calls and time.

It is possible that your server is not allowing the sufficient resources needed for the save to complete. The max_vars is a good place to start, but it is important to make sure that this value is being used by your server. Please google how to test server info such as max_vars.

Here are some similar threads:
http://support.advancedcustomfields.com/forums/topic/field-group-not-accepting-more-than-69-fields/
http://support.advancedcustomfields.com/forums/topic/is-there-a-limit-on-fields/

Hope that helps.

Thanks
E

• James

• January 7, 2014 at 4:20 pm

I’ve added these two bits to my functions file:

//raise custom field limit
function customfield_limit_increase( $limit ) {
    $limit = 60;
    return $limit;
}
add_filter( 'postmeta_form_limit' , 'customfield_limit_increase' );

//raise post per page count for advanced custom fields
function customize_admin(){
    global $per_page;
    global $post_type;
    if( $post_type == 'acf' ) $per_page = 500;
}
add_action('admin_head', 'customize_admin');

and also raised my max_vars to 3000 (it was 1000)
http://i.imgur.com/7TWSvld.png

Unfortunately, it’s still only showing/accepting 20 entries.

I’ll keep at it, but I’m still open to suggestions.

Thanks again 🙂

• Elliot

• January 7, 2014 at 4:49 pm

Hi @James

ACF doesn’t use the standard WP form, so the ‘postmeta_form_limit’ shouldn’t be an issue (unless i’m missing something).

Your best bet is to check your server logs for any hints as to server failure during the save.

Like I said, The max_vars is a good place to start, but it is important to make sure that this value is being used by your server. Please google how to test server info such as max_vars.

Good luck

Thanks
E

• James

• January 8, 2014 at 3:09 am

I’m getting this in my log:

[07-Jan-2014 08:06:21 America/Los_Angeles] PHP Warning:  PHP Startup: homeloader: Unable to initialize module
Module compiled with module API=20060613
PHP    compiled with module API=20090626
These options need to match
 in Unknown on line 0
[07-Jan-2014 08:06:21 America/Los_Angeles] PHP Warning:  PHP Startup: PDO: Unable to initialize module
Module compiled with module API=20060613
PHP    compiled with module API=20090626
These options need to match
 in Unknown on line 0
[07-Jan-2014 08:06:21 America/Los_Angeles] PHP Warning:  PHP Startup: pdo_sqlite: Unable to initialize module
Module compiled with module API=20060613
PHP    compiled with module API=20090626
These options need to match
 in Unknown on line 0
[07-Jan-2014 08:06:21 America/Los_Angeles] PHP Warning:  PHP Startup: Unable to load dynamic library '/usr/local/lib/php/extensions/no-debug-non-zts-20060613/sqlite.so' - /usr/local/lib/php/extensions/no-debug-non-zts-20060613/sqlite.so: undefined symbol: third_arg_force_ref in Unknown on line 0
[07-Jan-2014 08:06:21 America/Los_Angeles] PHP Warning:  PHP Startup: pdo_mysql: Unable to initialize module
Module compiled with module API=20060613
PHP    compiled with module API=20090626
These options need to match
 in Unknown on line 0

Google lead me here:
http://stackoverflow.com/questions/2394532/apache-is-unable-to-initialize-module-because-of-modules-and-phps-api-dont

I’ll give those suggestions a try and will post back if I get it working.

• Tim Triplett

• January 8, 2014 at 10:03 am

I’m having a similar situation with repeater fields. There’s a limit to how many repeater fields in a row I can use before they stop saving. I used a custom php.ini in the site root to do the following:

> php_value max_input_nesting_level 128
> php_value max_input_time 300
> php_value max_input_vars 3000
> php_value max_execution_time 300
> php_value post_max_size 32M

But this did not fix the problem. I’m going to try to boost the max_input_vars to higher.

• Tim Triplett

• January 9, 2014 at 12:28 am

I also tried setting the following because my server is using the Suhosin patch, but it did not fix the problem.

suhosin.post.max_vars = 20000
suhosin.request.max_vars = 20000

• Tim Triplett

• January 9, 2014 at 9:14 am

I’ve increased the value for the max_input_vars to 8000, and the problem is still not resolved. Can you give me any other direction to take?

• Elliot

• January 9, 2014 at 10:38 am

Hi guys

The quickest way to solve this issue is to contact your web host and clearly explain the issue. Ask them why the save process would be timing out. They will be able to instruct you as to what needs to be increased.

Thanks
E