Neutrope Lead Desk for Contact Form 7

変更履歴

0.3.0

• Add: generic extension points for the entry detail screen — nldcf7_entry_detail_main and nldcf7_entry_detail_sidebar — so an add-on can place panels in either column without modifying this plugin.
• Add: generic list extension points — nldcf7_entry_list_columns for columns and nldcf7_entry_list_column_content for their cells. Core columns are protected: an add-on cannot remove, rename or repurpose one, and returned cell markup passes through wp_kses_post().
• Add: nldcf7_entry_list_filters, which places an add-on’s own controls inside the existing filter bar.
• Add: nldcf7_entry_list_carried_args, so an add-on’s own filter stays applied across the All and Trash views and after row and bulk actions. Reserved keys such as nonces, action names and entry IDs are refused, non-scalar values are dropped, and size and count are capped, so a careless listener cannot put unsafe state into a list URL.
• Add: nldcf7_entry_query_args for high-level query constraints, including the existing ids argument, and nldcf7_entry_query_clauses for constraints that live in an add-on’s own table. Clauses are structured — a JOIN, conditions with placeholders, and their values kept separate — rather than a raw SQL string, and values always go through $wpdb->prepare().
• Add: optional distinct handling for add-on joins that can match a row more than once. It is applied to the row query and the count together, so the list and its total can never disagree.
• Add: query context. The entries screen and the CSV exporter share one repository, so each query now says which it is. An add-on constraint meant for the list no longer reaches CSV export unless the add-on opts in.
• Add: nldcf7_entry_list_items_prepared, which hands an add-on the current page’s rows once, before any cell is rendered, so custom columns can load their data in a single query instead of one per cell.
• Fix: the Activity preparation notice counted processing records (entries plus notes) but read as a number of inquiries. It now names the unit; the arithmetic is unchanged.
• Fix: the “history from before this plugin was updated” note no longer appears on sites that installed this version fresh and therefore have no earlier history to explain.
• No database change. The schema and database version (1.1.0) are identical to 0.2.0, no migration runs, and existing entries, notes, attachments, activity, settings, capabilities and URLs are untouched. With no add-on installed the plugin behaves exactly as 0.2.0 did.

0.2.0

• Add: an Activity Timeline (対応履歴) on the entry detail screen, showing what has already been done about an inquiry. It records the entry being received, status changes (including the previous and new status), internal-note activity, Trash and Restore, and spam-state changes — each with the user who performed it and a timestamp, newest first and paginated 50 events at a time.
• Add: a dedicated activity-event table ({prefix}nldcf7_entry_events). The database version moves from 1.0.0 to 1.1.0; the table is created on upgrade and on fresh activation.
• Add: existing entries get a historical timeline built in the background from the two things the database already recorded — each entry’s received timestamp and its existing internal notes. The backfill runs in batches, is resumable, and shows a progress notice on the plugin’s own screens while it works; you can keep using the plugin normally throughout.
• Historical status changes, trash/restore actions, and spam marking are deliberately NOT inferred. Those transitions were never stored before this release, so the timeline shows what was genuinely recorded and explains the gap rather than reconstructing a plausible-looking history that never happened.
• Your existing notes stay authoritative: the timeline links to them rather than copying or replacing them. Notes are also now rejected if their parent entry does not exist, so an orphaned note can no longer appear in a timeline that belongs to nothing.
• Fix: entry mutations are now transition-aware. Status, trash, restore, and spam changes distinguish a real transition from a no-op and from a failed write, so the timeline records a change only when the stored value actually changed. Previously a no-op update and a failed update were indistinguishable to callers.
• Fix: the entries list now keeps your keyword, status, form, date range, spam toggle, and sort order after a row or bulk action, instead of dropping you back into an unfiltered list after every single action.
• Housekeeping: resolved the remaining Plugin Check warning (WordPress.Security.ValidatedSanitizedInput.InputNotSanitized) by restructuring how list-filter input is read, not by suppressing the check. Plugin Check reports 0 errors and 0 warnings.
• No change to how submissions are captured or to what is stored for them: existing entries, notes, attachments, statuses, settings, option names, page slugs, capabilities, and existing hooks are all unchanged. Adds the actions nldcf7_after_entry_trashed, nldcf7_after_entry_restored, and nldcf7_after_spam_changed, and the filter nldcf7_event_render.

0.1.5

