Forum Replies Created

Viewing 15 replies - 106 through 120 (of 120 total)
  • Plugin Contributor dufour_l

    (@dufour_l)

    Hello Guys

    Can you all try with the new version 1.4.6

    Regards

    Plugin Contributor dufour_l

    (@dufour_l)

    @steffen, now in version 1.4.6, when you check the debug checkbox, you will have the instagram respone with error code, in instagram response, in your post on the box “auto post to instagram”. Please see the screenshots of Roland here https://ps.w.org/auto-post-to-instagram/assets/screenshot-2.png?rev=1999455

    Plugin Contributor dufour_l

    (@dufour_l)

    Hi Roland,

    now on version 1.4.6, all debug info and instragam response should appear in the box dedicated to the “auto post to instagram” part in a post

    My previous remark was before version 1.4.6 where we did not catch the response from Instagram and there was an error because we tried to log on twice, one with the constructor, and then with the login method.

    Now it is fixed since version 1.4.4

    • This reply was modified 7 years, 4 months ago by dufour_l.
    • This reply was modified 7 years, 4 months ago by dufour_l.
    Plugin Contributor dufour_l

    (@dufour_l)

    Hello

    The message “Never published” really means that it was not published on Instagram.

    Why it was not published this is another story.

    This has to be debugged, to find the reason why in your case.

    If you really want to know why it is not publishing, you will have to check the debug checkbox.

    And if you still not have any messages, then edit the file wp2instagram.php and search for line 869 to 874 and uncomment the following code

    //try {
    // $i->login();
    //} catch (Exception $e) {
    // $e->getMessage();
    // exit();
    //}

    You will then received all debug informations from the sub component “mpg25” that does all the underlaying connectivty of this plugin with Instagram.

    • This reply was modified 7 years, 4 months ago by dufour_l.
    • This reply was modified 7 years, 4 months ago by dufour_l.
    • This reply was modified 7 years, 4 months ago by dufour_l.
    Plugin Contributor dufour_l

    (@dufour_l)

    Hello Stevie

    I proposed a tips/fix a few days ago, can you try it just in case ?

    Details below

    Laurent.

    ——————————-

    Hello Guys,
    I had the same issue since a few hours today.

    Now I have found a work around that I share with you.

    The root cause of the issue probably came from Instagram in the yway they check the login and password.

    But so far in the plugin code, there is a use of a sub library “mgp25/Instagram-API” and in the way it is used so far there where something like

    $i = new \InstagramAPI\Instagram($username, $password, $debug);

    try {
    $i->login();
    } catch (Exception $e) {
    $e->getMessage();
    exit();
    }

    And the problem come from the phase whith the try section where it tries to authenticate twice the user. This has worked so far, but today it does not work anymore.

    The first line $i = new \InstagramAPI\Instagram($username, $password, $debug); already login the plugin to instagram.

    So to make it works, now I had to put in comment the following lines (Around line 724 to 729 in wp2instagram.php )

    //try {
    // $i->login();
    //} catch (Exception $e) {
    // $e->getMessage();
    // exit();
    //}

    And now my post are shown again in instagram.

    So Roland (The author of the plugin), if you pass here I do not know if this is normal or not or if something needs to be adapted with a new version of the plugin.

    I just wanted to share this tips with all of you.

    Laurent Dufour

    Plugin Contributor dufour_l

    (@dufour_l)

    Hello ruayrod,

    I have made a proposition to the maintener of the plugin to handle your request. As soon as he will accept the change in the code he will probably made it available.

    If you want to test it as a beta please try this current developpement version ==> http://laurentdufour.eu/auto-post-to-instagram-current.zip

    Laurent Dufour

    Plugin Contributor dufour_l

    (@dufour_l)

    Hello Guys,
    I had the same issue since a few hours today.

    Now I have found a work around that I share with you.

    The root cause of the issue probably came from Instagram in the yway they check the login and password.

    But so far in the plugin code, there is a use of a sub library “mgp25/Instagram-API” and in the way it is used so far there where something like

    $i = new \InstagramAPI\Instagram($username, $password, $debug);

    try {
    $i->login();
    } catch (Exception $e) {
    $e->getMessage();
    exit();
    }

    And the problem come from the phase whith the try section where it tries to authenticate twice the user. This has worked so far, but today it does not work anymore.

    The first line $i = new \InstagramAPI\Instagram($username, $password, $debug); already login the plugin to instagram.

    So to make it works, now I had to put in comment the following lines (Around line 724 to 729 in wp2instagram.php )

    //try {
    // $i->login();
    //} catch (Exception $e) {
    // $e->getMessage();
    // exit();
    //}

    And now my post are shown again in instagram.

    So Roland (The author of the plugin), if you pass here I do not know if this is normal or not or if something needs to be adapted with a new version of the plugin.

    I just wanted to share this tips with all of you.

    Laurent Dufour

    Plugin Contributor dufour_l

    (@dufour_l)

    Hello Guys,
    I had the same issue since a few hours today.

    Now I have found a work around that I share with you.

    The root cause of the issue probably came from Instagram in the yway they check the login and password.

    But so far in the plugin code, there is a use of a sub library “mgp25/Instagram-API” and in the way it is used so far there where something like

    $i = new \InstagramAPI\Instagram($username, $password, $debug);

    try {
    $i->login();
    } catch (Exception $e) {
    $e->getMessage();
    exit();
    }

    And the problem come from the phase whith the try section where it tries to authenticate twice the user. This has worked so far, but today it does not work anymore.

    The first line $i = new \InstagramAPI\Instagram($username, $password, $debug); already login the plugin to instagram.

    So to make it works, now I had to put in comment the following lines (Around line 724 to 729 in wp2instagram.php )

    //try {
    // $i->login();
    //} catch (Exception $e) {
    // $e->getMessage();
    // exit();
    //}

    And now my post are shown again in instagram.

    So Roland (The author of the plugin), if you pass here I do not know if this is normal or not or if something needs to be adapted with a new version of the plugin.

    I just wanted to share this tips with all of you.

    Laurent Dufour

    • This reply was modified 7 years, 6 months ago by dufour_l.
    • This reply was modified 7 years, 6 months ago by dufour_l.
    Thread Starter dufour_l

    (@dufour_l)

    I answer to my own question as I now have found why it does not work anymore.

    It is simple 500px.com has shutdown API services

    https://support.500px.com/hc/en-us/articles/360002435653-API-

    ———-

    The history of 500px has always encouraged creative development, but as of January 24th 2018, 500px will no longer be offering free access to our API. This decision was made in order to protect our assets and improve our website’s performance. On June 15th, access to the API was shut down. This is part of a larger strategic shift—focusing our energy on continuing to build the world’s best photography community at 500px.com.

    I have an existing key, so what does this mean for me?

    If you have an existing API key, you will lose access on June 15th 2018. You can email sales@500px.com to discuss further usage of the API.

    Thread Starter dufour_l

    (@dufour_l)

    Hello John

    I did more search and here is what I have found

    You are right the serach parametre works to find a title, but it does not work when it is used with a hyphen in front, so you cannot exclude title

    Same things, with args[‘title’], it does not handle the hyphen in front, so no real solution with keyword search.

    So I dig a little bit and found the solution here : https://wordpress.stackexchange.com/questions/18703/wp-query-with-post-title-like-something

    It needs to use a filter

    So I add one into the plugin

    ///////////////////////////////////////////////////////////////////////////////////////////////////////////////////

    // Title Filter
    //
    // Source code ==> https://wordpress.stackexchange.com/questions/18703/wp-query-with-post-title-like-something
    //

    function title_filter($where, &$wp_query){
    global $wpdb;
    if($search_term = $wp_query->get( ‘title_filter’ )){
    $search_term = $wpdb->esc_like($search_term); //instead of esc_sql()
    $search_term = ‘ \’%’ . $search_term . ‘%\”;
    $title_filter_relation = (strtoupper($wp_query->get( ‘title_filter_relation’))==’OR’ ? ‘OR’ : ‘AND’);
    $title_filter_search_type = (strtoupper($wp_query->get( ‘title_filter_search_type’))==’LIKE’ ? ‘LIKE’ : ‘NOT LIKE’);
    $where .= ‘ ‘.$title_filter_relation.’ ‘ . $wpdb->posts . ‘.post_title ‘.$title_filter_search_type.’ ‘.$search_term;
    }
    return $where;
    }

    And to use it, in the function aps_auto_post

    if (!empty($aps_keyword_search)) {
    $args[‘s’] = $aps_keyword_search;
    //$args[‘exact’] = TRUE;
    }

    if (!empty($aps_title_search)) {
    //$args[‘title’] = $aps_title_search;
    add_filter(‘posts_where’,’title_filter’,10,2);
    $args[‘title_filter’] = $aps_title_search;
    $args[‘title_filter_relation’] = ‘AND’;

    if ($aps_title_search_negate==TRUE) {
    $args[‘title_filter_search_type’] = ‘NOT LIKE’;
    } else {
    $args[‘title_filter_search_type’] = ‘LIKE’;
    }
    }

    $args = apply_filters(‘aps_eligible_query’, $args);

    So I modified the plugin “Auto Post Scheduler” to a new version to add a new field for the title and a negate checkbox, and now it works, I have made a version 1.80.1 that you can download here to see if you agree to use is or not

    I also by the way add the option to keep the original date in this version, you can if you decide ton incoporate it , in your plugin rename the option to whatever your prefer in order to not confuse user

    if ( $aps_recycle_keep_original_date ) {

    $update[‘post_date’] = get_the_date(‘Y-m-d H:i:s’);
    }
    else
    {
    $update[‘post_date_gmt’] = date(‘Y-m-d H:i:s’,current_time(“timestamp”,1));
    $update[‘post_date’] = get_date_from_gmt($update[‘post_date_gmt’]);
    }

    Here is a link for download : http://www.laurentdufour.eu/auto-post-scheduler-1.80.1.zip

    To answer to your question, to post to social network, I already use another plugin , it is called SNAP (Social Network Auto Poster), but to recycle I use your plugin, and the combination of both works like a charm.

    Best Regards

    Thread Starter dufour_l

    (@dufour_l)

    >> 1) How would the post be recycled if the date stays the same?

    Well I assume the term ‘recycled’ in my case was not what I have in mind, I mean for instance if we use ‘auto post scheduler’ to recycle post in order to push post on instagram,facebook or tweeter or any social network (This is what I do), I do not need that ‘recycled’ post to appear ‘again’ on the front page of my blog

    >> 2) It should already do this and the keyword search is handled by the WordPress function WP_Query.

    I tried already, and unfortunatly it does not exclude or include a title , nevertheless it works great whith tags.

    But it seems that in WP_Query $args[‘s’] does not handle title, it would be $args[‘title’], but the behavior is not the same, it search in WP_Query for a title, but I have not seen a way of excluding a title

    • This reply was modified 8 years, 1 month ago by dufour_l.
    • This reply was modified 8 years, 1 month ago by dufour_l.

    I had a similar issue this morning, upgrade from 4.6.1 to 4.7, then during the upgrade Error 500.
    I had to disable all my plugins one by one to find the one that caused the issue.

    In my case it was W3 Total Cache, once disabled, I was able to finish the upgrade, and now my wordpress site is working fine; and I am able to access to the dashboard.

    • This reply was modified 9 years, 5 months ago by dufour_l.

    This also happened to my web site, I had to renamme the folder “wordpress-23-related-posts-plugin” to “wordpress-23-related-posts-plugin-disabled” to enter my blog again, then I uninstalled this plugin that I used since at least a year. 🙁

    Thread Starter dufour_l

    (@dufour_l)

    UPDATED : New link for download as of August 2015

    ==> http://goo.gl/E7TaaM

    or

    ==> http://we.tl/J3z4uXeKhf

    Thread Starter dufour_l

    (@dufour_l)

    UPDATED : New link for download as of July 2015 ==> http://dl.free.fr/nZcvm9h4K

Viewing 15 replies - 106 through 120 (of 120 total)