Closed henninghorn closed 7 years ago
Hi @henninghorn not really sure how you reproduced this issue. Did you search for "John" in your Users
collection panel?
It seems that the generated MySQLÂ query does not have a limit
to come with the offset
.
I feel like this is the issue.
Hi @arnaudbesnier
Ah, sorry. Basically I had created two models, User and Event.
I had created 25 random users (through database seeding). I then went to Forest Admin and confirmed that these users could be seen. Then I went into "Events" (in Forest) where I created an event. Afterwards I wanted to add a relationship to one of the 25 created users. Forest picked up the relationship between Users and Events, so I clicked "Add existing user" and I was presented with a search field, and this is where the error appeared.
Basically the same view like this (from your Live Demo):
This works fine on your demo, but the Laravel implementation doesn't work.
Perfect I know how to reproduce now!
Hi @henninghorn , this is fixed in the new 0.0.19 Forest version.
@arnaudbesnier Great, thank you very much!
Hi @henninghorn ,
The brand new Laravel agent for Forest Admin is available here: https://github.com/ForestAdmin/laravel-forestadmin
As we now have a team of dedicated developers for this new Laravel agent, be sure Forest Admin will provide a much better Laravel support experience compared to the one you had in the past for v1.
Forest Admin also evolved a lot in 4 years as an internal tool platform, don’t hesitate to give it another try, you should not be disappointed 🌲🌲🌲
Best Regards.
When editing a model which has a belongsToMany relation to another model, the built-in search feature doesn't work.
It fires off a search query but response is always HTTP 500: