Forum Replies Created

Viewing 15 replies - 646 through 660 (of 4,099 total)
  • Plugin Author NextScripts

    (@nextscripts)

    1. What is difference between the contents of the “my_image” field in the posts that have a correct image and broken URL? Can I see some examples?

    2. SNAP has absolutely nothing to do with Twitter cards. Twitter assigns cards for approved domains by itself using it’s special metatags.

    Please see here: https://dev.twitter.com/cards/types/summary

    Plugin Author NextScripts

    (@nextscripts)

    Do you need any help with this error? It’s pretty self-explanatory.

    http://www.phasesmag.com/wp/wp-content/uploads/2017/11/Marinos-Tsagkarakis.jpg is NOT a real URL of your image. It’s a 301 redirect to https://www.phasesmag.com/wp/wp-content/uploads/2017/11/Marinos-Tsagkarakis.jpg

    Twitter does not follow redirects. You MUST provide the actual URL of the image.

    Plugin Author NextScripts

    (@nextscripts)

    Are you sure you have checkbox checked and featured image set?

    Are you getting any errors? Please check your Log/History page and let me know what do you have there.

    Plugin Author NextScripts

    (@nextscripts)

    @jeromem_net what problem exactly are you experiencing? There are no known Twitter issues with 4.0.11. Everything was fixed

    Plugin Author NextScripts

    (@nextscripts)

    Stable cron is a requirement for SNAP to work. It doesn’t mater if you use Windows scheduler, real unix cron, WordPress Builtin Cron, your hoster’s service, or third party service like easycron. WP Cron must be triggered once every minute or two.

    Please go to the Log/History tab and check only “All Cron Events” checkbox.

    It should look like this (Stable cron requests every minute):

    [2017-11-16 11:42:59] - [Cron Request]- 59.93s after the previous one. | Cron called from wget
    [2017-11-16 11:42:01] - [Cron Request]- 59.84s after the previous one. | Cron called from wget
    [2017-11-16 11:41:01] - [Cron Request]- 59.26s after the previous one. | Cron called from wget
    [2017-11-16 11:40:02] - [Cron Request]- 61.92s after the previous one. | Cron called from wget
    [2017-11-16 11:39:01] - [Cron Request]- 59.41s after the previous one. | Cron called from wget
    [2017-11-16 11:38:01] - [Cron Request]- 59.65s after the previous one. | Cron called from wget
    Plugin Author NextScripts

    (@nextscripts)

    That’s it?

    It yes, it sounds like you have Javascript broken on your site. Please take a look at your debug console in any browser for Javascript errors.

    Plugin Author NextScripts

    (@nextscripts)

    %IMG% does not insert the actual image. It inserts it’s URL.

    If you want featured image to be inserted in the medium post, you need to wrap %IMG% in the HTML tag. Something like:

    <img src="%IMG%" alt="%TITLE%"/>

    Plugin Author NextScripts

    (@nextscripts)

    It shows me a green Auth info box with no error.

    If it shows you the box, it has an error. Green auth box must disappear in couple seconds if there no issues.

    Plugin Author NextScripts

    (@nextscripts)

    Could you please provide some more details? What type of fields? How exactly you save them? How to replicate it?

    We just tried to install ACF add a text custom field and then publish a new post. That field was saved without any issues.

    Plugin Author NextScripts

    (@nextscripts)

    Do you have WP Cron setup correctly?
    http://www.nextscripts.com/tutorials/wp-cron-scheduling-tasks-in-wordpress/

    Please go to the Log/History tab and check only “All Cron Events” checkbox.

    You should see ONLY crons executed from WGET or Mozilla every one or two minutes. If you see nothing at all, calls from “WordPress/4.x.x” or calls made at irregular time intervals, your cron is not set correctly.

    Plugin Author NextScripts

    (@nextscripts)

    Could you please stop generating those threads?

    Plugin works fine for everyone. Our support done everything possible to help you. You don’t want to listen and follow our instructions.

    You are no longer our paid customer. Please uninstall our plugin ASAP.

    Plugin Author NextScripts

    (@nextscripts)

    Here is the story of your issue:

    1. [2012] Since first version of the plugin came out Facebook API allowed you to set/change title, description and the image of the shared link.
    —- SNAP passed description and the image to each API request to share a link.

    2. [July 18, 2017] Facebook made a description to stop allowing you to set/change title, description and the image of the shared link. They said they done it to \”fight fake news\”.
    —- SNAP was still passing description and the image to each API request to share a link, but those parameters were completely ignored by Facebook.More info about that: https://www.nextscripts.com/known-issues/facebook-shared-links-info/

    3. [July – November 2017] Many big Facebook\’s partners complained about their decision.
    —- SNAP was still passing description and the image to each API request to share a link, but those parameters were completely ignored by Facebook.

    4. [November 07, 2017] Facebook decided to partially rollback it\’s decision about disallowing an ability set/change link info. They decided to allow that to some \”selected partners\”.
    Facebook releases API v2.11. That API comes with one change affecting SNAP. Those \”Selected partners\” (officially called \”owners of the URL\”) are now able to set/change title, description and the image of the shared link. Everybody else is now getting \”(#100) Only owners of the URL have the ability to specify the picture, name, thumbnail or description params\” errors.
    —- SNAP was still passing description and the image to each API request to share a link, but those parameters were NOT IGNORED anymore. They were the cause of the (#100) error.

    5. [November 10, 2017] We release SNAP 4.0.11. We completely removed the part of the code that were passing description and the image to each API request to share a link. SNAP is no longer passing this parameters and that has fixed the (#100) error..

    SNAP is open source plugin, you can take a look the code and see by yourself that part that were sending \”picture, name, thumbnail or description params\” were removed from the fb.api.php file. All you need to do to fix your issue is update your plugin to 4.0.11. It\’s physically not possible to get this error in 4.0.11. If you are still getting the error, your plugin is not 4.0.11. Our support has told you that about 30 times. Please update your plugin. Make sure all they files are updated. Clean all the cache. Once you get the update it will work. This issue has affected a lot of people between November 7 and November 10. 4.0.11 fixed it for everyone.

    Plugin Author NextScripts

    (@nextscripts)

    cherlihy,

    Here is the story of your issue:

    1. [2012] Since first version of the plugin came out Facebook API allowed you to set/change title, description and the image of the shared link.
    —- SNAP passed description and the image to each API request to share a link.

    2. [July 18, 2017] Facebook made a description to stop allowing you to set/change title, description and the image of the shared link. They said they done it to “fight fake news”.
    —- SNAP was still passing description and the image to each API request to share a link, but those parameters were completely ignored by Facebook.More info about that: https://www.nextscripts.com/known-issues/facebook-shared-links-info/

    3. [July – November 2017] Many big Facebook’s partners complained about their decision.
    —- SNAP was still passing description and the image to each API request to share a link, but those parameters were completely ignored by Facebook.

    4. [November 07, 2017] Facebook decided to partially rollback it’s decision about disallowing an ability set/change link info. They decided to allow that to some “selected partners”.
    Facebook releases API v2.11. That API comes with one change affecting SNAP. Those “Selected partners” (officially called “owners of the URL”) are now able to set/change title, description and the image of the shared link. Everybody else is now getting “(#100) Only owners of the URL have the ability to specify the picture, name, thumbnail or description params” errors.
    —- SNAP was still passing description and the image to each API request to share a link, but those parameters were NOT IGNORED anymore. They were the cause of the (#100) error.

    5. [November 10, 2017] We release SNAP 4.0.11. We completely removed the part of the code that were passing description and the image to each API request to share a link. SNAP is no longer passing this parameters and that has fixed the (#100) error..

    SNAP is open source plugin, you can take a look the code and see by yourself that part that were sending “picture, name, thumbnail or description params” were removed from the fb.api.php file. All you need to do to fix your issue is update your plugin to 4.0.11. It’s physically not possible to get this error in 4.0.11. If you are still getting the error, your plugin is not 4.0.11. Our support has told you that about 30 times. Please update your plugin. Make sure all they files are updated. Clean all the cache. Once you get the update it will work. This issue has affected a lot of people between November 7 and November 10. 4.0.11 fixed it for everyone.

    Plugin Author NextScripts

    (@nextscripts)

    Nothing has been changed.

    “parse error. not well formed” error means that your post contains something that Tumblr can’t accept.

    Are you getting this error every time you are trying to publish new post?

    Plugin Author NextScripts

    (@nextscripts)

    This means cron is not running on your site at all. SNAP will not work, not posts will be autoposted automatically.

    Please setup WP Cron setup:
    http://www.nextscripts.com/tutorials/wp-cron-scheduling-tasks-in-wordpress/

Viewing 15 replies - 646 through 660 (of 4,099 total)