`index` blade file with deeply nested model route binding not working

[laravel]

`index` blade file with deeply nested model route binding not working

[nunomaduro]

@vmiguellima Does your posts table have a user_id? And an user() relation?

[vmiguellima]

@nunomaduro The relation exists and it works correctly. Just tried again, and for example I'm able to access using the following paths:

• /users/1/posts/1/index (resources/views/pages/users/[User]/posts/[Post]/index.blade.php)
• /users/1/posts/1/view(resources/views/pages/users/[User]/posts/[Post]/view.blade.php)
• /users/1/posts/1/index (resources/views/pages/users/[.App.Models.User]/posts/[App.Models.Post]/index.blade.php)
• /users/1/posts/1/view(resources/views/pages/users/[.App.Models.User]/posts/[.App.Models.Post]/view.blade.php)

But through the use of the index balde is expected to access via:

• /users/1/posts/1

The problem is not related with namespaces, but with index blade file, when deeply nested.

Working:

Not working:

[robw-raviga]

I'm experiencing the same issue, I have Folio directory structure like this:

resources/views/pages/
- [year]/
  - index.blade.php
  - [month]/
    - index.blade.php
    - [date]/
      - index.blade.php
      - [Article:slug].blade.php

When I access /2023, I get a 404.
When I access /2023/09, I get a 404.
When I access /2023/09/08, I get a 404.

If I access /2023/09/06/it-works, I get the page loaded with $year, $month, $date populated and the Article is found successfully by it's slug.

It seems to be an issue resolving the index in those routes from variable part.

When I run artisan folio:list, all the routes show as expected