Filevue

FAQ

Where can I get help?

Filevue offers two different support channels. Pick the one that fits your question:

• Filevue Support Portal — https://www.filevue.app/support/
  Official help from the Filevue team. Use this for setup guidance, bug reports, license questions, and opening or tracking support tickets. This is the Filevue website, not WordPress.org.

• WordPress.org Support Forum — https://wordpress.org/support/plugin/filevue/
  Free, public community discussions hosted on wordpress.org. Use this for general how-to questions you are happy to post publicly. It is separate from the Filevue Support Portal and is not where you open private Filevue tickets.

What is the difference between Filevue Free and Filevue Pro?

Filevue Free (WordPress.org) includes the full client portal workflow with caps of 5 clients, 20 folders, 100 files, and 2 staff members, plus SMTP, data sheets, team roles, basic portal styling, projects, staff portal login, and activity notifications.

Filevue Pro removes all usage caps and adds Portal Design (white-label portal and email styling), Telegram alerts, image compression, CSV export for the activity log, Elementor widgets, and priority support. See the comparison on filevue.app.

How do I upgrade to Filevue Pro?

Visit filevue.app pricing, choose a plan (Single Site, Agency, or Unlimited), and complete checkout:

• 🏠 Single Site — one WordPress site — Purchase
• 🏢 Agency — up to five WordPress sites — Purchase
• ♾️ Unlimited — unlimited WordPress sites — Purchase

Install the Pro package and activate your license under Filevue in WordPress. Your existing clients, files, and settings are kept.

What are the limits of Filevue Free?

Filevue Free is fully functional for solo practitioners and small teams. The current caps are:

• Up to 5 clients in total.
• Up to 20 folders in total across all clients.
• Up to 100 files in total across all clients.
• Up to 2 staff members.

When you reach any cap, an inline notice appears on the Home page, View Clients page, and Edit Client page. You can still log in, browse, download, and delete content normally. Upgrade to Pro for unlimited usage.

Where do clients log in?

Filevue automatically creates a page at /client-portal/ with the login form when the plugin is activated. Clients visit that URL, enter their Client ID and password, and immediately see their files. You can also place the [filevue_client_files] shortcode on any page to create an alternative portal entry point.

How can I preview the portal as a specific client?

On the Clients page, click the Portal button (the Filevue icon) next to any client. This generates a secure, single-use token that auto-logs you into the portal as that client in a new tab. The token expires after 60 seconds and can only be used once. No credentials are exposed.

Can clients upload files or update their own details?

Yes. After logging in, clients can:

• Upload files to folders using the upload button on each folder in the portal.
• Update personal details (name, email, country, phone, address, and notes) from My Account in the portal header.
• Change their password from the same My Account panel.

You and your team still manage clients from the WordPress admin. Clients only see and edit their own account and files.

Can clients see each other’s files?

No. Each client can only access files uploaded to their own folder. Downloads are verified against the logged-in client’s session.

Can staff see all clients?

No. Staff members only see the projects they are assigned to. They log in on the staff tab of the same portal page.

What file types can I upload?

PDF, XLSX, XLS, DOC, DOCX, TXT, PNG, JPG, JPEG, GIF, ZIP, and RAR. File size limits follow your WordPress and server configuration.

Can I use my own SMTP server?

Yes. Go to Filevue > SMTP Settings, enter your credentials, and send a test email. Settings only activate after a successful test.

What happens to client data if I deactivate or delete the plugin?

By default, all data is preserved, which is safe for updates and reinstalls. You can enable „Delete all data on uninstall“ from the home page if you want a clean removal.

Does the portal show my plugin or brand name?

No. The portal uses your WordPress site name for all labels and headings. There is no hardcoded branding.

How do I customise the look of the client portal? (Pro)

Open Filevue > Portal Design. Six tabs cover Login Page, Dashboard, Typography, Presets, Custom CSS, and Tools — plus an Emails tab for branded transactional messages. Free users can adjust basic button and accent colours from Filevue > Settings.

Are there Elementor widgets for the portal? (Pro)

Yes. Filevue Pro ships four widgets under a Filevue category: Login Form, Folder Tree, Recent Files, and Client Header. Four dynamic tags (Client name, Project name, File count, Last login) work in any Elementor text control. With Elementor Pro, a Filevue Portal Theme Builder location is available for fully custom layouts.

I get „Not Acceptable“ / HTTP 406 error when logging in or uploading files

