Skip to content

v1.6.4 - Fixed DELETE Endpoint Cache Issue

Choose a tag to compare

View all tags
@gserafini gserafini released this 30 Oct 06:48
· 10 commits to main since this release
v1.6.4
b130124

What's Changed

Critical Fix: DELETE endpoint now properly handles EME's void return value and WordPress object cache

The Problem

  • eme_db_delete_event() returns void/null (not success/failure)
  • Previous code incorrectly interpreted null as failure
  • WordPress object cache was serving stale data during verification
  • Result: Events were deleted but API returned 500 error

The Solution

  • Remove check on void return value from eme_db_delete_event()
  • Clear WordPress object cache: wp_cache_delete("eme_event $event_id")
  • Verification now queries fresh data from database
  • Returns proper 200 success when deletion succeeds

Technical Details

EME caches events using wp_cache_set("eme_event $event_id", $event, '', 60) for 60 seconds. After deletion, the cache must be cleared to verify the event is actually gone.

Installation

Download the ZIP file below and install via WordPress admin or upload to your plugins directory.

Full Changelog: v1.6.3...v1.6.4

Assets 3
Loading