Title: Yedekalma — Yedek Alma, Geri Yükleme ve Taşıma
Author: kamkactemha
Published: <strong>जुलाई 15, 2026</strong>
Last modified: अगस्त 8, 2026

---

Search plugins

![](https://ps.w.org/yedekalma/assets/banner-772x250.jpg?rev=3617989)

![](https://ps.w.org/yedekalma/assets/icon.svg?rev=3617981)

# Yedekalma — Yedek Alma, Geri Yükleme ve Taşıma

 [kamkactemha](https://profiles.wordpress.org/kamkactemha/) लिखले बारे

[डाउनलोड](https://downloads.wordpress.org/plugin/yedekalma.1.51.1.zip)

 * [Details](https://bho.wordpress.org/plugins/yedekalma/#description)
 * [समीक्षा](https://bho.wordpress.org/plugins/yedekalma/#reviews)
 *  [Installation](https://bho.wordpress.org/plugins/yedekalma/#installation)
 * [Development](https://bho.wordpress.org/plugins/yedekalma/#developers)

 [मदद](https://wordpress.org/support/plugin/yedekalma/)

## बिबरन

Yedekalma, **WordPress yedekleme** işini tek ekranda toplayan **ücretsiz bir yedek
alma eklentisidir**. Tek tıkla sitenizin **tam yedeğini** alır — dosyalar _ve_ veritabanı—
ve aynı ekrandan **geri yükler**. Ayrıca **WordPress site taşıma** (yeni sunucu 
veya yeni alan adı) yapar ve **virüs / zararlı yazılım taraması** ile bulaşmış dosyaları
temizler. Yedekleme, geri yükleme, taşıma ve güvenlik tek eklentide toplandığı için
her iş için ayrı bir araca ihtiyacınız olmaz.

Her şey kendi sunucunuzda çalışır. Hesap, kayıt veya API anahtarı gerekmez: kurun,
etkinleştirin, **Yedek Al**‘a basın. **Yedek dosyalarınız kendi hostingunuzda kalır**
ve dilediğiniz zaman ZIP olarak indirebilirsiniz.

#### Neler yapar?

 * **Site yedekleme** — tema, eklenti ve yüklemeler dahil tüm dosyalar.
 * **Veritabanı yedekleme** — gzip sıkıştırmalı MySQL dökümü (`.sql.gz`), büyük 
   siteler için uygun.
 * **Paylaşımlı hostingde çalışır** — `exec()` kapalı ve PHP limitleri dar olsa 
   bile parçalı (zaman dilimli) çalışıp yedeği tamamlar.
 * **Artımlı yedekleme** — dosyaların gerçek değişiklik zamanına bakar, değişen 
   dosya asla atlanmaz.
 * **Tek tıkla geri yükleme** — veritabanı, eklentiler, temalar ve yüklemeler; ya
   da yalnızca seçtiğiniz parça.
 * **Elinizdeki arşivden geri yükleme** — `.zip`, `.sql` veya `.sql.gz` dosyasını
   sürükleyip bırakın.
 * **Site taşıma / alan adı değiştirme** — geri yükleme sırasında site adresi veritabanında
   otomatik güncellenir.
 * **Virüs tarama** — WordPress çekirdeği, eklentiler ve aktif temada kod enjeksiyonu,
   web shell ve arka kapı arar; bulunanları toplu silebilirsiniz.
 * **Kendi bulutunuza gönderim (isteğe bağlı)** — Google Drive, Dropbox, OneDrive,
   Amazon S3 / S3 uyumlu, FTP / SFTP.
 * **Zamanlanmış otomatik yedekleme (isteğe bağlı)** — günlük, haftalık, saatlik
   veya birkaç dakikada bir; saklama kuralı ile.
 * **AES-256 uçtan uca şifreleme (BYOK)** — parola sitenizden çıkmaz.

Ücretsiz bir **yedekleme eklentisi** arıyorsanız: geri yükleme, taşıma ve virüs 
taraması dahil hepsi ücretsizdir; hiçbiri “premium” kilidinin arkasında değildir.

#### In English

Yedekalma is a free **WordPress backup plugin** that takes a one-click **backup**
of your entire site — files _and_ database — and **restores** it again from the 
same screen. It also **migrates** your WordPress site to a new host or domain and**
scans** it for **malware**. One backup plugin covers backup, restore, migration 
and security, so you do not need a separate tool for each job.

Everything runs on your own server. No account, no sign-up and no API key: install,
activate, click **Take Backup**. Your backup archives stay on your hosting, and 
you can download them as a ZIP at any time.

Looking for a **free backup plugin** that also does migration and malware scanning
without a paywall? Yedekalma gives you a full **WordPress backup**, a **database
backup**, one-click **restore**, site **migration** and a **malware scanner** in
a single plugin — no premium unlock required for any of it.

#### Backup

 * **Full backup** — every file (themes, plugins, uploads) plus the complete database.
 * **Database backup** — MySQL dump only, gzip compressed (`.sql.gz`) for large 
   sites.
 * **Files backup** — site files only, without the database.
 * **Works on shared hosting** — chunked, time-sliced backup that finishes even 
   when `exec()` is disabled and PHP limits are strict.
 * **Incremental backup** — compares real file modification times, so a changed 
   file is never skipped.
 * **Safe storage** — local backups live in a hardened, non-browsable folder with
   unguessable file names.

#### Restore

 * **One-click restore** of the database, plugins, themes and uploads straight from
   your dashboard.
 * **Restore only what you need** — pick just the database, just uploads, just plugins
   or the whole site.
 * **Restore from an archive you already have** — drag & drop a `.zip`, `.sql` or`.
   sql.gz` file and restore from it.
 * **Integrity checked** — a truncated or corrupt archive is refused instead of 
   half-applied, so a bad file can never damage a working site.
 * **SHA-256 verification** of every archive before a restore begins.

#### Migration

 * **Move your site to a new host** — download the backup, install Yedekalma on 
   the target server and restore.
 * **Change domain safely** — site URL and home URL are rewritten in the database
   automatically during the restore.
 * **New database server** — `wp-config.php` credentials can be updated as part 
   of a restore.
 * **Clone your website** to a fresh install for disaster recovery or a redesign.

#### Malware scanner

 * **Security scan** of PHP, JS and configuration files across WordPress core, your
   plugins and the active theme.
 * Detects **code injections, web shells and backdoors** using malicious-pattern
   matching.
 * **Persistent results** — the scan report survives page reloads, so you can review
   it whenever you like.
 * **Bulk clean** — select detected files and delete them in one click.
 * **Core protection** — WordPress core files are shielded from accidental deletion
   while planted files can still be removed.

#### Optional cloud service — backup to your own cloud storage

Local backup, restore, migration and the malware scanner are complete on their own
and never contact an external server. If you also want **off-site backup** copies,
you can connect the optional Yedekalma cloud service (see _External services_ below)
to:

 * **Backup to Google Drive** — stream backups straight to your own Google Drive.
 * **Backup to Dropbox and OneDrive** — send archives to your own Dropbox or Microsoft
   OneDrive account.
 * **Backup to Amazon S3** and S3-compatible storage — Backblaze B2, Wasabi, Cloudflare
   R2 and MinIO.
 * **Backup to FTP / SFTP** — upload to any FTP or SFTP server you control.
 * Run **scheduled automatic backups** — daily, weekly, hourly or as often as every
   few minutes for busy sites — with retention rules.
 * **Table-level incremental database backup** — only the database tables that actually
   changed are exported, so even very frequent backups stay small and fast; unchanged
   runs are skipped automatically.
 * Encrypt archives with **client-side AES-256 (BYOK)** before they leave your server—
   the passphrase never leaves your site.

#### Languages

Yedekalma ships with English, Turkish (Türkçe), German, Russian and Arabic translations.

### External services

This plugin can optionally connect to the Yedekalma cloud service (an external SaaS)
to perform off-site backup and restore operations, package backups for delivery 
to your own cloud storage, check subscription state, and monitor backup quota. This
connection only happens if you choose to use the cloud service (by entering an API
token, by clicking the optional “Connect with Google” button, by clicking the optional“
register this site” button, or by sending a support request from the Support screen—
all described below); the plugin’s local backup, restore, migration and malware-
scanner features work with no external connection at all.

 * **Service URL:** https://yedekalma.com
 * **Terms of Service:** https://yedekalma.com/legal
 * **Privacy Policy:** https://yedekalma.com/legal#privacy
 * **Connect with Google (opt-in):** The dashboard shows an optional “Connect with
   Google” button. It does nothing unless you click it. If you click it, your browser
   is sent to https://yedekalma.com where you sign in with Google; Yedekalma then
   creates or finds your account from your Google e-mail address and links this 
   site (identified by its Site URL) to it. Only your e-mail address and the Site
   URL are used for this; no Google Drive or other Google data permission is requested,
   and no site content is sent. A one-time connection token is returned to your 
   site and stored encrypted locally.
 * **Optional site registration (opt-in):** The dashboard also shows an optional“
   register this site with Yedekalma” button. It does nothing unless you click it.
   If you click it, the plugin sends only your Site URL and technical version info(
   plugin, WordPress, PHP version and locale) to https://yedekalma.com so the site
   can be listed in your Yedekalma panel; no site content or personal data is sent.
   If you also enter a notification e-mail, that address and your marketing-consent
   choice are sent as well. You can ignore the button entirely and every built-in
   feature still works.
 * **Support form (opt-in, no account needed):** The plugin has a **Yedekalma  Support**
   screen. It sends nothing until you fill it in and press “Send”. When you do, 
   the message you typed, the reply e-mail address and name you entered, the chosen
   category and your Site URL are sent to https://yedekalma.com so the support team
   can answer you by e-mail. A separate checkbox — shown ticked, and you can untick
   it — additionally sends technical details of this installation: plugin, WordPress,
   PHP and MySQL versions, web server, site language, multisite flag, active theme
   name, the _number_ of active plugins, PHP limits (`memory_limit`, `max_execution_time`,`
   upload_max_filesize`), whether ZipArchive and `exec()` are available, free disk
   space, whether the backup folder is writable, whether the site is connected to
   the cloud service, and the date and count of your local backups. The full list
   is shown on screen before you send it. No site content, database content, passwords,
   plugin list or user data is sent, and no Yedekalma account is required to use
   this form.
 * **Data Transmission:** When connected (or after opt-in registration), the plugin
   sends requests to the Yedekalma API containing your Site URL, active plugin features,
   backup metadata (such as file lists, sizes, and checksums), and your API token(
   or anonymous install id) to perform secure backup and restore tasks.

## Screenshots

[⌊Dashboard — one-click full, files-only or database backup; runs on your own server,
no account needed.⌉⌊Dashboard — one-click full, files-only or database backup; runs
on your own server, no account needed.⌉[

Dashboard — one-click full, files-only or database backup; runs on your own server,
no account needed.

[⌊All backups — one-click restore or download, each with size and SHA-256 checksum.⌉⌊
All backups — one-click restore or download, each with size and SHA-256 checksum
.⌉[

All backups — one-click restore or download, each with size and SHA-256 checksum.

[⌊Built-in malware scanner — scan WordPress core, plugins and the active theme for
injected code, web shells and backdoors.⌉⌊Built-in malware scanner — scan WordPress
core, plugins and the active theme for injected code, web shells and backdoors.⌉[

Built-in malware scanner — scan WordPress core, plugins and the active theme for
injected code, web shells and backdoors.

[⌊Settings — interface language and safe uninstall data handling.⌉⌊Settings — interface
language and safe uninstall data handling.⌉[

Settings — interface language and safe uninstall data handling.

[⌊Optional Yedekalma Pro — connect to schedule off-site backups straight to your
own cloud (Google Drive, S3, FTP) with client-side AES-256.⌉⌊Optional Yedekalma 
Pro — connect to schedule off-site backups straight to your own cloud (Google Drive,
S3, FTP) with client-side AES-256.⌉[

Optional Yedekalma Pro — connect to schedule off-site backups straight to your own
cloud (Google Drive, S3, FTP) with client-side AES-256.

## Installation

 1. In your WordPress admin, go to **Plugins  Add New**.
 2. Search for **Yedekalma**.
 3. Click **Install Now**, then **Activate**.
 4. Open **Yedekalma** in the admin sidebar.
 5. Click **Start without an account** and take your first backup.

Manual installation: upload the `yedekalma` folder to `/wp-content/plugins/` and
activate it from the Plugins screen.

## FAQ

### WordPress sitemin yedeğini nasıl alırım?

**Yedekalma  Kontrol Paneli**‘ni açın ve **Yedek Al**‘a basın. **Tam Yedek** (dosya
+ veritabanı), **Sadece Dosya** veya **Sadece Veritabanı** seçebilirsiniz. Yedekleme
kendi sunucunuzda parça parça çalışır; bittiğinde arşivi ZIP olarak indirebilirsiniz.

### Veritabanı yedeği nasıl alınır?

**Yedek Al  Sadece Veritabanı** deyin. Sıkıştırılmış bir MySQL dökümü (`.sql.gz`)
elde edersiniz; indirebilir veya daha sonra geri yükleyebilirsiniz.

### Yedek alma eklentisi ücretsiz mi?

Evet. Yedekleme, geri yükleme, taşıma ve virüs taraması hesap açmadan ve ücret ödemeden
tam olarak çalışır. İsteğe bağlı Yedekalma bulut hizmeti site dışı (off-site) depolama
ekler ve ücretsiz bir başlangıç paketi vardır.

### WordPress site taşıma nasıl yapılır?

Evet. Yedeği indirin, yeni sunucuda Yedekalma’yı kurun ve arşivden geri yükleyin.
Site adresi ve ana sayfa adresi veritabanında otomatik olarak yeni alan adına göre
güncellenir.

### Yedekler nerede saklanıyor?

Varsayılan olarak kendi hostingunuzda, dışarıdan listelenemeyen korumalı bir klasörde
ve tahmin edilemez dosya adlarıyla. İsterseniz isteğe bağlı bulut hizmetiyle kendi
Google Drive, Dropbox, OneDrive, S3 veya FTP alanınıza gönderebilirsiniz — yedeğin
içeriği Yedekalma sunucularında tutulmaz.

### Paylaşımlı hostingde çalışır mı?

Evet. Yedekleme zaman dilimli parçalar halinde ilerler; `exec()` kapalı olsa ve 
PHP zaman/bellek limitleri dar olsa bile tamamlanır. Sunucu yoğunluk nedeniyle isteği
reddederse eklenti bekleyip kaldığı yerden devam eder.

### WordPress virüs temizleme yapar mı?

Evet. **Yedekalma  Zararlı Yazılım Taraması** ekranından tarama başlatın: WordPress
çekirdeği, eklentiler ve aktif tema PHP/JS ve yapılandırma dosyaları için kod enjeksiyonu,
web shell ve arka kapı kalıplarına karşı taranır. Bulunan dosyaları tek tıkla toplu
silebilirsiniz; WordPress çekirdek dosyaları yanlışlıkla silinmeye karşı korunur.
Virüs temizleme ücretsizdir, hesap açmanız gerekmez.

### Otomatik (zamanlanmış) yedekleme var mı?

Evet, isteğe bağlı bulut hizmetiyle. Günlük, haftalık, saatlik ya da yoğun siteler
için birkaç dakikada bir otomatik yedekleme kurabilir, her biri için saklama kuralı
tanımlayabilirsiniz. Tek tıkla manuel yedek her zaman ücretsizdir ve zamanlama gerektirmez.

### Büyük siteleri (5 GB, 10 GB) yedekleyebilir mi?

Evet. Yedekleme küçük zaman dilimlerine bölünerek ilerler ve veritabanı doğrudan
gzip sıkıştırmalı döküme akıtılır; böylece PHP süre ve bellek limitlerine takılmadan
tamamlanır. Çok büyük siteler için isteğe bağlı bulut hizmetiyle arşivi hostinginizi
doldurmadan doğrudan kendi Google Drive, S3 veya FTP alanınıza gönderebilirsiniz.

### WooCommerce mağazamı yedekler mi?

Evet. Tam yedek tüm WordPress veritabanını içerir — WooCommerce siparişleri, ürünler,
müşteriler ve ayarlar dosyalarla birlikte kaydedilir. Yoğun mağazalarda isteğe bağlı
bulut hizmetiyle sık artımlı yedekleme kurup iki yedek arasındaki yeni siparişleri
de koruyabilirsiniz.

### Nasıl destek alabilirim? Üye olmam gerekiyor mu?

Hayır, üyelik gerekmez. WordPress yönetim panelinizde **Yedekalma  Destek** ekranını
açın, sorununuzu yazın ve gönderin. Site adresiniz otomatik olarak eklenir; isterseniz
PHP/WordPress sürümü ve sunucu limitleri gibi teknik bilgileri de tek tıkla iletebilirsiniz(
ne gönderileceğini göndermeden önce ekranda görürsünüz). Yanıt, yazdığınız e-posta
adresine gelir — yedekalma.com hesabınız olmasa bile.

### Yedeklerimi Google Drive’a gönderebilir miyim?

Evet, isteğe bağlı Yedekalma bulut hizmetiyle. Arşiv sunucunuzdan doğrudan **kendi**
Google Drive, Dropbox, OneDrive, Amazon S3 / S3 uyumlu veya FTP / SFTP alanınıza
aktarılır; Yedekalma bir kopyasını saklamaz.

### Is this backup plugin free?

Yes. Backup, restore, migration and the malware scanner are fully functional with
no account and no payment. The optional Yedekalma cloud service adds off-site storage
and has a free tier.

### Is this a good free backup plugin for WordPress?

Yedekalma is a free WordPress backup plugin that bundles full-site backup, database
backup, one-click restore, site migration and a malware scanner — features that 
many plugins split between free and premium tiers. Everything runs on your own server
and needs no account.

### How do I back up my WordPress site?

Open **Yedekalma  Dashboard** and click **Take Backup**. Choose **Full** (files 
+ database), **Files Only** or **Database Only**. The backup runs in time-sliced
chunks on your own server and you can download the archive as a ZIP when it finishes.

### How do I back up my WordPress database?

Open **Yedekalma  Dashboard**, click **Take Backup** and choose **Database Only**.
You get a compressed MySQL dump (`.sql.gz`) that you can download or restore later.

### Can I back up a WooCommerce store?

Yes. A full backup includes your entire WordPress database — WooCommerce orders,
products, customers and settings — together with your files, so your whole store
is captured. For very busy stores you can schedule frequent incremental backups 
through the optional cloud service so new orders are protected between runs.

### Can it back up large sites (5 GB, 10 GB or more)?

Yes. Backups run in small time-sliced chunks and the database is streamed to a gzip-
compressed dump, so large sites finish without hitting PHP time or memory limits.
For very large sites, connecting the optional cloud service lets archives stream
straight to your own Google Drive, S3 or FTP storage instead of filling your hosting
disk.

### Does it work on shared hosting, cPanel, Plesk or DirectAdmin?

Yes. Yedekalma is a pure-PHP plugin with no server dependencies, so it works on 
any standard WordPress host — shared hosting, cPanel, Plesk, DirectAdmin or a managed
platform. It does not need `exec()`, shell access or SSH.

### Does it work on LiteSpeed, Nginx and Apache?

Yes. The plugin runs inside WordPress itself and does not depend on the web server,
so it works the same on LiteSpeed, Nginx, Apache or any other server that runs PHP.

### Can I use it to migrate my site to a new host or domain?

Yes. Take a full backup, download the ZIP, install Yedekalma on the target site 
and restore the archive there. The site URL and home URL in the database are updated
for the new domain automatically.

### Can I clone my website for disaster recovery?

Yes. Take a full backup and restore it onto a completely separate install; the site
URL is rewritten for the new domain automatically. Your original site is never modified.

### Where are my backups stored?

In `wp-content/uploads/yedekalma-backups/` on your own server. The folder is protected
from directory browsing and the archive names include a random token, so nobody 
can guess the URL. If you connect optional cloud storage, backups go to your own
Google Drive, Dropbox, OneDrive, S3 or FTP account instead.

### Can I back up to Google Drive?

Yes, through the optional Yedekalma cloud service. Backups stream directly from 
your server to **your own** Google Drive; Yedekalma never keeps a copy.

### Can I back up to Dropbox or OneDrive?

Yes. With the optional cloud service you can send scheduled backups to your own 
Dropbox or Microsoft OneDrive account.

### Does it support Amazon S3, Backblaze B2 or Wasabi?

Yes. The optional cloud service supports Amazon S3 and any S3-compatible storage—
Backblaze B2, Wasabi, Cloudflare R2 and MinIO. Uploads use a client-side signed (
SigV4) request and your secret key is AES-256 encrypted on your own site, never 
sent to Yedekalma.

### Can I back up to FTP or SFTP?

Yes. The optional cloud service can upload backups to any FTP or SFTP server you
control. The credentials are encrypted on your own site.

### Does it support scheduled automatic backups?

Yes, through the optional cloud service. You can schedule automatic backups daily,
weekly, hourly or as often as every few minutes for busy sites, each with its own
retention rules. One-click manual backups are always available for free without 
any schedule.

### What is incremental backup and does it support it?

An incremental backup only saves what changed since the last run, so it stays small
and fast. Yedekalma compares real file modification times for files and, with the
cloud service, exports only the database tables that actually changed — unchanged
runs are skipped automatically.

### Can I encrypt my backups?

Yes. With the optional cloud service you can turn on client-side AES-256 (BYOK) 
encryption. Archives are encrypted on your own server before they leave it, and 
the passphrase never reaches Yedekalma.

### How does the malware scanner work?

It scans PHP, JS and configuration files in WordPress core, your plugins and the
active theme for malicious patterns, code injections, web shells and backdoors. 
Results are saved so you can review them later, and you can delete detected files
in bulk. Core WordPress files are protected from deletion.

### How do I restore a WordPress backup for free?

Open **Yedekalma  Backups**, find the backup you want and click **Restore**. You
can restore the database, plugins, themes and uploads separately or all at once.
You can also drag & drop a `.zip`, `.sql` or `.sql.gz` archive you already have 
and restore from it — no account and no payment required.

### Can I restore only the database?

Yes. When restoring, pick the **Database** section on its own and the rest of the
site is left untouched. This is handy for rolling back a bad content change without
reverting files.

### Can I restore only the uploads, media or a single component?

Yes. Restore offers each section your backup contains — database, plugins, themes
and uploads — so you can restore just your media/uploads, just plugins or any single
part instead of the whole site.

### Is there a free WordPress migration plugin here?

Yes. Yedekalma migrates your WordPress site to a new host or domain for free: take
a full backup, download the ZIP, install Yedekalma on the target site and restore.
The site URL and home URL are rewritten in the database automatically, and `wp-config.
php` credentials can be updated during the restore.

### How can I scan WordPress for malware without a subscription?

The built-in malware scanner is completely free and needs no account. Open **Yedekalma
Malware Scanner** and start a scan; it checks WordPress core, your plugins and the
active theme for injected code, web shells and backdoors, then lets you delete detected
files in bulk while protecting core files.

### How often should I back up my WordPress site?

For most sites a weekly full backup plus a daily database backup is a good baseline;
busy or e-commerce sites should back up daily or more often. You can run a one-click
backup any time for free, and the optional Yedekalma cloud service adds scheduled
automatic backups with retention rules.

### What happens to my backups if I delete the plugin?

Nothing. Local archives under `wp-content/uploads/yedekalma-backups/` stay where
they are unless you remove them yourself, and anything in your own cloud storage
stays there too.

### Türkçe destekliyor mu?

Evet. Yedekalma tamamen Türkçe arayüze sahiptir: site yedekleme, veritabanı yedekleme,
yedekten geri yükleme, site taşıma ve virüs/zararlı yazılım taraması işlemlerinin
tümünü Türkçe olarak yapabilirsiniz.

### Is Multisite supported?

Not in version 1 — a separate plugin instance per site is required. Full Multisite
support is on the roadmap.

### Is it GDPR / KVKK compliant?

Yes. The plugin makes no external connection at all unless you deliberately connect
the optional cloud service, and explicit consent is collected for that data transfer.

## समीक्षा

There are no reviews for this plugin.

## Contributors & Developers

“Yedekalma — Yedek Alma, Geri Yükleme ve Taşıma” is open source software. The following
people have contributed to this plugin.

Contributors

 *   [ kamkactemha ](https://profiles.wordpress.org/kamkactemha/)

[Translate “Yedekalma — Yedek Alma, Geri Yükleme ve Taşıma” into your language.](https://translate.wordpress.org/projects/wp-plugins/yedekalma)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/yedekalma/), check 
out the [SVN repository](https://plugins.svn.wordpress.org/yedekalma/), or subscribe
to the [development log](https://plugins.trac.wordpress.org/log/yedekalma/) by [RSS](https://plugins.trac.wordpress.org/log/yedekalma/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

For the full history of older releases, see `changelog.txt` in the plugin folder.

#### 1.51.1 — 2026-08-08

 * UX: After sending a support request you now get a confirmation screen instead
   of the empty form again. Seeing the form a second time made it look as if nothing
   had been sent, so the natural reaction was to send it once more. The screen states
   the request number, the address the answer will go to and what happens next. 
   The form is also processed before the page is drawn, so refreshing no longer 
   re-sends the request.
 * FIX: A support request could be dropped without a trace. The spam trap on the
   Support form was a hidden field named `website`, and browsers and password managers
   autofill exactly that name — a filled trap made the server discard the request
   while the screen still said “we received it”. The field no longer carries a name
   autofill recognises, and the server now logs every rejection so a false positive
   can be spotted instead of vanishing.
 * FIX: If sending failed, the form was redrawn with “send technical details” ticked
   again even when you had unticked it — a second attempt would have sent the details
   you chose to withhold. The checkbox now keeps your choice.
 * FIX: The confirmation after a successful request was always shown in Turkish 
   regardless of the site language; it is translated now. Error text still comes
   from the server, because that is where the diagnosis is.
 * FIX: Collecting technical details could raise a PHP warning on hosts with an 
   unusual uploads directory configuration.
 * TWEAK: The review prompt is now a small tab in the bottom corner instead of a
   bar pinned to the middle of the screen edge, where it sat at eye level and stayed
   there while you scrolled.
 * FIX: The technical-details list you are asked to approve before sending was printed
   in Turkish on English, German, Russian and Arabic sites — you were being asked
   to confirm a list you could not read. Labels and states are shown in your own
   language now. What is actually transmitted stays in one fixed language on purpose,
   so support reads every request with the same vocabulary.

#### 1.51.0 — 2026-08-08

 * NEW: A **Support** screen under Settings. Until now a user who hit a problem 
   had nowhere to write from inside WordPress — and because local backup, restore
   and the malware scanner work with no account at all, most of those users have
   no Yedekalma login either, so “open a ticket in the panel” was not an option 
   for them. The new screen needs no account: your site address is filled in automatically,
   you type the problem, and the reply comes to the e-mail address you give.
 * NEW: Optional one-click technical details with the request — plugin/WordPress/
   PHP/MySQL versions, PHP limits, whether ZipArchive and `exec()` are available,
   free disk space, whether the backup folder is writable and when the last local
   backup ran. Support answers usually start by asking exactly these. The complete
   list is shown on screen before sending and the checkbox can be unticked; no site
   content, database content or passwords are ever included.
 * NEW: If the request cannot be sent (hosts that block outgoing connections), the
   screen says so and gives the support e-mail address instead of failing silently.
 * UX: The “please rate us on WordPress.org” prompt no longer sits across the top
   of every Yedekalma page. Two lines of text and three buttons were eating the 
   top of the first screen on every visit until it was dismissed. It is now a slim
   tab on the edge of the screen; the message itself opens in a dialog only if you
   click it. Closing the dialog changes nothing — snoozing or dismissing still happens
   only when you press those buttons.

#### 1.50.12 — 2026-08-07

 * FIXED: Your excluded paths were still being ignored by the two code paths that
   actually build the backup. 1.50.5 added the check, but in both places it was 
   handed a variable that was never assigned — PHP treats that as “no patterns”,
   so every rule silently evaluated to “keep this file”. A site that excluded several
   folders was still packing 70,140 files. The panel-driven chunked backup and the
   full-ZIP endpoint now read your pattern list before they walk the site.

#### 1.50.11 — 2026-08-07

 * UX: The right column is narrower again (420px) and every pixel it gives up goes
   to the folder browser. The two buttons under the pattern box now sit one above
   the other at full column width, and `white-space: nowrap` makes it impossible
   for “Exclude the suggested unnecessary files and folders” to break onto a second
   line — if the measurement is ever wrong the button will visibly overflow instead
   of quietly wrapping.

#### 1.50.10 — 2026-08-07

 * UX: The two columns are no longer equal width. The right column is fixed at 440px—
   just enough for the “Exclude the suggested unnecessary files and folders” button
   to stay on one line — and every extra pixel goes to the folder browser on the
   left, where folder name, size, file count and button all share a row and a narrow
   column truncates the name you are trying to read.

#### 1.50.9 — 2026-08-07

 * UX: Dropped the “Excluded paths” row label from the exclusion screen. Once each
   column had its own heading, that label was a third heading lined up with nothing—
   and it was eating 200px that the folder browser now uses instead. The browser
   is wider, and two columns now fit from 1000px up instead of 1180px. The pattern
   box heading became a real `<label>` tied to the field, which the old row label
   never was.

#### 1.50.8 — 2026-08-07

 * UX: On wide screens the exclusion screen is now two columns — the folder browser
   on the left, the pattern box on the right. They used to sit one above the other,
   so clicking “Exclude” on a folder added a line you had to scroll up to see. Cause
   and effect are now on screen at the same time. On narrow screens it stays a single
   column, with the pattern box first.

#### 1.50.7 — 2026-08-07

 * Fix: The folder browser marked some folders “excluded by default” when they were
   in fact being backed up. A folder whose name merely _started_ with a skipped 
   name — `.github` next to `.git`, `node_modules_old` next to `node_modules` — 
   got the badge and lost its “Exclude” button, so it looked handled while it kept
   going into every backup. The badge and the backup now read the same rule from
   one place.
 * UX: Files are badged too. Opening an excluded folder used to show every file 
   inside it with an “Exclude” button, suggesting those files were in the backup.
   They now show the same “already excluded” badge and sink to the bottom of the
   list, while still showing their size — so you can still see how much space old
   archives take.

#### 1.50.6 — 2026-08-07

 * UX: The list explaining what the exclusion suggestion covers no longer takes 
   up half the settings screen. It now sits behind a “What does the suggestion cover?”
   link that opens a dialog, where you can also apply the whole list in one click.

#### 1.50.5 — 2026-08-07

 * UX: Every leftover file now shows the date and clock time it was created, in 
   your site’s own timezone, next to “6 hours ago” — so you can tell which backup
   attempt left it behind.
 * UX: The file settings screen is split into two sub-tabs: “Files to back up” (
   exclusions and the folder browser) and “Leftover files” (the cleaner). Deciding
   what goes into a backup and deleting stray working files are two different jobs
   and no longer sit in each other’s way. The cleaner scans by itself the first 
   time you open its tab.

#### 1.50.4 — 2026-08-07

 * UX: The leftover-file cleaner now lists **every** file it found, including the
   recent ones it protects — “38 files will be kept” told you nothing about which
   files those were. Each entry shows its folder, size and age, and duplicates are
   no longer listed twice.
 * NEW: A “Clean anyway” button removes the recent files too. The six-hour age rule
   is only an assumption — a file can look recent because the host cut the request
   off, not because a backup is still running. The real protection now sits where
   it belongs: if a backup genuinely is running (local job, panel-driven chunked
   backup, or the single-run lock), the cleanup is refused and tells you why.
 * FIX: Files that could not be deleted (permissions) are now reported instead of
   being counted as cleaned.

#### 1.50.3 — 2026-08-07

 * UX: The one-click exclusion suggestion now covers everything a WordPress site
   can safely leave out of a backup — 35 patterns grouped and, next to each one,
   the reason it is safe: operating-system leftovers (`__MACOSX`, `._*`, `.DS_Store`,`
   Thumbs.db`), logs, half-finished temp files, editor backups, WordPress’s own `
   upgrade` and `upgrade-temp-backup` folders (which otherwise store a second copy
   of every plugin and theme), regenerable plugin caches (Divi, Elementor, LiteSpeed,
   Wordfence, WooCommerce logs) and other backup plugins’ archives.
 * UX: Your actual site content is never on that list. Uploads, themes, plugins,
   translations and `vendor/` are always backed up, and patterns that could hide
   real data were deliberately left out.

#### 1.50.2 — 2026-08-07

 * FIX: The leftover-file cleaner now also looks in the places older versions used(
   wp-content, uploads, the system temp folder). Files left behind by earlier releases—
   the “yedekalma_db_….sql.gz” dumps you may see in your file manager — are found
   and removed instead of sitting there forever.
 * UX: The cleaner is now offered on the file settings screen too, right under the
   folder browser where you actually see those files, not only on the Backups page.
 * UX: The one-click exclusion suggestion now lists every pattern with the reason
   it is safe to skip, and adds `__MACOSX` — the leftover folder macOS creates when
   you zip something. It holds nothing WordPress reads, but often tens of thousands
   of tiny files, which is what actually slows a backup down.

#### 1.50.1 — 2026-08-07

 * UX: Every part of the folder path is now clickable, so you can jump straight 
   back to any level instead of pressing “up” repeatedly.
 * UX: The file tab now tells you the size and file count of your backup as soon
   as you open it, without pressing anything (the result is cached for ten minutes,
   so it appears instantly on later visits).
 * UX: Layout fixes — the page no longer sits flush against the admin menu, long
   paths wrap readably, and the summary line is shown as a proper panel.

#### 1.50.0 — 2026-08-07

 * UX: The Pro settings page has been reorganised. Tabs read as tabs, each section
   sits in its own card with room to breathe, and a save bar now stays at the bottom
   of the page — it turns amber the moment you change something, so settings no 
   longer get lost by switching tabs without saving.
 * UX: In the exclusion browser, folders and files are now one list sorted by size,
   largest first — the thing making your backup big is the first thing you see. 
   Folders that never enter a backup can still be opened (you may want to look inside),
   they simply carry an “already excluded” badge instead of a pointless button.

#### 1.49.9 — 2026-08-07

 * FIX: Every backup left a stray empty file behind, and an interrupted backup left
   its database dump (often 10-20 MB) on disk for good. Worse, these working files
   were written to a folder that is reachable from the web and were then packed 
   into the next backup. They now live in the plugin’s own hardened backup folder,
   the empty placeholder is no longer created, and the cleaner recognises them.
 * NEW: The Backups screen can list and remove leftover working files with one click,
   showing exactly how many files and how much space they take. Files touched in
   the last 6 hours are left alone — they may belong to a backup that is still running.

#### 1.49.8 — 2026-08-07

 * FIX (important): The paths you excluded were never actually applied. The setting
   was saved and reported to the panel, but the code that builds the backup only
   honoured its own built-in skip list — so a folder you excluded went into the 
   backup anyway and your backup never got smaller. Exclusions now apply to every
   backup path, and to the file manifest used by incremental backups.
 * NEW: “How much space does this save?” measures your exclusions before you save
   them and tells you exactly how much smaller the backup becomes and how many files
   are left out. The measurement uses the same matching rules as the backup itself,
   so the number is real rather than an estimate.

#### 1.49.7 — 2026-08-07

 * UX: The exclusion browser is far more useful. Every folder now shows its total
   size and file count, the list is sorted largest first, and folders that never
   enter a backup anyway (cache, other backup plugins, version control, and the 
   plugin’s own backup folder) are marked “already excluded” instead of offering
   a pointless exclude button. You can now see at a glance what is actually making
   your backup big.
 * NEW: A single “Exclude the usual junk” button adds the patterns most sites need(*.
   tmp, *.log, error_log, debug.log) without hunting for them.

#### 1.49.6 — 2026-08-07

 * UX: The Backups screen now explains that deleting here removes the file on this
   server, while the record in your yedekalma.com panel is a separate thing. The
   panel never deletes files at your backup destination — once the file is really
   gone you can remove the record there. Previously a record left in the panel looked
   like the deletion had failed.

#### 1.49.5 — 2026-08-07

 * NEW: When you delete a backup from your yedekalma.com panel, the archive stored
   on this site is now deleted too, instead of being left behind until it expired.
   The command targets that one archive only: the file is identified by the backup’s
   own download token, the token must already be in the plugin’s own download register,
   the resolved path is confined to the backup folder, and it must be a file — no
   folders, no patterns, no bulk deletes. Your site files, your other backups and
   your database are never touched. If the file cannot be deleted the panel keeps
   its record instead of losing track of it.
 * UX: In the exclusion browser, the plugin’s own backup folder is now shown as “
   already excluded” instead of offering an exclude button — it never goes into 
   a backup anyway (an archive is not packed into itself).

#### 1.49.4 — 2026-08-07

 * FIX: The plugin’s own backup folder was correctly left out of the backup itself,
   but it was still counted when measuring the size of your site and when building
   the file manifest. On a site holding a few large archives this made the reported
   site size far bigger than the site actually is, and it would have made incremental
   backups treat those archives as new files every time. The folder is now excluded
   everywhere.

#### 1.49.3 — 2026-08-07

 * FIX: A scheduled backup could be started again while the previous one was still
   running, so several full backups ran on the same site at once. Each of them slowed
   the others down and the same archive could be uploaded twice. The plugin now 
   refuses a second backup while one is in progress and tells yedekalma.com it is
   busy, so the panel simply waits instead of starting another. On a large site 
   this alone can cut the time a backup appears to take by more than half.

#### 1.49.2 — 2026-08-07

 * CHANGE: The backup schedule now says “Backup hour (from this hour onwards)” instead
   of implying an exact minute. Backups start at that hour or shortly after — they
   are spread over a short window so your server is not hit by several jobs at once,
   and WordPress’s own scheduler depends on a visitor arriving. Nothing is skipped;
   a late backup is retried by itself. The wording now matches what the system has
   always actually done.

#### 1.49.1 — 2026-08-07

 * FIX: When several sites you back up live on the same physical server, running
   their backups at the same moment strains that server and one of them can be killed
   mid-job. The plugin now reports a short, hashed identifier of the machine it 
   runs on (host name only, never sent in the clear), so yedekalma.com can start
   those backups one after another instead of together. Nothing about neighbouring
   sites is disclosed, and no setting of yours is changed.

#### 1.49.0 — 2026-08-06

 * FIX: Large sites could never finish a backup started from the yedekalma.com panel.
   Each slice reopened the archive with PHP’s ZipArchive, and closing a ZIP rewrites
   the whole file — so the cost grew with the archive. On a 70,000 file / 1.7 GB
   site the final step (adding the database dump to the archive) rewrote all 1.7
   GB and was cut off by the host after 60 seconds, every single time, until all
   eight automatic retries were spent. Panel backups now use the same append-only
   archive writer the plugin already used for its own backups: every entry is written
   at the end of the archive, nothing already written is touched again, and finishing
   the archive only writes the index. The step that used to time out now takes seconds.
 * FIX: If a slice was cut off by the host, the panel’s next attempt could start
   a second process writing into the same archive. Slices now take a lock; an overlapping
   request is turned away instead of corrupting the archive.
 * FIX: The database dump was recorded as 0 bytes in the backup’s file list.

#### 1.48.0 — 2026-08-06

 * NEW: The plugin can now keep itself up to date. A backup plugin that stays on
   an old release quietly misses the very fixes that keep backups working, and updating
   it was something you had to remember to do. Settings  Automatic Update turns 
   WordPress’s own updater on for this plugin; from then on new releases install
   themselves. It is off until you switch it on, it is never enabled behind your
   back, and it is the same preference WordPress shows on the Plugins screen, so
   either place can change it.
 * NEW: When an update is waiting, the Yedekalma pages and your Dashboard show it
   with a single button that installs it on the spot. The reminder can be dismissed
   for that version, and it comes back only when a newer one is released.
 * NEW: Sites that update themselves are marked as such in your Yedekalma panel,
   and the “your plugin is out of date” email now waits for them instead of arriving
   while WordPress is already installing the update.

#### 1.47.0 — 2026-08-06

 * FIX: After connecting with Google, the plugin briefly showed the “connect your
   site” screen — the very screen you had just finished with — before switching 
   to the connected one. The connection token comes back in the URL fragment (deliberately,
   so it never reaches a server log), which means the page is drawn before the site
   knows it is connected. The page now waits behind a short “connecting…” veil and
   comes back already connected, with a single confirmation.
 * FIX: Removed the 1.2 second pause that was sitting between “connected” and the
   page reload.
 * CHANGE: The plugin listing is now written in Turkish first, with the English 
   description kept underneath. Turkish searches such as “yedek alma” previously
   returned nothing at all, because every word in the listing was English.

#### 1.46.2 — 2026-08-06

 * FIX: The icon on the “Full Backup” button still sat below its label. The alignment
   rule added in 1.46.1 was written at the same weight as one of WordPress’s own
   button rules, so on screens where WordPress’s stylesheet was written last it 
   simply lost and the icon dropped again. The rule is now specific enough to win
   outright.

#### 1.46.1 — 2026-08-06

 * FIX: Icons sat slightly too high next to their labels on several screens — in
   buttons, tabs and section headings. Each screen had been patching this by hand
   with a different nudge, so the amount of drift varied from page to page. Icon
   alignment is now defined in one place and every screen uses it.
 * FIX: The “delete selected backups” bar put its button and its counter on different
   baselines when it appeared.

#### 1.46.0 — 2026-08-06

 * NEW: Backups now work on hosts that block outgoing connections. Until now the
   plugin had to reach the panel itself twice during an upload — once for permission
   to upload, once to record the finished backup. On a server where outbound HTTPS
   is restricted, the backup was packed but could never be sent, and the plugin 
   misdiagnosed it as “this storage destination is not supported”. The panel now
   hands both of those over inside the reply to a request the plugin has _already_
   opened, so your site never has to connect out to us. Interrupted uploads still
   resume where they left off.
 * FIX: The plugin’s recorded version was never read when deciding whether it supports
   a newer protocol, so newer features stayed switched off forever. The version 
   is now confirmed against the running plugin (and refreshed) when it looks out
   of date — which also happens when you update the plugin from inside WordPress
   instead of from the panel.

#### 1.45.0 — 2026-08-05

 * FIX: On resource-limited (shared) hosting the backup could be cut short with “
   503 Service Unavailable — the server is temporarily busy”. Each backup step now
   does less work at a time (8 seconds / 200 files / 32 MB instead of 15 seconds/
   400 files / 64 MB), so a single request stays below the host’s limit. The backup
   is split into more, smaller steps and still resumes exactly where it left off.
   Hosts can tune the limits with the `yedekalma_chunk_budget_seconds`, `yedekalma_chunk_file_cap`
   and `yedekalma_chunk_byte_cap` filters.

#### 1.44.6 — 2026-08-04

 * FIX: On large sites a backup could restart from scratch on every retry and therefore
   never finish. A half-finished backup was discarded after 10 minutes, but the 
   panel’s third retry arrives later than that. The window is now an hour, so a 
   backup really does resume where it left off.
 * FIX: The plugin crashed with a fatal error on hosts where `disk_free_space()`
   is disabled — both in the diagnostics endpoint and in the free-space pre-check
   that runs during a backup. The check is now skipped when the host does not provide
   the function.

#### 1.44.5 — 2026-08-01

 * FIX: The Pro screen showed the “Manage backups” and “Open panel” buttons twice—
   the page and the asynchronously loaded status block each drew their own copy.
   Only the page draws them now, so they also appear when the panel cannot be reached.

#### 1.44.4 — 2026-08-01

 * UX: The Pro screen no longer repeats the last few backups. The Backups page already
   lists them in full — with type, destination, source and restore — so the Pro 
   screen just links there. It also loads a little faster: one fewer request to 
   the panel.

#### 1.44.3 — 2026-08-01

 * FIX: Backups stored in the cloud never showed up in the Backups list. The plugin
   had always asked the panel for them, but the endpoint did not exist, so the request
   failed and the empty answer was accepted silently — only archives lying on this
   server were listed. They are now fetched and shown.
 * NEW: A “Destination” column tells you where each backup actually went — Google
   Drive (with the account), S3 (with the bucket), your own receiver module, or 
   this site’s own disk.

#### 1.44.2 — 2026-08-01

 * UX: The status card now shows where the backups are actually sent (Google Drive,
   S3, your own server, in-domain storage…), right under the backup times. It said“
   running” and listed the hours, but you had to open the panel to find out the 
   destination. When more than one destination is set, every one of them is listed
   and marked primary/copy.

#### 1.44.1 — 2026-07-31

 * UX: The Pro screen now names every place a backup can be sent. It listed Google
   Drive, S3 and FTP only, which left out the simplest destination of all — the 
   server WordPress itself runs on. The intro text, the setup step and the storage
   box in the diagram now all mention in-domain storage as well.

#### 1.44.0 — 2026-07-31

 * NEW: The Pro screen now explains the optional cloud service before asking you
   to sign in. When you are not connected it shows what the service does, a diagram
   of where a backup actually travels (packed and encrypted on your own server, 
   sent straight to your own storage, never through our servers), a three-step setup
   guide and what connecting adds. Previously there were four bullet points and 
   a sign-in button, so you had to connect first and find out afterwards. All artwork
   is inline SVG: the screen makes no external requests.
 * NEW: The connection screen lists your actual schedule. Files, database and e-
   mail each show when they are due (for example “Every day 02:00”); you no longer
   have to open the Yedekalma panel to find out.
 * FIX: A component that cannot run is no longer shown with a time next to it. E-
   mail is archived over IMAP, so with no mail account configured it never runs —
   yet the schedule still read “Every day 04:00”, which looked like mail was being
   backed up. It now reads that no mail account is defined and is greyed out, matching
   what the panel reports.

#### 1.43.0 — 2026-07-31

 * UX: The connection screen now tells you two separate things instead of one long
   sentence. Backup status (is it actually running, when was the last one) and membership
   status (days left, expiry date, renew) used to be crammed into a single paragraph
   that was easy to skim past. They are now two side-by-side panels, and the membership
   panel turns red with a primary “Manage subscription” button in the last seven
   days, so an expiring subscription is impossible to miss.

#### 1.42.2 — 2026-07-31

 * UX: You can now see which kind of backup is running. “Full Backup” was always
   drawn as the filled, primary button, so choosing “Database Only” left the screen
   looking as if a full backup had been started — the right backup was taken, but
   the screen said otherwise. The button you clicked is now highlighted for the 
   duration of the run and the progress line is prefixed with the backup type at
   every stage.

#### 1.42.1 — 2026-07-31

 * FIX: Deleting the plugin no longer orphans backups it deliberately keeps. Removing
   the plugin is meant to leave your archives on disk unless you explicitly opt 
   in to deleting them — but the cleanup was still wiping the records that point
   at those archives (the download-token map, the backup list and the backup folder
   name). The files survived while every download link returned 404, so it looked
   as if all backups had been lost. Those three records are now kept whenever the
   files are kept; opting in to full deletion still removes everything.

#### 1.42.0 — 2026-07-31

 * PERFORMANCE: Backups are dramatically faster on large sites. The archive is now
   written by appending each file to the end of it, instead of letting PHP rewrite
   the whole archive at the end of every step. Rewriting made the cost grow with
   the square of the site size — on a real 5,502-file site a single step had grown
   to over two minutes and kept getting slower. That cost is gone: the work is now
   proportional to the amount of data, once.
 * FIX: Backups no longer need roughly twice the backup size in free disk space.
   The old approach kept a second copy of the whole archive while rewriting it, 
   which is what turned a nearly-full disk into an “archive came out empty” failure.
   Only the archive itself needs to fit now, and the free-space check was relaxed
   accordingly.
 * FIX: A file is written into the archive the moment it is read, instead of being
   queued and read later. A file that changed or disappeared between being listed
   and being packed can no longer end up silently missing from the backup.
 * NEW: Archives larger than 4 GB (or with more than 65,535 files) are written with
   ZIP64 fields, so very large sites produce a valid archive.
 * UX: Because finishing a step is now free, steps are short again — the progress
   console updates continuously and a running backup no longer holds a PHP process
   long enough to make wp-admin unresponsive.

#### 1.41.4 — 2026-07-31

 * FIX: “Backup archive came out empty” told you nothing. The message now names 
   the most likely cause — no space left in the temporary directory — and reports
   the free space, the directory and the expected archive size, so you can act on
   it.
 * NEW: Free-space preflight. A backup that cannot possibly fit now stops before
   packing thousands of files instead of failing at the very last step. Writing 
   the archive keeps a second copy while it is rewritten, so roughly twice the backup
   size must be free.
 * FIX: A failing backup no longer deletes a half-finished archive that another 
   process may still be writing to; this could turn a recoverable hiccup into an“
   archive is empty” failure.
    …

## मेटा

 *  Version **1.51.1**
 *  Last updated **2 days पहिले**
 *  Active installations **10 गो से कम**
 *  WordPress version ** 5.8 चाहे एकरो से ऊपर **
 *  Tested up to **7.0.3**
 *  PHP version ** 7.4 चाहे एकरो से ऊपर **
 *  Language
 * [English (US)](https://wordpress.org/plugins/yedekalma/)
 * Tag
 * [backup](https://bho.wordpress.org/plugins/tags/backup/)
 *  [Advanced View](https://bho.wordpress.org/plugins/yedekalma/advanced/)

## रेटिंग्स

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/yedekalma/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/yedekalma/reviews/)

## Contributors

 *   [ kamkactemha ](https://profiles.wordpress.org/kamkactemha/)

## मदद

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/yedekalma/)