salaros

OK, I got rid of the limit. It was actually a php.ini entry, but one called max_input_vars. I suppose that by raising its value you allow PHP to post longer input variables (arrays), in your case wrgf_image_url[], wrgf_image_url2[], ..
Thanks for pointing out possible php.ini config issue.

I have just tested post_max_size set to 40M, the result is still the same – max 158 images. I’ve inserted a phpinfo();die; into the function which persists the $_POST content (BTW it’s few KBs of text, just like I said before).

I my case $TotalImages = count($_POST['wrgf_image_url']); is always = 158

Currently I have post_max_size, upload_max_filesize set to 30M + some other params such as max_execution_time in order to upload big images on slow connections.
I will test it on a local server, but I don’t get why post_max_size should influence the serialized image info.
I mean once I’ve uploaded the images into the native WordPress Media, I just have to create a set of those images and post their names/paths + some additional pieces of data to the script which persists them as post meta inside the DB.
These serialized meta values are just few KBs, so IMHO there is no need for “big” values of post_max_size