Bug Nonce is invalid error

Hi,

We don't find such an issue on our test websites. Could you please send the admin login details to info[at]gvectors.com email address? I'll ask the developers to check the issue for you.

I am experiencing the same issue on our site. 

@tensionmouse,

Please wait a bit—this issue is currently being checked by our developers.

You can send the admin login details to info[at]gvectors.com, as this will help us investigate the issue more efficiently.

@asti Dear Asti,

I appreciate your efforts in looking into this. I must say that I'm bit reluctant to sharing my admin credentials, which is not a best practice to follow in terms of data safety, and may also not be very effective if there's a large plugin userbase that experience the same, as I see more comments to this thread. 

Hope for a prompt solution and many thanks again for your support.

We are also experiencing this issue. 

it seems to be very situation-dependent in that a very few people can comment and we can also do so when logged in as Admin, but the vast majority of our readers are locked out by the nonce invalid error.

Mobile access seems more limited than desktop. 

We aren't certain it's the result of the update, but the timing and the fact others are experiencing this implies it could be.

Our site gets a lot of comments and this is a MAJOR problem for us. 

Is anyone actually, you know -  doing anything about this?

You are taking a very laidback and leisurely attitude to the fact your latest  update may have broken your product for many users. 

The hook you keep posting doesn't help btw.

We've just rolled back to the previous install and see if that fixes the issue. 

I will let you know

In most cases, the issue is resolved using the hook code:
https://wpdiscuz.com/community/troubleshooting/issues-with-nonce/#post-30175

Dear Sophie,

We’ve already replied to your email. Please continue the conversation there.

@asti Dear Asti,

As I mentioned on the first post of this thread, I have tried that code but it didn't work. It appears to miss some more lines of code. The filter calls some parameters or methodds, but no actual functions are being added.

I'd really appreciate your support in looking into this code, or whether the devs are working towards a solution. 

Thank you and kind regards,

HELP. I have this problem too and it's a big problem. When will this be fixed? 

@asti  The email I sent you was on a completely different topic.

I have NOT emailed you on this topic.

FYI - we rolled back to the prev installation (76.46) and this seems to have at least partially fixed this invalid nonce issue.

As we said in our previous reply the hook you reccomend does not work for us, in fact it breaks the site. 

@asti - My reply to you is still pending after TWO days? 

@asti Dear Asti,

This is a kind reminder that this topic is still not resolved - can you please give us any updates?

If only to at least advise that the devs are working on a solution behind the scenes. 

Or to provide more insights regarding the correct code snippet that should be used in order to have a temporary resolution?

Many thanks for your support and kind regards,

@ubweb,

Did you try this filter?

add_filter('wpdiscuz_is_update_nonce_with_ajax', '__return_true');

Reference: https://wordpress.org/support/topic/wpdiscuz_is_update_nonce_with_ajax/

Above solved both the caching conflict and comment posting issues I was experiencing.

Let me know!

Posted by: @ubweb

↑

@asti Dear Asti,

As I mentioned on the first post of this thread, I have tried that code but it didn't work. It appears to miss some more lines of code. The filter calls some parameters or methodds, but no actual functions are being added.

I'd really appreciate your support in looking into this code, or whether the devs are working towards a solution. 

Thank you and kind regards,

I managed to fix the nonce issue on our site adding the hook code to functions.php

/* disable wpdiscuz nonce for guests */
add_filter('wpdiscuz_validate_nonce_for_guests', '__return_false');

Importantly, I cleared all caches. Our comments returned to normal.