説明
Copy Report listens for the browser’s standard copy event and records qualifying text selections from your public pages. Context-menu copy, Ctrl+C, and Command+C are supported.
For each selection of at least 10 characters, Copy Report can store:
- Copy time in the WordPress site timezone
- ページタイトル
- Same-origin, sanitized page URL
- コピーされた文章
- Unicode character count
The administration screen provides a top-ten page ranking, search, sorting, pagination, and a UTF-8 CSV export that follows the current filters.
A detailed Japanese manual is included in docs/manual-ja.md.
プライバシーに配慮した記録
Recording is disabled by default. Review your privacy notice and recording scope before enabling it. By default, detection excludes logged-in visitors, password-protected pages, and recognized WooCommerce account and checkout pages.
Form controls, editable areas, and data-concretus-copy-report-ignore containers are excluded. URL fragments and non-allowlisted query parameters are removed before storage.
Copy Report does not persist raw IP addresses or session identifiers. Bounded, expiring HMAC counters and a random sessionStorage identifier support duplicate and abuse controls.
The plugin does not contact the developer’s servers or an external analytics service. If email notifications are enabled, copy-event data is passed to WordPress wp_mail() and may be processed by the mail or SMTP provider configured by the site owner.
メール通知と診断
Optional near-immediate, hourly, and daily notifications run through WP-Cron. Messages show copy and mail processing times. The history screen shows pending count, next processing time, and the latest WordPress mail result. Settings include test mail, manual queue processing, and privacy-minimized diagnostics.
An accepted wp_mail() result does not guarantee inbox delivery. WP-Cron timing depends on site traffic and server configuration.
データ保持とパフォーマンス
保存期間の初期値は90日で、30日、180日、365日、無期限も選択できます。整理処理は上限付きの分割処理を使用し、アンインストール時の削除も設定できます。
Normal page views add one event listener and no Copy Report database query. A same-site asynchronous request is made only after a qualifying copy. Bounded site, source, and payload limits apply.
Upgrading from CopyCheck or an earlier Copy Report package
Version 1.5.7 moves plugin-owned classes, constants, options, hooks, actions, and the custom table to the unique concretus_copy_report prefix. Existing CopyCheck history, settings, and notification cursors are migrated once during activation or the first request after update.
Copy Report provides behavioral observations, not identity, legal, compliance, or ranking guarantees.
プライバシー
Copy Report stores copy-event data in a custom WordPress table. Administrators can view, export, retain, or delete it. Raw session identifiers and IP addresses are not persisted. No telemetry is sent to the developer.
With notifications enabled, event details use the site’s mail/SMTP path. Copy Report adds suggested wording to the WordPress Privacy Policy Guide; administrators must adapt it to their site.
インストール
- Upload the
concretus-copy-reportfolder or installconcretus-copy-report.zipthrough Plugins > Add New > Upload Plugin. - Activate Copy Report.
- 「Copy Report」>「設定」を開き、プライバシー情報と記録範囲を確認して、サイトに適している場合は記録を有効にします。
- 対象となる公開ページから10文字以上をコピーし、「Copy Report」>「履歴一覧」を開いてイベントを確認します。
- 必要に応じてメール通知、保存期間、アンインストール時の動作を設定します。
When upgrading from CopyCheck or the earlier copy-report package, back up the database and disable its “delete data on uninstall” option. Deactivate and delete the old package before installing this one, then verify that history and settings were retained.
FAQ
-
Does Copy Report prevent people from copying my content?
-
いいえ。対応ブラウザーのコピーイベントをレポート用に記録するプラグインです。コピーの防止や、スクリーンショット、ブラウザー自動操作、スクリプト、キャッシュ済みコピー、すべての支援技術・プラットフォーム固有操作の検知はできません。
-
What data is stored for a copy event?
-
Copy time, page title, sanitized same-site URL, selected text, character count, and a keyed duplicate-detection hash.
-
Is the visitor’s IP address stored?
-
No raw IP is persisted by Copy Report. A site-secret keyed, time-window HMAC may be used in bounded abuse-prevention counters. Other hosting or security systems may keep separate logs.
-
No. Version 1.5.0 and later use a random identifier in browser
sessionStorage, with in-memory fallback when storage is unavailable. The plugin does not persist the raw identifier in its database. -
Are form entries or private editable text recorded?
-
The detector ignores form controls, editable areas, and
data-concretus-copy-report-ignorecontainers. Logged-in visitors, password-protected pages, and recognized WooCommerce account and checkout pages are excluded by default. Review templates for any other sensitive areas. -
How do I exclude a page section?
-
Add the
data-concretus-copy-report-ignoreattribute to a containing HTML element. Copies originating inside that element will be ignored. Existingdata-concretus-copy-report-ignoremarkup remains supported for backward compatibility. -
Why was a copy not recorded?
-
記録が有効であること、選択範囲が10文字以上であること、訪問者とページが設定した対象範囲内であること、コピー元が除外要素ではないことを確認してください。重複防止や送信回数制限により、繰り返しのイベントが拒否される場合もあります。
-
Why is an email delayed or missing even though history exists?
-
Check mail diagnostics, the pending count, next WP-Cron run, and test-mail result. A successful WordPress handoff does not guarantee delivery; also check spam filtering, SMTP, domain authentication, and WP-Cron.
-
Does Copy Report improve SEO?
-
Copy activity can help form hypotheses about useful passages, questions, calls to action, and content structure. Copy counts are not sent to search engines, are not a known ranking signal, and do not guarantee SEO results.
-
What happens to data when I uninstall the plugin?
-
設定画面で、アンインストール時に履歴と設定を削除するか管理者が選択できます。削除は元に戻せません。削除を無効にした場合、再インストールや移行に備えて独自テーブルと設定が保持されます。
評価
このプラグインにはレビューがありません。
貢献者と開発者
変更履歴
1.5.8
- Restored the administration styles on the history and settings screens.
- Ensured source rate-limit filters run exactly once per copy request.
1.5.7
- Moved all plugin-owned runtime identifiers to the unique
concretus_copy_reportprefix. - 既存の履歴、設定、通知位置を新しい識別子へ移行します。
- Removed the direct write to WordPress core’s shared
notoptionscache entry.
1.5.6
- Replaced migration bootstrap globals with a namespaced class to satisfy WordPress coding standards.
- 実行時の動作、保存データ、設定、データベース構造は変更していません。
1.5.5
- Matched the plugin directory, main file, and text domain to the assigned
concretus-copy-reportWordPress.org slug. - Added a safe activation guard for active CopyCheck and earlier
copy-reportpackages. - 既存のデータベーステーブル、設定、履歴、通知状態、公開連携識別子を保持しました。
1.5.4
- Added the Concretus brand to the public plugin name for WordPress.org submission.
- 設定、履歴、実行時の動作は変更していません。
1.5.3
- Resolved the remaining eight warnings reported by the official Plugin Check tool.
- 機能、保存データ仕様、データベース構造に変更はありません。
1.5.0
- Renamed CopyCheck to Copy Report while preserving history and settings.
- オプトイン方式の記録、プライバシーに配慮した初期対象範囲、上限設定、保存期間管理、プライバシーポリシーガイド文案を追加しました。
- Replaced the recorder cookie with a session-scoped identifier and expanded sensitive-area exclusions.
1.4.0
- Added asynchronous near-immediate notification scheduling, test mail, manual queue processing, delivery diagnostics, mail processing timestamps, and an easier-to-find CSV action.