profmikebroyles

This is just my opinion, but it’s not a good idea to go backwards in your deployment just so a plugin will work. For security purposes, it is very important to always be up to date on WordPress core.

No one else experiencing this challenge?

I actually was able to get a hold of him via Twitter. He is saying that he might have time to get a fresh release out that is compatible with WP 3.3.1.

I will have to look around more.

Have we had any clarity on the GPL vs. Non?

Personally, I think it’s difficult (at best) to attempt to release non-GPL code when you have to distribute the code as ‘uncompiled’ PHP.

3dperuna, I agree with you. If this plugin is not GPL, then it should be removed. If memory serve me correctly, I believe there is another site for paid WordPress plugins.

officeguy, I am looking into this as well. Not having much luck.

Let me know if you get things to actually work.

Is this plugin supported? I am going to track down the developer on twitter and find out.

…to be continued…

Well…it’s 9 months later, and I see no one has answered your question.

The only thing I can think to try is to not network activate it; but rather, activate it on a blog-by-blog basis.

I’ve noticed some plugins are not exactly network activation friendly…this very well may be one.

Let’s see if the actual developer chimes in…