Forum Replies Created

Viewing 15 replies - 256 through 270 (of 272 total)
  • I would need to setup the plugins and environment. I can’t do this at the moment..

    How urgent is a solution? Maybe we could do a debug session on your environment – this would spare the setup for me?

    There is your case:
    https://github.com/No3x/wp-mail-logging/issues/22

    Well, I think mandrill_payload is causing this. It would be nice if you could try the following for me:

    Find add_filter( 'wp_mail', array( &$this, 'log_email' ) ); in file WPML_Plugin.php. Change it to:
    add_filter( 'wp_mail', array( &$this, 'log_email' ), 99 );
    Maybe priority 11 should do it too, but just to make sure.
    Try sending another mail.

    Hi Austin Passy, I have already seen you on GitHub 🙂

    Edit: Forget the following – after I saw the screenshot I realised they use wp_mail in some way.:
    Well, I don’t know Mandrill but seems like they are bypassing wp_mail by using their own PHP mailer class. So WP doesn’t know anything about a mail sent by them.

    Of course this is necessary and now planned for a release.

    Thanks! What do you exactly (requirements) mean with housekeeping function?

    Closed. Feel free to reopen.

    Hi Li-An,

    the logged email has been sent by WordPress but please note this does NOT mean it has been delivered. With the given functionality of WordPress you can’t determine if a mail was sent successfully.

    WordPress just sends all the information to the relevant mail server. From here WordPress is out of business and there is no feedback from the mail server.

    What is your actual use case? Do you want to know if the email of the user is valid and mails are deliverable?

    In summary the plugin can’t help you with an unstable setup to your mail server and feedback if the email was delivered (for technical reasons).

    Closed

    Hey marvel32,

    1.3 is out!
    .. and all your issues are fixed. If not use the mentioned ways to help making the plugin better.

    (Pagination was fixed when I announced it here but not included in the icon branch)

    I fixed the per_page option some minutes ago.

    There are already huge changes for 1.3.
    Have a look at the milestone 1.3
    https://github.com/No3x/wp-mail-logging/milestones
    Check out the open and closed issues and give some hints and opinions.

    In general if you find a bug have a look at:
    https://github.com/No3x/wp-mail-logging/issues

    I regularly post the progress to the issue and request some tester and requirements. Commonly I post all changes that are necessary to test a feature.

    Hi marvel32,

    there is no limit of the logged mails!
    Is it possible that you updated from 0.1 or 1.1 to 1.2?
    The database schema changed in 1.2 but there is a bug that the update doesn’t change the schema. I’m so sorry this happened!

    The messed up HTML output for HTML email is also fixed by opening each mail in a modal window. (thanks to tripflex)
    I’ve also already implemented downloadable attachments and nice icons for the appropriate mime type as a first draft.

    There are 2 options:
    1. Deactivate the plugin, drop the whole database table wpml_mail via sql, activate the plugin again.
    2. Wait for plugin version 1.3

    Thread Starter No3x

    (@no3x)

    I’ve found the cause of the problem. It was my fault because I’ve hidden/skpped the “Registered Group” in the backend. So Groups_User_Group::delete() was always called.

    Just want to say.

    Thread Starter No3x

    (@no3x)

    Sorry for my late response. The method name is corrected now. But the problem is still present.
    The Post hast the restriction REQ_A.
    In the user_can_read_post() method the variable $read_caps has the value:
    [0] => "REQ_A"
    Everything is fine so far.
    In the foreach each required post cap is checked against the users capabilities. The return value is always false.

    I was able to fix the problem with this patch: (the injectRegistered part)

    $user_capability_table  = _groups_get_tablename( "user_capability" );
    
                $limit = $wpdb->get_var( "SELECT COUNT(*) FROM $group_table" );
                if ( $limit === null ) {
                    $limit = 1;
                }
    
                // note that limits by blog_id for multisite are
                // enforced when a user is added to a blog
                $user_groups = $wpdb->get_results( $wpdb->prepare(
                    "SELECT group_id FROM $user_group_table WHERE user_id = %d",
                    Groups_Utility::id( $this->user->ID )
                ) );
    if($this->user->ID != 0) {
                // the previous statement only covers user<->group dependencies created by the groups plugin but not the 'registered' dependency because it is not stored in the database.
                $injectRegistered = new stdClass(); //use same return type as db layer
                $injectRegistered->group_id = 1; //group_id for 'registered' is always 1
                $user_groups[] = $injectRegistered;
    }
                // get all capabilities directly assigned (those granted through
                // groups are added below
                $user_capabilities = $wpdb->get_results( $wpdb->prepare(
                    "SELECT c.capability_id, c.capability FROM $user_capability_table uc LEFT JOIN $capability_table c ON c.capability_id = uc.capability_id WHERE user_id = %d",
                    Groups_Utility::id( $this->user->ID )
                ) );

    My plugin version is 1.3.11. Afaik there where no changes in this file in the new version. I can’t update to the newest version because I have to fill in the post restrictions by JS. I was not able to do this in the newest version because of the usage of selectize js lib.

    Thread Starter No3x

    (@no3x)

    Hi chriscct7,

    thank you very much. I didn’t assumed that wp would handle the post_type for me.
    I just want to add additional js code on every download post in the admin section. I hooked into the post site and checked if post_type is download. This works very well for new downloads but if you are in the download overview list table and want to edit a download the argument post_type is not appended to the get parameters. There is just action=edit.
    Maybe there is a reason for this on your part.

    Thread Starter No3x

    (@no3x)

    Hello, thank you very much for your help.
    But the mentioned hook is not usefull for my requirements. I don’t want to show the download at all, if the user has not the caps. The download shouldn’t appear on the whole blog.
    So I have to check far before edd_process_verified_download.
    Do you have an idea?

Viewing 15 replies - 256 through 270 (of 272 total)