Beskrivelse
Vifee is a bug tracker and kanban board built into your WordPress admin, made for website projects. Clients, testers and teammates report bugs and change requests straight from the page they are looking at, and every report lands as a card on your board – with the exact spot, a screenshot and the browser details attached. Everything is stored in your own WordPress database; no external service is involved.
A kanban board for every bug and change request
- Columns for each status: To do, In progress, Needs review and Done. Drag a card to move it on, and archive finished work.
- Every card has an issue type (Task or Bug), a priority and an optional due date; overdue cards stand out.
- Filter by status, priority and issue type, search the text, and sort the board.
- Open a card to see the screenshot, the page it was left on, the reviewer’s browser, the full reply thread and the activity history. Reply from there (Markdown supported).
- The board refreshes itself while it is open, so new reports appear without reloading.
- The WordPress admin bar shows how many items are open.
- Export feedback to CSV or JSON.
Bug reports that point at the exact spot
- Reviewers click the element they mean – a headline, a button, a broken layout – and write a comment pinned to it.
- Each new comment gets a screenshot of the visible part of the page with the pin painted on it. Reviewers can add more, select an area and mark it up with arrows, shapes and text.
- Pins stay on the right element after content changes, theme switches and resizes: each one is anchored four ways, with a fallback when the element is gone.
- Comments are threaded, so you and your client can discuss a report where it was left.
Clients report without an account
- Send a review link. The reviewer opens it and starts commenting – no WordPress account, no browser extension, no separate app.
- Links can be limited to one page, set to expire, made view-only or switched off at any time.
- Reviewers get an e-mail when someone replies, once they confirm their address.
Access for your whole team
- Settings Access gives people Client, Team or Manager access. Clients reply and move items between statuses, Team members work on feedback like an administrator, and Managers also create review links.
- People with access use the widget on your site without a review link.
- Owners have full access to Vifee, including its settings and export. The administrator who installs Vifee becomes its owner and decides what every other administrator gets – so a client with an administrator account can be a Client in Vifee.
Nothing leaves your server
Feedback, screenshots and reviewer details are stored in your own WordPress database and a private, non-public uploads directory. Vifee makes no outbound requests, calls no third-party API and sends no telemetry. Screenshots hide passwords and form values before they leave the reviewer’s browser. For agencies working with public-sector, healthcare or legal clients, “the data never leaves our server” is often a procurement requirement.
Built to stay out of the way
- The widget loads only for people with a review link or access. Ordinary visitors never see it and download nothing extra.
- It works the same on Elementor, Divi, block themes and classic themes.
- No per-user, per-project or per-site fees: use it on as many sites and with as many reviewers as you need.
A paid add-on is planned
A separate PRO add-on is planned for agencies managing feedback across multiple client sites. It will be entirely optional – nothing described above is disabled, watermarked, or held back in this free version to encourage an upgrade, and every feature here stays free, forever.
Multisite
Vifee keeps separate feedback for every site of a network. When the plugin is active on a site – individually or network-wide – that site gets its tables, keys, the manage_vifee_feedback capability for administrators and its daily maintenance on its first request, including sites added to the network later. Uninstalling honours each site’s own “delete all data” setting.
Privacy
Feedback may contain a display name, an optional private email address, technical browser data, replies and screenshots. Optional email addresses are encrypted at rest, using a dedicated encryption key generated on activation, and are never exposed to other reviewers.
Feedback is retained indefinitely by default; there is no automatic expiry, and older feedback must be removed manually from the Vifee admin screen. Review sessions expire automatically after 30 days.
Go to Vifee Settings to opt in to deleting all Vifee feedback, attachments and reviewer data when the plugin is uninstalled. This is disabled by default, so uninstalling the plugin normally leaves your feedback data in place.
This plugin supports the WordPress Tools Export/Erase Personal Data screens. They find guest reviewers by the email they left and signed-in authors by their WordPress account, and cover the profile, submitted feedback, replies and attachments. Erasure replaces the person’s text with a removal notice, clears browser details, deletes their screenshots and ends their review sessions.
Screenshots hide personal data before they leave the reviewer’s browser, so nobody has to remember to cover it. Passwords and elements with the data-vifee-mask attribute are always hidden; values typed into form fields are hidden by default. On Vifee Settings Privacy you can list more elements to hide by CSS selector, or hide all page text. The reviewer can cover anything else with the Hide area tool, which paints a solid block into the image: only the finished image is uploaded, never the original.
By default each new comment gets a screenshot of the visible part of the page, taken when the reviewer places the pin, with the pin painted on it. The reviewer sees it under the comment and can remove it before sending; it is masked exactly like a screenshot taken by hand. Switch it off on Vifee Settings Privacy.
Screenshots are stored under random file names in a private uploads subdirectory protected by .htaccess / web.config. On servers that ignore those files (nginx) the random names keep them unguessable; to keep them out of the web root entirely, define VIFEE_PRIVATE_DIR in wp-config.php with a directory outside it.
Credits
Bundled library
The review widget bundles html2canvas-pro (MIT licence, GPL-compatible: https://github.com/yorickshan/html2canvas-pro), a maintained fork of html2canvas, to render the on-page screenshot capture entirely in the reviewer’s browser. No image processing happens server-side and no third-party service is involved.
Skærmbilleder




Installation
- Upload the plugin directory to
/wp-content/plugins/. - Activate Vifee Visual Feedback.
- Configure review access and data-retention preferences from the Vifee admin screens.
FAQ
-
Can I use Vifee to collect bug reports from clients, not just design feedback?
-
Yes. Every pin has an issue type – Task or Bug – plus a priority and a workflow status, so a client reporting “this form is broken” and a client suggesting “make this button bigger” both land on the same triaged board instead of two different inboxes.
-
Can I use it as a kanban board for my own team’s website tasks?
-
Yes. Anyone you give Team or Manager access on Settings Access can pin tasks and bugs on the site without a review link, and the whole team works through them on the same board – no client required.
-
Do reviewers need an account or a browser extension to leave feedback?
-
No. A reviewer opens the review link you send them and pins comments, screenshots and replies straight on the live page – no WordPress account, no browser extension, no separate app to install.
-
Can reviewers annotate a screenshot of the page instead of just leaving a comment?
-
Yes. A reviewer can attach a full-page or region screenshot to any pin and mark it up with arrows, shapes and text, or cover parts of it with the Hide area tool, before sending – so a bug report carries the exact picture you need, not just a text description.
-
Does Vifee slow down my website?
-
No. The widget loads only for people with a review link or Vifee access; ordinary visitors get the page without it. The board lives in wp-admin.
-
Does the visual feedback widget work with Elementor, Divi, or any page builder?
-
Yes. The widget loads as a standard front-end script, independent of the theme or page builder that rendered the page, so it works the same way on Elementor, Divi, block-theme, or classic-theme sites.
-
Can I use Vifee for client feedback across multiple websites?
-
Yes – install it on as many WordPress sites as you like at no extra cost; there’s no per-site, per-user or per-project fee. Each installation keeps its own feedback separate from every other one (see “Who can see feedback?” below for how that works within a single site).
-
Does Vifee send any data outside my WordPress installation?
-
No. Feedback, screenshots and reviewer data are stored in your own database and a private, non-public uploads subdirectory. The plugin does not call any third-party service and does not send telemetry.
-
Who can see feedback?
-
Only Vifee owners, other administrators at the level the owners chose, people given access on Settings Access and guests who used a valid, unexpired review link can see and submit feedback. The review widget is never shown to ordinary site visitors. The one exception: a page opened with a
?vifee_token=that is unknown, expired or switched off shows a small “This review link no longer works” notice instead of the comment form, and that page view skips page caching. The notice reveals nothing about the site or its feedback and looks the same for an unknown and a dead link. Clean-mode links never show it. Archived feedback is visible only in the admin panel, never in the widget.Note for agencies serving multiple clients on one installation: reviewers authenticated through any valid review link share ONE feedback space per site – a reviewer for Client A can read threads opened for Client B. Scope installations (or use WordPress multisite) accordingly.
-
Can a client with an administrator account be limited in Vifee?
-
Yes. On Settings Access, the Administrators list sets each administrator’s Vifee level: Owner, Manager, Team, Client or No access, or the default for administrators (Client unless you change it). The administrator who installed Vifee is its owner; until owners are chosen, as on sites that had Vifee before 1.5.1, every administrator is one. Only owners see Settings and Export. This keeps the board tidy; it is not a security boundary, since a WordPress administrator can always deactivate plugins or change the database.
-
I am no longer an owner and nobody can give it back. What now?
-
Add
define( 'VIFEE_RECOVERY', true );towp-config.php(your host’s file manager or FTP will do). While it is there, every administrator has full access to Vifee and a notice in wp-admin says so; the owners get one e-mail when it starts. Choose owners on Settings Access, then remove the line. If the last owner’s account is deleted or stops being an administrator, every administrator becomes an owner by itself. -
What happens to feedback when I uninstall the plugin?
-
By default, nothing – your database tables and any stored attachments are left in place so you can reinstall later without losing data. If you want uninstalling to permanently delete everything, enable that under Vifee Settings before you uninstall.
-
Does Vifee require any particular PHP extensions?
-
Yes: the GD extension (for screenshot processing) and the Fileinfo extension (for upload validation) are required in addition to PHP 8.1+. Most hosts enable both by default.
-
Does Vifee work on WordPress multisite networks?
-
Yes. Every site keeps its own feedback, review links and settings. Activate Vifee on single sites or network-wide: activating it on one site does not affect any other, and network-activating it sets up every site of the network, including sites added later (on their first request).
Anmeldelser
Der er ingen anmeldelser for denne widget.
Bidragsydere & udviklere
“Vifee – Bug Tracker & Kanban Board for Client Website Feedback” er open source-software. Følgende personer har bidraget til dette plugin.
BidragsydereOversæt “Vifee – Bug Tracker & Kanban Board for Client Website Feedback” til dit eget sprog.
Interesseret i udvikling?
Gennemse koden, tjek SVN repository, eller abonner på udviklerloggen via RSS.
Ændringslog
1.5.1
- [Feature] Owners: the administrator who installs Vifee owns it and decides what every other administrator gets on Settings Access – Owner, Manager, Team, Client or No access, with a default for administrators (Client). Only owners see Settings and Export. Sites updated from an earlier version keep every administrator as an owner until owners are chosen.
VIFEE_RECOVERYinwp-config.phpgives every administrator full access again and e-mails the owners. - [Changed] Team e-mails and the assignee list leave out administrators whose Vifee level does not include working on feedback.
- [Changed] For add-ons: the
administer_vifeecapability replacesmanage_optionsfor Vifee settings, access and export. - [Changed] A single image can be up to 5 MB (was 10 MB). Screenshots too large as PNG are saved as JPEG.
- [Fixed] Feedback can be added and changed on hosts whose firewall blocks brackets in anchor paths or drops the If-Match header.
1.5.0
- [Feature] For add-ons: the guest actions API reads a reply as it is now and changes a status together with a reply, so a refused change leaves no reply behind.
- [Security] A guest’s e-mail address gets reply notifications only after its owner confirms it from a one-time e-mail, and one unsubscribe stops mail to that address for good. Reply e-mails stop once the guest’s review link is revoked or expired, the thread is archived, or a client loses access.
- [Security] Guests can write at most 60 times per 10 minutes and 600 times a day per review link, a thread takes up to 200 replies, and attachments stop at 1 GB in total (filter
vifee_attachment_storage_quota). - [Security] Feedback must belong to a page of this site; add other domains with
vifee_allowed_page_hosts. The admin panel links only to those hosts. - [Security] Erasing a person’s data or deleting their account detaches and anonymizes their profile, and deleting a site on multisite removes its Vifee tables. On multisite, Settings Access changes only members of the current site.
- [Security] Pages with the widget cannot be framed by other sites, are not cached and do not pass review tokens on in the Referer header; guests’ REST responses are not cached either. “Hidden widget” links no longer start a guest session.
- [Security] Guest reviewers’ widget requests, reads included, must carry the session’s CSRF token, and API calls from pages of other sites (another subdomain, for example) are refused, so a neighbouring site cannot read a reviewer’s feedback with their cookie or start a review session for them.
- [Security] The widget’s “Open page” goes only to pages of this site, stored anchor paths are used only in the form the widget writes, screenshots also hide fields inside web components, and comments or captured errors with an unexpected shape no longer break the widget for the team.
- [Fixed] A retried request no longer sends the same notification twice, and the board loads quickly with very long comments.
1.4.0
- [Feature] Replies can be edited by their author and deleted by the author or a manager in the widget. An edited reply is marked “edited”; a deleted one leaves an entry in the item’s history.
- [Feature] For add-ons:
@mentions in replies. Without an add-on that allows them (vifee_allowed_mentions), a mention is saved as plain text. A mentioned person gets an e-mail, and the reply field in the admin panel suggests people fromvifee_mention_provideras you type@. - [Changed] JavaScript errors attached to feedback have tokens, passwords and keys removed before they leave the reviewer’s browser.
- [Fixed] On phones the comment form stays inside the screen.
- [Fixed] Keyboard pin placement reacts to the first key press.
- [Fixed] A comment with a long run of square brackets no longer freezes the page while it is shown.
Older versions are listed in changelog.txt.
