firebird75

Thanks Tobias, I appreciate the way you closed on the debate, it motivates me a lot to share my work with others…

Hi,

I didn’t thought I would have faced this kind of problems when I released my plugin. You are the first and only one who provided this kind of feedback, I am very surprised…

Having said that, few points :
1/ The WordPress site said : “Your plugin must be GPL Compatible”.
You can interpret this sentence in two ways. The first one is : “your plugin must be under GPL” and the second one is : “your plugin must be able to work together with GPL licensed S/W” which is the case for WordPress unless I am wrong so my understanding is that WordPress guys are just asking your plugin license to be compatible with WordPress license.

2/ What are compatible licenses? Extract from the GPL page :
https://www.gnu.org/licenses/gpl-faq.html#WhatIsCompatible
What does it mean to say that two licenses are “compatible”?
“In order to combine two programs (or substantial parts of them) into a larger work, you need to have permission to use both programs in this way. If the two programs’ licenses permit this, they are compatible. If there is no way to satisfy both licenses at once, they are incompatible…”

My plugin is in essence compatible with WordPress GPL license as I allow users to run it together with WordPress. If I wouldn’t (by asking them to notify me for any installation or restricting the delivery), then I would agree that these are hardly compatibles.

But my plugin is available for free (no money), the source is easily browsable and the plugin can be downloaded easily.

I spent hundred of hours developping this plugin. You could understand that I’d like to protect a bit my work. If you don’t, you probably have a good salary beside your wordpress plugin coding and that’s not a big deal for you if your work is stolen as you don’t expect anything from it anyway…

Now we could speculate on the risk. Everybody has its own vision on that.

To close on this discussion :
1/ Based on my current understanding of the GPL “compatibility” and the WordPress statment, my understanding is that my plugin with its license (and what you describe as restrictions) could stay here. Again, the gain here is more for the user than me.
2/ Many other plugins don’t have any license or are more restrictive than mine and still they are on the repository.
3/ If my interpretation is wrong, then I would be happy to get the point of view from the WordPress repository admin so that we can see what can be done…

Having said that, I thank you for your time and wish you a good day!

Free doesn’t always mean open source, isn’t it?

The plugin is free for the moment and my feeling is that it can be usefull for some users here.

Now I have spent a lot of time working on it and I don’t want someone to take the code, change few lines, change the name and publish it. So that’s why I have put in some “restrictions” but I am not naive and I know how easy it is to browse php code and reuse it. I have no problem with that as long as the plugin isn’t duplicated by someone else…

Another way to protect it could have been to make it payable. I understand that this wouldn’t have been very kind so I have made it free so that everybody can use it. You can understand that I want to protect a bit what I have done, isn’t it?

I didn’t make it for me, I still have a lot of problems ??

I have the same problem for months. I cannot find any durable solution. I had to disable the plugin because of it…

Yes I finally found out a solution. For me, it was a ressource problem. I activated PHP 5 on my hosting and the problem is gone ??

It still doesn’t track anything ??

It still doesn’t seem to work…

I have set up an objective on analytic to track :
/outbound/asclick

It doesn’t track anything. I haven’t touched any configuration on the WP plugin settings panel (default options).

Sill not fixed with the new version ??

Arnee, I have sent you the corrupted files.
Thanks

Mine is ok right now (disabled the automatic update on blog modification). The problem will happen every time you add or modify a note thus triggerring a sitemap update. My blog has more than 1.000 notes.

The url is : https://www.lautre-monde.fr

I will send you the files once I see them corrupted again.

Do you plan to fix this issue because it is really annoying, google is crawling wrong urls thus resulting in 404 errors…

I am not using anymore the .gz and apparently, this helped…

Hello,

I have the same problem for two months now. Sounds like it only affects the .gz extension, not sure…

Regards,

Olivier
https://www.lautre-monde.fr