Sites need the ability to sync comments missed in webhook pushes #33
Comments
|
we also need this feature, so if you need help please let me know |
|
OK, but manual mode is useless. Cron job is ok. Sync was working before fine before this round of plugin upgrades. |
|
I'm experiencing this issue as well. I was able to manually sync previously but since the last plugin update the comments aren't synching. I was directed here from disqus support saying that "there’s something on your site that is blocking the REST API endpoint that is responsible for enabling syncing." Is there any idea when a fix will be available? |
|
Exactly. It is still broken. Support are no longer responding to my thread. |
|
Disquis is very bad plugin. I will review them unfrotunately...:(
Best,
Jacek
2018-03-25 20:08 GMT+02:00 e-m-m-a <notifications@github.com>:
… Exactly. It is still broken. Support are no longer responding to my thread.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#33 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AavzWOHdj_W9Ld5YrZmTh72zZ9wsh2eTks5th90jgaJpZM4SF1tr>
.
|
|
I'm experiencing sync issue too, I sent full details about it to the support forums, contacted support through plugin, couldn't get a clear answer or solution, just the above mentioned "there’s something on your site that is blocking the REST API endpoint that is responsible for enabling syncing". But it's not true, it's not blocking! The syncing is working for about 2-3 minutes, then error occurs. I'm pretty sure this is because of the large amount of comments which are waiting to be synced. The problem occured AFTER an user deleted his/her Disqus user and tenthousands of comments tried to sync back. “The webhook subscription for your forum Üllői út 129. (shortname: ulloiut129) to the endpoint at https://ulloi129.hu/wp-json/disqus/v1/sync/webhook has been disabled due to a large number of errors being returned from your endpoint.” A think I managed to find where is the error: Sun Mar 18 11:25:18.455181 2018] [:error] [pid 2876] [client 208.101.7.43:27665] Error checking in buffer: The buffer you checked in was not checked out https://github.com/Automattic/jetpack/blob/master/sync/class.jetpack-sync-queue.php at 419. row private function validate_checkout( $buffer ) { Full details: |
|
peterszky,
thank you! Disqus support is very weak unfortunately, they are waiting for
users to find the problem (!).
Maybe they will help us after your post.
Best,
Jacek
2018-03-29 22:29 GMT+02:00 peterszky <notifications@github.com>:
… I'm experiencing sync issue too, I sent full details about it to the
support forums, contacted support through plugin, couldn't get a clear
answer or solution, just the above mentioned "there’s something on your
site that is blocking the REST API endpoint that is responsible for
enabling syncing". But it's not true, it's not blocking! The syncing is
working for about 2-3 minutes, then error occurs. I'm pretty sure this is
because of the large amount of comments which are waiting to be synced. The
problem occured AFTER an user deleted his/her Disqus user and tenthousands
of comments tried to sync back.
“The webhook subscription for your forum Üllői út 129
<https://maps.google.com/?q=%C3%9Cll%C5%91i+%C3%BAt+129&entry=gmail&source=g>.
(shortname: ulloiut129) to the endpoint at https://ulloi129.hu/wp-json/
disqus/v1/sync/webhook has been disabled due to a large number of errors
being returned from your endpoint.”
A think I managed to find where is the error:
Sun Mar 18 11:25:18.455181 2018] [:error] [pid 2876] [client
208.101.7.43:27665] Error checking in buffer: The buffer you checked in
was not checked out
[Sun Mar 18 11:25:18.993774 2018] [:error] [pid 2755] [client
208.101.7.44:20547] Error checking in buffer: There are no checked out
buffers
https://github.com/Automattic/jetpack/blob/master/sync/
class.jetpack-sync-queue.php
at 419. row
private function validate_checkout( $buffer ) {
Full details:
https://wordpress.org/support/topic/questions-about-syncing/
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#33 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AavzWFq4HfokrQzVO6HMy9qL14ZvrqgAks5tjUQjgaJpZM4SF1tr>
.
|
|
I am in exactly the same situation as Peter, and have suggested the same
issue - backed up comments to disqus. They are no longer answering my
messages.
…On Fri, 30 Mar 2018, 06:08 jaryszek, ***@***.***> wrote:
peterszky,
thank you! Disqus support is very weak unfortunately, they are waiting for
users to find the problem (!).
Maybe they will help us after your post.
Best,
Jacek
2018-03-29 22:29 GMT+02:00 peterszky ***@***.***>:
> I'm experiencing sync issue too, I sent full details about it to the
> support forums, contacted support through plugin, couldn't get a clear
> answer or solution, just the above mentioned "there’s something on your
> site that is blocking the REST API endpoint that is responsible for
> enabling syncing". But it's not true, it's not blocking! The syncing is
> working for about 2-3 minutes, then error occurs. I'm pretty sure this is
> because of the large amount of comments which are waiting to be synced.
The
> problem occured AFTER an user deleted his/her Disqus user and
tenthousands
> of comments tried to sync back.
>
> “The webhook subscription for your forum Üllői út 129
<https://maps.google.com/?q=%C3%9Cll%C5%91i+%C3%BAt+129&entry=gmail&source=g>
> <
https://maps.google.com/?q=%C3%9Cll%C5%91i+%C3%BAt+129&entry=gmail&source=g
>.
> (shortname: ulloiut129) to the endpoint at https://ulloi129.hu/wp-json/
> disqus/v1/sync/webhook has been disabled due to a large number of errors
> being returned from your endpoint.”
>
> A think I managed to find where is the error:
>
> Sun Mar 18 11:25:18.455181 2018] [:error] [pid 2876] [client
> 208.101.7.43:27665] Error checking in buffer: The buffer you checked in
> was not checked out
> [Sun Mar 18 11:25:18.993774 2018] [:error] [pid 2755] [client
> 208.101.7.44:20547] Error checking in buffer: There are no checked out
> buffers
>
> https://github.com/Automattic/jetpack/blob/master/sync/
> class.jetpack-sync-queue.php
>
> at 419. row
>
> private function validate_checkout( $buffer ) {
>
> Full details:
> https://wordpress.org/support/topic/questions-about-syncing/
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <
#33 (comment)
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AavzWFq4HfokrQzVO6HMy9qL14ZvrqgAks5tjUQjgaJpZM4SF1tr
>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#33 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQK7nAO9_gHPW_-dt9ygee0MPIMKCXSmks5tjb2zgaJpZM4SF1tr>
.
--
Emma Kane
Internet and Ecommerce Consultant
www.iknowthe.net
07787504673
|
|
@ryanvalentin Have there been any updates to this issue? It's been open since February |
|
Disqus ignoring us and our problem...
2018-05-08 19:51 GMT+02:00 buysoap <notifications@github.com>:
… @ryanvalentin <https://github.com/ryanvalentin> Have there been any
updates to this issue? It's been open since February
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#33 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AavzWBITkNqDXqr1NrCAnjAmwjfLS7Veks5twdsggaJpZM4SF1tr>
.
|
|
They are waiting until we fix it
Pobierz aplikację Outlook dla systemu iOS
On Sat, May 12, 2018 at 10:55 AM +0200, "shogtose" <notifications@github.com> wrote:
Yep, problem still occurs. People from Disqus don't even respond to questions via e-mail.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Same, they have stopped responding to my emails. Disqus I hope you are
reading these comments.
…On Sat, 12 May 2018, 10:17 jaryszek, ***@***.***> wrote:
They are waiting until we fix it
Pobierz aplikację Outlook dla systemu iOS
On Sat, May 12, 2018 at 10:55 AM +0200, "shogtose" <
***@***.***> wrote:
Yep, problem still occurs. People from Disqus don't even respond to
questions via e-mail.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#33 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQK7nJ8p1DkSl9Lv0v47yD_0VQ7Bp9Ehks5txqifgaJpZM4SF1tr>
.
--
Emma Kane
Internet and Ecommerce Consultant
www.iknowthe.net
<http://www.iknowthe.net/>
07787504673
|
|
I think that the last plugin update fixed the sync stop isssue. |
|
Manual syncing is working but automatic syncing is not. Where do I find the
site secret key. Is the same as the API key?
On Fri, 25 May 2018, 20:00 peterszky, ***@***.***> wrote:
I think that the last plugin update fixed the sync stop isssue.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#33 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQK7nHEnHZvnVdTfQ9CUFggwx-AlzRCVks5t2FTbgaJpZM4SF1tr>
.
--
Emma Kane
|
|
following |
|
@disqus/disqus-wordpress-plugin
<reply@reply.github.com>
you can sell me your plugin i will handle errors and fix issues.
pt., 16 lis 2018 o 09:14 Łukasz Jarych <jaryszek@gmail.com> napisał(a):
… Exactly Akira has right.
czw., 15 lis 2018 o 21:14 Akira Leir ***@***.***>
napisał(a):
> It has been abandoned, that's why it's not working. I'd suggest you to
> move on to any other alternatives to avoid more headaches. That, or just
> downgrade to 2.83 and live happy ever after.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#37 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AavzWCxWZb91ENeKZrHjj7MhpcODX4I_ks5uvcswgaJpZM4SNQbT>
> .
>
|
and others
There are scenarios where a site will not receive webhook events for new comments to sync them:
The enhancement here will be to provide a way of manually running a sync to make sure all comments are stored locally. This might also possibly include a recurring cron job to do the syncing as well.
The text was updated successfully, but these errors were encountered: