=== Volixta SSL & Security Headers ===
Contributors: volixta
Tags: security headers, mixed content, ssl, https, lets encrypt
Requires at least: 5.8
Tested up to: 7.1
Stable tag: 1.2.2
Requires PHP: 7.4
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Set up WordPress SSL, HTTPS redirects, Let’s Encrypt certificates, mixed content fixes, and security headers from one guided interface.

== Description ==

**Volixta SSL & Security Headers** helps you set up, verify, and manage HTTPS on WordPress without manually editing sensitive server configuration.

Request a free **Let’s Encrypt SSL certificate**, install it through supported hosting panels, switch WordPress to HTTPS, force **301 HTTPS redirects**, find and repair **mixed content**, configure modern **security headers**, and keep recovery files before server rules are changed.

Volixta guides you through the important steps while keeping advanced SSL and server controls available when you need them.

👉 **From SSL certificate setup to final HTTPS protection, Volixta keeps the whole process in one place.**

---

### 🔐 What does Volixta do?

- **Request free Let’s Encrypt certificates**: issue SSL certificates directly from WordPress using ACME v2 and HTTP-01 validation.
- **Install SSL certificates**: use supported cPanel, Plesk, and DirectAdmin integrations, or download the certificate files for manual installation.
- **Renew managed certificates**: automatically check eligible production certificates with WP-Cron and renew them when required.
- **Activate WordPress HTTPS**: safely update your WordPress `home` and `siteurl` to use `https://`.
- **Force HTTPS with a 301 redirect**: add a managed `.htaccess` block on Apache/LiteSpeed or use Nginx configuration guidance.
- **Fix mixed content**: check the frontend, run a Deep Scan, use the Live Fixer when needed, or perform serialization-safe Database Cleanup.
- **Apply modern HTTP Security Headers**: configure HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, COOP, COEP, and CORP.
- **Protect .htaccess changes**: create Safety Backups and automatic rollback copies before sensitive server changes.
- **Check SSL and server status**: view certificate, HTTPS, redirect, server, file, and Security Header information from WordPress.
- **Nginx friendly**: get ready-to-copy configuration when `.htaccess` is not available.
- **Localhost aware**: handle local environments separately and provide optional trusted HTTPS guidance with mkcert.
- **Site Health integration**: check important SSL, HTTPS, redirect, and Security Header states from WordPress Site Health.

---

### 🔐 Let’s Encrypt SSL Certificates

Volixta includes a native **ACME v2 client** for requesting Let’s Encrypt certificates directly from WordPress.

- **Request certificates**: use the ACME HTTP-01 challenge to request a free Let’s Encrypt SSL certificate.
- **Generate keys locally**: ACME account keys and certificate private keys are generated on your server.
- **Validate certificate files**: certificate and private-key pairs are checked before installation.
- **Use staging mode**: test the certificate workflow against the Let’s Encrypt staging environment before using production.
- **Detect managed certificates**: Volixta can identify certificate files it already manages.
- **View certificate information**: check the issuer, expiration date, and current certificate state.
- **Keep failed installations recoverable**: generated certificate files remain available if hosting installation does not complete.
- **Download certificate files**: use the generated files for manual installation when required.
- **Handle rate limits**: if Let’s Encrypt provides a retry time, Volixta temporarily prevents additional requests until that time has passed.

---

### ⚡ Hosting-Aware SSL Installation

Volixta can install generated SSL certificates automatically when a supported hosting integration is configured.

Supported hosting panels include:

- **cPanel**
- **Plesk**
- **DirectAdmin**

- **Automatic installation**: send the generated certificate to a configured supported hosting panel.
- **Public verification**: check the certificate actually served by the website after installation.
- **Manual installation fallback**: keep certificate files available when automatic installation is unavailable or unsuccessful.
- **Optional integration**: you can continue using certificates already managed by your hosting provider without configuring a hosting connection in Volixta.

---

### 🔄 Automatic Certificate Renewal

Eligible Volixta-managed production certificates can be checked using WP-Cron.

- **Renewal monitoring**: Volixta checks eligible managed certificates as they approach expiration.
- **30-day renewal window**: by default, renewal becomes available within 30 days of expiration.
- **Automatic replacement**: a new certificate can be requested when renewal is required.
- **Automatic installation**: the renewed certificate can be installed when the required hosting integration is configured.
- **Manual renewal**: certificate renewal can also be started manually.

---

### 🔒 WordPress HTTPS Setup

Having a valid SSL certificate does not necessarily mean WordPress is fully configured to use HTTPS.

Volixta helps complete the remaining setup.

- **WordPress Home URL**: update the Home URL from HTTP to HTTPS.
- **WordPress Site URL**: update the Site URL from HTTP to HTTPS.
- **Configuration verification**: check the effective WordPress URL configuration after the change.
- **301 HTTPS redirect**: redirect HTTP visitors permanently to the HTTPS version of the website.
- **Proxy-aware detection**: recognize HTTPS in supported reverse-proxy environments.
- **ACME compatibility**: keep HTTP-01 certificate challenges accessible while HTTPS redirects are active.
- **Apache and LiteSpeed support**: manage HTTPS redirect rules inside dedicated Volixta `.htaccess` blocks.
- **Nginx support**: provide the required configuration when `.htaccess` cannot be used.

---

### 🛟 Safe .htaccess Changes & Recovery

A bad redirect or server rule can make a website unreachable before WordPress even loads.

Volixta includes recovery protection for sensitive `.htaccess` changes.

- **Safety Backup**: create and download a recovery copy of the current `.htaccess` file.
- **Automatic rollback backup**: supported sensitive changes create a backup before the server file is modified.
- **Managed blocks only**: Volixta is designed to modify only its own marked sections.
- **Existing rules preserved**: unrelated WordPress, hosting, cache, and plugin rules remain outside Volixta-managed blocks.
- **Marker validation**: duplicate or incomplete Volixta markers are detected before changes are made.
- **Concurrent modification checks**: the operation is stopped if `.htaccess` changes unexpectedly during an update.
- **Symlink protection**: unsafe symbolic-link targets are refused.
- **Line-ending preservation**: the existing file format is preserved where possible.
- **Backup verification**: sensitive changes require the recovery copy to be created and verified.
- **Safe file replacement**: server-rule updates use a controlled temporary-file replacement process.
- **Fail-closed behavior**: if Volixta cannot complete the operation safely, the existing `.htaccess` file is left unchanged.

---

### 🔎 Mixed Content Detection & Repair

A valid SSL certificate does not guarantee that every resource on the website is loaded through HTTPS.

Images, scripts, stylesheets, fonts, or other resources can still use insecure HTTP URLs and cause browser mixed content warnings.

- **Frontend Check**: manually inspect the rendered HTTPS page for insecure resources.
- **Manual verification**: the frontend check runs only when you start it and does not scan the website every time you open Volixta.
- **Live Fixer**: upgrade eligible insecure resource URLs while pages are rendered without permanently changing the database.
- **Use Live Fixer only when needed**: if the frontend is already clean, there is normally no reason to keep the Live Fixer enabled.
- **Deep Mixed Content Scan**: search more deeply for HTTP resources and help trace detected URLs back to their source.
- **Database Cleanup**: permanently repair eligible insecure URLs stored in WordPress when needed.
- **Serialization-safe processing**: eligible serialized WordPress values are handled without using a blind raw string replacement.
- **Canonical hostname protection**: permanent replacements are restricted to the site's own hostname rather than replacing every external `http://` URL.

Database Cleanup can inspect eligible:

- Posts and pages
- Post metadata
- WordPress options

---

### 🛡️ Security Headers

Volixta lets you configure modern browser security protections from the WordPress admin area.

Supported headers include:

- **Strict-Transport-Security (HSTS)**
- **Content-Security-Policy (CSP)**
- **X-Frame-Options**
- **X-Content-Type-Options**
- **Referrer-Policy**
- **Permissions-Policy**
- **Cross-Origin-Opener-Policy (COOP)**
- **Cross-Origin-Embedder-Policy (COEP)**
- **Cross-Origin-Resource-Policy (CORP)**
- **Cross-Origin-Opener-Policy-Report-Only**
- **Cross-Origin-Embedder-Policy-Report-Only**
- **X-Permitted-Cross-Domain-Policies**
- **X-Content-Security-Policy**
- **Access-Control-Allow-Headers**
- **Access-Control-Allow-Methods**

- **Recommended configuration**: start with a simpler set of browser protections for common WordPress websites.
- **Advanced configuration**: enable, disable, and customize individual policies when more control is required.
- **Explicit activation**: Security Headers are not applied to the server until an administrator chooses to apply them.
- **Server-aware configuration**: use managed rules on supported Apache/LiteSpeed environments or copy the provided Nginx configuration.

---

### 🧭 Guided Security Setup

Volixta includes a guided setup that adapts to the current state of the website.

Instead of showing every technical option at once, the Setup page focuses on the next relevant action.

The complete workflow can include:

1. Check the website and server environment.
2. Create a recovery backup when needed.
3. Detect an existing SSL certificate or request a new Let’s Encrypt certificate.
4. Install the certificate when required.
5. Verify the active public certificate.
6. Switch WordPress URLs to HTTPS.
7. Enable the HTTP → HTTPS 301 redirect.
8. Check the website for mixed content.
9. Configure Security Headers.

- **Current-state detection**: completed steps are recognized automatically where possible.
- **Next-action guidance**: the interface focuses on what still needs to be done.
- **Safety backup reminder**: recovery is presented before server changes when `.htaccess` is involved.
- **Advanced controls remain available**: experienced users can still access certificate, server, mixed content, and Security Header tools directly.

---

### 💻 Local Development Support

Volixta detects common local-development environments.

Supported local patterns include:

- `localhost`
- Single-label local hostnames
- `.local`
- `.test`

- **Public SSL not required**: Volixta does not expect a public Let’s Encrypt certificate on a detected local environment.
- **HTTPS remains optional**: you can intentionally continue developing over HTTP.
- **Production checks do not block setup**: missing public certificates, redirects, or production Security Headers are not treated as setup failures locally.
- **mkcert guidance**: if you want trusted local HTTPS, Volixta provides hostname-aware instructions for using mkcert.

---

### 🌐 Apache, LiteSpeed & Nginx

Volixta adapts to the detected web-server environment.

- **Apache**: use dedicated Volixta `.htaccess` blocks for supported HTTPS redirects and Security Headers.
- **LiteSpeed**: use compatible `.htaccess` rules while keeping Volixta changes isolated in managed blocks.
- **Nginx**: get ready-to-copy configuration because Nginx does not use `.htaccess`.
- **Reverse proxies**: HTTPS detection accounts for supported proxy configurations.

---

### 🔬 SSL & Server Diagnostics

Volixta provides technical status information when you need to troubleshoot SSL or HTTPS configuration.

Depending on the environment, diagnostics can include:

- **HTTPS request status**: check whether the current request is using HTTPS.
- **Public SSL certificate**: check whether a valid certificate is currently served.
- **Certificate issuer**: see which certificate authority issued the active certificate.
- **Certificate expiration**: see when the active SSL certificate expires.
- **WordPress URLs**: check whether Home URL and Site URL use HTTPS.
- **Web server**: identify the detected server environment.
- **.htaccess availability**: check whether server-rule management is available.
- **HTTPS redirect**: inspect the current redirect configuration.
- **Security Headers**: check configured browser protections.
- **Certificate files**: see whether Volixta-managed certificate files are available.
- **Hosting integration**: check the configured certificate-installation method.

This helps distinguish between having an SSL certificate and having a fully configured HTTPS website.

---

### ⚡ Low Frontend Overhead

Most Volixta operations run only when they are needed in the WordPress admin area.

- **Certificate issuance**: does not run during normal frontend visits.
- **Hosting installation**: runs only when certificate installation or renewal requires it.
- **Mixed Content scans**: do not run automatically for normal visitors.
- **Database Cleanup**: runs only when an administrator explicitly starts it.
- **Frontend Check**: runs manually when requested.
- **WP-Cron renewal checks**: use a lightweight scheduled process for eligible managed certificates.
- **Optional frontend features**: only features that specifically need frontend processing, such as the PHP redirect fallback or enabled Live Fixer, run during visitor requests.

---

### 🔐 Security-Focused Design

Sensitive operations are restricted to authorized administrators and use standard WordPress security controls.

- **Capability checks**: sensitive actions require the appropriate WordPress permissions.
- **WordPress nonces**: administrative requests are protected against unauthorized submissions.
- **Input sanitization**: submitted values are validated and sanitized before use.
- **Contextual escaping**: output is escaped for its destination.
- **Prepared database queries**: database operations use WordPress query protections where required.
- **Encrypted cPanel API tokens**: configured cPanel credentials are stored using encrypted token storage.
- **Protected certificate storage**: certificate and private-key files are kept in protected plugin-managed storage.
- **Certificate/key validation**: certificate and private-key pairs are checked before installation.
- **TLS verification**: remote hosting requests use TLS certificate verification.
- **Recovery requirements**: sensitive `.htaccess` changes require appropriate backup protection.
- **Fail-closed operations**: when a sensitive server change cannot be completed safely, Volixta stops instead of forcing the modification.

---

### ✅ Why choose Volixta?

- **Guided instead of complicated**  
  Volixta shows the next relevant SSL or security action instead of requiring you to understand every server setting first.

- **Built-in Let’s Encrypt support**  
  Request, inspect, install, renew, and download SSL certificates from WordPress.

- **Safe by design**  
  Sensitive `.htaccess` operations use recovery backups, consistency checks, and fail-closed handling.

- **Existing server rules stay separate**  
  Volixta manages its own marked blocks instead of intentionally replacing unrelated `.htaccess` configuration.

- **Serialization-safe mixed content repair**  
  Database Cleanup handles eligible serialized WordPress data instead of using a blind database-wide replacement.

- **Hosting-aware certificate installation**  
  Supported cPanel, Plesk, and DirectAdmin environments can install generated certificates directly.

- **Nginx friendly**  
  Ready-to-copy server rules are provided when `.htaccess` is not available.

- **Localhost aware**  
  Local development environments are handled differently from public production websites.

- **Low frontend overhead**  
  Certificate management, scans, cleanup, and most configuration tasks stay out of normal visitor requests.

---

### 🔎 Typical problems solved

**How do I get a free SSL certificate for WordPress?**  
→ Request a Let’s Encrypt certificate directly from Volixta using the built-in ACME client.

**I already have SSL, but WordPress still uses HTTP.**  
→ Volixta can update your WordPress Home URL and Site URL to HTTPS.

**How do I force HTTPS with a 301 redirect?**  
→ Enable the HTTPS redirect from Volixta. Apache/LiteSpeed can use a managed `.htaccess` block, while Nginx users receive the required configuration.

**My browser still reports mixed content after installing SSL.**  
→ Run the Frontend Check or Deep Scan to find insecure resources, then use the appropriate repair tool.

**How do I add Security Headers to WordPress?**  
→ Use the Recommended profile or configure individual headers from the Advanced section.

**Can I change .htaccess without risking my existing rules?**  
→ Volixta provides Safety Backups and manages its own marked blocks. If a supported sensitive change cannot be completed safely, the existing file is left unchanged.

**I use Nginx and do not have .htaccess.**  
→ Volixta provides ready-to-copy Nginx configuration for supported HTTPS and Security Header features.

**Can I use Volixta on localhost?**  
→ Yes. Local environments are detected and handled separately from public production websites.

---

== Installation ==

1. Upload the plugin to `/wp-content/plugins/` or install **Volixta SSL & Security Headers** from the WordPress plugin directory.
2. Activate the plugin.
3. Open **Volixta SSL & Security** from the WordPress admin menu.
4. Follow the Guided Setup.
5. Create a Safety Backup when `.htaccess` changes will be used.
6. Detect an existing SSL certificate or request a free Let’s Encrypt certificate if needed.
7. Install and verify the certificate.
8. Activate WordPress HTTPS and enable the HTTPS redirect.
9. Check the website for mixed content.
10. Apply the recommended Security Headers if appropriate for your website.

---

== Frequently Asked Questions ==

= Do I need an SSL certificate before using Volixta? =

No. Volixta can detect an existing public certificate or request a free Let’s Encrypt certificate for an eligible public domain.

If your hosting provider already manages SSL, you can continue using that certificate.

= Can Volixta request a free Let’s Encrypt SSL certificate? =

Yes. Volixta includes an ACME v2 client and supports Let’s Encrypt certificate requests using the HTTP-01 challenge.

The domain must be publicly reachable and meet the certificate authority requirements.

= Can Volixta install the SSL certificate automatically? =

Yes, when a supported hosting integration is configured.

Volixta supports certificate installation through cPanel, Plesk, and DirectAdmin integrations.

If automatic installation is unavailable, the generated certificate files remain available for manual installation.

= Can Volixta renew SSL certificates automatically? =

Yes. Eligible Volixta-managed production certificates can be checked through WP-Cron.

When a certificate reaches the renewal window, Volixta can request and install a replacement when the required hosting integration is configured.

= How do I activate HTTPS in WordPress? =

Once a valid certificate is available, open Volixta and follow the Guided Setup or the SSL & HTTPS section.

Volixta can update the WordPress Home URL and Site URL to use HTTPS.

= How do I force HTTP to HTTPS? =

Volixta can enable a permanent 301 HTTPS redirect.

On Apache and LiteSpeed, the redirect can be added inside a Volixta-managed `.htaccess` block.

For Nginx, Volixta provides the configuration that needs to be added to the server.

= Does Volixta replace my .htaccess file? =

No. Volixta is designed to manage only its own marked sections inside `.htaccess`.

For example:

- `# BEGIN Volixta HTTPS Redirect`
- `# END Volixta HTTPS Redirect`

Rules outside Volixta-managed blocks are preserved by the managed-block writer.

Sensitive operations also use backup and consistency checks. If the file cannot be modified safely, Volixta leaves it unchanged.

= What is the Safety Backup? =

The Safety Backup is a recovery copy of the current `.htaccess` file.

You can download it before changing redirects or server Security Headers.

If a server configuration problem makes WordPress unavailable, the backup can be restored manually through your hosting File Manager.

= Does Volixta create automatic .htaccess backups? =

Yes. Supported sensitive `.htaccess` operations create an automatic rollback backup before the file is changed.

You can also create and download a manual Safety Backup.

= What happens to .htaccess when I uninstall Volixta? =

Volixta does not intentionally delete or replace the whole `.htaccess` file.

The uninstall process only attempts to remove Volixta-managed blocks.

Before modifying an existing `.htaccess` file during uninstall, a verified recovery snapshot is required. If that snapshot cannot be created safely, the existing `.htaccess` file is left unchanged.

= What is mixed content? =

Mixed content happens when an HTTPS page still loads one or more resources through HTTP.

This can include images, scripts, stylesheets, fonts, or embedded resources.

= Does the Mixed Content Scan modify my database? =

No. Frontend checks and scans do not permanently modify WordPress content.

Permanent changes are made only when you explicitly use Database Cleanup.

= Is Database Cleanup safe with serialized WordPress data? =

Volixta handles eligible serialized WordPress values instead of performing a blind database-wide text replacement.

As with any permanent database operation, keeping a normal website backup before cleanup is recommended.

= What does the Live Fixer do? =

The Live Fixer upgrades eligible insecure resource URLs while the page is rendered.

It does not permanently change the stored database values.

If your rendered frontend does not contain mixed content, there is normally no need to enable it.

= Which Security Headers does Volixta support? =

Volixta supports common browser protections including HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, COOP, COEP, CORP, and additional advanced policies.

= Can Security Headers break parts of a website? =

Strict browser policies can affect external scripts, embedded content, APIs, media, fonts, or other resources.

Volixta therefore provides a Recommended configuration and keeps more technical controls in the Advanced section.

Review custom policies carefully before applying them to a production website.

= Does Volixta work with Nginx? =

Yes.

Nginx does not use `.htaccess`, so Volixta provides ready-to-copy configuration for supported HTTPS redirects and Security Headers instead of attempting to modify `.htaccess`.

= Can I use Volixta locally? =

Yes.

Volixta detects common local environments such as `localhost`, `.local`, and `.test`.

A public Let’s Encrypt certificate is not required locally. If you want trusted local HTTPS, Volixta provides guidance for tools such as mkcert.

= Does Volixta slow down my website? =

Most plugin operations run only in the WordPress admin area.

Certificate issuance, hosting communication, Deep Scan, Database Cleanup, and configuration operations do not run during normal frontend requests.

Only explicitly enabled frontend features, such as the PHP redirect fallback or Live Fixer, add frontend processing.

= Does Volixta collect personal data? =

Volixta does not include visitor analytics or usage tracking.

Some features communicate with external services only when required for an operation you request, such as Let’s Encrypt certificate issuance or a configured hosting-panel connection.

---

== Screenshots ==

