RichEditor not working after update to Filament V4
I'm using standard RichEditor and after updating everything from Filament V3 to Filament V4 I'm getting this error in console when I open modal with RichEditor inside and my content doesn't get pasted in, any ideas?
Not sure where to even begin figuring this one out.
->schema([
TextInput::make('name')
->required()
->maxLength(255),
RichEditor::make('content')
->required()
->label('Test Editor')
Solution:Jump to solution
I did solve it, but no idea why. I went to another branch to fix something, went back to the branch where I'm updating to filament v4 and then ran composer update, npm install, npm run build and npm run dev again and now it works.
6 Replies
I did some more digging and I can see I'm still serving old rich-editor.js from public/js/filament/forms/components/rich-editor.js instead of TipTap rich-editor.js for filament v4 that I have in vendor/filament/forms/resources/js/components/rich-editor.js along with a lot of other files.
There's still a ton of other files in my public/js/filament from V3 I guess, what do I do with this situation now? This isn' exactly automatically solved by running commands.
php artisan filament:assets should publish the new assets. If you're behind a CDN, clear cache there too.Remove them and run
php artisan filament:assets to republish them.@borg @Dennis Koch still same problem.
Well it is obvious that the assets are still the old ones. I'm lacking information about your project, but publishing the new ones should work. You should also have a lot of changes if you use GIT, because of the newly published assets.
maybe you have a filesystem issue, or the mounted files are not refreshing to your docker, who knows what setup you're running
maybe delete the already published assets inside your public directory and run the command again
Solution
I did solve it, but no idea why. I went to another branch to fix something, went back to the branch where I'm updating to filament v4 and then ran composer update, npm install, npm run build and npm run dev again and now it works.