Chrome disabled it

Thank you for this report (and your review too!)

I’ve generally been using it on a Mac, so hadn’t come across this problem with Windows.

The reason I can’t just add it to the Chrome store is because each WordPress installation needs its own customized extension (CRX file), which you download from within WordPress. Otherwise, there would be no easy way to mark the extension as requiring web access to your specific WordPress site.

However, it should be possible to use the development features of Chrome to install the extension in a different way. Hopefully that won’t require users to switch to a completely different Chrome install.

I’ll take a look over the next few days and see if I can tweak things to give Windows users an easy way to install the extension without problems.

Thanks again!

Dan

I’ve had a further look into this issue on Windows, and it’s pretty depressing that Google doesn’t seem to offer any way to tell it you know what you’re doing and to please leave it alone.

Installing as a CRX (the current solution) is pretty bad – it will always disable the extension. You have to completely delete and reinstall to enable it again.

However, things are a tiny bit better if you try to install as a directory. So, the latest version of the plugin, 1.1, allows you to download the extension as a ZIP so you can load it into Chrome as a development extension.

That way, it will still warn you on Chrome load, but you can simply click Cancel to get it to leave things in place.

Sorry that things aren’t better here – Google seems adamant that there should be no way round this warning. I’ve no idea why it lets you install unauthorized extensions for the current session, and only complains when you restart.

Please let me know how you get on if you try it out this way!

Thanks,

Dan

Thanks for looking into this Dan. How long do you think until 1.1 is released?

You should be able to get it now!

Please take a look and let me know what you think.

Thanks,

Dan

It’s working for me, thanks!