-
-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RunwayRoutes trait throws a "Maximum call stack size" exception #420
Comments
Are you using the |
What does your migration look like? Do you have a |
In my real project I do have a slug |
Do you get the same error when creating models with the |
After some tests I found out that the exception only occurs if the In my case the user has the possibility to set the slug manually. If it's not set, in the life cycle event But the content of the I have to use this workaround: Get all attributes with |
Thanks for doing some digging! Runway's The We do need the |
Description
If a model uses the trait
RunwayRoutes
, an existing (also a not existing) attributeslug
cannot be accessed without crashing the entire application.With
PHP 8.2.15
the application simply exits without an error message.With
PHP 8.3.0
the exceptionError Maximum call stack size of 8355840 bytes reached. Infinite recursion?
is displayed.Steps to reproduce
4.47.0
statamic-rad-pack/runway
package with composer (6.0.5
)RunwayRoutes
trait to the existingUser
model$user = new App\Models\User()
$user->slug
Environment
Environment
Application Name: Statamic
Laravel Version: 10.43.0
PHP Version: 8.2.15 / 8.3.0
Composer Version: 2.5.5
Environment: local
Debug Mode: ENABLED
URL: statamic-runway.test
Maintenance Mode: OFF
Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: NOT CACHED
Drivers
Broadcasting: log
Cache: statamic
Database: mysql
Logs: stack / single
Mail: smtp
Queue: sync
Session: file
Statamic
Addons: 1
Antlers: runtime
Stache Watcher: Enabled
Static Caching: Disabled
Version: 4.47.0 Solo
Statamic Addons
statamic-rad-pack/runway: 6.0.5
The text was updated successfully, but these errors were encountered: