v0.9.5

• Fix: Notifications were still sent even when IfOnly conditions were not met. Root cause: the gform_notification filter fires inside GFCommon::send_notification(), but Gravity Forms does not re-check isActive after the filter — the email proceeds regardless. Replaced the isActive = false approach with a two-hook strategy: gform_notification now flags the notification (ifonly_suppress), and a new gform_pre_send_email callback sets abort_email = true for flagged notifications, which is the documented GF mechanism to cancel delivery.

• Fix: On notification and confirmation settings pages, IfOnly rules appeared to be lost after clicking the save button (they were actually saved — a page refresh showed them correctly). Root cause: GF's settings framework builds the field HTML before running process_postback(), and for existing items it does not redirect after save, so the rendered page contained stale data. The POST fallback now always reads from $_POST on a save postback instead of only when $ifonly was empty.

• Fix: The delete (−) button was missing on the sole rule of a group when multiple groups existed, making it impossible to remove an entire group. The button is now shown whenever deletion is meaningful: when the group has more than one rule, or when there is more than one group.

• Fix: Translated operator labels containing apostrophes (e.g. French "n'est pas") were rendered as HTML entities (') in the rule editor dropdowns. Replaced esc_html__() with __() for all strings serialized into the JavaScript configuration object — HTML-escaping is inappropriate for values passed through wp_json_encode().