Problem running plugins on MacOS

[DiapDealer]

You're not downloading an official release asset from my github repository. You're downloading some sort of branch source archive. The download from the plugin's thread here at Mobileread is identical to the one from the latest release on github.

But Sigil will not let you install a plugin whose internal folder name does not match the plugin name. So something strange is still happening here.

[DiapDealer]

I've doubled checked the official release of DOCXImport_v0.2.8.zip from its GitHub release page (https://github.com/dougmassay/docxim...eleases/latest) against the DOCXImport_v0.2.8 from the plugins thread here at Mobileread (https://www.mobileread.com/forums/sh...d.php?t=273966), and the zip archives are identical. The question becomes what you are doing in order to get a malformed/misnamed zip archive installed as a plugin with Sigil's official 'Add Plugin' feature, which will resist installing plugins that don't meet strict naming and structural requirements.

Are you manually modifying the zip you're mistakenly getting from github in order to get it to install, or are you unzipping and manually moving its contents into the plugins folder of Sigil's preferences location?

[BBouy]

I changed nothing on the ZIP file or the corresponding folder.

I used the Github file in your post here in the forum.

https://github.com/dougmassay/docximport-sigil-plugin

[KevinH]

Ah, you did not actually go to Releases on that page and instead used the Code menu there to get a zip of the source. But how did you install it?

[BBouy]

Preferences >> Plugins

Added the ZIP file.

[DiapDealer]

Yes. Your picture indicates your are downloading a source archive from Github and not an actual release of the plugin.

But again.... It is impossible to install what you downloaded via Preferences >> Plugins >> Add Plugin. Sigil simply won't allow you to install that incorrect zip file. Not without a lot of renaming and restructuring. I just tried it. It doesn't work.

[DiapDealer]

Actually, I must apologize. Sigil IS allowing incorrectly named/structured zip archives to be installed via Add Plugin. It doesn't show up in the list of plugins immediately after adding, but it will be there the next time Sigil is restarted. What's more, the invalid plugin cannot be removed by normal means. Once Sigil is restarted, it will still be there.

This is a bug that needs fixing. Again... apologies. And thank you for bringing this to our attention.

[DiapDealer]

Hmmm.. might not be a bug. But it's still not right. I could have sworn we had more validation than a base_name that doesn't already exist and the presence of a plugin.xml file. @Kevin: didn't it use to check that the name in the plugin.xml matched the folder name and the base name of the zip file?

EDIT: Nevermind. Now I see. The base name of the zip (minus any version info) is checked against the internal folder name to see if they match. If they do match, and a plugin.xml file is present, then Sigil sees the plugin as valid. Which means downloads of branch sources from my github plugin repositories are going to be considered valid. At least for installation purposes. But not for running or removal purposes. That's unfortunate.