vue-email-editor icon indicating copy to clipboard operation
vue-email-editor copied to clipboard

Custom Image Library not working

Open NaturalDevCR opened this issue 1 year ago • 5 comments

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.

NaturalDevCR avatar Oct 26 '24 11:10 NaturalDevCR

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.

daniesy avatar Oct 29 '24 00:10 daniesy

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.

NaturalDevCR avatar Oct 30 '24 23:10 NaturalDevCR

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

Czy1307 avatar Nov 15 '24 13:11 Czy1307

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 avatar Nov 15 '24 14:11 NaturalDevCR

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.

NaturalDevCR avatar Nov 18 '24 06:11 NaturalDevCR