![]() |
Quote:
|
Quote:
|
Quote:
|
Quote:
:thumbsup |
Quote:
http://markjaquith.wordpress.com/201...-of-wordpress/ |
where's the free burgers?
|
Quote:
Quote:
Quote:
I don't see any reason to continue the GPL "educational" discussion with GFY'ers, just because I have direct contacts with the WP developers. :2 cents: |
Quote:
|
Quote:
|
I did read the other thread so the "case is closed". However, there is a couple important things I want to repeat:
|
ANAL HOBBIT TIP: Buy a single site license, share it, report it & receive an unlimited license!
|
FIDDY!.... shit I missed it.
|
I just tied my dick in a knot. Can you?
|
Interesting, I wondered when one of these threads would pop up. Anna isn't the only one releasing CyberSEO to their clients.
I've been using it on a number of domains for a while now. |
Quote:
|
Quote:
Ive never even heard of the script untill today.. |
i dont have either code because i have no idea how to use it but from what i have seen it looks good
|
Quote:
CyberSEO isn't the only one releasing CyberSEO script to their clients. |
Quote:
Quote:
|
Quote:
|
Quote:
|
Quote:
The same with WP plugins. Here is a quote from the WP freedom declaration: Quote:
This is exactly that happened to my own Simple-FLV plugin which was removed from the WP repository because it was considered as a non-GPL one (even if I stated that it is in the license) because the package does contain a non-GPL code. I got this explanation directly from the WP team. I was also told that if I want my Simple-FLV plugin to be included into the repository, I have to make it GPL-compatible, otherwise it just can not be distributed via WordPress.org. |
Quote:
|
Quote:
so tell me how its not using any wp code, being a plugin at all? i could see if it was an external app and just connected via another method, but its inside wp, it has to use SOME wp code or how else is it posting to wordpress? creating a post is using wp code. |
Quote:
https://gfy.com/showpost.php?p=18994713&postcount=48 |
Quote:
Quote:
Quote:
Actually I don't see any reason to discuss this, because the WP team has stated it very clear: there could be GPL and non-GPL extensions, and they do not recommend the non-GPL ones. My Simple FLV plugin is a good example. Try to submit it into the WP repository and it will be rejected as a non-GPL one. The mentioned plugin also does interacts with WP API, but this fact dose not make it a GPL product. The same applies to the CyberSEO plugin which explicitly contains a non-GPL proprietary code itself. If someone will try to distribute it under the GPL license, it will be a direct violation of GPL itself and a violation of the proprietary license under which it was released. So what exactly we are discussing here? I believe it was explained in the WP freedom declaration too (please re-read my previous post carefully). |
I think if you make money with CyberSEO, pay full price. Capitalism is why people like this author innovate and create products like this. Plus if you ever need help with something you've got "the man" to ask.
No slithering down dark allys. |
Quote:
since you have to wordpress header code. as soon as you have this added, its considered gpl. Code:
<?php |
Almost correct. You may consider it as a split GPL license. Because the mentioned above header code is located in open source PHP file which can be distributed as GPL.
As far as you know, the split GPL license allows to have open source GPL file along with proprietary ones. E.g. RedHat Linux which package has both GPL and non-GPL files. The GPL file can be re-distributed, the proprietary ones - can not be since they are covered by another license. |
About Wordpress and GPL stuff: such a things, like CyberSEO product, uses dual licensing.
Wordpress is GPL and CyberSEO uses Wordpress for his software, but he is selling only his product - not Wordpress. CyberSEO does not modify WP code, it uses only it's api. He have only to provide a source code of Wordpress for free, as GPL says. |
i guess we will never know unless he actually shows the code thats encoded with ioncube ;)
|
Quote:
|
Quote:
get_option update_option are all part of wp settings api and other gpl bits remove_filter term_exists wp_set_post_cats add_action wp_insert_post also using the $wpdb class |
These are called API's. E.g. get_option is not a WP code. It's just a function name. The source code of that function is located in /wp-includes/functions.php and is not included into the CyberSEO distributive. Do you want me to provide it? Just let me know and I'll give you the download URL :)
As kazymjir has said above, I sell CyberSEO only. If you need WP, you have to download it separately. |
Quote:
not saying your whole code is gpl, but its split between wp and your own. |
So? Answer at these questions please:
1) Is Linux a GPL product? 2) Does it have API functions? 3) Are Linux API function names part of Linux code? 4) Does it mean that any Linux application that calls Linux API functions must be a GPL product too? |
Furthermore, get_option is NOT a part of the wp codebase. It's just a function name which is not copyrighted or so.
What if I write my own non-GPL CMS where I will declare my own version of the get_option function? E.g.: <?php function get_option($name) { return $_GET[$nane]; } ?> Now lets consider I have a file (say "something.php") which contains the following code: <?php echo get_option('hello'); ?> Does it mean that my something.php is a GPL product because it calls a function named get_option? |
Quote:
not saying your *OWN* code is gpl. just the parts that you use wp functions for are which only looks like vrery little, options, and some of the post creating via wp_insert_post |
All times are GMT -7. The time now is 12:34 PM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
©2000-, AI Media Network Inc123