Adds a documented extension foundation for add-ons, plus two small Activity-history wording fixes. Your leads, notes, activity and database schema are unchanged, and no migration runs. With no add-on installed the plugin behaves exactly as before.<\/p>","0.2.0":"
Adds a per-entry activity history. Existing entries have their received time and existing notes reconstructed in the background; status, trash, and spam changes made before this update were never recorded and are not invented. Existing lead data is preserved.<\/p>","0.1.5":"
Adds a Trash view with per-row and bulk Restore, so an accidental Trash click is undoable from the admin. No database, settings, or URL changes.<\/p>","0.1.4":"
Fixes the row-level "Trash" link on the entries list, which could silently do nothing. No data, settings, or URL changes.<\/p>","0.1.3":"
Detail screen now shows the "Status updated." \/ "Note added." flash notice (regression from v0.1.1 menu move; v0.1.2 fixed the equivalent for Settings). No data, option, or URL changes.<\/p>","0.1.2":"
Fixes the missing "Settings saved." confirmation on the Settings page. No data or URL changes.<\/p>","0.1.1":"
Menu moved under Contact Form 7 ("\u304a\u554f\u3044\u5408\u308f\u305b"). No data, settings, or URLs change.<\/p>","0.1.0":"
First public release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3553617,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3553617,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3664838,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3664838,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.1.0","0.1.1","0.1.2","0.1.3","0.1.5","0.2.0","0.3.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3553617,"resolution":"1","location":"assets","locale":"","width":1440,"height":1100},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3553617,"resolution":"2","location":"assets","locale":"","width":1440,"height":1100},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3553617,"resolution":"3","location":"assets","locale":"","width":1440,"height":1100},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3553617,"resolution":"4","location":"assets","locale":"","width":1440,"height":1100},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3553617,"resolution":"5","location":"assets","locale":"","width":1440,"height":1100}},"screenshots":{"1":"Entry list with summary cards, filters, and bulk actions.","2":"Detail view: submission fields, status management, internal notes.","3":"Settings page: field mapping, capture toggles, uninstall behaviour.","4":"CSV export form.","5":"Help screen."}},"plugin_section":[],"plugin_tags":[5445,1152,36677,14097,335],"plugin_category":[42],"plugin_contributors":[264944],"plugin_business_model":[],"class_list":["post-313747","plugin","type-plugin","status-publish","hentry","plugin_tags-cf7","plugin_tags-contact-form-7","plugin_tags-inquiries","plugin_tags-lead-management","plugin_tags-leads","plugin_category-contact-forms","plugin_contributors-neutropeinc","plugin_committers-neutropeinc"],"banners":{"banner":"https:\/\/ps.w.org\/neutrope-lead-desk-for-contact-form-7\/assets\/banner-772x250.png?rev=3664838","banner_2x":"https:\/\/ps.w.org\/neutrope-lead-desk-for-contact-form-7\/assets\/banner-1544x500.png?rev=3664838","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/neutrope-lead-desk-for-contact-form-7\/assets\/icon-128x128.png?rev=3553617","icon_2x":"https:\/\/ps.w.org\/neutrope-lead-desk-for-contact-form-7\/assets\/icon-256x256.png?rev=3553617","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/neutrope-lead-desk-for-contact-form-7\/assets\/screenshot-1.png?rev=3553617","caption":"Entry list with summary cards, filters, and bulk actions."},{"src":"https:\/\/ps.w.org\/neutrope-lead-desk-for-contact-form-7\/assets\/screenshot-2.png?rev=3553617","caption":"Detail view: submission fields, status management, internal notes."},{"src":"https:\/\/ps.w.org\/neutrope-lead-desk-for-contact-form-7\/assets\/screenshot-3.png?rev=3553617","caption":"Settings page: field mapping, capture toggles, uninstall behaviour."},{"src":"https:\/\/ps.w.org\/neutrope-lead-desk-for-contact-form-7\/assets\/screenshot-4.png?rev=3553617","caption":"CSV export form."},{"src":"https:\/\/ps.w.org\/neutrope-lead-desk-for-contact-form-7\/assets\/screenshot-5.png?rev=3553617","caption":"Help screen."}],"raw_content":"\n
Neutrope Lead Desk for Contact Form 7 captures every Contact Form 7 submission into a dedicated database table and provides a simple WordPress admin interface for managing those submissions as leads.<\/p>\n\n
The free version is intentionally focused: it saves submissions reliably, gives you an admin list\/detail UI, lets you change status, add internal notes, and export to CSV. It does this without pulling in external services, trackers, or upsell banners on unrelated screens.<\/p>\n\n
Version 0.3.0 is mainly a foundation release for add-ons: it adds documented, generic extension points so other plugins can add columns, filters and detail-screen panels without forking this one. Nothing in the plugin's own behaviour changes because of them, and no database change is involved. See \"Extending the plugin\" below.<\/p>\n\n
Since 0.2.0 each entry also keeps an Activity Timeline<\/strong> (\u5bfe\u5fdc\u5c65\u6b74) so you can see what has already been done about an inquiry -- when it arrived, who changed its status and to what, when notes were added, and when it was moved to trash, restored, or marked as spam -- instead of inferring the handling history from the current status alone.<\/p>\n\n Key features<\/strong><\/p>\n\n Requirements<\/strong><\/p>\n\n Does NOT include (outside the scope of the free version)<\/strong><\/p>\n\n These may be considered for a future Pro release. The free plugin is designed to be fully useful on its own.<\/p>\n\n Version 0.3.0 adds nine extension points for add-on developers. They are\ngeneric: this plugin knows nothing about what an add-on stores. All of them are\nno-ops when nothing is listening, so a site with no add-on behaves exactly as\nit did in 0.2.0.<\/p>\n\n Action. Introduced in 0.3.0. Fires on the entry detail screen after this\nplugin's own cards in the main column, before the column closes.<\/p>\n\n own markup, including its own card wrapper, and is responsible for escaping it.\nOutput is not buffered or altered.<\/p>\n\n Action. Introduced in 0.3.0. The same contract, for the sidebar column. Two\nhooks exist so an add-on can place content in both columns of one screen.<\/p>\n\n Filter. Introduced in 0.3.0. Adds columns to the entries list.<\/p>\n\n Return the column map with your own keys appended; prefix them to avoid\ncollisions. Core columns cannot be removed, renamed or repurposed -- every core\nkey is restored to its own label after the filter runs, and the checkbox column\nis forced back to the front. Labels are plain text and are escaped on output.<\/p>\n\n Filter. Introduced in 0.3.0. Renders a cell for a column you added.<\/p>\n\n Return HTML for your own column, or the value you were given for anything else.\nEscape your own output; the plugin then passes the result through\n wp_kses_post() as a second layer, so ordinary post markup survives while\nscripts and event handlers do not. A non-string return renders an empty cell.<\/p>\n\n Action. Introduced in 0.3.0. Fires inside the list's existing GET filter form,\nbefore the Filter button, so a plain select or input submits alongside the\nbuilt-in filters.<\/p>\n\n own your field names, your values and your escaping. No nonce is involved: the\nfilter bar only reads.<\/p>\n\n Filter. Introduced in 0.3.0. Keeps your own filter state across the All and\nTrash views, the row actions, and the redirect after a row or bulk action.<\/p>\n\n Add your own already-sanitized scalar values. The plugin re-checks the result\nafterwards: reserved keys ( Filter. Introduced in 0.3.0. Adjusts the entries query using arguments the\nrepository already understands, without writing SQL.<\/p>\n\n The most useful is Filter. Introduced in 0.3.0. Constrains the entries query using a table of your\nown, resolved by the database rather than by loading matching IDs into PHP.<\/p>\n\n Values must go in Action. Introduced in 0.3.0. Fires once per list page after the rows are known\nand before any cell is rendered.<\/p>\n\n to load everything your columns need in one query and keep it in a\nrequest-local cache, instead of querying once per cell. It is read-only, has no\nreturn value, and fires with an empty array when the page has no rows. It\nbelongs to the entries screen only and never fires during CSV export.<\/p>\n\n\n No. The plugin depends on Contact Form 7. If CF7 is not active, the plugin will not capture submissions and will show a warning banner on its own admin screens (it does not nag elsewhere in wp-admin).<\/p><\/dd>\n No \u2014 only metadata (file name, MIME type, file size). The actual files remain with Contact Form 7's default handling.<\/p><\/dd>\n IP capture is disabled by default for privacy. You can enable it under \u304a\u554f\u3044\u5408\u308f\u305b > \u8a2d\u5b9a > IP \u4fdd\u5b58<\/strong>. If you enable it, make sure your site's privacy policy covers IP logging.<\/p><\/dd>\n Open \u304a\u554f\u3044\u5408\u308f\u305b > \u30a8\u30af\u30b9\u30dd\u30fc\u30c8<\/strong>, apply any filters (date range, status, form, include spam), and click the download button. The CSV is UTF-8 with BOM, so it opens correctly in Japanese Excel without manual encoding conversion.<\/p><\/dd>\n Each of the four mapped columns (name, email, phone, company) has a comma-separated candidate list. The first field name that exists in the submission wins and its value is copied to the mapped column. Unmapped fields still end up in the No, by default data is preserved. If you explicitly want a clean uninstall, enable \u8a2d\u5b9a > \u30a2\u30f3\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u6642\u306b\u30c7\u30fc\u30bf\u524a\u9664<\/strong> first, then delete the plugin.<\/p><\/dd>\n No. Nothing is sent outside your WordPress installation. There is no phone-home, no analytics, and no tracking.<\/p><\/dd>\n By default Yes. Use the Because it is built only from what was actually recorded at the time. Before 0.2.0 the plugin stored each entry's received timestamp and your internal notes, but it did not keep a log of status changes, trash\/restore actions, or spam marking. Those older transitions cannot be recovered, and the plugin will not fabricate them. Entries received from 0.2.0 onward record the full set of activity as it happens.<\/p><\/dd>\n Please open an issue on the plugin's support forum or the project's issue tracker.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
{prefix}nldcf7_entries<\/code>)<\/li>\nnldcf7_after_entry_saved<\/code>, nldcf7_after_note_added<\/code>, nldcf7_after_status_changed<\/code>, nldcf7_after_entry_trashed<\/code>, nldcf7_after_entry_restored<\/code>, nldcf7_after_spam_changed<\/code>, nldcf7_entry_data_before_insert<\/code>, nldcf7_export_columns<\/code>, nldcf7_export_row<\/code>, nldcf7_statuses<\/code>, nldcf7_event_labels<\/code>, nldcf7_event_render<\/code>, nldcf7_required_capability<\/code><\/li>\n\n
\n
Extending the plugin<\/h3>\n\n
nldcf7_entry_detail_main<\/h4>\n\n
do_action( 'nldcf7_entry_detail_main', array $entry )\n\n$entry is the entry row as stored, passed by value. The listener prints its\n<\/code><\/pre>\n\nnldcf7_entry_detail_sidebar<\/h4>\n\n
do_action( 'nldcf7_entry_detail_sidebar', array $entry )\n<\/code><\/pre>\n\nnldcf7_entry_list_columns<\/h4>\n\n
apply_filters( 'nldcf7_entry_list_columns', array $columns )\n<\/code><\/pre>\n\nnldcf7_entry_list_column_content<\/h4>\n\n
apply_filters( 'nldcf7_entry_list_column_content', string $html, string $column_name, array $item )\n<\/code><\/pre>\n\nnldcf7_entry_list_filters<\/h4>\n\n
do_action( 'nldcf7_entry_list_filters', array $current_args )\n\n$current_args is this plugin's own sanitized filter state, for reference. You\n<\/code><\/pre>\n\nnldcf7_entry_list_carried_args<\/h4>\n\n
apply_filters( 'nldcf7_entry_list_carried_args', array $args, array $core )\n<\/code><\/pre>\n\npage<\/code>, paged<\/code>, action<\/code>, action2<\/code>, entry_id<\/code>,\n _wpnonce, _wp_http_referer<\/code>, view<\/code>, event_page<\/code>, status_view<\/code>) are\nstripped, keys are normalised, non-scalars are dropped, and both value length\nand argument count are capped. Core values always win. Do not attempt to\nforward the whole query string.<\/p>\n\nnldcf7_entry_query_args<\/h4>\n\n
apply_filters( 'nldcf7_entry_query_args', array $args )\n<\/code><\/pre>\n\nids<\/code>, an array of entry IDs to restrict the query to.\n $args['context'] says who is asking: list<\/code> for the entries screen, export<\/code>\nfor CSV, default<\/code> otherwise. Check it -- both callers share the same\nrepository, so an unconditional constraint would also change what CSV exports.<\/p>\n\nnldcf7_entry_query_clauses<\/h4>\n\n
apply_filters( 'nldcf7_entry_query_clauses', array $parts, array $args )\n\n$parts has four keys:\n<\/code><\/pre>\n\n\n
join<\/code> -- a JOIN clause string.<\/li>\nwhere<\/code> -- an array of condition strings, each using %s<\/code> or %d<\/code> placeholders.<\/li>\nprepare_args<\/code> -- the values for those placeholders, in order.<\/li>\ndistinct<\/code> -- boolean, default false.<\/li>\n<\/ul>\n\nprepare_args<\/code>, never inside the condition strings; the plugin\npasses them to $wpdb->prepare()<\/code>. A single pre-built SQL string is not\naccepted. If the placeholder count and the value count disagree, the whole\ncontribution is discarded. Table and column identifiers inside join<\/code> are your\nresponsibility. Set distinct<\/code> when your JOIN can match a row more than once: it\nis applied to the row query and the count together, so the list total and\npagination stay correct. $args['context']<\/code> applies here too.<\/p>\n\nnldcf7_entry_list_items_prepared<\/h4>\n\n
do_action( 'nldcf7_entry_list_items_prepared', array $items )\n\n$items is the current page's rows only -- never the whole result set. Use it\n<\/code><\/pre>\n\n\n
neutrope-lead-desk-for-contact-form-7<\/code> folder to the \/wp-content\/plugins\/<\/code> directory, or install it via the Plugins screen in WordPress (\"Upload Plugin\").<\/li>\n\n
Does this work without Contact Form 7?<\/h3><\/dt>\n
Are uploaded files stored?<\/h3><\/dt>\n
Will this capture IP addresses?<\/h3><\/dt>\n
How do I export data to CSV?<\/h3><\/dt>\n
How does field mapping work?<\/h3><\/dt>\n
raw_payload_json<\/code> column.<\/p><\/dd>\nWill deleting the plugin lose my captured leads?<\/h3><\/dt>\n
Does the plugin send data to any external service?<\/h3><\/dt>\n
What capability is required?<\/h3><\/dt>\n
manage_options<\/code> is required for all admin screens. The required capability can be changed via the nldcf7_required_capability<\/code> filter.<\/p><\/dd>\nCan I add custom columns to the CSV export?<\/h3><\/dt>\n
nldcf7_export_columns<\/code> filter to add\/remove header columns, and nldcf7_export_row<\/code> to return custom values per row.<\/p><\/dd>\nWhy is the activity history short for entries I received before updating?<\/h3><\/dt>\n
How do I report a bug or request a feature?<\/h3><\/dt>\n
0.3.0<\/h4>\n\n
\n
nldcf7_entry_detail_main<\/code> and nldcf7_entry_detail_sidebar<\/code> -- so an add-on can place panels in either column without modifying this plugin.<\/li>\nnldcf7_entry_list_columns<\/code> for columns and nldcf7_entry_list_column_content<\/code> 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()<\/code>.<\/li>\nnldcf7_entry_list_filters<\/code>, which places an add-on's own controls inside the existing filter bar.<\/li>\nnldcf7_entry_list_carried_args<\/code>, 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.<\/li>\nnldcf7_entry_query_args<\/code> for high-level query constraints, including the existing ids<\/code> argument, and nldcf7_entry_query_clauses<\/code> 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()<\/code>.<\/li>\ndistinct<\/code> 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.<\/li>\nnldcf7_entry_list_items_prepared<\/code>, 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.<\/li>\n0.2.0<\/h4>\n\n
\n
{prefix}nldcf7_entry_events<\/code>). The database version moves from 1.0.0 to 1.1.0; the table is created on upgrade and on fresh activation.<\/li>\nWordPress.Security.ValidatedSanitizedInput.InputNotSanitized<\/code>) by restructuring how list-filter input is read, not by suppressing the check. Plugin Check reports 0 errors and 0 warnings.<\/li>\nnldcf7_after_entry_trashed<\/code>, nldcf7_after_entry_restored<\/code>, and nldcf7_after_spam_changed<\/code>, and the filter nldcf7_event_render<\/code>.<\/li>\n<\/ul>\n\n0.1.5<\/h4>\n\n
\n
is_deleted<\/code> 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()<\/code> 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\".<\/li>\nconfirm()<\/code> gate, for exactly the reason given in the v0.1.4 entry below.<\/li>\nis_deleted<\/code> flag, and status, spam flag, notes, and attachments all survive a trash\/restore round trip. Adds the nonce action nldcf7_restore_<id><\/code> and the query var status_view<\/code>; existing ?page=nldcf7-*<\/code> 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.<\/li>\n<\/ul>\n\n0.1.4<\/h4>\n\n
\n
onclick=\"return confirm(...)\"<\/code> gate; because confirm()<\/code> 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()<\/code> -- kept working. The Trash row action is now a plain nonce-protected link, matching WordPress core's own \"Move to Trash\" row action.<\/li>\nnldcf7_trash_<id><\/code>), capability check, and redirect target are unchanged.<\/li>\n<\/ul>\n\n0.1.3<\/h4>\n\n
\n
NLDCF7_Entry_Detail_Page::render()<\/code> did not accept the consumed transient and its view template had no notice block. render()<\/code> now mirrors NLDCF7_Settings_Page::render()<\/code> and accepts an optional $notice<\/code>; the detail view renders the standard notice notice-success \/ notice-error is-dismissible<\/code> banner; and NLDCF7_Admin_Menu::render_entries_route()<\/code> passes the consumed transient when routing to the detail screen.<\/li>\n0.1.2<\/h4>\n\n
\n
0.1.1<\/h4>\n\n
\n
?page=nldcf7-*<\/code> URLs continue to resolve unchanged.<\/li>\n<\/ul>\n\n0.1.0<\/h4>\n\n
\n