* feat(images): route Cloudflare Workers AI via AI Gateway by default
Direct probe on 2026-04-21 confirmed the Cloudflare AI Gateway
route to Workers AI (`gateway.ai.cloudflare.com/.../workers-ai/@cf/...`)
is no longer 403ing — the upstream regression noted in v0.8.0's
ARCHITECTURE.md #16 and in thread image-pipeline seq 6 has been
resolved. Routing via the gateway gives us the same benefits we
already get for OpenRouter LLM calls: response caching, cost/latency
dashboard, rate limiting.
Changes:
- `Cloudflare_Image_Support::build_endpoint_url()` now prefers the
gateway URL derived from the existing `prautoblogger_ai_gateway_base_url`
option. Direct API remains the fallback.
- New private helper `build_gateway_workers_ai_url()` strips the
OpenRouter path suffix from the configured gateway URL and appends
`/workers-ai/{model}`. Returns empty string (fallback to direct) when:
no gateway URL configured, the new toggle is off, or the URL isn't a
valid `https://gateway.ai.cloudflare.com/...` shape.
- New admin toggle `prautoblogger_cf_image_via_gateway` (default on) in
the Images section. Operators can disable to force direct API without
clearing the LLM-path gateway URL.
- ARCHITECTURE.md #16 rewritten to reflect the v0.8.2+ gateway routing.
- CHANGELOG.md v0.8.2 entry under Changed.
Tests (new `CloudflareImageSupportTest`):
- Direct URL when gateway not configured.
- Gateway URL derived correctly when configured + toggle on.
- Toggle off forces direct URL even with gateway configured.
- Malformed gateway URL falls back to direct (defensive).
- `is_nsfw_error()` only matches error code 3030 (pinned separately so
a tolerance regression fails early).
Cost impact: near-zero. Gateway adds a few ms of latency and enables
response caching — could *reduce* cost on identical prompts within the
configurable cache TTL.
Uninstall: new option covered by existing prautoblogger_% LIKE sweep.
Implements Commit 1b (narrow AI-Gateway-migration scope) per thread
image-pipeline seq 7.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* chore(cost): seed new toggles in activator defaults; tighten URL stripper
QA review on cd45ae2 surfaced two things; one real, one hallucinated:
- **Real (fixed):** `prautoblogger_cf_image_via_gateway` and v0.8.1's
`prautoblogger_image_nsfw_retry` weren't seeded in
`Activator::set_default_options()`. Belt-and-braces — the `get_option()`
fallback at the read site already defaults to '1', so no user-visible
regression exists, but seeding the options follows the established
pattern for every other plugin setting and makes intent legible to
operators inspecting `wp_options` directly.
- **Hallucinated (rejected):** the reviewer claimed
`CloudflareImageSupportTest` methods 2–5 were empty stubs. Verified
— every test has real `$this->assert*` calls (10 total across the 5
cases). Ignoring. Flagging the false-positive to the CTO per the
qa-review quality-tracking protocol.
Also clarified the docblock + tightened the ternary inside
`build_gateway_workers_ai_url()` — explicit `strrpos` false-check
instead of the `?:` short-circuit, so a no-slash base (defensive edge)
falls through cleanly instead of returning a weirdly-sliced URL.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(schedule): interpret `prautoblogger_schedule_time` in site timezone
Per thread scheduled-gen-timezone seq 1: WordPress core calls
`date_default_timezone_set('UTC')` early in bootstrap, so the activator's
`strtotime("tomorrow HH:MM")` was resolving in UTC regardless of the
site's configured timezone. On peptiderepo.com (Asia/Singapore, UTC+8)
a `schedule_time` of `06:00` fired at 14:00 local.
Fold this into the existing v0.8.2 branch (PR #102) since both this fix
and the earlier CF-image-gateway change target the same version and
touch overlapping files (activator, settings-fields-extended).
Changes:
- `Activator::next_daily_generation_timestamp()` — new public helper
that reads `prautoblogger_schedule_time`, constructs a
`DateTimeImmutable('tomorrow', wp_timezone())`, applies the
configured hour/minute, returns a Unix timestamp. Defensive fallback
to the old UTC-interpretation behaviour on any DateTime parse error
so a bad tz string can't brick the schedule.
- `Activator::schedule_cron()` delegates to the helper instead of
calling `strtotime` directly.
- New `Activator::reschedule_daily_in_site_timezone_v082()` — one-shot
migration that clears the stale UTC-scheduled event and re-queues
using the helper. Gated by `prautoblogger_migrated_schedule_tz_v082`
option so it runs exactly once. Logs an INFO line comparing
before/after next_run for auditability.
- `class-prautoblogger.php::on_check_db_version()` invokes the
migration on every admin_init; the one-shot flag handles re-run
guarding (no DB_VERSION bump needed — the migration is independent
of the schema version).
- Settings description for "Generation Time" now says
"...in your site's configured timezone (Settings → General →
Timezone). Current site timezone: <wp_timezone_string()>" instead
of the ambiguous "server timezone" phrasing.
File-size compliance:
- Adding the timezone helpers pushed `class-activator.php` to 352
lines. Extracted the 104-line `create_tables()` SQL to a new
`class-schema-installer.php` (136 lines). Activator now 245 lines,
schema file fully dedicated to dbDelta.
Tests (new):
- `ActivatorScheduleTest` — SGT 06:00 → 22:00 UTC prev day; UTC 06:00
→ 06:00 UTC (no-op case); Asia/Kathmandu UTC+5:45 → 00:15 UTC
(fractional offset); malformed time input doesn't throw.
- `ActivatorMigrationTest` — pre-seeded UTC cron gets cleared and
rescheduled in SGT; second pass is idempotent.
CHANGELOG v0.8.2 entry now also covers the timezone fix under Fixed +
the description wording change under Changed.
Implements thread `scheduled-gen-timezone` seq 1 spec.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: peptiderepo <peptiderepo@users.noreply.github.com>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
246 lines
9.0 KiB
PHP
Executable File
246 lines
9.0 KiB
PHP
Executable File
<?php
|
|
declare(strict_types=1);
|
|
|
|
/**
|
|
* Handles plugin activation: creates database tables, sets default options,
|
|
* and schedules the initial cron job.
|
|
*
|
|
* Triggered by: WordPress `register_activation_hook` in prautoblogger.php.
|
|
* Dependencies: WordPress $wpdb, dbDelta().
|
|
*
|
|
* @see class-deactivator.php — Reverses transient/cron setup on deactivation.
|
|
* @see ARCHITECTURE.md — Database schema definitions.
|
|
*/
|
|
class PRAutoBlogger_Activator {
|
|
|
|
/**
|
|
* Run activation tasks.
|
|
*
|
|
* Creates custom database tables if they don't exist, sets default option
|
|
* values (without overwriting existing ones), and schedules the daily
|
|
* generation cron event.
|
|
*
|
|
* Side effects: writes to wp_options, creates database tables, schedules WP-Cron event.
|
|
*
|
|
* @return void
|
|
*/
|
|
public static function activate(): void {
|
|
self::create_tables();
|
|
self::set_default_options();
|
|
self::schedule_cron();
|
|
self::backpopulate_run_id_meta_v081();
|
|
|
|
// Store the DB version so we can run migrations on future updates.
|
|
update_option( 'prautoblogger_db_version', PRAUTOBLOGGER_DB_VERSION, false );
|
|
}
|
|
|
|
/** Delegate to `PRAutoBlogger_Schema_Installer::install()` — see that class. */
|
|
private static function create_tables(): void {
|
|
PRAutoBlogger_Schema_Installer::install();
|
|
}
|
|
|
|
/**
|
|
* Set default option values without overwriting existing ones.
|
|
*
|
|
* Uses add_option() which is a no-op if the option already exists.
|
|
*
|
|
* Side effects: writes to wp_options.
|
|
*
|
|
* @return void
|
|
*/
|
|
private static function set_default_options(): void {
|
|
$defaults = [
|
|
'prautoblogger_analysis_model' => PRAUTOBLOGGER_DEFAULT_ANALYSIS_MODEL,
|
|
'prautoblogger_writing_model' => PRAUTOBLOGGER_DEFAULT_WRITING_MODEL,
|
|
'prautoblogger_editor_model' => PRAUTOBLOGGER_DEFAULT_EDITOR_MODEL,
|
|
'prautoblogger_daily_article_target' => 1,
|
|
'prautoblogger_writing_pipeline' => 'multi_step',
|
|
'prautoblogger_niche_description' => '',
|
|
'prautoblogger_target_subreddits' => '[]',
|
|
'prautoblogger_monthly_budget_usd' => 50.00,
|
|
'prautoblogger_tone' => 'informational',
|
|
'prautoblogger_min_word_count' => 800,
|
|
'prautoblogger_max_word_count' => 2000,
|
|
'prautoblogger_topic_exclusions' => '[]',
|
|
'prautoblogger_enabled_sources' => '["reddit"]',
|
|
'prautoblogger_article_font_family' => 'default',
|
|
'prautoblogger_article_font_size' => 0,
|
|
'prautoblogger_table_borders' => '1',
|
|
'prautoblogger_schedule_time' => '03:00',
|
|
'prautoblogger_log_level' => 'info',
|
|
'prautoblogger_image_nsfw_retry' => '1',
|
|
'prautoblogger_cf_image_via_gateway' => '1',
|
|
];
|
|
|
|
foreach ( $defaults as $key => $value ) {
|
|
add_option( $key, $value );
|
|
}
|
|
}
|
|
|
|
/**
|
|
* Schedule the daily generation cron event if not already scheduled.
|
|
*
|
|
* The custom 'prautoblogger_six_hours' schedule is normally registered via
|
|
* the `cron_schedules` filter in class-prautoblogger.php. However, activation
|
|
* runs before `plugins_loaded`, so the filter may not be registered yet.
|
|
* We register it inline here to ensure it exists at scheduling time.
|
|
*
|
|
* Side effects: registers a WP-Cron event, may register a cron schedule.
|
|
*
|
|
* @return void
|
|
*/
|
|
private static function schedule_cron(): void {
|
|
if ( ! wp_next_scheduled( 'prautoblogger_daily_generation' ) ) {
|
|
$timestamp = self::next_daily_generation_timestamp();
|
|
if ( $timestamp > 0 ) {
|
|
wp_schedule_event( $timestamp, 'daily', 'prautoblogger_daily_generation' );
|
|
}
|
|
}
|
|
|
|
// Ensure the six-hour schedule exists before referencing it.
|
|
// Activation can fire before plugins_loaded, so the cron_schedules filter
|
|
// in class-prautoblogger.php may not be hooked yet.
|
|
$schedules = wp_get_schedules();
|
|
if ( ! isset( $schedules['prautoblogger_six_hours'] ) ) {
|
|
add_filter( 'cron_schedules', static function ( array $scheds ): array {
|
|
$scheds['prautoblogger_six_hours'] = [
|
|
'interval' => 6 * HOUR_IN_SECONDS,
|
|
'display' => __( 'Every Six Hours', 'prautoblogger' ),
|
|
];
|
|
return $scheds;
|
|
} );
|
|
}
|
|
|
|
// Schedule a separate metrics collection job (runs every 6 hours).
|
|
if ( ! wp_next_scheduled( 'prautoblogger_collect_metrics' ) ) {
|
|
wp_schedule_event( time() + HOUR_IN_SECONDS, 'prautoblogger_six_hours', 'prautoblogger_collect_metrics' );
|
|
}
|
|
|
|
// v0.8.1: daily reaper for orphan `llm_research` rows. Pinned to
|
|
// 03:15 so it runs 15 min after the primary generation cron, giving
|
|
// any live pipeline time to finish and call amortize_research_costs
|
|
// cleanly before the reaper scans.
|
|
if ( ! wp_next_scheduled( 'prautoblogger_reap_orphan_research_rows' ) ) {
|
|
$tomorrow = strtotime( 'tomorrow 03:15' );
|
|
if ( false !== $tomorrow ) {
|
|
wp_schedule_event( $tomorrow, 'daily', 'prautoblogger_reap_orphan_research_rows' );
|
|
}
|
|
}
|
|
}
|
|
|
|
/**
|
|
* Compute the next daily-generation timestamp in the site's configured
|
|
* timezone. Fixes the v<0.8.2 bug where `strtotime("tomorrow HH:MM")`
|
|
* evaluated in UTC (WP core sets `date_default_timezone_set('UTC')`),
|
|
* firing the cron N hours off from user intent where N is the site's
|
|
* UTC offset.
|
|
*
|
|
* @return int Unix timestamp, or 0 on any failure.
|
|
*/
|
|
public static function next_daily_generation_timestamp(): int {
|
|
$time_str = (string) get_option( 'prautoblogger_schedule_time', '03:00' );
|
|
$parts = explode( ':', $time_str );
|
|
$hour = isset( $parts[0] ) ? absint( $parts[0] ) : 3;
|
|
$minute = isset( $parts[1] ) ? absint( $parts[1] ) : 0;
|
|
|
|
try {
|
|
$site_tz = function_exists( 'wp_timezone' )
|
|
? wp_timezone()
|
|
: new \DateTimeZone( 'UTC' );
|
|
$local = ( new \DateTimeImmutable( 'tomorrow', $site_tz ) )
|
|
->setTime( $hour, $minute, 0 );
|
|
return (int) $local->getTimestamp();
|
|
} catch ( \Exception $e ) {
|
|
// Defensive: never leave the site without any schedule because
|
|
// of a bad tz string. Fall back to the pre-fix behaviour.
|
|
$timestamp = strtotime( "tomorrow {$hour}:{$minute}" );
|
|
return false === $timestamp ? 0 : (int) $timestamp;
|
|
}
|
|
}
|
|
|
|
/**
|
|
* v0.8.2 one-shot migration — reschedule `prautoblogger_daily_generation`
|
|
* in the site's timezone.
|
|
*
|
|
* Existing installs had their daily cron scheduled with the v<0.8.2
|
|
* UTC-interpretation bug. This clears the stale event and reschedules it
|
|
* using the timezone-aware helper, exactly once per site (gated by
|
|
* `prautoblogger_migrated_schedule_tz_v082`). Logs an INFO line with the
|
|
* before/after next-run times so the outcome is auditable.
|
|
*
|
|
* @return void
|
|
*/
|
|
public static function reschedule_daily_in_site_timezone_v082(): void {
|
|
if ( get_option( 'prautoblogger_migrated_schedule_tz_v082' ) ) {
|
|
return;
|
|
}
|
|
|
|
$old_timestamp = wp_next_scheduled( 'prautoblogger_daily_generation' );
|
|
wp_clear_scheduled_hook( 'prautoblogger_daily_generation' );
|
|
|
|
$new_timestamp = self::next_daily_generation_timestamp();
|
|
if ( $new_timestamp > 0 ) {
|
|
wp_schedule_event( $new_timestamp, 'daily', 'prautoblogger_daily_generation' );
|
|
}
|
|
|
|
if ( class_exists( 'PRAutoBlogger_Logger', false ) ) {
|
|
PRAutoBlogger_Logger::instance()->info(
|
|
sprintf(
|
|
'Rescheduled daily generation in site timezone (was UTC). Old next_run: %s, new next_run: %s.',
|
|
false !== $old_timestamp ? gmdate( 'Y-m-d H:i:s \\U\\T\\C', (int) $old_timestamp ) : 'unscheduled',
|
|
$new_timestamp > 0 ? gmdate( 'Y-m-d H:i:s \\U\\T\\C', $new_timestamp ) : 'unscheduled'
|
|
),
|
|
'activator'
|
|
);
|
|
}
|
|
|
|
update_option( 'prautoblogger_migrated_schedule_tz_v082', '1' );
|
|
}
|
|
|
|
/**
|
|
* One-shot v0.8.1 migration — back-populate `_prautoblogger_run_id`
|
|
* post_meta for existing posts from their gen-log rows.
|
|
*
|
|
* Lets the orphan-research-row reaper (v0.8.1+) attribute historic
|
|
* orphan rows to sibling posts via post_meta lookup, without having
|
|
* to walk the generation_log table. Gated by
|
|
* `prautoblogger_migrated_run_id_meta_v081` so it runs exactly once
|
|
* per site.
|
|
*
|
|
* Side effects: adds post_meta rows for existing PRAutoBlogger posts
|
|
* that don't already have `_prautoblogger_run_id`.
|
|
*
|
|
* @return void
|
|
*/
|
|
private static function backpopulate_run_id_meta_v081(): void {
|
|
if ( get_option( 'prautoblogger_migrated_run_id_meta_v081' ) ) {
|
|
return;
|
|
}
|
|
|
|
global $wpdb;
|
|
$gen_log = $wpdb->prefix . 'prautoblogger_generation_log';
|
|
|
|
// For each (post_id, run_id) pair present in the gen-log, write
|
|
// the run_id meta if it's not already set. Uses the first run_id
|
|
// seen per post — in practice each post is linked to exactly one run.
|
|
// phpcs:ignore WordPress.DB.DirectDatabaseQuery.DirectQuery
|
|
$pairs = $wpdb->get_results(
|
|
"SELECT post_id, MIN(run_id) AS run_id FROM {$gen_log}
|
|
WHERE post_id IS NOT NULL AND run_id IS NOT NULL AND run_id != ''
|
|
GROUP BY post_id"
|
|
);
|
|
|
|
if ( is_array( $pairs ) ) {
|
|
foreach ( $pairs as $row ) {
|
|
$post_id = (int) ( $row->post_id ?? 0 );
|
|
$run_id = (string) ( $row->run_id ?? '' );
|
|
if ( $post_id > 0 && '' !== $run_id && ! metadata_exists( 'post', $post_id, '_prautoblogger_run_id' ) ) {
|
|
update_post_meta( $post_id, '_prautoblogger_run_id', $run_id );
|
|
}
|
|
}
|
|
}
|
|
|
|
update_option( 'prautoblogger_migrated_run_id_meta_v081', '1' );
|
|
}
|
|
}
|