yshimizu
Forum Replies Created
-
Thanks for the reply, @kevinb
I will try to implement this with action hooks.I am also looking forward to implementing the revision decline notification!
Hello.
I found a similar problem and solution described in another topic.
https://wordpress.org/support/topic/frontend-click-on-a-checkbox-field-triggers-validation/Why don’t you read it and give it a try?
@kevinb
I just confirmed the update of the plugin.
Thanks for the diligent communication and response!@kevinb
Thank you for your prompt work.I have tried it and 3.0.12-rc2 seems to work as expected.
The scheduled revisions were successfully reflected at the date and time you set!If there is one thing that concerns me, it is that when WordPress debug mode is on, when I click New Revision from the post list to create a revision, I get some Warning errors in functions.php of the revisionary.
(If debug mode is off, these errors will not interfere with the operation.)The error may be due to the theme you are using or other plug-ins you have installed, but just in case, here is a summary
(File paths are omitted)Warning: array_diff(): Expected parameter 1 to be an array, null given in (File path)/wp-content/plugins/revisionary/functions.php on line 159 Warning: Invalid argument supplied for foreach() in (File path)/wp-content/plugins/revisionary/functions.php on line 163 Warning: Cannot modify header information - headers already sent by (output started at (File path)/wp-content/plugins/revisionary/functions.php:159) in (File path)/wp-includes/pluggable.php on line 1355 Warning: Cannot modify header information - headers already sent by (output started at (File path)/wp-content/plugins/revisionary/functions.php:159) in (File path)/wp-includes/pluggable.php on line 1358
If, after reviewing the above, the error appears to be due to a theme or other plugin, please mark this topic as resolved.
Thank you so much for taking the time to help me out on this one!
Very helpful!@kevinb
Thank you too for your reply.
I have tried turning on WordPress debug mode and using the error log monitor plugin.1. before the reserved update process started.
At least, I didn’t find any errors for this plugin or revision.2. after the scheduled date and time.
No errors were found.The server PHP version is 7.4 and WordPress version is 5.9.1.
(The same applies to environments built with Local by Flywheel)I don’t know if this is related to this issue, but I have noticed something else.
When I create a new revision or edit a revision from the revision queue with the asynchronous publish box unchecked in the settings area, the screen goes blank when I save the changes.
If you turn on WordPress debug mode and perform the same operation, the error is not displayed. You will just see a blank screen as well.
In both cases, the edits themselves were saved.This phenomenon was also observed only on the site where the problem occurred, and was not reproduced in the environment built with Local by Flywheel.
Is there anything else I should check?
@benjaminprojas
I have confirmed that the issue has been successfully resolved by updating to 4.0.9.
Thank you for your quick response!