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

Changelog

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

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.
• FIX: If the temporary archive disappears mid-run (server temp cleanup or a full disk), packing no longer silently starts a fresh archive and produces an incomplete backup — it stops with a clear message.

1.41.3 — 2026-07-31

• UX: The backup screen now says what it is waiting for. Writing the archive to disk, adding the database dump and computing the SHA-256 signature can each take minutes, and during them the file counter does not move — previously the screen just showed the last file name with a ticking counter, which reads as a frozen system. Each of those steps is now announced before it starts (“Archive is being written to disk…”, “Computing integrity signature…”), the headline above the progress bar shows the same thing, and the seconds counter now reads “running…” instead of a bare number.
• UX: Preparation is no longer silent either — the database dump and the file scan are announced as they happen.

1.41.2 — 2026-07-31

• UX: The star on the “Yedekalma Pro” menu item now sits after the label instead of before it, so the submenu items line up on the left.

1.41.1 — 2026-07-31

• FIX: On shared hosting a running backup could make the whole WordPress admin unresponsive — pages and plugin uploads would spin forever. Version 1.40.3 let a single backup slice hold a PHP worker for up to 90 seconds plus the archive write, and most shared accounts allow only one or two PHP processes at a time, so admin requests queued behind it. A slice is now capped at 30 seconds, which still removes most of the slow repeated archive writes without blocking your dashboard.

1.41.0 — 2026-07-31

• REMOVED: The Test Environment (staging) feature has been dropped completely. It cloned your live site into a /staging subfolder with a stg_ table prefix — useful on its own, but unrelated to backup and restore, and it carried a large amount of code and a write-capable surface on your server for no backup benefit. The “Test Ortamı” menu item, its page, the REST endpoint and all clone/teardown code are gone. Existing /staging folders and stg_ tables on your server are left untouched; delete them yourself if you no longer need them.