Sugbo
Rich Editor - Displaying to Front-end
@awcodes
I notice that when I use the public local storage with
RichEditor::make('content')
In the 'content' field of blog table the following element exists:
<figure data-trix-attachment="" data-trix-content-type="image/png"></figure>
And that is why when I do {!! $blog->content !!} it is showing the image in the front-end. The element is responsible for referring to the location of the image in the storage.
However when I use s3 and modify the code as follows
RichEditor::make('content')
->fileAttachmentsDisk('s3')
->fileAttachmentsDirectory('attachments'),
The <figure></figure> element does not exist in the 'content' field of blog table and so no image is being displayed
Again the image is being stored in the folder livewire-tmp in S3 it is not being displayed on front-end
Kindly help bro. Thanks
8 replies
Rich Editor - Displaying to Front-end
Switched back my storage to public local storage. {!! $blog->content !!} actually works. But when I switch to s3 thats when the images are not showing up.
This is the code in the BlogResource
RichEditor::make('content')
->fileAttachmentsDisk('s3')
->fileAttachmentsDirectory('attachments')
What happens is that the image is stored in livewire-tmp folder in s3 but its not going to the folder 'attachments' . The image is not being displayed in the blade view, not even like the the attribute specified in 'alt'
8 replies
Rich Editor - Displaying to Front-end
Thats basically what I did. The image is what I am looking and putting it in the right spot when I display them. How Filament know which $blog model the images belong to and how do you call those images when you display them?. When you do {!! $blog->content !!} its only calling the text (at least ony my side)
8 replies