mwmcw
Forum Replies Created
-
Thanks for your quick reply! I’ve already altered some of those capabilities. Unfortunately this is not an update-proof solution. After every update, I’ve to change those lines again. And there’s one more snippet which has to be changed.
So in total you’d have to change the following lines:
(1) It’s the snippet on line 109 which has to be changed to:
$capability = 'edit_others_posts';(2) But also the
manage_optionson line 272 which has to be changed to:
&& current_user_can( 'edit_others_posts' )Otherwise editors wouldn’t be able to save / update their changed content.
Maybe this would be a feature enhancement for an upcoming update, to have a checkbox or anything similar, where you could set the roles, which are able to edit/delete etc. Just as a humble suggestion. Otherwise thanks for a fantastic plugin and all the work you’ve put into this!
- This reply was modified 6 years, 1 month ago by mwmcw.
Thank you very much for the quick fix, David Anderson!
Hello again and thanks for getting back to this issue!
I’m not using any remote storage.
The backup files on the same server are intact and properly backed up. Maybe helpful in addition to my last post: I am using PHP 7.1 – could this be a factor? Although it hasn’t been before in previous versions.
My log file statement is:
[11-Sep-2017 13:38:09 UTC] PHP Warning: include_once(/XXX/wp-content/plugins/updraftplus/methods/.php): failed to open stream: No such file or directory in /XXX/wp-content/plugins/updraftplus/class-updraftplus.php on line 3658 [11-Sep-2017 13:38:09 UTC] PHP Warning: include_once(): Failed opening '/XXX/wp-content/plugins/updraftplus/methods/.php' for inclusion (include_path='.:/opt/alt/php71/usr/share/pear') in /XXX/wp-content/plugins/updraftplus/class-updraftplus.php on line 3658 [11-Sep-2017 13:38:09 UTC] UpdraftPlus: no such storage class: UpdraftPlus_BackupModule_It’s day for day the same error notice in the log file. Scheduled are daily database backups, and weekly complete backups.
Cheers
MarkusHey there,
got the same error notice on two sites. I also ignored it initially, but then deinstalled and reinstalled the plugin. Same same again … any help / instructions would be much appreciated.
Thanks!