cmaverick

Forum Replies Created

Viewing 15 replies - 1 through 15 (of 23 total)
1 2
  • Forum: Plugins
    In reply to: [NextScripts: Social Networks Auto-Poster] Facebook Comments not working
    cmaverick

    (@cmaverick)

    7 years, 2 months ago

    I’m actually having the same issue. Did anyone ever resolve this?

    Forum: Plugins
    In reply to: [NextScripts: Social Networks Auto-Poster] Pro version- open ticket over a month now
    cmaverick

    (@cmaverick)

    7 years, 7 months ago

    Did you ever get a response on your ticket? I’ve been waiting for a long time for mine as well… it’s not clear if anyone is watching.

    Forum: Plugins
    In reply to: [NextScripts: Social Networks Auto-Poster] Pro version not loading comments.
    Thread Starter cmaverick

    (@cmaverick)

    7 years, 8 months ago

    I actually do have a support ticket. But as per the other user who makes a similar comment: https://wordpress.org/support/topic/pro-version-open-ticket-for-months/ there’s not feedback coming from the support ticket at all.

    Is there any way to tell if anyone is checking them?

    Forum: Plugins
    In reply to: [NextScripts: Social Networks Auto-Poster] FB Comments not importing
    Thread Starter cmaverick

    (@cmaverick)

    8 years ago

    I can’t get that error to popup at all. But I may not know how to turn on debug mode. I assume you mean: “My Content Filters (apply_filters(‘the_content’) are broken, don’t use them” since that’s only reference to a debug mode in your FAQ.

    But that doesn’t add any extra content to the comment import dialog. Is there something else I am missing?

    In any case, I assume that you’re probably correct as to what is happening. Do you have any advice for fixing it or is this assumed to be something that will be corrected once the plugin has its own API?

    Forum: Plugins
    In reply to: [NextScripts: Social Networks Auto-Poster] FB Comments not importing
    Thread Starter cmaverick

    (@cmaverick)

    8 years ago

    As an addendum. Went back and checked the log hours later and now see these:

    | WHERE (flt = "snap" OR (flt = "cron" AND (type = "E" OR type="W"))) |
[2018-04-18 03:21:08] - [**WARNING. Unhealthy Cron Request**] [ [More info] ] - Too close (4.80s) to the previous one. Now - 03:21:08 | Previous - 03:21:03| Cron called from 207.254.60.242 (WordPress/4.9.5; http://voxpopcast.com/wp)
[2018-04-18 03:19:08] - [Comments Import] [ALL] - Checking for new comments now... Array ( [0] => 287 [1] => 245 [2] => 241 [3] => 210 [4] => 205 [5] => 181 [6] => 177 [7] => 172 [8] => 165 [9] => 163 [10] => 157 [11] => 154 [12] => 149 [13] => 146 [14] => 141 ) 
[2018-04-18 03:03:14] - [**WARNING. Unhealthy Cron Request**] [ [More info] ] - Too close (16.60s) to the previous one. Now - 03:03:14 | Previous - 03:02:57| Cron called from 207.254.60.242 (WordPress/4.9.5; https://voxpopcast.com/wp)
[2018-04-18 03:02:57] - [Comments Import] [ALL] - Checking for new comments now... Array ( [0] => 287 [1] => 245 [2] => 241 [3] => 210 [4] => 205 [5] => 181 [6] => 177 [7] => 172 [8] => 165 [9] => 163 [10] => 157 [11] => 154 [12] => 149 [13] => 146 [14] => 141 ) 
[2018-04-18 02:46:54] - [Comments Import] [ALL] - Checking for new comments now... Array ( [0] => 287 [1] => 245 [2] => 241 [3] => 210 [4] => 205 [5] => 181 [6] => 177 [7] => 172 [8] => 165 [9] => 163 [10] => 157 [11] => 154 [12] => 149 [13] => 146 [14] => 141 ) 
[2018-04-18 02:30:28] - [Comments Import] [ALL] - Checking for new comments now... Array ( [0] => 287 [1] => 245 [2] => 241 [3] => 210 [4] => 205 [5] => 181 [6] => 177 [7] => 172 [8] => 165 [9] => 163 [10] => 157 [11] => 154 [12] => 149 [13] => 146 [14] => 141 ) 
[2018-04-18 02:15:08] - [**WARNING. Unhealthy Cron Request**] [ [More info] ] - Too close (15.89s) to the previous one. Now - 02:15:08 | Previous - 02:14:52| Cron called from 207.254.60.242 (WordPress/4.9.5; http://voxpopcast.com/wp)
[2018-04-18 02:14:53] - [Comments Import] [ALL] - Checking for new comments now... Array ( [0] => 287 [1] => 245 [2] => 241 [3] => 210 [4] => 205 [5] => 181 [6] => 177 [7] => 172 [8] => 165 [9] => 163 [10] => 157 [11] => 154 [12] => 149 [13] => 146 [14] => 141 ) 
[2018-04-18 01:58:41] - [Comments Import] [ALL] - Checking for new comments now... Array ( [0] => 287 [1] => 245 [2] => 241 [3] => 210 [4] => 205 [5] => 181 [6] => 177 [7] => 172 [8] => 165 [9] => 163 [10] => 157 [11] => 154 [12] => 149 [13] => 146 [14] => 141 ) 
[2018-04-18 01:42:48] - [Comments Import] [ALL] - Checking for new comments now... Array ( [0] => 287 [1] => 245 [2] => 241 [3] => 210 [4] => 205 [5] => 181 [6] => 177 [7] => 172 [8] => 165 [9] => 163 [10] => 157 [11] => 154 [12] => 149 [13] => 146 [14] => 141 ) 
[2018-04-18 01:26:49] - [Comments Import] [ALL] - Checking for new comments now... Array ( [0] => 287 [1] => 245 [2] => 241 [3] => 210 [4] => 205 [5] => 181 [6] => 177 [7] => 172 [8] => 165 [9] => 163 [10] => 157 [11] => 154 [12] => 149 [13] => 146 [14] => 141 ) 
[2018-04-18 01:24:04] - [**WARNING. Unhealthy Cron Request**] [ [More info] ] - Too close (2.33s) to the previous one. Now - 01:24:04 | Previous - 01:24:02| Cron called from 207.254.60.242 (WordPress/4.9.5; http://voxpopcast.com/wp)
[2018-04-18 01:15:07] - [**WARNING. Unhealthy Cron Request**] [ [More info] ] - Too close (14.14s) to the previous one. Now - 01:15:07 | Previous - 01:14:53| Cron called from 207.254.60.242 (WordPress/4.9.5; http://voxpopcast.com/wp)
[2018-04-18 01:11:31] - [Comments Import] [ALL] - Checking for new comments now... Array ( [0] => 287 [1] => 245 [2] => 241 [3] => 210 [4] => 205 [5] => 181 [6] => 177 [7] => 172 [8] => 165 [9] => 163 [10] => 157 [11] => 154 [12] => 149 [13] => 146 [14] => 141 ) 
[2018-04-18 00:52:07] - [Comments Import] [ALL] - Checking for new comments now... Array ( [0] => 287 [1] => 245 [2] => 241 [3] => 210 [4] => 205 [5] => 181 [6] => 177 [7] => 172 [8] => 165 [9] => 163 [10] => 157 [11] => 154 [12] => 149 [13] => 146 [14] => 141 )

    Note: before the plugin went bad, comments were importing just fine, as can be seen at this post: http://voxpopcast.com/wp/2018/03/26/call-for-comments-superhero-origins-and-ours/

    I don’t think anything else has changed. Is this affecting anyone else?

    Forum: Plugins
    In reply to: [NextScripts: Social Networks Auto-Poster] Forced to post as visitor
    Thread Starter cmaverick

    (@cmaverick)

    8 years ago

    As an addendum. Went back and checked the log hours later and now see these:

    | WHERE (flt = "snap" OR (flt = "cron" AND (type = "E" OR type="W"))) |
[2018-04-18 03:21:08] - [**WARNING. Unhealthy Cron Request**] [ [More info] ] - Too close (4.80s) to the previous one. Now - 03:21:08 | Previous - 03:21:03| Cron called from 207.254.60.242 (WordPress/4.9.5; http://voxpopcast.com/wp)
[2018-04-18 03:19:08] - [Comments Import] [ALL] - Checking for new comments now... Array ( [0] => 287 [1] => 245 [2] => 241 [3] => 210 [4] => 205 [5] => 181 [6] => 177 [7] => 172 [8] => 165 [9] => 163 [10] => 157 [11] => 154 [12] => 149 [13] => 146 [14] => 141 ) 
[2018-04-18 03:03:14] - [**WARNING. Unhealthy Cron Request**] [ [More info] ] - Too close (16.60s) to the previous one. Now - 03:03:14 | Previous - 03:02:57| Cron called from 207.254.60.242 (WordPress/4.9.5; https://voxpopcast.com/wp)
[2018-04-18 03:02:57] - [Comments Import] [ALL] - Checking for new comments now... Array ( [0] => 287 [1] => 245 [2] => 241 [3] => 210 [4] => 205 [5] => 181 [6] => 177 [7] => 172 [8] => 165 [9] => 163 [10] => 157 [11] => 154 [12] => 149 [13] => 146 [14] => 141 ) 
[2018-04-18 02:46:54] - [Comments Import] [ALL] - Checking for new comments now... Array ( [0] => 287 [1] => 245 [2] => 241 [3] => 210 [4] => 205 [5] => 181 [6] => 177 [7] => 172 [8] => 165 [9] => 163 [10] => 157 [11] => 154 [12] => 149 [13] => 146 [14] => 141 ) 
[2018-04-18 02:30:28] - [Comments Import] [ALL] - Checking for new comments now... Array ( [0] => 287 [1] => 245 [2] => 241 [3] => 210 [4] => 205 [5] => 181 [6] => 177 [7] => 172 [8] => 165 [9] => 163 [10] => 157 [11] => 154 [12] => 149 [13] => 146 [14] => 141 ) 
[2018-04-18 02:15:08] - [**WARNING. Unhealthy Cron Request**] [ [More info] ] - Too close (15.89s) to the previous one. Now - 02:15:08 | Previous - 02:14:52| Cron called from 207.254.60.242 (WordPress/4.9.5; http://voxpopcast.com/wp)
[2018-04-18 02:14:53] - [Comments Import] [ALL] - Checking for new comments now... Array ( [0] => 287 [1] => 245 [2] => 241 [3] => 210 [4] => 205 [5] => 181 [6] => 177 [7] => 172 [8] => 165 [9] => 163 [10] => 157 [11] => 154 [12] => 149 [13] => 146 [14] => 141 ) 
[2018-04-18 01:58:41] - [Comments Import] [ALL] - Checking for new comments now... Array ( [0] => 287 [1] => 245 [2] => 241 [3] => 210 [4] => 205 [5] => 181 [6] => 177 [7] => 172 [8] => 165 [9] => 163 [10] => 157 [11] => 154 [12] => 149 [13] => 146 [14] => 141 ) 
[2018-04-18 01:42:48] - [Comments Import] [ALL] - Checking for new comments now... Array ( [0] => 287 [1] => 245 [2] => 241 [3] => 210 [4] => 205 [5] => 181 [6] => 177 [7] => 172 [8] => 165 [9] => 163 [10] => 157 [11] => 154 [12] => 149 [13] => 146 [14] => 141 ) 
[2018-04-18 01:26:49] - [Comments Import] [ALL] - Checking for new comments now... Array ( [0] => 287 [1] => 245 [2] => 241 [3] => 210 [4] => 205 [5] => 181 [6] => 177 [7] => 172 [8] => 165 [9] => 163 [10] => 157 [11] => 154 [12] => 149 [13] => 146 [14] => 141 ) 
[2018-04-18 01:24:04] - [**WARNING. Unhealthy Cron Request**] [ [More info] ] - Too close (2.33s) to the previous one. Now - 01:24:04 | Previous - 01:24:02| Cron called from 207.254.60.242 (WordPress/4.9.5; http://voxpopcast.com/wp)
[2018-04-18 01:15:07] - [**WARNING. Unhealthy Cron Request**] [ [More info] ] - Too close (14.14s) to the previous one. Now - 01:15:07 | Previous - 01:14:53| Cron called from 207.254.60.242 (WordPress/4.9.5; http://voxpopcast.com/wp)
[2018-04-18 01:11:31] - [Comments Import] [ALL] - Checking for new comments now... Array ( [0] => 287 [1] => 245 [2] => 241 [3] => 210 [4] => 205 [5] => 181 [6] => 177 [7] => 172 [8] => 165 [9] => 163 [10] => 157 [11] => 154 [12] => 149 [13] => 146 [14] => 141 ) 
[2018-04-18 00:52:07] - [Comments Import] [ALL] - Checking for new comments now... Array ( [0] => 287 [1] => 245 [2] => 241 [3] => 210 [4] => 205 [5] => 181 [6] => 177 [7] => 172 [8] => 165 [9] => 163 [10] => 157 [11] => 154 [12] => 149 [13] => 146 [14] => 141 )

    Is there something wrong with WP-Cron or is something else just not working right?

    Forum: Plugins
    In reply to: [NextScripts: Social Networks Auto-Poster] Forced to post as visitor
    Thread Starter cmaverick

    (@cmaverick)

    8 years ago

    So as a note. The sub problem of my original issue is STILL a problem. Comments still do not import. They also don’t work when I hit the import manually button. I looked through the forums here and I’ve seen this is a problem that has cropped up before. The suggestion seems to be:

    1. Please click on the “Posted on…” link.
    2. Write a comment.
    3. Switch back to the plugin and click “Import Comments”
    4. Please check your Log/History page and let me know what do you have there.

    I tried that. Nothing interesting appears in the logs. It’s as if it’s not even trying:

    FB post: https://www.facebook.com/1774745869257270/posts/1810440449021145
    Blog post: http://voxpopcast.com/wp/2018/04/16/episode-2-do-you-remember-nostalgia/

    Logs:

    Y:| WHERE (flt = "snap" OR flt = "cron" OR flt = "sys") |
[2018-04-18 00:49:08] - [Cron Request]- 60.75s after the previous one. | Cron called from 207.254.60.242 (WordPress/4.9.5; http://voxpopcast.com/wp)
[2018-04-18 00:48:07] - [Cron Request]- 45.53s after the previous one. | Cron called from 207.254.60.242 (WordPress/4.9.5; http://voxpopcast.com/wp)
[2018-04-18 00:47:22] - [Cron Request]- 33.00s after the previous one. | Cron called from 207.254.60.242 (WordPress/4.9.5; http://voxpopcast.com/wp)
[2018-04-18 00:46:49] - [Cron Request]- 101.08s after the previous one. | Cron called from 207.254.60.242 (WordPress/4.9.5; http://voxpopcast.com/wp)
[2018-04-18 00:45:08] - [Cron Request]- 39.18s after the previous one. | Cron called from 207.254.60.242 (WordPress/4.9.5; http://voxpopcast.com/wp)
0
    Forum: Plugins
    In reply to: [NextScripts: Social Networks Auto-Poster] Forced to post as visitor
    Thread Starter cmaverick

    (@cmaverick)

    8 years ago

    That seems to work. At least for me.

    Forum: Plugins
    In reply to: [NextScripts: Social Networks Auto-Poster] Forced to post as visitor
    Thread Starter cmaverick

    (@cmaverick)

    8 years ago

    updated and reauthorized. But the software is still posting the test message as user rather than as the page. Is there some other change that needs to be made under the new version?

    Forum: Plugins
    In reply to: [NextScripts: Social Networks Auto-Poster] Forced to post as visitor
    Thread Starter cmaverick

    (@cmaverick)

    8 years, 1 month ago

    So it was working for me, but then it seemed to use the ability to import comments. I’ve since reauthorized and now it’s broken again.

    Forum: Plugins
    In reply to: [NextScripts: Social Networks Auto-Poster] Forced to post as visitor
    Thread Starter cmaverick

    (@cmaverick)

    8 years, 1 month ago

    It’s fixed for me (I commented as such, but it is back a page). Didn’t mark resolved because some people seem to still be having issues.

    Forum: Plugins
    In reply to: [NextScripts: Social Networks Auto-Poster] Forced to post as visitor
    Thread Starter cmaverick

    (@cmaverick)

    8 years, 1 month ago

    Changes at FB seem to have taken effect and this is working now…. at least for me (currently using 2.8API. Haven’t tried updating back to 2.12 yet)

    Forum: Plugins
    In reply to: [NextScripts: Social Networks Auto-Poster] Forced to post as visitor
    Thread Starter cmaverick

    (@cmaverick)

    8 years, 1 month ago

    It turned out that this is a Facebook API bug. It affects Facebook APIs Version 2.11 and 2.12. The bug was reported and confirmed by Facebook, but they are not so fast on fixing.

    If you have an older Facebook App(v2.10 or earlier), you can use it and it will work fine.

    This appears to not be the case.

    I had an older testbed app sitting around that I was able to revert to older APIS. I just tried posting with API 2.10, 2.9 and 2.5 (the earliest I have access to… and it’s expiring next month). All of them seem to have the same issue of posting as me rather than the page.

    2.10 post: http://voxpopcast.com/wp/2018/03/24/test-seven-api-2-10/
    2.10 FB: https://www.facebook.com/voxpopcast/posts/1785024731562717

    2.9 post: http://voxpopcast.com/wp/2018/03/24/test-five-fb-api-v2-9/
    2.9 FB: https://www.facebook.com/voxpopcast/posts/1785008414897682

    2.5 post: http://voxpopcast.com/wp/2018/03/24/test-six-api-2-5/
    2.5 FB: https://www.facebook.com/voxpopcast/posts/1785018858229971

    So it doesn’t seem that rolling the API back works. Something is forcing the the app to post as visitor no matter what version of the API is being used.

    I am using v4.1.7 of SNAP for all of this… is it possible that an earlier version of the plugin is needed to correctly use the old APIs?

    Forum: Plugins
    In reply to: [NextScripts: Social Networks Auto-Poster] Forced to post as visitor
    Thread Starter cmaverick

    (@cmaverick)

    8 years, 1 month ago

    The user who authorizes plugin MUST be an owner of the Facebook app and MUST be an admin of the page or group at the time of authorization. If both those requirements are met it will post as the “page name”.

    I am both the page owner and the authenticated user. In fact, as I am only in the setup phase, the page only has myself and 3 friends following it. So I am the admin of the page, the owner of the app and the authenticated user.

    I also tried the disabling visitor posts idea that buy4me tried and had the same result. For some reason the app seems to not realize that I am the admin of the page.

    I also tried deleting the plugin and creating a brand new facebook app just in case (based on other feedback on other posts in this forum). None of that seems to work.

    Forum: Plugins
    In reply to: [NextScripts: Social Networks Auto-Poster] Forced to post as visitor
    Thread Starter cmaverick

    (@cmaverick)

    8 years, 1 month ago

    periodically I get this error on the plugin’s Facebook Account Info page under “Where to Post”

    Can't get Page Token. Array
(
    [headers] => Array
        (
            [strict-transport-security] => max-age=15552000; preload
            [x-fb-trace-id] => GWjt4E4slT/
            [x-fb-rev] => 3745862
            [content-type] => application/json; charset=UTF-8
            [facebook-api-version] => v2.12
            [cache-control] => no-store
            [pragma] => no-cache
            [access-control-allow-origin] => *
            [expires] => Sat, 01 Jan 2000 00:00:00 GMT
            [www-authenticate] => OAuth "Facebook Platform" "insufficient_scope" "(#200) Access to this data is temporarily disabled for non-active accounts due to changes we are making to the Facebook Platform"
            [vary] => Accept-Encoding
            [content-encoding] => gzip
            [x-fb-debug] => zgmXsGoX/OaG1Wqx7sxTluophfB8GaiirUgpdMy8Iiq3tzXY90rgS6Vx7bU6pITFsYSG+gTz/1MGNUNw/QMyKA==
            [date] => Thu, 22 Mar 2018 17:47:21 GMT
            [connection] => keep-alive
            [content-length] => 205
        )

    [body] => {
   "error": {
      "message": "(#200) Access to this data is temporarily disabled for non-active accounts due to changes we are making to the Facebook Platform",
      "type": "OAuthException",
      "code": 200,
      "fbtrace_id": "GWjt4E4slT/"
   }
}
    [response] => Array
        (
            [code] => 403
            [message] => Forbidden
        )

    [cookies] => Array
        (
        )

)

    But refreshing the options removes it.

Viewing 15 replies - 1 through 15 (of 23 total)
1 2