Privacy policy: https:\/\/eyesite.pl\/polityka-prywatnosci\/<\/li>\n<\/ul>\n\nPrivacy<\/h3>\n\n
Visitor data stays on your site. When a front-end error happens (a JavaScript error, a failed contact-form submission) or a WooCommerce cart is abandoned after a technical error, the plugin stores in your site's own database: the error message, script source and stack trace, the page URL, browser and device type, the user-agent string and a random session identifier. For abandoned carts it also stores the cart total. It does not store IP addresses, form contents, cart contents or customer details, and none of this data is sent to EyeSite or any other service.<\/p>\n\n
Cookie: in those situations only, the browser sets a first-party cookie eyesite_session<\/code> holding a random identifier, valid for 30 minutes. It is used solely to group error reports from the same visit. It is not set on normal page views, so full-page caching is not affected. Treat it as a functional cookie in your consent banner.<\/p>\n\nRetention: records are deleted automatically after 60 days, resolved errors after 3 days. Uninstalling the plugin removes its tables and options.<\/p>\n\n
The plugin adds a suggested paragraph to Settings -> Privacy -> Policy guide that you can copy into your privacy policy.<\/p>\n\n\n
\n- Upload the plugin folder to the
\/wp-content\/plugins\/<\/code> directory, or install it from the WordPress admin under \"Plugins\" -> \"Add New\".<\/li>\n- Activate the plugin from the \"Plugins\" menu in the admin panel.<\/li>\n
- Open the
Eyesite<\/code> menu to view monitoring results and the API credentials.<\/li>\n<\/ol>\n\n\n\nIs this plugin free?<\/h3><\/dt>\nYes. The plugin is a free part of the Eyesite ecosystem.<\/p><\/dd>\n
Does the plugin support multisite?<\/h3><\/dt>\nThe plugin is designed for single-site installations. On multisite networks the error-tracking tables are only created for the site the plugin is activated on, activate it per site rather than network-wide.<\/p><\/dd>\n
The disk space check says everything is fine, but my hosting account is full<\/h3><\/dt>\nThe check measures free space on the server volume. On shared hosting the account quota<\/em> can be exhausted while the volume still has space, the check cannot see hosting quotas.<\/p><\/dd>\nHow do I enable SMS alerts?<\/h3><\/dt>\nExtended SMS notifications are part of the paid service - visit our website eyesite.pl.<\/p><\/dd>\n\n<\/dl>\n\n\n
7.4.7<\/h4>\n\n\n- Changed: connect button wording and trust line.<\/li>\n<\/ul>\n\n
7.4.6<\/h4>\n\n\n- Changed: the connect call to action talks about tomorrow, not about the scan that just ran, and names a real risk from this site when there is one.<\/li>\n
- Changed: until the site is connected, every detail section opens with a one-line reminder that the result is a one-off scan.<\/li>\n
- Changed: no more em or en dashes anywhere in the plugin's text.<\/li>\n<\/ul>\n\n
7.4.5<\/h4>\n\n\n- Changed: the \"connect\" call to action is the primary button; before monitoring is on, the score card shows a quiet link instead of a second button.<\/li>\n
- Changed: the feedback box is folded by default.<\/li>\n
- Changed: the preview alert cards show this site's own top problems (no more \"customers cannot pay\" on a site that is not a shop) and animate in one after another.<\/li>\n<\/ul>\n\n
7.4.4<\/h4>\n\n\n- Changed: known vulnerabilities now appear in their own alert section at the top of the dashboard, above the to-do list, with a one-click \"Update\" button that runs the normal WordPress updater (when an update is available in the plugin's own update source).<\/li>\n
- Changed: shorter AI visibility cards.<\/li>\n<\/ul>\n\n
7.4.3<\/h4>\n\n\n- Fixed: a short home page is no longer described as built with JavaScript. That wording now needs real evidence of a JavaScript application; otherwise the plugin only says there is little text.<\/li>\n<\/ul>\n\n
7.4.2<\/h4>\n\n\n- Added: AI visibility checks in the Google group: robots.txt rules for AI search bots (ChatGPT, Claude, Perplexity) versus training bots, whether the server turns an AI search bot away, schema.org data about the business, and whether the content is readable without JavaScript. Reads your own site only.<\/li>\n<\/ul>\n\n
7.4.1<\/h4>\n\n\n- Added: optional check for plugins and themes with publicly known security holes, with the version that fixes them. Off by default; data from Wordfence Intelligence.<\/li>\n<\/ul>\n\n
7.4.0<\/h4>\n\n\n- Added: warning when the installed WordPress version has publicly known security holes (WordPress.org marks it as \"insecure\"). Checked once a day against the public WordPress.org release list; nothing about your site is sent.<\/li>\n<\/ul>\n\n
7.3.2<\/h4>\n\n\n- Fixed: no more \"problem fixed\" e-mails about WP-Cron. On low-traffic sites background tasks pause between visits, which is normal and not worth a message.<\/li>\n
- Fixed: the \"problem fixed\" e-mail says \"site\" instead of \"store\" when WooCommerce is not active.<\/li>\n<\/ul>\n\n
7.3.1<\/h4>\n\n\n- Docs: new Privacy section describing the visitor data stored locally (front-end errors, abandoned carts), the
eyesite_session<\/code> cookie and retention.<\/li>\n- Added: suggested privacy policy text in Settings -> Privacy -> Policy guide.<\/li>\n<\/ul>\n\n
7.3.0<\/h4>\n\n\n- Changed: all features are free. Google visibility checks and the real e-mail delivery test are available to every site (the delivery test requires a connection to EyeSite, as it uses the EyeSite mailbox).<\/li>\n
- Removed: PRO licence key, licence verification requests and locked previews.<\/li>\n<\/ul>\n\n
7.2.5<\/h4>\n\n\n- Fixed: \"problem fixed\" e-mails were repeated every hour when a check flapped. A problem must now stay open for 2 hours, and the same problem is reported as fixed at most once every 7 days.<\/li>\n
- Fixed: WP-Cron is reported as not working only when scheduled tasks are overdue by more than an hour (low-traffic sites no longer trigger false warnings).<\/li>\n<\/ul>\n\n
7.2.4<\/h4>\n\n\n- Fixed: mail configuration check now audits the domain e-mails are actually sent from (WooCommerce sender address, SMTP plugin sender, or the site domain) instead of the administrator's e-mail domain. Old results are re-checked automatically.<\/li>\n
- Fixed: the PRO preview overlay no longer overlaps neighbouring check groups.<\/li>\n<\/ul>\n\n
7.2.3<\/h4>\n\n\n- Privacy: page-speed measurement is now opt-in and off by default (new setting); no measurement is scheduled on activation.<\/li>\n
- Privacy: domain expiry check (RDAP) is now opt-in and off by default (new setting).<\/li>\n
- Changed: admin CSS moved to assets\/css\/eyesite-admin.css (loaded only on EyeSite screens); all inline JavaScript is added with wp_add_inline_script().<\/li>\n
- Docs: External services section now covers audit\/repair requests, the connection notice, PRO licence check, e-mail delivery test and RDAP.<\/li>\n
- Removed: unused warning e-mail helper, redundant core includes, \"Tested up to\" plugin header.<\/li>\n<\/ul>\n\n
7.2.2<\/h4>\n\n\n- Coding standards: Plugin Check 2.1 annotation for the read-only error_reporting() level check in the PHP error handler.<\/li>\n<\/ul>\n\n
7.2.1<\/h4>\n\n\n- Security: all queries on the plugin's own tables now pass the table name through $wpdb->prepare() with the %i identifier placeholder.<\/li>\n
- Security: display-only URL flags are sanitized; every state-changing request remains capability- and nonce-checked.<\/li>\n
- Changed: minimum WordPress version raised to 6.2 (required for %i).<\/li>\n
- Coding standards: Plugin Check clean-up (same fixes as 6.7.2).<\/li>\n<\/ul>\n\n
7.2.0<\/h4>\n\n\n- Added: three hardening checks in \"Bezpiecze\u0144stwo\", checked from inside (no guessing): XML-RPC open, user logins exposed via the REST API, directory listing in uploads. Each with a plain explanation and a one-click fix request.<\/li>\n
- Fixed: a corrupted character in the DMARC explanation.<\/li>\n<\/ul>\n\n
7.1.0<\/h4>\n\n\n- Changed: the visitor session cookie is no longer set by PHP on every page view. It is created in the browser only when there is something to report (a front-end error or an abandoned cart), so full-page caches (LiteSpeed, WP Rocket, Cloudflare APO, Varnish) keep serving cached pages to every visitor.<\/li>\n
- Fixed: an uncaught front-end error on a page without a form was recorded twice (once without browser\/session context).<\/li>\n
- Changed: error tables, wider action column so the \"Zle\u0107 napraw\u0119\" button is never cut off; the resolve button now reads \"Oznacz jako naprawione\".<\/li>\n<\/ul>\n\n
7.0.0<\/h4>\n\n\n- Added: score history (daily point, sparkline in the hero), a short \"problem naprawiony\" e-mail when a reported problem stops occurring (toggle in settings), and a \"Naprawione w tym tygodniu\" block in the weekly report.<\/li>\n
- Added: PRO licence key field in settings (verified daily against the EyeSite backend, 14-day offline grace).<\/li>\n
- Changed: returns check is one line inside \"Reklamy i analityka\"; server errors live only on their own page; the real-delivery mail test is a PRO feature.<\/li>\n
- New dashboard for shop owners, not engineers: a \"Zdrowie sklepu\" score (0-100) with three plain sentences (can customers buy, do e-mails arrive, is the domain paid) and proof of work, checks run since install, problems found, problems fixed.<\/li>\n
- First-run onboarding: the plugin runs its real checks once, shows the score and the first thing to fix, then offers 24\/7 alerts. No tooltip tour.<\/li>\n
- \"Do zrobienia\" is the one action list: every item explains what it means for sales and offers a single \"Zle\u0107 napraw\u0119, darmowa wycena\" button (price shown only via the eyesite_fix_price filter).<\/li>\n
- Detailed sections (checks grid, analytics, returns, carts, settings) are folded by default; they open when something needs attention.<\/li>\n
- Weekly report opens with the score and the checks\/problems counters.<\/li>\n<\/ul>\n\n
6.9.1<\/h4>\n\n\n- Fixed: when the shop was reported as down, the availability hero and KPI card jumped into the connection card (WordPress core relocates every
div.error<\/code> under the first heading).<\/li>\n- Changed: the purchase-path section is collapsible (open automatically when something is wrong); Google visibility is a PRO feature and shows as a locked preview on free sites.<\/li>\n<\/ul>\n\n
6.9.0<\/h4>\n\n\n- Added: purchase-path test for WooCommerce, once a day (and on demand) the plugin walks product \u2192 add to cart \u2192 cart \u2192 checkout over HTTP like a visitor and checks that a payment method is offered. No order is placed. Fails show up in \"Do naprawienia\" and the weekly report.<\/li>\n
- Added: domain expiry check (RDAP), warning 30 days before, critical at 7 days or expired.<\/li>\n
- Added: Google visibility check, \"discourage search engines\", noindex on the home\/shop page (meta or X-Robots-Tag), robots.txt blocking everything, missing sitemap, canonical pointing at another host.<\/li>\n
- Improved: mail deliverability section rewritten in plain language; the probe inbox no longer requires plus-addressing.<\/li>\n
- Status endpoint: new aspects
checkout<\/code>, seo<\/code>, domain<\/code>.<\/li>\n<\/ul>\n\n6.8.1<\/h4>\n\n\n- Fixed: disconnecting now confirms the revocation with the EyeSite backend and retries from cron when the call fails, previously a lost request left the site monitored (and alerted on) after \"Roz\u0142\u0105cz\".<\/li>\n
- Added: real delivery test for the mail audit, once a day (and on demand, at most hourly) the plugin sends one minimal plain-text probe message to an EyeSite inbox and reads back how the receiver authenticated it: SPF\/DKIM\/DMARC results, whether the message actually carried a DKIM signature, sending IP and host, Return-Path\/From alignment, blacklist hits and delivery time. Only a random token is sent, no site or customer data. Skipped automatically when the site is not connected or the DNS audit already reports a critical SPF\/MX problem.<\/li>\n<\/ul>\n\n
6.8.0<\/h4>\n\n\n- Added: mail deliverability audit, daily DNS check of the sending domain (SPF record count and lookup limit,
all<\/code> policy, DMARC policy, MX, common DKIM selectors) with a 0-100 score, plain-language fixes, a card in the checks grid and a section in the weekly report. Nothing is sent; only DNS is read.<\/li>\n- Redesigned: calmer admin interface, single brand accent, monochrome SVG icons instead of emoji, flat hairline cards, tabular numerals.<\/li>\n
- Fixed: error tables, the sticky header no longer covers the first row.<\/li>\n
- Improved: error pages get severity chips, an empty state and an icon in the filter field.<\/li>\n<\/ul>\n\n
6.7.1<\/h4>\n\n\n- Added: weekly HTML report e-mail (Monday 08:00) with uptime, PageSpeed, 7-day errors, abandoned carts, SSL days left and bestseller availability. Can be disabled in settings.<\/li>\n
- Added: daily SSL certificate expiry check, warning at 21 days, error at 7 days or expired.<\/li>\n
- Added: bestseller stock watch, an out-of-stock top-5 product raises a dashboard warning and a one-time e-mail.<\/li>\n
- Added: feedback form on the dashboard (rate-limited, nonce-protected).<\/li>\n<\/ul>\n\n
6.7.0<\/h4>\n\n\n- Added: KPI trend cards on the dashboard (availability, response time, speed, errors) with inline SVG sparklines built from real measurement history.<\/li>\n
- Improved: speed and uptime history is stored (bounded) so trends accrue over time; all new data is removed on uninstall.<\/li>\n
- Improved: calmer visual style, white cards, neutral borders, solid buttons.<\/li>\n<\/ul>\n\n
6.6.3<\/h4>\n\n\n- Improved: sticky top bar with live status and section quick-navigation, \"Status systemu\" moved above the checks grid, side-by-side error\/cart bands, live filters on error pages, back-to-top button. No logic changes.<\/li>\n<\/ul>\n\n
6.6.2<\/h4>\n\n\n- Fixed: connect\/disconnect notices were never displayed on the plugin pages.<\/li>\n
- Fixed: downtime cost calculator now supports WooCommerce HPOS order storage (returned 0 on WooCommerce 8.2+).<\/li>\n
- Security: cart dashboard widget restricted to shop managers\/admins; user ID for JS error reports is taken server-side; session ID and cart values are validated and clamped; global rate limit on cart-abandonment reports; oversized payloads are truncated instead of dropped.<\/li>\n
- Compatibility: XHR breadcrumb wrapper preserves the prototype chain and static constants used by third-party scripts.<\/li>\n<\/ul>\n\n
6.6.1<\/h4>\n\n\n- Redesigned admin interface: refreshed design system (typography, depth, color), refined status cards and availability sparkline, gradient action buttons, styled error tables, accessible focus states, and reduced-motion support. No functional changes.<\/li>\n<\/ul>\n\n
6.6<\/h4>\n\n\n- Fixed: HTTPS check now recognises TLS terminated at a proxy\/CDN (X-Forwarded-Proto, Cloudflare), no more false \"no HTTPS\" alarms behind load balancers.<\/li>\n
- Fixed: task-queue check counts only overdue actions, shops with subscriptions\/automations (which always hold future-scheduled actions) no longer trigger false \"queue overloaded\" alerts.<\/li>\n
- Fixed: \"series of failed payments\" counts only genuinely failed orders, batch auto-cancellations of unpaid orders no longer trigger it.<\/li>\n
- Fixed: Contact Form 7 submission results are now detected via CF7's DOM events (the legacy CSS classes were removed in CF7 5.2), so successes are counted on modern installs.<\/li>\n
- Fixed: the returns\/withdrawal page scan reads all pages separately from blog posts, an active blog can no longer hide the returns page from detection.<\/li>\n
- Improved: a single failed e-mail is a warning; the error-level alert requires repeated failures within 15 minutes.<\/li>\n
- Improved: order-anomaly \"critical\" requires a minimum volume (3+ orders), so low-traffic shops aren't paged over a single refund.<\/li>\n
- Improved: browser-extension errors and opaque cross-origin \"Script error.\" events are filtered out of user error tracking.<\/li>\n
- Improved: the status endpoint runs after WooCommerce initialises its cart, avoiding payment-gateway edge cases.<\/li>\n<\/ul>\n\n
6.5.1<\/h4>\n\n\n- Fixed: status endpoint could return a fatal error (HTTP 500) instead of a status when the API token option was missing; an empty stored token is now always rejected.<\/li>\n
- Fixed: PHP error occurrence counts were inflated by repeated log scans, each log line is now ingested only once.<\/li>\n
- Fixed: false \"jQuery not loaded\" reports on non-WooCommerce themes that ship without jQuery.<\/li>\n
- Fixed: WooCommerce failed-payment window was widened by the site's UTC offset (timezone-safe date query).<\/li>\n
- Fixed: leftover scheduled events and transients are now cleaned up on deactivation\/uninstall.<\/li>\n
- Fixed: PHP warning (and self-recorded error) when error_log points to a character device such as \/dev\/stderr (common in containers).<\/li>\n
- Improved: uptime data is now fetched in the background (like the speed check), a slow status-page response can no longer delay the dashboard.<\/li>\n
- Improved: Cloudflare loopback detection is cached for an hour instead of running on every status poll.<\/li>\n
- Improved: the visitor session cookie is now set before output starts, so error reports correlate across pages.<\/li>\n
- Hardened admin consent card against stale cached data from older versions.<\/li>\n<\/ul>\n\n
6.5<\/h4>\n\n\n- Added Consent Mode v2 and Meta Conversion API checks.<\/li>\n
- Added detection of right-of-withdrawal (returns) signals.<\/li>\n
- Added connection to the EyeSite service (connect \/ verify \/ disconnect handshake) and the required \"External services\" section.<\/li>\n
- Connect form is served from eyesite.pl\/connect; verify\/disconnect run on the EyeSite automation backend (filterable via eyesite_connect_url \/ eyesite_verify_url \/ eyesite_disconnect_url).<\/li>\n
- Status endpoint accepts an optional &aspect= parameter (cart, payments, forms, ssl, cron\u2026) returning 200\/503 for a single check, so each aspect can be monitored separately.<\/li>\n
- Fixed a PHP \"headers already sent\" warning when generating the session id.<\/li>\n<\/ul>\n\n
6.4<\/h4>\n\n\n- Added intelligent order anomaly tracking.<\/li>\n
- Refactored result tiles and dynamic titles.<\/li>\n<\/ul>\n\n
6.3<\/h4>\n\n\n- Added logging of form submission problems.<\/li>\n<\/ul>\n\n
6.2<\/h4>\n\n\n- Improved error tracking and Lighthouse metrics.<\/li>\n<\/ul>\n\n
6.0<\/h4>\n\n\n- First public release of the advanced Eyesite agent.<\/li>\n<\/ul>","raw_excerpt":"We watch your site 24\/7. Eyesite Monitor guards against outages, monitors orders and alerts you to critical problems.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/368928","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=368928"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/bieleckiconsulting"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=368928"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=368928"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=368928"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=368928"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=368928"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=368928"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}