Fix per-job cron schedule reverting when it matches the global default

[Copilot]

When a per-import cron schedule was set to the same value as the global default, it was silently discarded on save and the import fell back to "Once Daily" on reload.

Root cause

save_feedzy_import_feed_meta() unset fz_cron_schedule not only when empty, but also when it equalled the global schedule value — meaning an explicit per-job selection was never persisted if it happened to match the global setting.

// Before — incorrectly drops matching per-job schedules
$global_cron_schedule = ! empty( $this->free_settings['general']['fz_cron_schedule'] ) ? $this->free_settings['general']['fz_cron_schedule'] : '';
if (
    empty( $data_meta['fz_cron_schedule'] ) || $global_cron_schedule === $data_meta['fz_cron_schedule']
) {
    unset( $data_meta['fz_cron_schedule'] );
}

// After — only strip when not set
if ( empty( $data_meta['fz_cron_schedule'] ) ) {
    unset( $data_meta['fz_cron_schedule'] );
}

Changes

• includes/admin/feedzy-rss-feeds-import.php — Remove the global-schedule equality check from the per-job schedule unset condition; the meta is now only discarded when empty, preserving any explicit per-job value regardless of what the global default is.

[Copilot]

Pull request overview

This PR updates Feedzy’s import-job meta saving behavior so a per-import cron schedule selection is no longer discarded when it matches the global default, ensuring the chosen value persists across reloads.

Changes:

• Stop unsetting fz_cron_schedule when it equals the global schedule; only unset when the value is empty.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.