Freexya – Cookie Consent, SMTP, Redirects & Security Toolkit
| 开发者 | nexyadev |
|---|---|
| 更新时间 | 2026年10月23日 22:58 |
| PHP版本: | 8.2 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
One plugin for the jobs every WordPress site needs, instead of five or six:
- E-mails that do not arrive — send through SMTP or an API, keep a log of every message, and read the server's own reason when one fails.
- A cookie banner that really blocks — third-party scripts and embeds wait for consent, with Google Consent Mode v2.
- 404s after a redesign — a log of the broken addresses visitors hit, with their count, redirected in one click.
- Security — a light firewall, HTTP headers, a limit on failed logins, and your plugins checked against known vulnerabilities.
- Dashboard — a readable admin home and a tidied toolbar.
- Shortcuts — duplicate content, reorder it by hand, add entries in one click.
- Roles & capabilities — capabilities sorted under the post type that creates them, and the site seen through a role's eyes without leaving your own account.
- Activity log — who changed what, with the before and the after.
- Cookies — a consent banner, third-party scripts held back until consent, and a scan that finds them.
- SEO — titles and descriptions with a suggestion drawn from the page's text, sitemap, schema, llms.txt.
- Mail — SMTP, an API provider, or a Gmail or Microsoft 365 account connected with OAuth, a delivery log, a test message, an invisible captcha for the site's forms.
- Redirects — exact redirects and a 404 log with the hit count.
- Media — regenerate thumbnails in the background, in batches.
- Security — a light firewall that refuses requests carrying an attack before WordPress runs, security headers, a content policy, a limit on failed logins, and a check of the installed plugins against known vulnerabilities.
- Maintenance — a holding page, database clean-up, a database export, and the previous version of each extension kept before its update.
- Custom fields — field groups with repeaters, flexible content and relations, kept in their own tables, and content types and taxonomies of your own.
- Element — sixteen Elementor widgets for custom fields, NCF’s or ACF’s: repeaters as cards, tabs or tables, galleries and sliders, key figures, teams, timelines, taxonomies, maps.
- Translate — your site in several languages: each page linked to its translations, a translation editor beside the original (blocks, Elementor, ACF and NCF fields), addresses in /en/, a menu per language, a language switcher, hreflang, and every text of the site translated from the admin. A site coming from WPML or Polylang moves over in one click.
安装:
- In Plugins > Add New, search for “freexya”, then install and activate it. You can also upload the folder to
wp-content/plugins/. - Open nexya in the admin menu. On a new install, a first card asks what kind of site this is — a showcase site, a shop or a blog — and switches on the modules that suit it in one click. You can also pick them yourself.
- The hub lists every module with its switch: a module that is off registers nothing on the site. Each module that is on gets its own page in the nexya menu, with its settings.
- The hub's other tabs hold what is shared: Settings (the panel language, and whether your settings are kept if the plugin is deleted), Colours (your brand colours for the cookie banner, forms, messages and holding pages), AI (the connector the AI features use) and Export & import (every setting in one file, to copy a set-up to another site).
屏幕截图:
常见问题:
Does a module I turned off still cost anything?
Almost nothing. The registry declares them all, but only boots the modules that are on: the others register no hooks, load no assets and run no queries.
Where are SMTP passwords stored?
Encrypted with AES-256-GCM in a single option, under a key derived from your WordPress salts. If you rotate those salts the stored secrets can no longer be read, and the panel tells you to enter them again.
And the licence?
The licence is handled by Freemius: the key, its activation and the checkout live in the Freemius screens under the nexya menu. The plugin stores nothing about it.
What happens when I uninstall?
You choose, when you deactivate the plugin (or in Settings › If the plugin is deleted):
- Keep my settings — its scheduled tasks are cleared and the server rules it wrote are taken out; everything else stays, for a reinstall or a move to nexya Pro.
- Erase everything — roles go back to the capabilities they had before the plugin touched them, the plugin's tables and options are dropped, its scheduled tasks are cleared and the private folder is removed. A copy of the settings only (no logs, no page data) stays for 30 days as a WordPress transient, which WordPress deletes on its own once it expires; if the plugin comes back within that time, it offers to import it.
Can I move from WPML or Polylang?
Yes, in Translate › Import, after a backup and ideally on a copy of the site first. Languages, versions of contents, terms, menus, strings and forms come over; the former plugin is only switched off, so switching it back on restores the site. The addresses keep their shape, and those that change are redirected (301) through the Redirects module. Not taken over: prices per currency from WooCommerce Multilingual, a domain or subdomain per language (redirect it at the host), translated media files, and add-ons that need WPML or Polylang themselves. Image alternative texts are translated in Texts › Images.
How do I move to nexya Pro without losing my settings?
Install and activate nexya Pro while this plugin is still in place: both read the same settings, and Pro switches this version off. Then delete this version.
更新日志:
1.5.16
- Forms: three new settings in Look for the buttons: background, border and border on hover.
- Mailya: the button takes its own colours on hover, background, text and border, set beside the normal ones.
- Translate: the SEO of Yoast, Rank Math, SEOPress, All in One SEO and The SEO Framework is now translated with each content, like nexya's own SEO; the canonical address is never copied. SEO written by hand stays as it is, unless “Translate the SEO again too” is ticked when translating everything again.
- Translate: two new tabs in Translation, SEO for the site-wide SEO texts (title templates, home, organisation) and Contents SEO for the title and description of every translated content.
- Custom fields: new Anchor field — a card, a row or a field becomes a link to another element of the same page, with a smooth scroll that stops below a sticky header.
- Custom fields: the link field switches between a page of the site and an address typed by hand.
- Custom fields: on pages edited with the block editor, a rich text field could no longer be typed into once the page had loaded; it now stays editable.
- Admin: cleaner editor toolbars, a dark border on the field being typed in, lighter boxes and a Booking box in the same style as the nexya panel.
- Translate: a repeater, group or flexible content set to Copy keeps the same rows in every language while each sub-field follows its own setting, translated or copied.
- Translate: “Translate everything again” now also rewrites the terms, menus, options pages, strings and shop texts written by hand or imported from WPML or Polylang.
- Translate: a one-word text of an options page or a term, such as a title or a button label, is now translated by the AI like the rest; only a word that looks technical, like an icon name or a code, is left as it is.
- Translate: a product translated in one go is now published with the status chosen in the settings, like any other new translation, instead of staying a draft and leaving the translated shop's categories empty.
- Security: the PHP alert now tells when the server’s PHP is missing the security fixes released on 21 October 2026 (PHP2Shell), with the release to ask the host for (8.2.35, 8.3.36, 8.4.27 or 8.5.12).
- Security: the watch tab lists spam pages found in the database over the last 90 days: pharmacy or gambling spam, injected Japanese text and contents whose author no longer exists.
- The complete history is in changelog.txt, in the plugin folder.