[5.x] Prevent error when redirecting to first asset container

[duncanmcclean]

This pull request prevents a Call to undefined method Closure::first() error from happening when redirecting to the first asset container.

Sometimes, due to how the CP Nav gets cached, a nav item's children property may be a closure. In our case, we can simply call ->resolveChildren() to ensure a nav item's children are "resolved" before we get them.

Fixes#10520.

[duncanmcclean]

This pull request prevents a Call to undefined method Closure::first() error from happening when redirecting to the first asset container.

Sometimes, due to how the CP Nav gets cached, a nav item's children property may be a closure. In our case, we can simply call ->resolveChildren() to ensure a nav item's children are "resolved" before we get them.

Fixes#10520.

[duncanmcclean]

This pull request prevents a Call to undefined method Closure::first() error from happening when redirecting to the first asset container.

Sometimes, due to how the CP Nav gets cached, a nav item's children property may be a closure. In our case, we can simply call ->resolveChildren() to ensure a nav item's children are "resolved" before we get them.

Fixes#10520.

[duncanmcclean]

This pull request prevents a Call to undefined method Closure::first() error from happening when redirecting to the first asset container.

Sometimes, due to how the CP Nav gets cached, a nav item's children property may be a closure. In our case, we can simply call ->resolveChildren() to ensure a nav item's children are "resolved" before we get them.

Fixes#10520.

[duncanmcclean]

This pull request prevents a Call to undefined method Closure::first() error from happening when redirecting to the first asset container.

Sometimes, due to how the CP Nav gets cached, a nav item's children property may be a closure. In our case, we can simply call ->resolveChildren() to ensure a nav item's children are "resolved" before we get them.

Fixes#10520.

[duncanmcclean]

This pull request prevents a Call to undefined method Closure::first() error from happening when redirecting to the first asset container.

Sometimes, due to how the CP Nav gets cached, a nav item's children property may be a closure. In our case, we can simply call ->resolveChildren() to ensure a nav item's children are "resolved" before we get them.

Fixes#10520.

[duncanmcclean]

This pull request prevents a Call to undefined method Closure::first() error from happening when redirecting to the first asset container.

Sometimes, due to how the CP Nav gets cached, a nav item's children property may be a closure. In our case, we can simply call ->resolveChildren() to ensure a nav item's children are "resolved" before we get them.

Fixes#10520.

[duncanmcclean]

This pull request prevents a Call to undefined method Closure::first() error from happening when redirecting to the first asset container.

Sometimes, due to how the CP Nav gets cached, a nav item's children property may be a closure. In our case, we can simply call ->resolveChildren() to ensure a nav item's children are "resolved" before we get them.

Fixes#10520.