VE Events 1.4.4 - Unified Meta Key Naming

Changes in v1.4.4

Unified Meta Key Naming

Prefix	Type	Description
_vev_*	Stored	Database fields (private)
ve_*	Virtual	Computed/formatted output

Virtual Meta Keys

Key	Example
ve_start_date	"January 15, 2025"
ve_start_time	"2:00 PM"
ve_end_date	"January 17, 2025"
ve_end_time	"5:00 PM"
ve_date_range	"January 15 – 17, 2025"
ve_time_range	"2:00 PM – 5:00 PM" or "All day"
ve_datetime_formatted	"January 15, 2025, 2:00 PM – 5:00 PM"
ve_status	"Upcoming" / "Ongoing" / "Past"
ve_is_upcoming	true / false
ve_is_ongoing	true / false

Code Cleanup

• Consolidated duplicate formatting logic (single source of truth)
• Fixed critical bug: timestamp formatting used strtotime() on Unix integers
• VEV_Fields callbacks now delegate to VEV_Frontend helpers
• computed_meta filter delegates to VEV_Fields registry
• Removed all legacy vev_* constants and references
• Fixed fatal error on event edit page (deleted constants)
• Status calculation now consistently uses grace period