Another plugin removed from WP.org extend directory [Me too]

[KnxDT]

Since couple of days ago I can't able to see my plugin in the Wordpress.org Extend Directory.

I can't see it on http://wordpress.org/extend/plugins nor in my profile with the other plugins I created. However I can open that page http://wordpress.org/extend/plugins/...iption-widget/ when I log in with my account.

Looking for some answers, I encountered this post in the Wordpress forums:
http://wordpress.org/support/topic/3...4#post-1277795

Then I found this forum with a similar topic:
My plugin removed from WP.org extend directory

In fact, was almost the same situation... but the diference is that my plugin it's not SEO based. It's a widget that allow bloggers to configure a Feedburner form subscription to put it on their sidebar.

The SVN is still working and is still hosting my plugin (even it can be downloaded, my plugin, but only with the direct link, because it doesn't appear anymore in the directory, like I said).

I read in the other topic that maybe could be a GPL problem, but I have no problems with that. Maybe... could be a security problem and that could be an option because I'm not a SEO pro plugin developer but I'm trying to learn.

The SVN link directory is: http://svn.wp-plugins.org/feedburner...-widget/trunk/ (I hope this link don't break this forum's rules).

¿Any ideas? I really appreciate it :)

PS: I sent an email to Mark Jaquith but he didn't answer me and it's comprensible because he must be working in other more important things.

[Ryan]

Try asking on the WP Hackers mailing list ... http://lists.automattic.com/mailman/listinfo/wp-hackers. It seems to be the best way to get the attention of the powers that be.

There is also an email address you can try (I'm not sure what it is though), but I haven't heard of anyone having any luck asking questions via that before.

[Ryan]

I quickly skim read your plugin code and didn't see anything blatantly out of order. It's very possible I've missed something though.

You may want to use the built in wp_kses() function instead of strip_tags() and stripslashes():
http://codex.wordpress.org/Function_Reference/wp_kses

I doubt that would have had your plugin removed though.

[KnxDT]

Thanks for your answers, Ryan. I'm now suscribed to WP Hackers mailing list. I'll send a message explaining my situation.

Also I'll mention the wp_kses function your are refering in this thread.

[aldenml]

Hi KnxDT, two questions:

1- Why don't you put the GPL license header?
2- Why you put this

 $cierre_final1=base64_decode('PGg0PjxhIGhyZWY9Imh0dHA6Ly93d3cudGVjbm9sb2dpYWRpYXJpYS5jb20vMjAwOS8xMS9mZWVkYnVybmVyLXN1YnNjcmliZXJzLXdpZGdldC5odG1sIiB0aXRsZT0iRmVlZGJ1cm5lciBTdWJzY3JpYmVycyBXaWRnZXQiPkZlZWRidXJuZXIgU3Vic2NyaWJlcnMgV2lkZ2V0PC9hPjwvaDQ+PC9kaXY+PCEtLWZpbiBkZWwgZGl2IHN1c2NyaWJlLS0+'); 
  

instead the plain html?

Try to reach MarkR at IRC, remember the timezone, he is GTM +0.

[KnxDT]

Hi KnxDT, two questions:

1- Why don't you put the GPL license header?
2- Why you put this

 $cierre_final1=base64_decode('PGg0PjxhIGhyZWY9Imh0dHA6Ly93d3cudGVjbm9sb2dpYWRpYXJpYS5jb20vMjAwOS8xMS9mZWVkYnVybmVyLXN1YnNjcmliZXJzLXdpZGdldC5odG1sIiB0aXRsZT0iRmVlZGJ1cm5lciBTdWJzY3JpYmVycyBXaWRnZXQiPkZlZWRidXJuZXIgU3Vic2NyaWJlcnMgV2lkZ2V0PC9hPjwvaDQ+PC9kaXY+PCEtLWZpbiBkZWwgZGl2IHN1c2NyaWJlLS0+'); 
  

instead the plain html?

Try to reach MarkR at IRC, remember the timezone, he is GTM +0.

Hi aldenml, thanks for the answer.

I put it in that form because other sites put my plugin to download, but the code was so simple that they edited the credits and they replaced my plugin link with theirs.

Now I have two (newbie) questions:

- What IRC? Should I install a software to use it or just Internet?
- I need to add the "[wp-hackers]" tag when I send a message to the mailing list? Or... the tag is automaticly generated to the email subject?

EDIT:

By the way. To create the readme.txt file I use this standar readme.txt:

http://wordpress.org/extend/plugins/about/readme.txt

And there isn't anything about GPL. I checked the All in One SEO Pack readme.txt and it doesn't have anything with GPL either.

Anyway, I'll add those lines. If you have any other advices, thank you very much :)

I really appreciate your help.

[Ryan]

$cierre_final1=base64_decode('PGg0PjxhIGhyZWY9Imh0 dHA6Ly93d3cudGVjbm9sb2dpYWRpYXJpYS5jb20vMjAwOS8xMS 9mZWVkYnVybmVyLXN1YnNjcmliZXJzLXdpZGdldC5odG1sIiB0 aXRsZT0iRmVlZGJ1cm5lciBTdWJzY3JpYmVycyBXaWRnZXQiPk ZlZWRidXJuZXIgU3Vic2NyaWJlcnMgV2lkZ2V0PC9hPjwvaDQ+ PC9kaXY+PCEtLWZpbiBkZWwgZGl2IHN1c2NyaWJlLS0+');

That would explain it then. You should report it to the powers that be that you weren't notified of the removal, but if you had that code in there then that would definitely explain why it was removed.

Anything that uses base64 encoding to obfuscate it's content from the site owner is not acceptable for the plugin repository and should be removed immediately.

Not mentioning the GPL is also going to get you removed as well. It's clearly outlined in the repository rules that everything submitted must be GPL. I'm not sure they mention anything about obfuscating code, but I think that's a given.

[Jeffro]

Yep, having the base_64 code in their is the most likely reason your plugin was removed. There are tons of plugins that do not contain the GPL license within them as I guess they naturally inherit the license stuff if no specific one is mentioned but I could be wrong. They don't do a good job of making sure plugins maintain the license text within the plugin before approval. I doubt that had much to do with the removal.

[Ryan]

There are tons of plugins that do not contain the GPL license within them as I guess they naturally inherit the license stuff if no specific one is mentioned but I could be wrong.

You are definitely wrong. If no explicit license is present, then the code is deemed copyright to the author(s).

[aldenml]

@KnxDT, I recommend you follow these links for get into the IRC

http://codex.wordpress.org/IRC
http://codex.wordpress.org/WordPress_IRC_Live_Help

The tag for the mailing list is not necessary.

Your plugin must be GPL Compatible (http://wordpress.org/extend/plugins/about/) with a strong bias toward GPL.

The license header must be located inside the PHP code. I suggest you make these changes: license inclusion and base64 removal.