Frank P. Walentynowicz

Same.

The short answer is – no. This plugin was created to handle standard posts, and categories, only. Support for custom posts, and custom taxonomies, is not a simple task. It would be better handled by a new plugin.

Thank you Ben. I had to change #sidebar to #sidebar-primary, and it works perfectly.

Because rmdir NEVER throws an exception, you’ll have to replace:

try {
    rmdir($this->xcloner_settings->get_xcloner_tmp_path());
} catch (Exception $e) {
    //silent continue
}

with:

if (file_exists($this->xcloner_settings->get_xcloner_tmp_path()))
    rmdir($this->xcloner_settings->get_xcloner_tmp_path());

which will check if directory exists. This does not check if directory is empty, but I believe that it was emptied (if exists) by preceding code.

• This reply was modified 3 years, 8 months ago by Frank P. Walentynowicz.
• This reply was modified 3 years, 8 months ago by Frank P. Walentynowicz.
• This reply was modified 3 years, 8 months ago by Frank P. Walentynowicz.

Old methods of checking if translation file (.mo) is available will be removed in new version. Current method uses language packs.

If the new post belongs to category already mapped, no action is needed. if it does belong to new category, you map it first, then either do apply mapping, or update your post and save it without changes.

Fixed in version 1.7.7

Hi Marius,

Thanks for your quick response.

These are last relevant messages taken from the backup log:
—-
[2018-02-15 18:09:01] xcloner_archive.INFO: Closing the backup archive backup_fw2s.com-2018-02-15_18-08-sql-2767e.tgz with 2*512 zero bytes blocks. [] []
[2018-02-15 18:09:01] xcloner_scheduler.INFO: File archive process FINISHED. [“CRON”] []
[2018-02-15 18:09:01] xcloner_archive.INFO: Sending backup notification to [email protected] [] []
[2018-02-15 18:09:01] xcloner_file_system.INFO: Cleaning the backup storage on matching rules [] []
[2018-02-15 18:09:01] xcloner_file_system.INFO: Deleting backup backup_fw2s.com-2018-02-10_07-01-sql-2dcd5.tgz matching rule [“BACKUP QUANTITY LIMIT”,”1 >= 2″] []
[2018-02-15 18:09:01] php_system.INFO: E_WARNING: array ( ‘type’ => 2, ‘message’ => ‘A non-numeric value encountered’, ‘file’ => ‘/home/fw2scom0/public_html/wp-content/plugins/xcloner-backup-and-restore/vendor/league/flysystem/src/Adapter/Local.php’, ‘line’ => 424, ) [] []
[2018-02-15 18:09:01] php_system.INFO: E_WARNING: array ( ‘type’ => 2, ‘message’ => ‘A non-numeric value encountered’, ‘file’ => ‘/home/fw2scom0/public_html/wp-content/plugins/xcloner-backup-and-restore/vendor/league/flysystem/src/Adapter/Local.php’, ‘line’ => 424, ) [] []
—-
Note: the backup finishes correctly, warning messages appear after deleting old backups (that finishes correctly, too).

• This reply was modified 6 years, 9 months ago by Frank P. Walentynowicz.

Would you please be more specific? Latest update of WordPress or the plugin. State version of updated item. I think we have problem with terminology – what do you mean by “auto-upload” feature?

Thank you for reporting.
This bug had been fixed in version 1.7.1

Unfortunately Apply Mapping will only add category thumbnails to your posts. The program has no way of knowing about thumbnails added manually.

Use Apply Mapping button. It will add thumbnails to all existing posts.

1) No. It already uses category name as alt text
2) Yes.

Thank you for reporting this issue. It is not FPW Category Thumbnails plugin making incorrect call but built in FPW Post Thumbnails. It is fixed now in version 1.6.7