Kaloyan
Forum Replies Created
-
Forum: Plugins
In reply to: Best practices with commercial pluginsThank you, you have been really helpful!
Forum: Plugins
In reply to: Best practices with commercial pluginsOne last question regarding the licensing stuff: about the service approach – the custom-build plugin will be GPL licensed, so can the “customer” re-distribute it ? Not without my consent, right ?
Forum: Plugins
In reply to: Best practices with commercial pluginsCorrect approach to doing what?
In general. You pretty much hit all the points I need information about.
If you want to sell your plugin, then sell it. Nothing in the GPL prevents you from doing that.
Thank you, I was never good at understanding licensing stuff, and your replies helped me clear out some stuff.
Forum: Plugins
In reply to: Best practices with commercial pluginsThank you a lot.
Forum: Plugins
In reply to: Best practices with commercial pluginsThanks for that information. Considering this, what’s the correct approach ?
Forum: Developing with WordPress
In reply to: WP hacks; customize output with query_poststhere are a couple of plugin hooks (actions) you can use to change the query_posts() sql query, like:
- posts_where
- posts_join
- posts_orderby
- posts_request
Using this you can tap into the “sql query” and modify it. For details do open the
wp-includes/query.phpand explore it to see where the hooks are applied.Forum: Plugins
In reply to: Have You Ever Paid for a Plugin?I am planning on making a commercial WordPress plugin. I’ve published plugins that are open-source and free, which help the average WordPress customers. In the mean time, if a build a plugin which functionality in general will be used by “commercial” means, then I myself I do not see any issues w/ releasing with a proprietary license and for a price.
Forum: Plugins
In reply to: Deactivating “Better Alexa-Redirect” PluginHi,
this is Kaloyan Tsvetkov. There is a really easy way to detect if the plugin is active or not: when active, it injects a JavaScript snippet in the footer of the blog. If you check my blog (kaloyan.info/blog) you will see it in the footer. This JS snippet is used to add the prefix to your links.
However, your blog does not have this JS snippet in the footer. In the same time, all your links have “hardcoded” prefixes for Alexa. I took the liberty to check your /plugins folder (http://www.bitesizebio.com/wp-content/plugins/), and it seems that you also have the original AlexaRedirect plugin installed. I think this is what’s causing your problem: nevertheless Better-Alexa-Redirect is disabled, you still have the originla AlexaRedirect on: that’s why all your links have hardcoded “redirect.alexa…” prefix.
For last, one advice: you seem to still run WordPress 2.2.2, while it should be better if you upgrade to the latest release WordPress 2.3.1