Support » Plugin: Social Media Share Buttons | MashShare » Fix: content you requested cannot be displayed right now. It may be temporarily

  • Plugin Author Rene Hermenau

    (@renehermi)


    For quite some time user facing the following error message when they want to share via Mashshare or other Social sharing plugins:

    “The content you requested cannot be displayed right now. It may be temporarily unavailable, the link you clicked on may have expired, or you may not have permission to view this page.”

    We’ve found out that this issue affects (only) sites which are using facebook comments or any third party plugin that embeds facebook comments.
    The problem seems to be an broken app id here. For the moment we can only confirm that you can fix this you disabling the comment plugin:

    Try again to share the page! This should be working now.

    You have to repeat all these steps for every entire page of your website if you want to resolve it immediately. If you can wait or if you have too many pages you have to be patient until facebook is purging its internal cache.
    This can take hours or up to some days!

    Its possible that creating a new facebook app id is also able to fix this. I have not test this, yet.

    If you have any other solution how to solve this facebook bug please let us know here.

    ~ René

    https://wordpress.org/plugins/mashsharer/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Tyler Johnson

    (@tylerjohnsondesign)

    Hey René,

    I tested creating a new app ID, but that didn’t fix it. However, taking the code from Facebook’s plugin generator site and inputting it myself using a plugin (code is below), comments display fine and I’m still able to share just fine. So, something other WordPress Facebook comments plugins are adding is causing the issues.

    <?php
    /**
     * Plugin Name: WP Developers Facebook Comments
     * Plugin URI: http://wpdevelopers.com
     * Description: Facebook comments by WP Developers.
     * Version: 1.1
     * Author: Tyler Johnson
     * Author URI: http://tylerjohnsondesign.com
     * License: GPL2
     */
    
    $appid = 'FACEBOOKAPPIDHERE';
    
    // Add Facebook Code to Footer
    function wpdev_fbcomments_footer() {
        global $appid;
        if($appid) {
            echo '<div id="fb-root"></div>
                    <script>(function(d, s, id) {
                      var js, fjs = d.getElementsByTagName(s)[0];
                      if (d.getElementById(id)) return;
                      js = d.createElement(s); js.id = id;
                      js.src = "//connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.5&appId=' . $appid . '";
                      fjs.parentNode.insertBefore(js, fjs);
                    }(document, \'script\', \'facebook-jssdk\'));</script>';
        }
    }
    add_action('wp_footer', 'wpdev_fbcomments_footer');
    
    // Output Facebook Comments
    function wpdev_fbcomments() {
        global $appid;
        if($appid) {
            $output = '<div class="fb-comments" data-href="' . get_permalink() . '" data-width="100%" data-numposts="6"></div>';
            return $output;
        }
    }
    add_shortcode('wpdevfb', 'wpdev_fbcomments');
    add_action('wpdevfb', 'wpdev_fbcomments');
    Plugin Author Rene Hermenau

    (@renehermi)

    > So, something other WordPress Facebook comments plugins

    What facebook comments plugin are you using? Did you already try to reach the author of it to fix it? If you compare the original code of the facebook comments and the one of the plugin that is causing the issue it should be simple to check out whats wrong.

    However, thanks for your feedback. Interesting to see that it is not a broken app id rather than (propbably) broken facebook comment sdk implementation.

    Hey René and Tyler,

    Same issue happened to us, we can’t pin point when it happened, but sometime during the week last week.

    We tried fetching new scrape info, and it didn’t help. We disabled our facebook comments plugin ( super socializer ). But we disabled everything, and then only enabled mashshare, and then tried sharing and got the same error.

    So when I use the facebook debugger, I re-scrape my homepage, and I then click the graph API button on the bottom, I get this error. Does this make any sense to anyone? Tyler does it do this for you too?

    {
    “error”: {
    “message”: “An access token is required to request this resource.”,
    “type”: “OAuthException”,
    “code”: 104,
    “fbtrace_id”: “G/aF4BM7ENU”
    }
    }

    We have inquiries into facebook as well, but they haven’t responded yet. Also found this URL to report blocked websites, Tyler maybe you want to give it a shot as well? :

    https://www.facebook.com/help/contact/244560538958131

    In case we were mistakenly blocked.

    What do you guys think? Is it just a coincidence for mashshare users? Have other social plugins been experiencing similar things?

    Thanks
    Matt

    Plugin Author Rene Hermenau

    (@renehermi)

    Hi Matt,

    > “An access token is required to request this resource.

    This means the fb account you are using for accessing the open graph api needs an generated access token. (You can do this in the developer section but this is not related to the issue here.)

    I notice that the socializer is using the fb sdk v. 2.4 the Like-Bar add-on is using the version 2.0.
    Its possible that this leads to the error.

    Please disable the likebar add-on, call fb debugger and “fetch new”.

    Try than again.

    If this does not work disable the socializer AND the likebar add-on, call fb debugger and “fetch new”.

    Try than again.

    Does that help?

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Fix: content you requested cannot be displayed right now. It may be temporarily’ is closed to new replies.