Strange, I didn’t do any of those 3 items, and yet it deactivated. It’s happened at least once, maybe twice. I did not check the purchase history before activating it again, but will do that if it happens again.

I’ll keep a close eye on it in the coming days/weeks, and will let you know if it happens again.

And some sort of grace period and email notification would be very helpful rather than it lapsing silently and making capabilities available to people who should have very limited access. Thanks!

The license deactivated on its own again. When it was deactivated, the license page on your site still said the license was being used by my website, but it was deactivated on my website.

I checked the live site and the development site.

On the live site, the ‘id’ column is not set to auto-increment, but on the development site it is. The problem of the license deactivating hasn’t happened on the development site, so I think you are correct in your diagnosis of this issue.

However, when I try to change the ‘id’ column to auto-increment on the live site, I get this error: “#1075 – Incorrect table definition; there can be only one auto column and it must be defined as a key”. What do you suggest?

I tried making it the primary key, but doesn’t like that there are multiple rows with 0. Does it matter what values I give for the “id” for these?
wpfront-user-role-editor-personal-pro-license-key-last-checked
wpfront-user-role-editor-personal-pro-license-key-expires
wpfront-user-role-editor-personal-pro-license-key-status
wpfront-user-role-editor-personal-pro-license-key

I have no idea how this happened, I’ve not modified the database structure, just copied it directly from my development environment when I set up the live server. It’s set up properly on the development environment.

Thanks, I made the fixes to the db, and now the table is set to auto-increment. I’ll keep an eye on this in the coming days and will let you know if the problem returns. Thanks for your assistance.