• Add: the entries list now has a Trash view alongside All, with a per-row “Restore” action and a “Restore” bulk action. Trashing an entry has always been a soft delete (an is_deleted flag, never a row deletion), but until now nothing in the admin could list or restore those entries, so recovering from an accidental Trash click meant editing the database by hand. v0.1.4 deliberately removed the confirm() gate from the row-level Trash link because that gate silently cancelled the click in browsers that suppress dialogs; this release supplies the recoverability that makes a one-click, unconfirmed Trash safe — the same trade WordPress core makes with “Move to Trash”.
• The Trash view keeps the active keyword / status / form / date filters and the “Show spam” toggle when you switch views, and the All / Trash counts show how many entries are in each bucket. Restoring from the Trash view leaves you in the Trash view instead of bouncing you back to All. The Trash link stays hidden while the trash is empty, matching core list screens.
• Restore is a plain nonce-protected link with no confirm() gate, for exactly the reason given in the v0.1.4 entry below.
• No database schema change: restore simply clears the existing is_deleted flag, and status, spam flag, notes, and attachments all survive a trash/restore round trip. Adds the nonce action nldcf7_restore_<id> and the query var status_view; existing ?page=nldcf7-* URLs, option names, page slugs, capabilities, and hooks are unchanged, and the Export screen’s “Include entries moved to trash” option behaves exactly as before.

0.1.4

• Fix: the row-level “Trash” link on the entries list did nothing when clicked — no confirmation, no notice, and the entry was not moved to trash. The link carried an onclick="return confirm(...)" gate; because confirm() returns false whenever the browser suppresses the dialog (Chrome’s “Prevent this page from creating additional dialogs”, embedded webviews, dialog-blocking extensions), the anchor’s navigation was cancelled and no HTTP request was ever sent. The server-side GET route was therefore never reached, which is why bulk actions — plain form posts with no confirm() — kept working. The Trash row action is now a plain nonce-protected link, matching WordPress core’s own “Move to Trash” row action.
• No database, option, page slug, capability, or hook contract changes. The GET trash route, its nonce action (nldcf7_trash_<id>), capability check, and redirect target are unchanged.

0.1.3

• Fix: the entry detail screen did not surface flash notices after status updates or note additions. v0.1.2 had added the same per-user transient flash mechanism to the Settings page, but the detail screen still discarded notices because NLDCF7_Entry_Detail_Page::render() did not accept the consumed transient and its view template had no notice block. render() now mirrors NLDCF7_Settings_Page::render() and accepts an optional $notice; the detail view renders the standard notice notice-success / notice-error is-dismissible banner; and NLDCF7_Admin_Menu::render_entries_route() passes the consumed transient when routing to the detail screen.
• No database, option, page slug, capability, or hook contract changes.

0.1.2

• Fix: the “Settings saved.” confirmation notice did not appear after saving on the Settings page (admin menu moved under Contact Form 7 in 0.1.1 changed the form’s effective post target in some setups, suppressing the post-save redirect and notice flag). The settings form now posts to an explicit URL and the success notice is delivered via the same per-user transient flash mechanism the entries list uses, so the confirmation reliably appears on the next page render.
• No database, option, page slug, capability, or hook contract changes.

0.1.1

• Admin menu relocated: the four screens (Entries / Export / Settings / Help) now appear as submenus directly under the existing Contact Form 7 menu (“お問い合わせ” in Japanese), instead of as a standalone top-level menu.
• When Contact Form 7 is not active, no plugin submenu is registered (no broken/orphan menu is produced). The missing-dependency warning is now also shown on the Dashboard and the Plugins screen, in addition to deep-link hits to plugin pages.
• Help screen: navigation hint updated to match the new location (“Contact > Entries” / 「お問い合わせ > 一覧」).
• No database, option, page slug, or capability changes. Existing ?page=nldcf7-* URLs continue to resolve unchanged.

0.1.0

• Initial release.
• Automatic capture of Contact Form 7 submissions into a dedicated DB table.
• Raw payload stored as JSON plus mapped columns for name/email/phone/company.
• Admin list screen (search, status/form/date filtering, bulk actions).
• Detail screen with status management and internal notes.
• CSV export with date/status/form/spam filters (UTF-8 + BOM, chunked streaming).
• Attachment metadata capture.
• Privacy-friendly defaults (IP capture off).
• Opt-in data deletion on uninstall.
• Extensibility hooks for future Pro integrations.