Tagify not working again after their last cdn update

Wappler General Bugs
9

Here is a workaround to prevent Wappler from overwriting your custom script version for tagify:

Add your custom tag:

<script src="http://unpkg.com/@yaireo/tagify@4.15.2" defer=""></script>
 <link rel="stylesheet" href="https://unpkg.com/@yaireo/tagify/dist/tagify.css" />
 <script src="/dmxAppConnect/dmxTagify/dmxTagify.js" defer=""></script>

Now Wappler will automatically add

<script src="http://unpkg.com/@yaireo/tagify" defer></script>

Since the application logic looks for missing packages and compares the source, it doesn’t compare the type, though, so you can disable Wappler’s additional source by adjusting the script type:

<script type="application/json" src="http://unpkg.com/@yaireo/tagify" defer></script>

So the entire code to load only v4.15.2 would be:

 <script src="http://unpkg.com/@yaireo/tagify@4.15.2" defer=""></script>
  <link rel="stylesheet" href="https://unpkg.com/@yaireo/tagify/dist/tagify.css" />
  <script src="/dmxAppConnect/dmxTagify/dmxTagify.js" defer=""></script>
  <script type="application/json" src="http://unpkg.com/@yaireo/tagify" defer></script>

It’s not the most elegant solution and is a little hacky, but better than modifying the code with a third-party code editor after every page update and before every deployment.

This won’t be needed anymore when Wappler allows custom script sources.

3 Likes