For anyone else who finds this rolling back the version will work. But if you want to take advantage of the new functionality of the laravel-localization package you can change 2 files and add 1 file as outlined here.

https://github.com/AsgardCms/Platform/pull/670

@kenmonster you can edit the admin-bar partial template in the theme to give it more logic.

bump

How can you extend the form views in Page and User modules now that they are all ajaxy with Vue

When using built in relationships you don't need the get() or first() methods.

Also you can see $self is being passed in. $this is out of context you want to use $self.

return $self->belongsTo(\Modules\Brokerquotes\Entities\Insurer::class, 'user_id', 'id');

Try this URL in the front end:

/blog/posts

@chiragpipariya It is using Vue.js to load the data.

This is almost for sure git changing your line endings in the font files (.woff and so on) and will likely break again when you do another push/pull in git. Your browser will keep good ones cached so you may not see broken ones if you have pushed, but new users will likely see the broken icons.

Because these are binary files, when git changes the line endings it breaks the fonts.

You will have to get a good copy of the fonts again then add this to your .gitattributes file

*.otf binary
*.eot binary
*.svg binary
*.ttf binary
*.woff binary
*.woff2 binary

This tells git that the files are binary and it won't try to change the line endings anymore.

@arocca

The only way that could happen is if you changed the secrect_key in the .env file. if the secret key changes it can't decode the password.

@kenmonster

try adding a backslash in front

\LaravelLocalization

@kenmonster It can support it if you want to mess with the Authentication module. Maybe look at JWT.