-
Notifications
You must be signed in to change notification settings - Fork 752
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
Api call happening on using registerCallback images #337
Comments
We use it this editor for private mailers and don't want anything to go to any external service, currently unlayer editor is making call for images. |
@adeelraza @lucasbesen @umairsiddique Is there any way we can disable these proxy calls happening because right now we are using custom image chooser where we are passing the image url back to done callback on registerCallback('images') Currently it is looking like things are unnecessarily making api call when they are not being used as well. or Is it a bug. Please help. |
I'm looking for the same issue Is there any way we can upload images to our domain and giver URL here? |
selectImage callback will place you in direct control of the image uploading and management. unlayer.registerCallback('selectImage', function (data, done) { |
to use your own storage you can use the "image" callback. const onReady = async () => {
..... <EmailEditor |
even when using the image callback for custom image handling, I observe that a request is still made to:
|
This call happens when you try to edit the image. This is because the image editor in browser does not allow CORS URLs so Unlayer has to proxy the image from our servers. Do you want to disable the image editor in the builder? |
Are you still getting the issue @greedysiru ? I am getting this issue. It was working fine, but now I noticed that the request is being made to unlayer. |
Why api call is happening to https://api.tools.unlayer.com/v1/image?url=customImageUrl
when using custom image library.
Is there any way to disable this call happening to unlayer server.
The text was updated successfully, but these errors were encountered: