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

Remote Images #30

Open
nilshoerrmann opened this issue Jun 12, 2015 · 7 comments
Open

Remote Images #30

nilshoerrmann opened this issue Jun 12, 2015 · 7 comments
Assignees

Comments

@nilshoerrmann
Copy link

This is a feature request:
Would it be possible to make this field handle remote images?
Sounds strange? Okay …

The Background

We have a site that grabs Facebook feeds and imports entries using XML Importer. Due to the way Facebook handles their media attachments, links to images change after a while which results invalid references in our imported entries. If we could store a copy on our own server, everything would continue to work as expected.

The Idea

If the extension receives a link to a remote ressource instead of a local image, it first stores a copy on the server and then continues as usual.

@nitriques
Copy link
Member

I like that.

A "from url" option would do the trick.... Do you have ideas UI-wise ?

@nitriques nitriques self-assigned this Aug 10, 2015
@nilshoerrmann
Copy link
Author

I'm not sure if a UI is a good idea because this niche feature would bloat the interface visually. If an UI is desired, I'd stick to something simple similar to Google's image search: a tab switch between a file input and a text input.

But I really thought of this as a UI-less feature: something documented that works under the hood but isn't exposed in the backend itself. The reason behind this is that the primary function of this extension is managing local files and my request is just about making files local in case they are hosted externally.

@nitriques
Copy link
Member

Ok great, thanks for sharing your ideas.

I would definitivly make the remote image local (so the only difference would be the first time). But I wonder how to expose this to user... and I think we should be able to disable it on a per field basis.

How would it work if there are no UI ?

@nilshoerrmann
Copy link
Author

Quite simple: if the POST data contains a remote file, the field copies it first to the specified local folder and then proceeds as usual. Nothing else.

This'll make remote files work with any kind of field import (custom ones as well as XML Importers) and it'll allow other extensions to add a special UI for remote files on top of the default one using JavaScript if needed without bloating this field's UI. Thus, the normal user wouldn't notice anything at all, it would be an advanced feature.

@nitriques
Copy link
Member

Ok but how do I input the remote file's url ? Only via code ?

@nilshoerrmann
Copy link
Author

Using "a third party", either a custum script or extension, yes.

@nitriques
Copy link
Member

Ah now I get it. Yeah, support would be easy to add. But I feel like I'd still like a UI for that (but as I said, it must be opt-in)

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

No branches or pull requests

2 participants