themastercut

Sorry for the big disappointment.

This is a problem that I am by no means personally encountering on clean environments and is apparently related to companion plugins that modify the post state on update.

We tried many times to reproduce this problem but we never succeeded.

This is something we just have to accept until WordPress introduces something like a query queue for post state changes. As long as something else overwrites the state of the entry or blocks the deletion of the duplicate – we can’t do anything about it ??

Again, I’m very sorry for ignoring this thread in the past. I’m really unable to influence collisions in post state changes.

Please give me some more time. I will try to contact the developers of WordPress with a proposal for changes to the core of the engine and we will get rid of this problem once and for all.

Hello!
Our plugin is fully compatible with PHP 8.2.

Just to be sure, we rolled out some more tests with the newest version of WordPress. Everything works fine ??

Could you send us some error descriptions?

That’s really odd, because Revision Manager does not change anything about ACF definitions etc. It only applies additional styles for borders.

Does your post use Gutenberg editor or is it a classic editor?

Hi!

Could you send us your fields definition?
ACF > Tools > Export > Json

I am trying to replicate your issue. No success on ACF PRO 6.1.7 and WordPress 6.2.2

Hi!
It seems like it’s connected to filtering posts content by WordPress wp_kses function.
In short: any external modifications of posts are filtered and only accepted tags stay untouched.

I belive it is by design. You should not leave any scripts in content and use shortcodes instead ??

https://tommcfarlin.com/what-is-wordpress-kses/`

• This reply was modified 1 year, 11 months ago by themastercut.

Hello, sorry for late response.
We were unable to respond, due to geopolitical issues.

I am reaching you right now trough the e-mail.
Again, sorry!

Our plugin does not change the url’s of the target post.
Its purpose is to handle changes in the post content.

I am not sure if I understand your question correctly, but if you are asking if posts are linked by url:

– no, they are linked by ID ??

You can change everything in the target post. No worries.

Hello ??
I’m not sure which “issue” with staging/prod you mean.
License is activated “per WordPress instalaltion”. You can activate/deactivate the license and move it somewhere else, or just buy the “developers bundle”.

Scheduled revisions works out of box. You just set the time of revision post to be pushed in the future. It blends into WordPress ecosystem.

There are methods designed to use RM outside of the WordPress dashboard, but you have to design how your frontend works.

How is your issue connected with Revision Manager TMC plugin?
Our plugin does not interfere with core WordPress functionality ??

We’ve got a message:

“Your plugin is using the admin-page-framework framework which is shipped with the outdated and no longer maintained library jQueryFileTree known to be affected by a path traversal issue, allowing unauthenticated attackers to disclose the folder structure of the web server (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000170)”

In short – it’s admin backend was based on popular framework with some vurnabilities.
The whole re-coding and communication with www.remarpro.com officials took some time, but we are back!

Hello!
It seems that external library is outdated.
We will try to update it as quickly as possible.

WordPress Dashboard is the first screen you see once entering the “/wp-admin/index.php” permalink.

Revision Manager Section is the Dashboard widget ( a white rectangle with title and arrows on the top ).

Hello!
If this happened during merging, it is a known bug in WordPress. Something prevented the old post from deleting it ( like some other plugin was still working on it or something ).

Just simply remove the old one and modify permalink manually ( remove “-2” from the last part of url ).

Sorry to hear you got an issue. It really does not depend on us ??

For future readers: we sorted out it’s the issue with outdated OpenSSL certificate on the client hosting. The renewal of the certificate solved the problem with cUrl.