1. Guided SSL and security setup with score and safety backup
2. HTTPS setup with certificate check and one-click redirect
3. SSL certificate status, expiry, and certificate tools
4. Let’s Encrypt issuance, installation, and renewal
5. SSL file management and `.htaccess` safety backup
6. Mixed content scan, fixer, and cleanup tools
7. Recommended security headers with one-click protection
8. Advanced security headers configuration

---

== Changelog ==

= 1.2.2 – 2026-08-21 =

* Updated readme.txt

= 1.2.1 – 2026-08-21 =

* Fixed WordPress compatibility metadata for WordPress 7.1

= 1.2.0 – 2026-08-21 =

This is a major update to Volixta SSL & Security Headers.

* Added native Let’s Encrypt / ACME certificate issuance directly from WordPress.
* Added hosting-aware SSL installation for cPanel, Plesk, and DirectAdmin.
* Added automatic renewal for eligible managed certificates.
* Added certificate validation, active-certificate detection, expiration information, and protected SSL file management.
* Added Let’s Encrypt staging support and rate-limit protection with retry-time detection.
* Added manual certificate download and installation support.
* Redesigned the Guided Setup for certificate creation, installation, HTTPS activation, redirects, recovery, and Security Headers.
* Added dedicated localhost support with optional local HTTPS and mkcert guidance.
* Added `.htaccess` Safety Backups and automatic rollback protection.
* Added managed-block validation, concurrent-change detection, symlink refusal, backup verification, and fail-closed `.htaccess` editing.
* Redesigned Mixed Content tools with manual frontend verification, Deep Scan, Live Fixer only when needed, and serialization-safe Database Cleanup.
* Expanded Recommended and Advanced Security Header controls.
* Improved Apache, LiteSpeed, Nginx, reverse-proxy, and hosting compatibility.
* Improved SSL, certificate, server, and hosting diagnostics.
* Improved mobile responsiveness and admin UX across the plugin.
* Improved security checks, escaping, sanitization, SQL handling, and WordPress.org compatibility.
* Fixed multiple edge cases and regression issues discovered during the 1.2.0 development audit.

= 1.1.6 – 2026-08-20 =

* Tested up to WordPress 7.1.

= 1.1.5 – 2026-05-21 =

* Tested up to WordPress 7.0.

= 1.1.4 – 2026-03-11 =

* Updated readme.txt.

= 1.1.3 – 2026-03-09 =

* Removed the Security Hardening module to improve stability and compatibility.

= 1.1.2 – 2025-12-10 =

* Added Security Hardening controls for Secure and HttpOnly cookies.
* Added directory-indexing protection.
* Added user-enumeration protection.
* Improved PHPCS compliance and sanitization.
* Updated the uninstall routine.
* Improved the Security Hardening interface.
* Updated readme.txt.

= 1.1.1 =

* Tested up to WordPress 6.9.

= 1.1.0 =

* Improved SSL detection and code compliance.

= 1.0.10 =

* Updated readme.

= 1.0.0 =

* Initial release.

---

== Upgrade Notice ==

= 1.2.0 =

Version 1.2.0 adds native Let’s Encrypt certificate management, hosting-panel installation, automatic renewal, safer `.htaccess` recovery, improved Mixed Content tools, and a redesigned SSL and Security Headers workflow.

= 1.1.3 =

The Security Hardening module was removed to improve stability and compatibility.

Broader WordPress security and site-management features are planned for the separate **Volixta Toolkit** plugin.

---

== Privacy ==

Volixta SSL & Security Headers does not include analytics, usage tracking, or visitor tracking.

The plugin stores the configuration required for enabled features inside your WordPress installation.

Some actions communicate with external services when you explicitly use features that require them.

Examples include:

- **Let’s Encrypt**: certificate requests and ACME validation.
- **Hosting integrations**: configured cPanel, Plesk, or DirectAdmin connections used for certificate installation.

Only information required to perform the requested operation is sent to those services.

---

== Localization ==

Text domain: `volixta-ssl-security-headers`  
Load path: `/languages`

---

== What’s Next ==

If you like this plugin, check out our other tools:

- [VOLIXTA Booking – The All-in-One WordPress Booking Plugin](https://volixta.com)  
  Manage unlimited staff, services, clients, payments, and locations in one powerful system.  

- [VOLIXTA Toolkit – A collection of practical WordPress tools for configuration, maintenance, security, and site management.](https://volixta.com/volixta-security-suite)