Revisions Control not functioning

Resolved akar1
(@akar1)

2 years ago

Hello dear Bowo,

First I’d like to appreciate your awesome work on this plugin.

I use the free version for most of my websites. One anomaly I have detected is that the “Revisions Control” feature works on a number of my websites on a server (let’s call it Server A for instance), yet the same feature does not work on a number of websites on a different server (Server B), and by “not working” I mean that revisions go over the specified limit.
Although both servers are from the same provider. (albeit they are different plans, but I assume that is irrelevant).

I can not share the URLs to any of these website due to confidentiality unfortunately.
I know you can not really do much with this information, that’s why I was wondering if you have already come across any known pre-requirements for “Revisions Control” to work or not? Or if there are any common issues with it.

I’d appreciate any assistance you could provide.
Regards,

Viewing 5 replies - 1 through 5 (of 5 total)

Plugin Author Bowo
(@qriouslad)

2 years ago

@akar1 thank you for reporting this. Revisions Control does not perform clean up. In other words, if existing posts already have more revisions than the limit set, it will not delete the ‘excess’ revisions. Maybe that’s what’s happening with your other server? i.e. it hosts older sites with posts having revisions that’s already above the limit set in Revisions Control?

Otherwise, do you know of any difference in the way both servers are set up? e.g. one is on Apache, one is on Nginx.

Thread Starter akar1
(@akar1)

2 years ago

Thanks for the reply @qriouslad , I am aware that the feature does not delete previously stored revisions.

In terms of server type, both use Apache. Although I should note that the server in which the feature works utilizes Apache/2.4.57 . And the one in which the feature does not work uses Apache/2.4.59. If that makes any difference.

Plugin Author Bowo
(@qriouslad)

2 years ago

@akar1 have you tried again with the latest version? There was an issue related to how number input fields were not properly saving default values, which resulted in no limit being set when you don’t manually type in the value 10 (which is the default value). There’s a placeholder showing 10, which may look like it’s the saved value, when it’s not, i.e. saved value is none / empty, but input field is showing the placeholder value.

Thread Starter akar1
(@akar1)

2 years ago

Yes I have tried with different values ranging from 1 – 5.
Unfortunately the same issue persists.

I will mark this thread as resolved for now, as there isn’t much information to provide on my end, and I don’t want you to waste time looking around without a solid lead.

If I figure out what exactly is causing the revision control to not function, I will open a new thread in the future.

Thanks,

Plugin Author Bowo
(@qriouslad)

2 years ago

Thanks @akar1
Do open a new thread should you have some clue.
At the moment, I’m unable to replicate the issue as well, i.e. revisions control is limitting revision number as intended on my test site.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Revisions Control not functioning’ is closed to new replies.