Forum Replies Created

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

    (@chipbennett)

    Thanks for your patience. I found the issue, and it’s an easily-fixed bug with the Plugin. This line:

    if ( ! $options['active'] ) {
        add_filter( 'auto_upgrader_disabled', '__return_true', 1 );
        return; // It's all disabled, no need to check the others.
    }

    The name of the filter is wrong. It should be auto_updater_disabled.

    If I recall correctly, many of the filter names were changed during WordPress 3.7 beta-testing prior to release. I missed this one. I apologize.

    I’ll push out a fix immediately.

    Forum: Plugins
    In reply to: [Update Control] Updated
    Plugin Author Chip Bennett

    (@chipbennett)

    Thanks for your patience, all. I found the issue, and it’s an easily-fixed bug with the Plugin. This line:

    if ( ! $options['active'] ) {
        add_filter( 'auto_upgrader_disabled', '__return_true', 1 );
        return; // It's all disabled, no need to check the others.
    }

    The name of the filter is wrong. It should be auto_updater_disabled.

    If I recall correctly, many of the filter names were changed during WordPress 3.7 beta-testing prior to release. I missed this one. I apologize.

    I’ll push out a fix immediately.

    Plugin Author Chip Bennett

    (@chipbennett)

    You’ll only get email notification for core, unfortunately. You could enable the debug email, which will notify you of all update attempts (including core, Plugins, and Themes), but that will give you probably more information than you want.

    As for timing: the automatic updates are still being throttled. The core team has taken a ramped approach to rolling out the automatic updates, to watch for any potential issues (as it is still a very new feature). Eventually, the goal is for automatic updates to be pushed out immediately.

    If you got the email, though: congrats! Core successfully updated automatically. 🙂

    Forum: Plugins
    In reply to: [Update Control] Updated
    Plugin Author Chip Bennett

    (@chipbennett)

    @persiusx please start a separate support topic.

    Forum: Plugins
    In reply to: [Update Control] Updated
    Plugin Author Chip Bennett

    (@chipbennett)

    What are your settings?

    Plugin Author Chip Bennett

    (@chipbennett)

    Works for me. 3.8 updated automatically. Plugins all update automatically.

    Can you provide any additional detail?

    (Note: multisite network updates are still problematic, and I haven’t been able to track down the reason.)

    Thread Starter Chip Bennett

    (@chipbennett)

    @myksmith, thanks; I think that clarification is perfect.

    Plugin Author Chip Bennett

    (@chipbennett)

    Please re-read the Plugin description. I removed all functionality from the Plugin almost exactly a year ago. It literally does nothing.

    Plugin Author Chip Bennett

    (@chipbennett)

    ok i just tested the comments with the plug in deactivated and the admin is still getting 2 emails per comment.

    Thanks for that. Unfortunately, that indicates some issue on your end, either with your WordPress configuration or your email configuration.

    The functionality of this Plugin itself is actually quite simple. It merely filters the email distribution list, to add additional email addresses. As your issue doesn’t appear to be related to the Plugin, I’ll close this as “resolved”, but please post again if you have any other issues.

    Plugin Author Chip Bennett

    (@chipbennett)

    Let’s try to figure this one out:

    1) Do you get double notification emails with the Plugin disabled?
    2) What other Plugins do you have active?
    3) What are the settings you have configured for the Plugin?
    4) Are the emails going to the same email address (i.e. could it be an issue with an email alias)?

    Plugin Author Chip Bennett

    (@chipbennett)

    @stepjoe, per the WPORG forum rules, please start a new topic for your issue, as it is separate from the OP in this topic. Also, separate topics facilitate me being able to follow up and resolve all issues. Thanks.

    Plugin Author Chip Bennett

    (@chipbennett)

    You’re running WordPress 3.7.1, right?

    What other Plugins do you have active?

    don’t see any problem with a GPL licensed extension interfacing with proprietary code, probably through an API no less! The plugin extension is useless without the proprietary component, yet it remains functional as far as it goes.

    Yes! I believe this is the same point Otto made previously, and the same thing I suggested above: create a GPL-distributed WordPress Plugin, that interfaces with the proprietary code through an exposed API.

    Plugin and theme code from the perspective of the PHP parser is the at same level as any other WordPress code. Typically, API code is at least conceptually at a different level than the code calling it, even if at the processor level there is no difference.

    Precedent case law makes a distinction between derivative code, which requires actual code incorporation, and dependent code, which would be the case here. Code linking/combination happens by the user, at the time of execution by the PHP parser, and under any case law I have been able to find, does not constitute incorporation of code from one into the other, and therefore does not cause the dependent work to be derivative.

    What the GPL defines as a derivative work and what FSF defines as a derivative work are entirely irrelevant, if those definitions contradict what the Copyright Act and precedent case law define as a derivative work. That is the case here: precedent case law clearly states that a derivative work requires actual code incorporation, and further clearly states that mere function calls do not constitute actual code incorporation – though if anyone can find any case law to refute Galoob v Nintendo, Sega v Accolade, and Sony v Connectix, I would gladly consider it.

    Note that you can also try using remove_post_type_support():

    function mvandemar_remove_post_type_support() {
        remove_post_type_support( $post_type, 'title' );
        remove_post_type_support( $post_type, 'editor' );
    }
    add_action( 'init', 'mvandemar_remove_post_type_support' );
Viewing 15 replies - 91 through 105 (of 3,660 total)