This is most definitely an edge case, but here's the issue.

  1. Install campaignmonitor.
  2. Enter api and list keys.
  3. Place list block (via blocks or context).
  4. Change api and list keys.
  5. Refresh list cache.
  6. Observe that old block still appears with an error.
  7. Via context menu, edit block and set it to appear in no regions.
  8. No more errors.

We like to call it our ghost block :)

I'm assuming that either on api/list key update or list refresh a check for existing blocks should run and purge.

Comments

cableman0408’s picture

Assigned: Unassigned » cableman0408

Thanks for reporting the ghost blocks :-) I'll look into finding a solution to this.

cableman0408’s picture

Status: Active » Fixed

The block cache is now rebuild if the API keys are updated in the development branch.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.