Kurt Johnson Photography — DevKinsta Setup & Bug Fixes

Date: 2026-02-10 Site: kurtjohnsonphotography.com Local: https://kurtjohnsonphotographycom.local:50382 Theme: gmlaunch Site Path: /Users/edowns/DevKinsta/public/kurtjohnsonphotographycom

DevKinsta Setup

• Resolved MariaDB authentication issue (root password out of sync) preventing site creation
• Resolved port conflict with Local by Flywheel (both competing for ports 80/443)
• Added SSH key to MyKinsta for direct access
• Synced 16GB uploads and 707MB database via rsync/SSH (faster than DevKinsta's built-in sync)
• Performed full URL search-replace (52,046 replacements) for local development
• Fixed wp-config.php for local DB connection
• Granted MariaDB root access from Docker network

SSH Details

• Host: 34.162.230.19
• Port: 61436
• User: kurtjohnsonphotographycom
• Auth: SSH key (ed25519)
• Remote path: /www/kurtjohnsonphotographycom_376/public/

Bug Fix Report

1. Fixed PHP warnings on Photography archive pages

• File: inc/cpt-loops/loop-photography.php (line 65)
• Issue: Undefined variable $have_posts caused two PHP warnings on every photography archive page load — "Undefined variable $have_posts" and "Attempt to read property post_count on null." These fired repeatedly per page load (once per loop iteration), flooding error logs.
• Fix: Replaced undefined $have_posts with WordPress global $wp_query to properly check total post count against the loop counter.

2. Fixed ACF translation loading notice (WordPress 6.7+ compliance)

• File: functions/acf-add-options-page.php
• Issue: acf_add_options_page() was called at file include time, triggering a "Translation loading triggered too early" notice introduced in WordPress 6.7.
• Fix: Wrapped the function call in an init action hook to comply with updated WordPress translation loading standards.

3. Deactivated Bulk Delete plugin

• Issue: Plugin loads translations too early, triggering the same WP 6.7+ notice. This is a plugin-side issue with no available fix.
• Action: Deactivated the plugin. It was not in active use on the site.

All three issues verified resolved — debug log is clean after fixes.