Digiprove daily limit reached

Hi Blamedutchie,

Your daily allowance will reset automatically tomorrow. There is a different allowance for each type of subscription. in the case of free accounts it is 10.

To avoid in future we suggest only Digiproving each post or page once you have completed making changes. Or you could upgrade to a paid subscription. The entry-level “Personal” subscription allows 50 txns per day and costs $10 per month (or $100 per year). See digiprove.com/payment_plans.aspx for full details of costs and benefits.

I understand that fact, I should have been more clearly:

Yesterday I had not Digiproved 10 posts, not even one actually, still the plugin said I have. I just tried to Digiprove the same post and it works flawlessly.

So… Let’s see if I understand the current GUI correctly:

At the top-right of the editor screen we have the & Digiprove part that should be used.

At the lower part of that screen, there is also the “Digiprove this post yes/no” option… When editing an existing post that has already been Digiproved, does this option do anything? Meaning, if we let the option set to yes, does it add to the daily count when we update the post without setting the “& Digiprove” at the top of the screen?

After testing that on a post, the obvious answer is yes. The post gets DP’d again.

So, now the question is: is this by design?

Thanks for detailed description. Sounds like we have a problem related to the Block-based editor. The counter should not be incremented in Block Editor mode unless the & Digiprove option is ticked. And that option should not be visible unless “Digiprove This” is set to Yes.

So we will get to work to verify and resolve.

We have been unable to replicate this behaviour so far. Although we have noticed one GUI issue whereby repeated Digiprove transactions on the same post/page sometimes do not update the highlighted result text which can cause confusion. We will fix this but but it’s not a solution to the problem you experienced. We will keep looking.

Update: We did find a couple of related problems that can lead to the behaviour you described. All in code related to the new/changed features of WordPress 5.

We have published a new version of the plugin (4.02) which solves those problems.

It would be great if you could confirm that this works for you.

Once again thanks for pointing this out.

Thanks for your quick action!

I will get back to you shortly.

It appears the issue has been resolved.

I am still doing a lot of work on existing data and have not had the need to DigiProve a fresh post, but so far so good!

Thanks for feedback, and we remain available if you have any further issues. We will leave this topic as “unresolved” for now.