Change status/Delete page: Error = Nesting level too deep - recursive dependency?

For a few time now, when:

  • I delete an unlisted sub-page from my panel
  • Change the status of a sub-page from draft to unlisted in the panel or programmatically

I’ve got this error:

Nesting level too deep - recursive dependency?
Whoops\Exception\ErrorException ...kirby/src/Toolkit/Collection.php:917

I’ve tried without plugins > error message still appears.
I’v got around 600 sub-posts. when I delete few of them (60-70), the error message disappears.

What do you think? could it be limits set in my PHP config file? I left the default ones.

Hm, this obviously occurs when sorting the collection in kirby/src/Toolkit/Collection.php:917

// array_multisort receives $params as separate params

But I don’t know how to solve that.

What is your memory_limit set actually set to? Does increasing it have any effect?

This is my php.ini settings:

max_execution_time = 30
max_input_time = 60
memory_limit = 128M

I going to increase memory_limit to 256M and see … let me few minutes :slight_smile:

I have restarted php-fpm after increasing memory_limit to 256M but still have the error message

Hm, I have no idea if this is a problem with your server settings or something else.

Maybe you can post more details about your server setup, PHP version, Kirby version, server etc.

Yes of course.

My server setup:

  • Host = Vultr VPS Ubuntu 512M Ram
  • Web server = Caddy
  • PHP-FPM 7.2 (memory_limit to 256M)
  • Kirby 3.1.3
  • Number of pages > 600

I will see if I can set up another server with another environment (Apache or Nginx) and check if I can reproduce this error message.

This might be unrelated to your issue but i’ve seen that recursive error recently and the cause was having two blueprints with different file names, but with the same title set in the yaml. Are you sure all your blueprints are unique?

Thanks @jimbobrjames for your suggestion to check my blueprints title but each of them has a unique title.

I’ve set up a LAMP server on a new VPS and download my website on it > no error message anymore!

So the problem should maybe come from my server config? :-/

Update: very weird, today the error message also disappears on my Caddy server installation …

Hm, maybe a weird caching issue after all?