Forum Replies Created

Viewing 15 replies - 151 through 165 (of 3,660 total)
  • Plugin Author Chip Bennett

    (@chipbennett)

    I just pushed this commit to the development version. Doing a bug sweep, and then I’ll release an update shortly.

    Plugin Author Chip Bennett

    (@chipbennett)

    Hi Andrew,

    I’m working on an update now that WordPress 3.7 is out. (I’ve been waiting for some filters to be added to core, that will simplify the Plugin considerably.)

    I’d like to track down if this is a bug that I need to fix. Can you tell me what happens if you clear out the text field that has the "Array" in it? Do the notices disappear, or are they still there?

    Plugin Author Chip Bennett

    (@chipbennett)

    The Plugin relies on the comment_form_after_fields action hook that is output as part of the WordPress core comment_form() function.

    As Builder is a commercial Theme, I don’t have access to the code. You’ll have to ask the iThemes folks if they’re doing anything non-standard with the comment form functionality.

    This, naturally, raises the question as to how the commercial theme/plugin sites are different.

    Commercial Theme/Plugin shops are different in that they are not bound by wordpress.org policy and guidelines. That means that you could find commercial shops distributing Themes/Plugins under non-GPL-compatible licenses, or bundling non-GPL-compatible resources with their distributed Themes/Plugins.

    If anything which is made from wordpress must be GPL, what stops people from paying for a theme on a commercial site, then simply uploading to wp.org for free?

    Policy and guidelines. While it’s simply not feasible to stop any and all attempts, the Theme Review Team would not accept any submission known to be a commercial Theme, or otherwise not owned by the person attempting to submit the Theme. (And it does happen, from time to time.)

    That is where my confusion comes in. In reading the GPL FAQ, I can’t see anything which allows people to prevent others from redistributing GPL works (including themes/plugins), for free.

    Indeed, no such restriction exists in the GPL. It is fully within the terms of the license to obtain a free Theme or purchase a commercial Theme, and then redistribute that Theme for free or for cost.

    Why don’t we see premium themes/plugins or slightly modified versions of them on wp.org? Is it a wp.org policy thing or is there a GPL loophole I’m not seeing?

    Exactly: it is wordpress.org policy.

    (Note: you’ll find plenty of premium Themes on wordpress.org; what you won’t find are commercial Themes. Not all commercial Themes are premium, and not all premium Themes are commercial. I would put the overall code quality of the Themes hosted in the official Theme directory up against the overall code quality of just about any commercial Theme shop.)

    I have a question regarding the GPL license and images included in themes/plugins. Are the same GPL rules applied to the images?

    Themes (and Plugins) hosted by wordpress.org are required to be 100% GPL-compatible, including all bundled resources (such as images).

    I notice many authors mention the images in their themes/plugins are copyright.

    Yes, they must be. In order to apply a license (including GPL) to a work, copyright must be asserted. The potential issue is not that a work is copyrighted, but rather the license under which that copyrighted work is distributed.

    Does the copyright override the GPL, to mean I cannot legally use/share the images when sharing the plugin/theme with others? Or include the images when making/selling derivative plugins/themes using the original images?

    There are two issues:

    1) The legal/copyright issue
    2) The wordpress.org policy issue

    A copyright holder has the right to define the terms under which the copyrighted work is used, modified, and distributed. So if a copyright holder asserts a given license to a work, that license applies – even if that work is bundled with a GPL work.

    The issue there is obvious, which is where wordpress.org policy comes in: all works hosted by wordpress.org must be 100% GPL-compatible, in order to preserve user freedoms, and to avoid issues such as the one above, where a non-GPL-compatible work is bundled with a GPL work.

    So, if you find a Theme or Plugin hosted by wordpress.org that has non-GPL-compatibly licensed resources (images, scripts, fonts, etc.), please let us know:

    Themes: email the theme-reviewers mail-list: http://lists.wordpress.org/mailman/listinfo/theme-reviewers

    Plugins: email plugins@wordpress.org

    Hi @tubaplayer, you should post your question directly in the forum for the Contango Theme:
    http://wordpress.org/support/theme/contango

    Just a couple of things to add:

    1) ThemeForest now offers a 100% GPL license, that their vendors may choose to use. If you wish to retain the software freedoms promoted by WordPress, then you should look for ThemeForest Themes sold under the “100% GPL” license, rather than the Regular Envato license.

    2) ThemeForest has made great strides in improving their quality guidelines. Their current iteration is remarkably in-line with the WPORG Theme Review Guidelines, though it will take some time for those new guidelines to propagate into their currently offered Themes.

    I don’t consider “ThemeForest” to be a dirty word; you just have to know what you’re getting in to, and what to look for.

    Plugin Author Chip Bennett

    (@chipbennett)

    Hi Andrrew,

    Can you tell me what settings you changed, and were trying to save?

    That line in settings.php is expecting a comma-separated list of email addresses.

    Plugin Author Chip Bennett

    (@chipbennett)

    That’s a great recommendation; thanks!

    I’ve added it as a support issue in the Plugin’s GitHub repo, and will include it in the next update.

    Taken care of. I’ve suspended PressWork. Please let me know if/when the issue is resolved.

    Plugin Author Chip Bennett

    (@chipbennett)

    @tenshinhikaru

    Thanks for using the Plugin.

    I am unable to provide support specific to that Theme, as it is a commercial Theme and not distributed under a GPL-compatible license.

    That said, in general, the issue is that the Theme uses a hard-coded comment form, rather than using the core comment_form() function, and does not include the hooks that the Plugin uses to output the CAPTCHA.

    You would have to output cbnet_rscc_captcha() in the appropriate place within the comment fields in order for the Plugin to work.

    Theme Author Chip Bennett

    (@chipbennett)

    Hi etimbuk,

    The easiest way to remove all of the post header content is via filter. Add the following to the functions.php file of a Child Theme:

    add_filter( 'oenology_hook_post_header_metadata', __return_false() );

    To see where this filter is defined, look in functions/hooks.php, on Lines 931-969.

    Plugin Author Chip Bennett

    (@chipbennett)

    Thanks for using the Plugin!

    What is the “old template”? Do you have a link either to your site, or better yet a download link for the Theme being used?

    The Plugin relies on a hook in the comment form code; if you’re using a really old Theme, that hook might not be there. That’s what I would initially suspect is the problem, anyway.

    In a Child Theme functions.php file (or in a site functionality Plugin), add the following:

    remove_action( 'contango_footer', 'contango_footer_init' );

    That will remove the current footer credit.

    You’ll also lose the copyright information, including your Theme setting. To restore it, add the following in the same place as above:

    add_action( 'contango_footer', 'custom_contango_footer' );
    function custom_contango_footer() {
    	$contango_options = contango_get_settings();	
    
    	/** Footer Copyright Logic */
    	$contango_copyright_code = '&copy; Copyright '. date( 'Y' ) .' - <a href="'. esc_url( home_url( '/' ) ) .'">'. get_bloginfo( 'name' ) .'</a>';
    	if( $contango_options['contango_copyright_control'] == 1 ) {
    
    		$contango_copyright_code = '&nbsp;';
    		if( ! empty( $contango_options['contango_copyright'] ) ) {
    			$contango_copyright_code = wp_specialchars_decode( $contango_options['contango_copyright'], ENT_QUOTES );
    		}
    
    	}
    }

    I’m not saying I knew that Chip has a notification filter for posts like this one. But I did know that and I’m not surprised by the prompt reply. 😉

    When the Brute Squad comes calling, I can’t really ignore him. 😉

Viewing 15 replies - 151 through 165 (of 3,660 total)