I am seeing something similar here, curious how this can be resolved.
-
This reply was modified 5 years, 5 months ago by
dunrie.
Hi Per and dunrie,
In the latest update, we added a new REST route to receive the callbacks send by WordProof. To try if this solves your issue, please update the plugin to version 2.9. After updating, you need to change the webhook url in my.wordproof.com.
1. Go to my.wordproof.com/content
2. Hover over the three dots next to the WordPress icon
3. Click ‘Edit source’
4. Click on ‘Advanced setup’
5. For the webhook url, insert https://$yoursite.$tld/wp-json/wordproof-timestamp/v1/posts and click save
You can check if this solves your problem by clicking the ‘Retry webhook’ button in the WordPress backend.
If this doesn’t solve the issue, please sent us a message at [email protected].
Worked as a charm on a post with the button “Timestamp this page” however the other issue seem to be there still. When I click the “Retry webhook” I still get “Something went wrong”.
In chrome console I get this error on the “Retry webhook”:
Uncaught (in promise) TypeError: Cannot read property ‘createNotice’ of null
at x.addEditorNotice (Timestamp.js:197)
at Timestamp.js:185
Dont know if this error message helps
Hi Per,
Is it possible that you timestamped those items with a different account? If you can send a mail to [email protected], I’ll have some extra tools available to look at the problem!
@dunrie, let me know if the updated plugin solves your issue as well!
I sent a mail to [email protected] with more details, thanks!
Hey Per,
I can’t see any mail from you, can you try to send it again? You can reach me directly via [email protected]. I will close this topic for now while I wait for your email so I keep things organized, but we’ll get to the bottom of this:)
We have rolled out several updates in the past week, so trying the setup (and timestamps) again might help as well!
Jelle | WordProof
