Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check/display new or existing files/medias in page #2410

Open
bonnebulle opened this issue May 10, 2024 · 0 comments
Open

Check/display new or existing files/medias in page #2410

bonnebulle opened this issue May 10, 2024 · 0 comments

Comments

@bonnebulle
Copy link

Hello everybody
Am working with the grav-plugin-admin web interface
but some time am using the "folder way" to edit / add contents
and so for images / medias !
For example I can drag-n-drop file directly into pages/test_page/image_1.jpg

But files I add ( in the folder/manual or admin way )
dont appears into the admin/edit page ! 😢

The filepicker show me them, cool
... but, it would be much more easier to show the new added files
directly after/in/under the media field ("media" in blueprint)

( like when I upload some )
( but for already existing ones )
image

My blueprint :

            media_files:
              type: file
              label: Médias
              multiple: true
              destination: 'self@'
              random_name: false
              avoid_overwriting: false
              limit: 10
              accept:
                - image/*

Some links I follow ( much more about filepicker / pagemediaselect )


So my question is, for now :
How do the admin-plugin is "searching"/"scanning" for new media files ?
What it the task trigger ? Can I force this process to start ?

I follow this question :
task.addmedia
https://discourse.getgrav.org/t/issues-with-page-media-in-admin-task-addmedia/1311/6

Maybe using an other cron / routine task ?

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant