[ad_1]
Plugin Author
finnj
(@finnj)
The update should not have broken Frontier Post.
I have actually done quite some testing the past couple of day, and the only challenges was with php 8, not 6.0.2
I just uploaded a new version 6.0.0, but it is not the Stable version yet.
You can see description here:
Thread Starter
TMonto
(@tmonto)
I updated the plugin to 6.0.0 but that had no effect on this problem, editing posts still turn them into drafts and clears the content.
This happens with authors and I’ve also tested it myself as an admin. Disabling the capability “Can Drafts” has no effect, it removes the draft option from the edit page but still the post ends up as a draft. I can’t find any other settings that might help with this.
Plugin Author
finnj
(@finnj)
What versions (WP & PHP) are you running:
Go to frontier settings, it is listed on the first row.
You might have another plugin interferring, as you are the only one reporting this.
You might want to turn logging on temporary:
In wp-config.php, add these 2 lines before
/* That’s all, stop editing! Happy publishing. */
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
Then try and recreate, and see if there are errors in the log.
remember to set the logging to false, when you are done.
Thread Starter
TMonto
(@tmonto)
WP is 6.0.2 and PHP 7.4.30
For some reason I didn’t manage to get debug working (I’ll see more on that), but in error_log I got these:
[02-Oct-2022 05:23:34 UTC] PHP Warning: array_key_exists() expects parameter 2 to be array, null given in /wp-content/plugins/frontier-post/include/frontier_post_util.php on line 446 [02-Oct-2022 05:23:34 UTC] PHP Warning: count(): Parameter must be an array or an object that implements Countable in /wp-content/plugins/frontier-post/include/frontier_post_util.php on line 452
Thread Starter
TMonto
(@tmonto)
Got the debug working, and it pointed out that there were out-of-date custom form files in my theme folder which caused the problem (eg. frontier_post_form_standard.php). I replaced those with original files and the issue went away.
Thanks!