This error is returned by your hosting provider’s ModSecurity (a Web Application Firewall), not by Filevue itself. It’s a false positive where a legitimate request is being blocked because it matches a „suspicious“ pattern.

Common triggers:

• Passwords containing special characters like %, ', ", <, >, =, or words like select, union, drop.
• Uploading files with unusual filenames (brackets, quotes, encoded characters).
• Filenames or folder names with accented / non-ASCII characters (very common in Spanish, French, Portuguese, German, etc. — e.g. Facturación.pdf, Año 2026.xlsx, Diseño.png, Niño.jpg). When the browser URL-encodes ó as %C3%B3, ModSecurity may block the request as a suspected encoding attack.
• Saving content that contains SQL-like words or HTML/JS snippets.

Good news: As of version 1.5.0, Filevue prevents most of these 406 errors automatically:

• Filenames are auto-transliterated at upload time while keeping spaces intact: Año 2026.pdf becomes Ano 2026.pdf (not Ano-2026.pdf), Facturación enero.pdf becomes Facturacion enero.pdf, Diseño final.png becomes Diseno final.png.
• Folder names follow the same rule: Diseño becomes Diseno, Año 2026 becomes Ano 2026.
• Client passwords can no longer contain characters that trigger ModSecurity: quotes (' "), angle brackets (< >), backslash (\), percent (%), semicolon (;), or accented / non-ASCII characters. Allowed characters are letters, numbers and - _ . ! @ # $ * + = : ? ~ ^ ( ) [ ] { } | ,. Existing passwords keep working; only newly-saved ones are validated.
• Client names, descriptions, and email messages are not affected — they fully support accented characters (á, é, í, ó, ú, ñ, ü, ¿, ¡), so you can still enter José García as a client name, write Spanish/French/Portuguese descriptions, and send localized emails. These fields are never sent through URLs, so WAFs can’t block them.

If you have existing files with accents on disk or old passwords with special characters and still hit the error, rename those files / reset the password to a safe one, or use one of the solutions below.

Solutions (in order of recommendation):

Option 1. Contact your hosting provider. Ask them to check the ModSecurity logs for the blocked request and either whitelist the triggered rule IDs for your site or disable ModSecurity for /wp-admin/admin-ajax.php and /wp-admin/admin-post.php.

Option 2. Try a different password for the client (use only letters, numbers, and -_.!@#) to confirm the password is the trigger.

Option 3. Rename the file you are uploading to something simpler (letters, numbers, hyphens, underscores only).

Option 4. Add a rule to your .htaccess if your host allows it. Both endpoints (admin-ajax.php and admin-post.php) need to be covered because Filevue uses admin-post.php for uploads, login, and form submissions, and admin-ajax.php for inline actions. Edit the .htaccess file at the root of your WordPress install (the same folder where wp-config.php lives) and paste the block below near the top, before the WordPress block.

The snippet disables ModSecurity only for the two WordPress admin endpoints that Filevue uses, so the rest of your site remains protected by ModSecurity:

<IfModule mod_security.c>
    <LocationMatch "/wp-admin/admin-ajax\.php">
        SecRuleEngine Off
    </LocationMatch>
    <LocationMatch "/wp-admin/admin-post\.php">
        SecRuleEngine Off
    </LocationMatch>
</IfModule>

Some hosts ship ModSecurity 2.9 or newer under the module name mod_security2.c. If the rules above are ignored, replace the wrapper with the alternative module name:

<IfModule mod_security2.c>
    <LocationMatch "/wp-admin/admin-ajax\.php">
        SecRuleEngine Off
    </LocationMatch>
    <LocationMatch "/wp-admin/admin-post\.php">
        SecRuleEngine Off
    </LocationMatch>
</IfModule>

After saving the file, retry the action that produced the 406 error. If you still get it, check with your host whether .htaccess overrides for mod_security are enabled. Some managed hosts (WP Engine, Kinsta, Pressable) do not allow this and require a support ticket instead.

Option 5. Whitelist a specific rule ID if you want to keep ModSecurity active and only silence the false positive. Replace 949110 with the rule ID shown in your host’s ModSecurity log:

<IfModule mod_security.c>
    <LocationMatch "/wp-admin/(admin-ajax|admin-post)\.php">
        SecRuleRemoveById 949110
    </LocationMatch>
</IfModule>

This error is almost always a hosting configuration issue, not a plugin bug. Most shared hosts (Bluehost, SiteGround, HostGator, GoDaddy) ship with ModSecurity enabled and will gladly tune the rules if you contact support.