Alex Joffroy

Using Nginx, I fixed the issue in my site config (thanks to @gauravmak 's link). ``` if ($request_uri ~* "^(.*/)index\.php(\/?)(.*)") { return 301 $1$3; } ```

Hi :) Tests seems ok, even in 5.4, no ? https://travis-ci.org/eusonlito/laravel-Meta/jobs/383735080 Anyway, when I submitted my PR, I have a fork from commit 51f0b44979d700035eba9c9cd318f33411ba014e, tests were failing with my php...

Yes, when using the Facade to set the meta, it works: no problem with that. My issue is when I try to resolve the Meta object from the container, as...

Ok, I finally managed to make it work. I missed a `composer dump-autoload` after manually editing `MetaServiceProdvider` in my vendors. Will soon submit a PR to fix this :)

@jeremymlane @nilportugues Are you working on something about this ? Indeed, I ran into a similar problem, and it could be great to have optional fields others than timestamps.

Hi, thanks for reporting the issue. I guess it comes from an update in React core. If you (or someone) want(s) to contribute, I'll accept a PR fixing this.