laravel-medialibrary VS nova-flexible-content

I have it working ok for a single image using this idea but need the user to be able to add multiple images.

The current version as of writing this is 10.5.2 released 8 days ago.

Use this, i use it in all my projects.

An example of a good use of a polymorphic relationship can be seen in the Rails Active Storage module, which allows you to attach files to a model, and instead of duplicating the database columns and tables for each model that has attachments, there are two general tables: activestorage_attachments (attachments; relationship info) and activestorage_blobs (blobs; file info). A model can have one or many attachments (has_one_attachment and has_many_attachments, both can be used more than once depending on your needs), an attachment belongs to a record (record_id and record_type) and belongs to a blob (blob_id), and blobs have one attachment. You can access an attachment attribute on the related model like so, user.avatar # has_one_attachment(:avatar); or for many attachments of the same type, user.photos # an array of attachments; has_many_attachments(:photos). There’s a Laravel package similar to this called spatie/laravel-medialibrary.

For storing files and associating them with models, I can highly recommend Spatie's Media Library. Used it in a project recently and haven't had any hassle with it.

I've gotten close using the above inside a whitecube nova-flexible-content repeating field, but that's not storing the image for me like it does when using a single Nova image field.

I realised that Nova Flexible Content does most of what I needed – define layouts, add them, rearrange them etc. It was just missing the visual preview bit. So I started experimenting and quite quickly I was sending the layout data to the server and getting back rendered Blade views populated with that data. I opened a PR just to share my progress and I've been updating it to share my progress.

So I have a package I installed called https://github.com/whitecube/nova-flexible-content for Nova - I did the composer require whitecube/nova-flexible-content and everything works without an issue - it's live and working fine - problem comes when I want to edit it - since everyone here is adamant editing in vendor folder is wrong as it will overwrite on composer update I tried to do what I did with another package using isntructions here:

So... long story short I'm trying to fork a Laravel Nova custom field - long story but here's my composer.json file - https://gist.github.com/HeadStudios/cce18add25b48693d2416e651239efcd - now if you see here - I've "tried" to pull from the github fork I created here: https://github.com/HeadStudios/nova-flexible-content.git .. which by the way is a fork of nova-flexible-content here: https://github.com/whitecube/nova-flexible-content ... now.. I know when I just do a naked composer require whitecube/nova-flexible-content (without having my github require)... all my namespaces work.. as soon as I try to pull with my github definition.. which I imagine may not work because I haven't got that psr-4 which I don't know how to setup... forgetabout it... no namespaces are being found so... I'm navigating in this trench and if anyone has any input it would be much appreciated.

Hey, so.. I have a folder in vendor in my Laravel Nova which is the whitecube flexible repeater field (here: https://github.com/whitecube/nova-flexible-content).... works great but... I need to make some modifications to it (long story). Anyway... people keep saying don't touch the vendor folder so... I guess i have to fork the repo then pull it then composer require.. has anyone ever done this... like because I check composer.json and composer.lock and they have various values for the other fields I created (custom laravel nova fields in nova-components) - so my question is... what would be the step by step process to move a vendor folder into the nova-componetns folder for custom field so it all works with compiling and being seen and all that... hope that makes sense. Thanks!

Github Ticket:https://github.com/whitecube/nova-flexible-content/issues/392

So... I have a Laravel nova extension called flexible fields - handy Github link here: https://github.com/whitecube/nova-flexible-content - this is for Laravel Nova and allows you to have repeatable fields (very useful). I'm setting up a templating system with a new nova-component field where the user can select a drop down and it populates a bunch of fields.. now I have this written because populating static text fields is pretty straightforward right - the challenge comes with 'clicking' on the Add Layout button and then populating the repeater field groups - like I might want to add 5 repeater groups. Does that make sense?

I've got this amazing repeater field thingie from whitecube - https://github.com/whitecube/nova-flexible-content - obviously Vue stuff that gets installed but... well... I want to create (and populate) repeater sections based on click in another Vue component (it's like a templating thing - so I can have templates)... just thought it would be cool.... how... would I do that? I'm guessing you guys want more details right?

So I got this amazing Laravel Nova extensions https://github.com/whitecube/nova-flexible-content - so it's a repeater field for Laravel Nova - works great etc. Now.. here's the challenge. I want to be able to do a (proof of concept) of being able to add repeater rows through some kind of... code so for example let's say I have a repeater with 3 fields in a record of Campaign class... and I want to add these records through code.. I've tried everything and it hasn't worked for me. I'd love for any input on how I could do this or a concept I could test or suggestions.