Title: Nivoli Edge: Login Security, WP Audit and Firewall
Author: calimonk
Published: 2026-يىلى 3-سېنتەبىر
Last modified: 2026-يىلى 14-ئۆكتەبىر
---
قىستۇرما ئىزدە
# Nivoli Edge: Login Security, WP Audit and Firewall
يازغۇچى [calimonk](https://profiles.wordpress.org/calimonk/)
[چۈشۈر](https://downloads.wordpress.org/plugin/nivoli-edge.1.93.5.zip)
* [تەپسىلاتلار](https://ug.wordpress.org/plugins/nivoli-edge/#description)
* [باھالاشلار](https://ug.wordpress.org/plugins/nivoli-edge/#reviews)
* [ئورنىتىش](https://ug.wordpress.org/plugins/nivoli-edge/#installation)
* [ئىجادىيەت](https://ug.wordpress.org/plugins/nivoli-edge/#developers)
[قوللاش](https://wordpress.org/support/plugin/nivoli-edge/)
## چۈشەندۈرۈش
**Security one layer above WordPress.** Audit what your site exposes, lock down
logins, and stop attacks at Cloudflare’s edge before they reach PHP. Even if someone
takes over wp-admin, your protection stays on.
#### Login Security
* **Login rate limit:** 10 attempts per 10 minutes per address, answered at the
edge
* **Login country lock:** wp-login.php only for the countries you list
* **wp-admin IP lock:** only your addresses, with a self-lockout guard and email
rescue
* **XML-RPC block:** no guessing hundreds of passwords in one request
* **Hidden usernames:** nothing to find at ?author=N or in the REST API
* **Code at login:** every piece of code that runs when someone logs in, who put
it there, and the warning signs a password thief leaves
#### WordPress Security Audit
* **Security check:** 19 checks of what your site exposes, from inside WordPress
and from its own front door
* **Hidden from itself:** unlisted must-use plugins, administrators the Users screen
does not show, suspicious login code
* **Hardening:** 8 one-click fixes (XML-RPC, usernames, code editors, security
headers, version leaks), also as a must-use plugin nothing in wp-admin can disable
* **Plain answers:** every finding says what it means and how to fix it
#### Edge Firewall
Twelve shields at Cloudflare’s edge: your server never runs PHP to turn an attack
away.
* **Stray-PHP lock:** every .php request except WordPress’s own entry points refused
* **Surface lock:** user lists, readme.html, the installer and debug.log closed
to visitors
* **Traversal guard:** path tricks refused in any encoding
* **Scanner lockout:** five refusals and the address is shut out for ten minutes
* **Flood limits:** comment and search floods stopped per address
* **AI-crawler block** and **security headers** on every response
* **Monitor mode:** see what a shield would block before it blocks anything
* **Cloudflare’s managed WAF rulesets** in front of every site on the edge
#### Protection that stays on after a takeover
A takeover of wp-admin owns every plugin’s settings. These live at the edge.
* **Change lock:** weakening protection waits for a click on a link mailed to you
* **Install lock:** plugin and theme installs, updates and file edits refused until
you open a 15-minute window by email
* **Origin lock:** code changes that skip the edge are refused, so knowing your
server’s address does not help
* **Activity log:** every refused attempt in your inbox and on the Locks page
#### Speed and uptime
* **Edge page cache:** full pages from Cloudflare’s network, with surgical purge
so only the pages a change touches refresh
* **Origin Shield:** your site keeps serving when your server is down
* **Right-sized images:** WebP and AVIF through your own Cloudflare zone or the
Managed Images add-on
* **Analytics without a tracking script:** audience, attacks and top URLs from
the edge
#### Free and with a plan
Free on every install, no account: the security check, Hardening, Code at login,
the image tools on your own Cloudflare zone, and page-cache purging to your own
Fastly, Cloudflare Enterprise or webhook. With a Nivoli plan: the edge firewall,
the three locks, the login rate limit, country lock and wp-admin IP lock, the edge
page cache, Origin Shield and the edge analytics. Every plan starts with a 14-day
free trial.
#### Requirements
* WordPress 6.2+ and PHP 7.4+. The security tools need nothing else.
* Image tools on your own zone: Cloudflare with Image Resizing (**Images Pipeline
check** verifies it). Page cache on your own edge: Fastly, Cloudflare Enterprise
or a webhook.
* Managed: an API key, plus the DNS records the setup pane shows.
### External services
The free tier’s core image rewriting sends **no data to any external service**;
it only rewrites `![]()
` URLs in your site’s HTML so browsers fetch through your
own Cloudflare zone. Beyond that, the plugin contacts external services only for
the specific, opt-in features listed below.
**Nivoli managed edge** (api at html-caching-admin.nivoli.workers.dev, dashboard
at console.nivoli.com): used **only if you enter an API key**. On activation and
on a daily background re-check it sends your API key, this site’s URL, the plugin
version, and the list of broken-image file paths you have marked handled (so the
monthly report can exclude them; these are addresses the CDN already sees in its
own traffic) to validate the key and provision your managed CDN/page-cache tenant;
it then reads back the aggregate usage statistics shown on the dashboard. When content
changes it sends the cache tags of the affected pages, so only those pages are purged.
After each security check it sends the titles of any findings the check marked exposed(
no paths or values), so the monthly report can list them. The page cache, stats
and purge endpoint lives under console.nivoli.com. If you configure monthly reports
or alerts, the recipient email address and optional report branding (a name and
logo URL) are stored with your account. No visitor data is ever sent. Terms: https://
nivoli.com/terms · Privacy: https://nivoli.com/privacy
**Cloudflare** (api.cloudflare.com): used **only if you configure the Cloudflare
Enterprise page-cache backend** with your own API token, to dispatch tag-based cache
purges when your content changes. Terms: https://www.cloudflare.com/terms/ · Privacy:
https://www.cloudflare.com/privacypolicy/
**Fastly** (api.fastly.com): used **only if you configure the Fastly page-cache
backend** with your own API token, to dispatch surrogate-key purges on content change.
Terms: https://www.fastly.com/terms/ · Privacy: https://www.fastly.com/privacy/
**TinyPNG / Tinify** (api.tinify.com): used **only if you add your own Tinify API
key and click «Shrink original»** on an image, to compress that source file. Only
the image you choose is sent. Terms & Privacy: https://tinify.com/terms
## ئېكران كەسمىسى
[⌊Overview: what the edge did for you in the last 30 days. Delivered, Protected
and your plan at work, with 30-day trends, under the five tabs Overview, Security,
Pages, Images and Account.⌉⌊Overview: what the edge did for you in the last 30 days.
Delivered, Protected and your plan at work, with 30-day trends, under the five tabs
Overview, Security, Pages, Images and Account.⌉[
Overview: what the edge did for you in the last 30 days. Delivered, Protected and
your plan at work, with 30-day trends, under the five tabs Overview, Security, Pages,
Images and Account.
[⌊Edge shields: the attack surface strip (XML-RPC, logins, AI crawlers, comment
and search floods) and every shield with its switch, enforced before your server.
Every shield on every managed plan.⌉⌊Edge shields: the attack surface strip (XML-
RPC, logins, AI crawlers, comment and search floods) and every shield with its switch,
enforced before your server. Every shield on every managed plan.⌉[
Edge shields: the attack surface strip (XML-RPC, logins, AI crawlers, comment and
search floods) and every shield with its switch, enforced before your server. Every
shield on every managed plan.
[⌊Locks: change lock, install lock and origin lock, what they refused in the last
14 days with the exact plugin named, and the lock activity log with a filter for
state changes only.⌉⌊Locks: change lock, install lock and origin lock, what they
refused in the last 14 days with the exact plugin named, and the lock activity log
with a filter for state changes only.⌉[
Locks: change lock, install lock and origin lock, what they refused in the last
14 days with the exact plugin named, and the lock activity log with a filter for
state changes only.
[⌊Security check: what this WordPress exposes, measured from inside it and from
one visit to its own front door, with what this plugin can switch off and what the
managed edge already refuses.⌉⌊Security check: what this WordPress exposes, measured
from inside it and from one visit to its own front door, with what this plugin can
switch off and what the managed edge already refuses.⌉[
Security check: what this WordPress exposes, measured from inside it and from one
visit to its own front door, with what this plugin can switch off and what the managed
edge already refuses.
[⌊Probe shields: stray PHP, enumeration, traversal probes and the scanner lockout,
with off, monitor and block for each and the refusal counts.⌉⌊Probe shields: stray
PHP, enumeration, traversal probes and the scanner lockout, with off, monitor and
block for each and the refusal counts.⌉[
Probe shields: stray PHP, enumeration, traversal probes and the scanner lockout,
with off, monitor and block for each and the refusal counts.
[⌊Stats and overview: hour-by-hour traffic, origin offload, hit rates by window,
surgical purges.⌉⌊Stats and overview: hour-by-hour traffic, origin offload, hit
rates by window, surgical purges.⌉[
Stats and overview: hour-by-hour traffic, origin offload, hit rates by window, surgical
purges.
[⌊Heaviest images: the files costing the most bandwidth, one-click Tinify shrinking,
and what the shrinking has saved so far.⌉⌊Heaviest images: the files costing the
most bandwidth, one-click Tinify shrinking, and what the shrinking has saved so
far.⌉[
Heaviest images: the files costing the most bandwidth, one-click Tinify shrinking,
and what the shrinking has saved so far.
[⌊Redirects: legacy URLs answered at the edge, patterns and exact rules with usage,
unused rules folded away.⌉⌊Redirects: legacy URLs answered at the edge, patterns
and exact rules with usage, unused rules folded away.⌉[
Redirects: legacy URLs answered at the edge, patterns and exact rules with usage,
unused rules folded away.
[⌊Recent 404s: paths your server keeps answering with a 404, with bot share and
one-click redirect or block.⌉⌊Recent 404s: paths your server keeps answering with
a 404, with bot share and one-click redirect or block.⌉[
Recent 404s: paths your server keeps answering with a 404, with bot share and one-
click redirect or block.
[⌊Your audience: humans versus bots, served-from-cache speed, referrers, devices
and countries, no tracking script.⌉⌊Your audience: humans versus bots, served-from-
cache speed, referrers, devices and countries, no tracking script.⌉[
Your audience: humans versus bots, served-from-cache speed, referrers, devices and
countries, no tracking script.
[⌊Static assets: edge hit rate for stylesheets, scripts and fonts, versioned addresses,
bandwidth offloaded.⌉⌊Static assets: edge hit rate for stylesheets, scripts and
fonts, versioned addresses, bandwidth offloaded.⌉[
Static assets: edge hit rate for stylesheets, scripts and fonts, versioned addresses,
bandwidth offloaded.
[⌊Query params: which parameters split the cache, which are guarded, with one-click
collapse.⌉⌊Query params: which parameters split the cache, which are guarded, with
one-click collapse.⌉[
Query params: which parameters split the cache, which are guarded, with one-click
collapse.
[⌊Hardening: eight things WordPress exposes by default, one click each, with the
ones the edge already refuses grouped and saying so.⌉⌊Hardening: eight things WordPress
exposes by default, one click each, with the ones the edge already refuses grouped
and saying so.⌉[
Hardening: eight things WordPress exposes by default, one click each, with the ones
the edge already refuses grouped and saying so.
[⌊Broken images: failed image requests from the last 7 days, files gone from disk
with a placeholder ready, and the momentary failures that handled themselves.⌉⌊Broken
images: failed image requests from the last 7 days, files gone from disk with a
placeholder ready, and the momentary failures that handled themselves.⌉[
Broken images: failed image requests from the last 7 days, files gone from disk
with a placeholder ready, and the momentary failures that handled themselves.
## ئورنىتىش
1. Install and activate the plugin. Open **Nivoli Edge Security Security check**
and run it: no setup, no account. **Code at login** and **Hardening** sit beside
it.
2. Free images on your own Cloudflare zone: open **Images Hosts & routing**, confirm
the auto-detected image host and path prefix, then switch Enabled on under **Images
Optimization**. Add rules under **Images Rules**, or let **Size mapping** create
them from your theme’s sizes in one click.
3. Free page caching on your own edge: open **Pages Cache backend** and pick Fastly,
Cloudflare Enterprise or a webhook.
4. Managed edge: paste your API key on the **Account** tab. The edge provisions itself
and the setup overview walks the rest: the DNS records, the shields, the locks,
the report.
## FAQ
### Is the free version limited?
No trial, no time limit and no feature walls. Everything that runs on your own server
is free and stays free: the security check, Code at login, Hardening, the image
tools on your own Cloudflare zone, page-cache purging to your own edge, the audits
and WP-CLI. The managed edge is a separate service for what a plugin cannot do from
inside the site it protects.
### Do I need an account?
Not for anything free. The security tools work on any WordPress site as soon as
the plugin is active. An account and API key only come in when you connect the managed
edge.
### Does this replace Wordfence or Sucuri?
It sits above them. Those plugins inspect requests inside WordPress, after PHP has
started; Nivoli Edge refuses hostile traffic at Cloudflare’s edge before your server
sees it, and its settings cannot be switched off from inside a compromised WordPress.
Run both if you like; they do not overlap.
### What do the twelve shields stop?
Login, comment and search floods, XML-RPC abuse, logins from countries you do not
serve, wp-admin from addresses that are not yours, AI crawlers, direct requests
to PHP files that are not WordPress entry points, the probes that map a site (user
lists, readme, license file, installer, debug.log), path traversal attempts in any
encoding, addresses that keep probing after five refusals, and missing security
headers. All twelve come with every managed plan.
### Does this require Cloudflare Pro?
Only for the free image rewriting on your own zone: Cloudflare Image Resizing is
bundled with Pro plans or available pay-as-you-go. The managed edge needs no Cloudflare
account at all.
### Will this break my theme?
No. The plugin only modifies URLs at the filter boundary; the HTML structure your
theme outputs is unchanged. Use the `no-cf` CSS class on any element to opt out.
### How is this different from Smush / ShortPixel / Optimole?
Those plugins compress and re-host images on their own CDN. Nivoli Edge transforms
on the fly from your origin: no asset duplication, no migration step, no storage
bill.
### What’s the difference between Free and Managed?
Everything the plugin does on your own server is free and fully functional: the
security check, Code at login, Hardening, image rewriting, page-cache purging, audits,
prewarming and alerts. Nothing phones home. An API key connects the plugin to the
Nivoli managed edge: we run the Cloudflare zone and page cache for you (no Cloudflare
setup at all) and the service adds what a plugin alone can’t, such as edge-side
usage statistics, per-URL traffic insights, edge URL rules and security shields,
and multi-site fleet management; custom image hostnames and watermarking come with
the Managed Images add-on.
### What if I lose access to my license email?
Confirmation and unlock links go to the email address on your Nivoli license and
nowhere else; that is what makes the locks hold against a takeover. Support can
move the license to a new address after verifying you own it. Until then the locks
stay as they are and the site keeps running; only changes that weaken protection
wait.
### Does the install lock break automatic updates?
No. Automatic background updates run from wp-cron on your server and WP-CLI runs
on the box; neither passes through the edge, so neither is affected. Only installs,
uploads, updates and deletes started from wp-admin are refused, and you open a 15-
minute window by email when you want to do one yourself.
### What if my site gets hacked anyway?
The locks stop the intruder from switching the shields off, installing anything
through WordPress, or redirecting the confirmation address, and every attempt lands
in your inbox and on the Locks page with its time and address. What no edge control
can do is undo code already running on your server: cleaning the box is still yours(
scan, restore, rotate). The locks make sure the compromise stays where it landed.
### Does the page caching conflict with my security plugin (Wordfence, Sucuri)?
No. Different layers: security plugins inspect requests inside WordPress/PHP; Nivoli
Edge’s twelve shields run at Cloudflare’s edge, before the request reaches your
server. It sheds junk traffic so your origin and your security plugin only see real
visitors. They complement each other.
### Does the plugin add a link to my site?
Not unless you ask it to. Account, Footer credit has a switch, off by default, that
prints one small «Protected by Nivoli Edge» line in your footer with a nofollow
link. Nothing appears on your public site until you tick it, and unticking it removes
the line again.
### Do I need to change my nginx / web-server config?
Only if your origin runs its own micro-cache (nginx fastcgi/proxy cache, Varnish)
and you use the manual purge trigger; the Cache protection pane shows the exact
one-line snippet. A standard PHP-FPM origin needs no server changes at all.
## باھالاشلار
### [Highly recommended](https://wordpress.org/support/topic/highly-recommended-803/)
[intinig](https://profiles.wordpress.org/intinig/) 2026-يىلى 14-ئۆكتەبىر
I've been running Nivoli Edge on my site for a few weeks now, on a managed plan,
and it's earned its keep.The security check was the first surprise: 19 concrete
findings about what my site exposed, each explained in plain language with how to
fix it. The one-click hardening took care of most of them in minutes: XML-RPC, version
leaks, the lot.What sold me on the managed edge is that the protection lives at
Cloudflare's edge, not inside WordPress. Login attempts get rate-limited before
PHP even runs, the shields refuse stray-PHP probes and scanners, and monitor mode
let me see exactly what would be blocked before I switched anything to block. The
change lock and install lock are the kind of thing you don't appreciate until you
think about what a wp-admin takeover means for every other security plugin. Bonus:
the edge page cache made the site noticeably faster, and I get real analytics without
injecting a tracking script.Setup was straightforward, the free tools work with
no account, and the managed side provisioned itself once I added the API key. Highly
recommended.
[ 1 باھالاشنىڭ ھەممىنى ئوقۇش ](https://wordpress.org/support/plugin/nivoli-edge/reviews/)
## تۆھپىكار ۋە ئىجادكار
«Nivoli Edge: Login Security, WP Audit and Firewall» كودى ئوچۇق يۇمشاق دېتال. تۆۋەندىكى
كىشىلەر بۇ قىستۇرمىغا تۆھپە قوشقان.
تۆھپىكار
* [ calimonk ](https://profiles.wordpress.org/calimonk/)
[«Nivoli Edge: Login Security, WP Audit and Firewall» نى تىلىڭىزغا تەرجىمە قىلىڭ](https://translate.wordpress.org/projects/wp-plugins/nivoli-edge)
### ئىجادىيەتكە قىزىقامسىز؟
[كودقا كۆز يۈگۈرتۈپ](https://plugins.trac.wordpress.org/browser/nivoli-edge/)، [SVN خەزىنە](https://plugins.svn.wordpress.org/nivoli-edge/)
تەكشۈرۈپ ياكى [RSS](https://plugins.trac.wordpress.org/log/nivoli-edge/?limit=100&mode=stop_on_copy&format=rss)
ئارقىلىق [ئىجادىيەت خاتىرىسى](https://plugins.trac.wordpress.org/log/nivoli-edge/)
گە مۇشتەرى بولغىلى بولىدۇ.
## ئۆزگىرىش خاتىرىسى
Recent releases are listed below. The full history for every version is in CHANGELOG.
md, which ships with the plugin, and on the GitHub releases page.
#### 1.93.5
WordPress.org listing: every feature name in bold, cleaner lists, and one paragraph
at the end on what is free and what comes with a plan. No change to the plugin itself.
#### 1.93.4
Clearer opening line on the WordPress.org listing. No change to the plugin itself.
#### 1.93.3
A shorter WordPress.org listing, organised by what the plugin does: Login Security,
WordPress Security Audit, Edge Firewall, the locks, speed and uptime. Managed features
are tagged. No change to the plugin itself.
#### 1.93.2
The plugin’s name on WordPress.org and in your Plugins list now says what it does:
Nivoli Edge: Login Security, WP Audit and Firewall. The Nivoli Edge menu in wp-admin
is unchanged.
#### 1.93.1
Wording: eleven messages in the plugin still used long dashes; they now read as
plain sentences, and the pipeline probe message points to Images, Pipeline check.
This also prepares the plugin’s text for translation into Dutch, German, French
and Spanish.
#### 1.93.0
A small note on the plugin’s own pages asks for a review on WordPress.org once the
plugin has done something for your site (a security check run and a hardening switch
on) or after two weeks. It says a review needs a free WordPress.org account. «Maybe
later» asks again in 30 days; «Leave a review» and «Don’t ask again» end it. It
never appears on other admin screens.
#### 1.92.1
The WordPress.org listing now leads with what the free plugin does on its own: the
security check, Code at login and one-click Hardening, then the free image and page-
cache tools, with the managed edge as what to add when you want more. New answers
for «Is the free version limited?» and «Do I need an account?». No change to the
plugin itself.
#### 1.92.0
The Nivoli Edge item in the WordPress sidebar now carries a red count when something
waits for you, like Comments or Plugins: exposed security-check findings, a change
waiting for your emailed click, shields still monitoring, broken, heavy or fake
images, a license that needs attention. Each tab entry under it shows its own count,
the same numbers as the dots on the tabs. The first entry is now called Overview,
like the tab.
#### 1.91.0
XML-RPC has a switch again on the Edge shields pane, and this one the edge obeys.
The block is on by default; «Allow XML-RPC» opens /xmlrpc.php for sites that publish
through the Jetpack app or the WordPress mobile app, or want pingbacks, and «Block
XML-RPC» closes it again. With the change lock on, allowing waits for the emailed
confirmation. The security check’s «Switch on at the edge» button for XML-RPC is
back.
#### 1.90.2
XML-RPC on the Edge shields pane now reports what the edge does. The edge refuses/
xmlrpc.php on every enabled site with a 404, cached for five minutes, before any
URL rule runs, so a site without the old 410 rule no longer reads «not blocked».
The «Block XML-RPC (410)» switch is gone because it changed nothing; a 410 rule
already in your list stays. The security check no longer offers «Switch on at the
edge» for XML-RPC.
#### 1.90.1
Accuracy pass over the listing and the plugin’s own wording. The listing names all
twelve shields, says how long Origin Shield serves on each plan (up to a day on
Shield, 7 days on Shield Plus and Agency), uses the current tab names in the install
steps, and its External services section now also covers the cache tags sent on
purge and the finding titles sent after a security check. The plan card on free
installs no longer says Shield Plus adds shields: every plan has every shield and
lock. XML-RPC is described as what the edge really answers, a 404 cached for five
minutes. WP-CLI help shows `wp nivoli-edge` examples.
#### 1.90.0
New under Account, Your site: Footer credit, an optional small «Protected by Nivoli
Edge» line at the bottom of your public pages. It is off unless you switch it on,
the link is always nofollow, and it never shows in wp-admin, feeds or API responses.
Themes can move or restyle it with two filters.
#### 1.89.5
Code at login: room between its blocks, and the expected list shows every item,
one line each under its source with a count, instead of merging them into one line
per source.
#### 1.89.4
Fixes Code at login drawing twice and the Edge shields pane appearing underneath
it.
#### 1.89.3
Code at login: more room between cards, the level shown as a coloured pill, and
where the code lives set out one fact per line: from, file with its line range,
the shared copy it links to, last changed.
## Meta
* Version **1.93.5**
* ئاخىرقى يېڭىلانغان ۋاقىت **6 سائەت بۇرۇن**
* ئاكتىپ ئورنىتىش سانى **10 دىن ئاز**
* WordPress نەشرى ** 6.2 ياكى يۇقىرى **
* **7.1.3** دا سىنالغان
* PHP نەشرى ** 7.4 ياكى يۇقىرى **
* تىل
* [English (US)](https://wordpress.org/plugins/nivoli-edge/)
* بەلگە
* [cache](https://ug.wordpress.org/plugins/tags/cache/)[cloudflare](https://ug.wordpress.org/plugins/tags/cloudflare/)
[firewall](https://ug.wordpress.org/plugins/tags/firewall/)[hardening](https://ug.wordpress.org/plugins/tags/hardening/)
[security](https://ug.wordpress.org/plugins/tags/security/)
* [ئالىي كۆرۈنۈش](https://ug.wordpress.org/plugins/nivoli-edge/advanced/)
## دەرىجە
5/5 يۇلتۇز
* [ 1 5-يۇلتۇز باھالاش ](https://wordpress.org/support/plugin/nivoli-edge/reviews/?filter=5)
* [ 0 4-يۇلتۇز باھالاش ](https://wordpress.org/support/plugin/nivoli-edge/reviews/?filter=4)
* [ 0 3-يۇلتۇز باھالاش ](https://wordpress.org/support/plugin/nivoli-edge/reviews/?filter=3)
* [ 0 2-يۇلتۇز باھالاش ](https://wordpress.org/support/plugin/nivoli-edge/reviews/?filter=2)
* [ 0 1-يۇلتۇز باھالاش ](https://wordpress.org/support/plugin/nivoli-edge/reviews/?filter=1)
[Your review](https://wordpress.org/support/plugin/nivoli-edge/reviews/#new-post)
[بارلىق ئىنكاسنى كۆرسەت](https://wordpress.org/support/plugin/nivoli-edge/reviews/)
## تۆھپىكار
* [ calimonk ](https://profiles.wordpress.org/calimonk/)
## قوللاش
چۈشەندۈرۈشىڭىز بارمۇ؟ ياردەم لازىممۇ؟
[قوللاش مۇنبىرىنى كۆرسەت](https://wordpress.org/support/plugin/nivoli-edge/)