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

Custom Image Library not working #110

Open
NaturalDevCR opened this issue Oct 26, 2024 · 5 comments
Open

Custom Image Library not working #110

NaturalDevCR opened this issue Oct 26, 2024 · 5 comments

Comments

@NaturalDevCR
Copy link

Environment:

  • "vue": "^3.5.12",
  • "vue-email-editor": "2.1.4",
  • "quasar": "^2.17.1",

Code:

<template>
  <EmailEditor
      :appearance="appearance"
      :locale="locale"
      :tools="tools"
      style="height: 700px"
      :min-height="minHeight"
      ref="emailEditor"
      v-on:load="editorLoaded"
      v-on:ready="editorReady"
  />
</template>

 <script setup lang="ts">

  const emailEditor = ref();

  const appearance = {
    theme: commonStore.isDarkMode ? 'dark' : 'light',
    panels: {
      tools: {
        dock: 'right',
      },
    },
  };
  
  const locale = ref('es');
  
  const minHeight = ref('700px');
  
  const tools = ref({
    textEditor: {
      spellChecker: true,
      tables: true,
    },
    svgImageUpload: true,
    sendTestEmail: true,
    image: {
      enabled: true,
    },
  });
  
  const editorLoaded = () => {
    console.log('editorLoaded');
  };
  
//This is NOT working anymore
  const editorReady = async () => {
    emailEditor.value.editor.registerCallback(
      'selectImage',
      async function (data: any, done: any) {
        console.log('SelectImage triggered ', data)
        await uploadImage().then((img) => {
          done({ url: img });
        });
      }
    );
  };

</script>

So basically the custom image library stopped working, I can't take full control of all Upload Image buttons in the editor as the unlayer documentation states it should be possible.

image

This stopped working even without any update, so not sure what's going on now, the callback it's not even triggering, there are no errors on the console.

I have tried with or without the project-id specified but still won't work.

Thanks in advance.

@daniesy
Copy link

daniesy commented Oct 29, 2024

I have the same problem.
Update: it seems that in the paid version this functionality is still working. Strange because it was supposed to be free.

@NaturalDevCR
Copy link
Author

NaturalDevCR commented Oct 30, 2024

I have the same problem. Update: it seems that in the paid version this functionality is still working. Strange because it was supposed to be free.

It is indeed suposed to be free, it was working before and the documentation doesn't indicate that is only for paid users.

There was another issue submited after this one, and that one was answered, I guess they just don't really care about the free features, or probably they removed this feature for free users with no warning.

@Czy1307
Copy link

Czy1307 commented Nov 15, 2024

I have the same problem. Update: it seems that in the paid version this functionality is still working. Strange because it was supposed to be free.

It is indeed suposed to be free, it was working before and the documentation doesn't indicate that is only for paid users.

There was another issue submited after this one, and that one was answered, I guess they just don't really care about the free features, or probably they removed this feature for free users with no warning.

They have enabled domain name verification, which needs to be configured in the account settings corresponding to the projectId

@NaturalDevCR
Copy link
Author

I have the same problem. Update: it seems that in the paid version this functionality is still working. Strange because it was supposed to be free.

It is indeed suposed to be free, it was working before and the documentation doesn't indicate that is only for paid users.
There was another issue submited after this one, and that one was answered, I guess they just don't really care about the free features, or probably they removed this feature for free users with no warning.

They have enabled domain name verification, which needs to be configured in the account settings corresponding to the projectId

I have tried adding my domain (which leads me to ask how I'm I supposed to work on localhost before deployment on this functionality) but anyway it's not working.

I get this on console:

422 (Unprocessable Entity) and 500 (Internal Server Error)

image

Also I did not see any indications that domain name verification should be enabled for this feature to work

@NaturalDevCR
Copy link
Author

NaturalDevCR commented Nov 18, 2024

So, it’s confirmed that you’ve made the Custom Image Library a paid feature. This isn’t reflected in the documentation, but it is mentioned on the pricing page. Honestly, this is a disappointing move. This feature doesn’t use any resources from Unlayer—it simply allows users to upload images to their own servers and manage them independently.

For small developers like me, who use this tool just to send a few emails, paying such a high price is simply not feasible.

I understand that you run a business, and many users already pay for your editor, which is arguably the best one available. However, removing free features that cost you nothing to provide, and doing so without any prior notice, feels unfair.

Changes like these make using your library much more difficult and frustrating.

Features like dark/light themes and the Custom Image Library should remain free since they don’t impose any costs on your end.

This decision, coupled with the lack of communication, was disappointing.

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

3 participants