{"id":332082,"date":"2026-07-15T16:54:49","date_gmt":"2026-07-15T16:54:49","guid":{"rendered":"https:\/\/tr.wordpress.org\/plugins\/yedekalma-wp-yedekleme-baglayicisi\/"},"modified":"2026-08-22T08:39:02","modified_gmt":"2026-08-22T08:39:02","slug":"yedekalma","status":"publish","type":"plugin","link":"https:\/\/yor.wordpress.org\/plugins\/yedekalma\/","author":23519696,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.58.2","stable_tag":"1.58.2","tested":"7.1","requires":"5.8","requires_php":"7.4","requires_plugins":null,"header_name":"Yedekalma \u2014 Backup, Restore, Migration & Malware Scanner","header_author":"Yedek Alma A.\u015e.","header_description":"Local one-click WordPress backup & restore (files + database), no account required. Optionally connect the free Yedekalma cloud service for off-site, multi-cloud storage.","assets_banners_color":"1f4177","last_updated":"2026-08-22 08:39:02","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/yedekalma.com\/wordpress-plugin","header_author_uri":"https:\/\/yedekalma.com","rating":0,"author_block_rating":0,"active_installs":0,"downloads":1581,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.10.0":{"tag":"1.10.0","author":"kamkactemha","date":"2026-07-15 17:13:52"},"1.10.1":{"tag":"1.10.1","author":"kamkactemha","date":"2026-07-15 17:16:07"},"1.10.10":{"tag":"1.10.10","author":"kamkactemha","date":"2026-07-20 13:42:08"},"1.10.11":{"tag":"1.10.11","author":"kamkactemha","date":"2026-07-20 13:43:41"},"1.10.2":{"tag":"1.10.2","author":"kamkactemha","date":"2026-07-18 05:55:53"},"1.10.3":{"tag":"1.10.3","author":"kamkactemha","date":"2026-07-18 08:19:52"},"1.10.4":{"tag":"1.10.4","author":"kamkactemha","date":"2026-07-20 07:27:19"},"1.10.5":{"tag":"1.10.5","author":"kamkactemha","date":"2026-07-20 07:43:01"},"1.10.6":{"tag":"1.10.6","author":"kamkactemha","date":"2026-07-20 08:51:13"},"1.10.7":{"tag":"1.10.7","author":"kamkactemha","date":"2026-07-20 10:46:51"},"1.10.8":{"tag":"1.10.8","author":"kamkactemha","date":"2026-07-20 12:00:03"},"1.10.9":{"tag":"1.10.9","author":"kamkactemha","date":"2026-07-20 12:07:30"},"1.11.0":{"tag":"1.11.0","author":"kamkactemha","date":"2026-07-20 13:46:35"},"1.11.1":{"tag":"1.11.1","author":"kamkactemha","date":"2026-07-20 14:00:08"},"1.11.2":{"tag":"1.11.2","author":"kamkactemha","date":"2026-07-20 14:14:31"},"1.11.3":{"tag":"1.11.3","author":"kamkactemha","date":"2026-07-20 14:25:54"},"1.11.4":{"tag":"1.11.4","author":"kamkactemha","date":"2026-07-21 05:35:25"},"1.11.5":{"tag":"1.11.5","author":"kamkactemha","date":"2026-07-21 05:39:14"},"1.11.6":{"tag":"1.11.6","author":"kamkactemha","date":"2026-07-22 05:24:35"},"1.11.7":{"tag":"1.11.7","author":"kamkactemha","date":"2026-07-22 06:04:50"},"1.12.0":{"tag":"1.12.0","author":"kamkactemha","date":"2026-07-27 08:01:14"},"1.13.0":{"tag":"1.13.0","author":"kamkactemha","date":"2026-07-27 08:15:13"},"1.14.0":{"tag":"1.14.0","author":"kamkactemha","date":"2026-07-28 06:04:43"},"1.18.0":{"tag":"1.18.0","author":"kamkactemha","date":"2026-07-28 06:47:07"},"1.19.0":{"tag":"1.19.0","author":"kamkactemha","date":"2026-07-28 07:23:46"},"1.20.0":{"tag":"1.20.0","author":"kamkactemha","date":"2026-07-28 07:50:58"},"1.22.0":{"tag":"1.22.0","author":"kamkactemha","date":"2026-07-28 20:20:51"},"1.22.1":{"tag":"1.22.1","author":"kamkactemha","date":"2026-07-29 06:48:11"},"1.22.2":{"tag":"1.22.2","author":"kamkactemha","date":"2026-07-29 06:55:01"},"1.28.0":{"tag":"1.28.0","author":"kamkactemha","date":"2026-07-30 05:48:22"},"1.29.0":{"tag":"1.29.0","author":"kamkactemha","date":"2026-07-30 07:38:02"},"1.30.0":{"tag":"1.30.0","author":"kamkactemha","date":"2026-07-30 07:46:36"},"1.31.0":{"tag":"1.31.0","author":"kamkactemha","date":"2026-07-30 08:48:35"},"1.32.0":{"tag":"1.32.0","author":"kamkactemha","date":"2026-07-30 12:00:27"},"1.33.0":{"tag":"1.33.0","author":"kamkactemha","date":"2026-07-30 12:35:12"},"1.34.0":{"tag":"1.34.0","author":"kamkactemha","date":"2026-07-30 12:53:22"},"1.35.0":{"tag":"1.35.0","author":"kamkactemha","date":"2026-07-30 13:17:03"},"1.36.0":{"tag":"1.36.0","author":"kamkactemha","date":"2026-07-30 13:42:54"},"1.37.0":{"tag":"1.37.0","author":"kamkactemha","date":"2026-07-30 13:56:58"},"1.40.0":{"tag":"1.40.0","author":"kamkactemha","date":"2026-07-30 20:13:37"},"1.43.0":{"tag":"1.43.0","author":"kamkactemha","date":"2026-07-31 13:30:49"},"1.44.0":{"tag":"1.44.0","author":"kamkactemha","date":"2026-07-31 13:46:50"},"1.44.1":{"tag":"1.44.1","author":"kamkactemha","date":"2026-07-31 14:42:49"},"1.44.2":{"tag":"1.44.2","author":"kamkactemha","date":"2026-08-01 07:11:21"},"1.44.3":{"tag":"1.44.3","author":"kamkactemha","date":"2026-08-01 08:53:11"},"1.44.5":{"tag":"1.44.5","author":"kamkactemha","date":"2026-08-01 10:59:17"},"1.44.6":{"tag":"1.44.6","author":"kamkactemha","date":"2026-08-04 17:22:08"},"1.45.0":{"tag":"1.45.0","author":"kamkactemha","date":"2026-08-05 08:32:17"},"1.46.0":{"tag":"1.46.0","author":"kamkactemha","date":"2026-08-06 08:12:12"},"1.46.1":{"tag":"1.46.1","author":"kamkactemha","date":"2026-08-06 08:29:32"},"1.46.2":{"tag":"1.46.2","author":"kamkactemha","date":"2026-08-06 08:48:22"},"1.47.0":{"tag":"1.47.0","author":"kamkactemha","date":"2026-08-06 10:40:56"},"1.48.0":{"tag":"1.48.0","author":"kamkactemha","date":"2026-08-06 11:27:48"},"1.49.0":{"tag":"1.49.0","author":"kamkactemha","date":"2026-08-06 14:48:22"},"1.49.1":{"tag":"1.49.1","author":"kamkactemha","date":"2026-08-07 07:03:46"},"1.49.2":{"tag":"1.49.2","author":"kamkactemha","date":"2026-08-07 07:24:50"},"1.49.3":{"tag":"1.49.3","author":"kamkactemha","date":"2026-08-07 07:31:03"},"1.49.4":{"tag":"1.49.4","author":"kamkactemha","date":"2026-08-07 08:00:41"},"1.49.5":{"tag":"1.49.5","author":"kamkactemha","date":"2026-08-07 08:14:33"},"1.49.6":{"tag":"1.49.6","author":"kamkactemha","date":"2026-08-07 08:34:11"},"1.49.7":{"tag":"1.49.7","author":"kamkactemha","date":"2026-08-07 08:50:44"},"1.49.8":{"tag":"1.49.8","author":"kamkactemha","date":"2026-08-07 11:14:27"},"1.49.9":{"tag":"1.49.9","author":"kamkactemha","date":"2026-08-07 13:18:29"},"1.50.0":{"tag":"1.50.0","author":"kamkactemha","date":"2026-08-07 13:25:51"},"1.50.1":{"tag":"1.50.1","author":"kamkactemha","date":"2026-08-07 13:34:03"},"1.50.10":{"tag":"1.50.10","author":"kamkactemha","date":"2026-08-07 14:43:00"},"1.50.11":{"tag":"1.50.11","author":"kamkactemha","date":"2026-08-07 14:49:23"},"1.50.12":{"tag":"1.50.12","author":"kamkactemha","date":"2026-08-08 06:44:40"},"1.50.2":{"tag":"1.50.2","author":"kamkactemha","date":"2026-08-07 13:41:07"},"1.50.3":{"tag":"1.50.3","author":"kamkactemha","date":"2026-08-07 13:50:07"},"1.50.9":{"tag":"1.50.9","author":"kamkactemha","date":"2026-08-07 14:36:15"},"1.51.1":{"tag":"1.51.1","author":"kamkactemha","date":"2026-08-08 08:55:41"},"1.51.4":{"tag":"1.51.4","author":"kamkactemha","date":"2026-08-12 08:11:18"},"1.52.0":{"tag":"1.52.0","author":"kamkactemha","date":"2026-08-12 13:44:17"},"1.53.0":{"tag":"1.53.0","author":"kamkactemha","date":"2026-08-13 05:58:49"},"1.53.2":{"tag":"1.53.2","author":"kamkactemha","date":"2026-08-15 08:40:40"},"1.53.3":{"tag":"1.53.3","author":"kamkactemha","date":"2026-08-16 16:03:42"},"1.54.0":{"tag":"1.54.0","author":"kamkactemha","date":"2026-08-17 06:26:55"},"1.54.1":{"tag":"1.54.1","author":"kamkactemha","date":"2026-08-17 07:12:51"},"1.54.2":{"tag":"1.54.2","author":"kamkactemha","date":"2026-08-17 08:04:26"},"1.54.3":{"tag":"1.54.3","author":"kamkactemha","date":"2026-08-17 08:21:37"},"1.54.4":{"tag":"1.54.4","author":"kamkactemha","date":"2026-08-17 10:41:29"},"1.54.5":{"tag":"1.54.5","author":"kamkactemha","date":"2026-08-17 11:32:31"},"1.54.7":{"tag":"1.54.7","author":"kamkactemha","date":"2026-08-17 12:32:36"},"1.54.8":{"tag":"1.54.8","author":"kamkactemha","date":"2026-08-17 12:49:47"},"1.54.9":{"tag":"1.54.9","author":"kamkactemha","date":"2026-08-17 13:15:15"},"1.55.0":{"tag":"1.55.0","author":"kamkactemha","date":"2026-08-17 14:06:10"},"1.55.1":{"tag":"1.55.1","author":"kamkactemha","date":"2026-08-17 14:44:05"},"1.55.2":{"tag":"1.55.2","author":"kamkactemha","date":"2026-08-17 21:02:30"},"1.55.3":{"tag":"1.55.3","author":"kamkactemha","date":"2026-08-18 05:44:05"},"1.55.4":{"tag":"1.55.4","author":"kamkactemha","date":"2026-08-18 05:51:04"},"1.55.5":{"tag":"1.55.5","author":"kamkactemha","date":"2026-08-18 05:56:29"},"1.55.6":{"tag":"1.55.6","author":"kamkactemha","date":"2026-08-18 06:03:28"},"1.55.7":{"tag":"1.55.7","author":"kamkactemha","date":"2026-08-18 06:07:21"},"1.55.8":{"tag":"1.55.8","author":"kamkactemha","date":"2026-08-18 06:20:52"},"1.56.0":{"tag":"1.56.0","author":"kamkactemha","date":"2026-08-18 06:28:36"},"1.57.0":{"tag":"1.57.0","author":"kamkactemha","date":"2026-08-18 06:38:30"},"1.57.1":{"tag":"1.57.1","author":"kamkactemha","date":"2026-08-18 12:05:48"},"1.57.10":{"tag":"1.57.10","author":"kamkactemha","date":"2026-08-20 08:44:04"},"1.57.11":{"tag":"1.57.11","author":"kamkactemha","date":"2026-08-20 09:11:37"},"1.57.12":{"tag":"1.57.12","author":"kamkactemha","date":"2026-08-20 13:59:03"},"1.57.13":{"tag":"1.57.13","author":"kamkactemha","date":"2026-08-21 08:53:06"},"1.57.2":{"tag":"1.57.2","author":"kamkactemha","date":"2026-08-18 13:10:12"},"1.57.3":{"tag":"1.57.3","author":"kamkactemha","date":"2026-08-18 13:42:30"},"1.57.4":{"tag":"1.57.4","author":"kamkactemha","date":"2026-08-18 19:56:42"},"1.57.5":{"tag":"1.57.5","author":"kamkactemha","date":"2026-08-18 20:14:03"},"1.57.6":{"tag":"1.57.6","author":"kamkactemha","date":"2026-08-19 08:19:00"},"1.57.7":{"tag":"1.57.7","author":"kamkactemha","date":"2026-08-19 12:48:05"},"1.57.8":{"tag":"1.57.8","author":"kamkactemha","date":"2026-08-19 13:07:12"},"1.58.0":{"tag":"1.58.0","author":"kamkactemha","date":"2026-08-22 07:52:08"},"1.58.1":{"tag":"1.58.1","author":"kamkactemha","date":"2026-08-22 08:05:53"},"1.58.2":{"tag":"1.58.2","author":"kamkactemha","date":"2026-08-22 08:39:02"}},"upgrade_notice":{"1.57.8":"<p>Hardening: a corrupt or malicious encrypted backup can no longer exhaust memory and kill a restore. Encrypted archives are read frame by frame, and the integrity (HMAC) pass had no upper bound on the declared frame length, so a tampered file could request up to a 4 GB read and crash PHP. The decrypt pass already had that bound, but it runs second, so it was never reached. Both passes are bounded now.<\/p>","1.57.7":"<p>Restore now lets you deliberately bring back wp-config.php, .htaccess and .user.ini with an explicit checkbox. They stay protected by default - that default is what saves a site whose database credentials or server changed after the backup was taken - but you finally have a supported way to restore them on purpose. The restore result screen also tells you what actually happened: whether those files were protected, and whether the archive could only be verified structurally because the backup carried no SHA-256 record. Fixed: a site whose storage target is a self-hosted &quot;Receiver Module&quot; could never finish a backup, because the plugin did not implement that upload method at all - the archive was built and then the upload step failed. It is implemented now, with resumable chunked upload for large archives.<\/p>","1.57.6":"<p>Important for recovery: restoring a CLOUD backup from wp-admin always failed with a 403 - the required header was added to only one of the two call sites. Fixed, and both paths now go through a single gate. Also critical: on hosts where the document root is a symlink (common on shared hosting), a restore wrote NO files at all yet still reported &quot;completed successfully&quot; - the site was never repaired and you would only find out on the day you needed it. The root is now resolved, and &quot;the archive had files but none were written&quot; is now an error instead of a success. Restore also verifies transfer length and archive consistency before overwriting your site, exclusion patterns behave identically on every host, and failures on extra storage destinations are finally reported instead of being swallowed.<\/p>","1.57.5":"<p>Important: on shared hosts that disable PHP functions such as set_time_limit, backups could die with a fatal error in their first second. All remaining unguarded calls are now routed through a single safe gate. This release also stops restore from overwriting wp-config.php and .htaccess - if your database credentials or server changed after the backup was taken, restoring no longer takes your site down. Plus a security fix: the upload-limit tweak that writes .user.ini required no capability check and could be triggered by any logged-in user.<\/p>","1.54.5":"<p>Critical: your exclusion list was never applied to the backup. The patterns you set under Files worked only on screen - the badge counted them, the &quot;how much will this save?&quot; measurement used them, and the list reported to the panel was correct - but the code that PRODUCES the backup read them from a different record that nothing ever wrote to. The list was therefore always treated as empty and everything you excluded went into the archive anyway. The same fault inflated the reported site size. Measured in the field: the estimate said 9,214 files would be backed up while the backup was processing 16,669 - the ~8.1 GB difference was exactly the data that should have been excluded.<\/p>","1.54.4":"<p>Critical: two backups could run at once on the same site. The plugin has two backup paths and each used its own run lock, so a scheduled trigger could start a second full backup while the panel was still driving a chunked one - double disk, double CPU, and neither finishing on a constrained server. Both paths now share one lock; whichever starts first wins and the other backs off without disturbing its progress.<\/p>","1.54.3":"<p>Critical fix for the plugin&#039;s own scheduled backup on large sites. Panel-triggered backups moved to the streaming archive writer in 1.49, but backups started by the plugin&#039;s own schedule still used PHP&#039;s ZipArchive, which rewrites the whole archive on every close - and it was closing every 400 files. On a multi-gigabyte site each round copied the entire archive into a temporary &quot;.part&quot; file next to it; shared hosting cut the request off at 60 seconds, so the copy never finished and the next round started from zero. Both paths now use the streaming writer: entries are appended, never rewritten.<\/p>","1.54.2":"<p>Large sites could never finish a backup. Two steps read or wrote the whole archive inside a single request: the finished archive was COPIED from the temporary folder to the backup folder, and its SHA-256 was recomputed on every round of the upload handshake. On a 7-9 GB site neither fits in the 60-second window shared hosting allows, so each round restarted from zero - leaving a file that grew and reset forever while the disk filled up. The archive is now moved (same disk, instant, atomic) and the checksum is computed once. Leftovers from interrupted runs are also cleaned up now, even when the session record is gone.<\/p>","1.54.1":"<p>Archive integrity follow-up to 1.54.0. When a disk or hosting quota fills up, the OS can complete a write only partially; the archive writer treated that as success and the tracked offset drifted from the real file size, which silently corrupts every later entry. Partial writes are now completed, and packaging stops if the data really cannot be written. Encryption also now reports &quot;not enough disk space&quot; instead of blaming OpenSSL.<\/p>","1.54.0":"<p>Critical backup and restore fixes. Backups: the plugin never verified the archive it produced, so a write error during packaging (full disk, hosting quota, transient I\/O) did not stop the run and the damaged file was uploaded looking like a valid zip \u2014 you would only find out on the day you restored. Archives are now checked before upload and packaging aborts on the first write error. Restores: the component selection you make in the panel was ignored, so unchecking &quot;Database&quot; still overwrote your live database; the &quot;do not touch this file&quot; list was not applied to the deletion step, so protected paths could be deleted from your site; and a truncated database dump was applied first and rejected afterwards, with no rollback. All are fixed.<\/p>","1.53.3":"<p>Important restore fixes. Files you chose to KEEP were being overwritten anyway (wp-config.php, .htaccess and uploads were the usual victims), with no warning. Archives made by the standalone module also unpacked into a &quot;dosya\/&quot; subfolder instead of your site root, and the database dump was written to the web root where it could be downloaded. Both are fixed.<\/p>","1.53.2":"<p>Backup integrity fix. If a file could not be read while the archive was being written, it was silently padded with zero bytes: the backup looked successful but that file was empty on restore. Read failures now fail the file loudly instead of corrupting it quietly.<\/p>","1.51.1":"<p>Fixes a Support form spam trap that browser autofill could trip, which silently discarded the request while the screen said it was sent. Also keeps your &quot;send technical details&quot; choice after a failed attempt, and shows that list in your own language.<\/p>","1.51.0":"<p>New Support screen under Settings: write to us straight from wp-admin, with your site address filled in and no Yedekalma account required.<\/p>","1.50.12":"<p>Important: your excluded paths were still being backed up. Update \u2014 the exclusion list is now actually read by the backup.<\/p>","1.50.11":"<p>Narrower right column, wider folder browser, and the suggestion button can no longer wrap onto two lines.<\/p>","1.50.10":"<p>The folder browser now takes every pixel the pattern box does not need, so folder names stop getting truncated.<\/p>","1.50.9":"<p>The folder browser is wider \u2014 the redundant row label next to it is gone and the space went to the browser.<\/p>","1.50.8":"<p>The exclusion screen is now two columns on wide screens: browse folders on the left, see the excluded patterns fill up on the right.<\/p>","1.50.7":"<p>The folder browser no longer claims a folder is &quot;excluded by default&quot; when it is actually being backed up \u2014 <code>.github<\/code> was wrongly badged because of <code>.git<\/code>.<\/p>","1.50.6":"<p>The long &quot;what does the suggestion cover?&quot; list is now a dialog you open when you want it, instead of half a screen of text.<\/p>","1.50.5":"<p>Leftover files now show the date and time they were created, and the file settings screen is split into two sub-tabs: what gets backed up, and leftover files.<\/p>","1.50.4":"<p>The leftover-file cleaner now shows every file it found \u2014 including the recent ones it protects \u2014 and a &quot;Clean anyway&quot; button removes those too, unless a backup really is running.<\/p>","1.50.3":"<p>One click now excludes everything a WordPress site can safely leave out of a backup \u2014 35 patterns, each with the reason next to it, including WordPress&#039;s own upgrade-temp-backup folder that quietly stores a second copy of every plugin and theme.<\/p>","1.48.0":"<p>Yedekalma can now keep itself up to date: turn on Settings \u2192 Automatic Update and new releases install themselves, so your backup plugin never quietly falls behind on fixes.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3617981,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3617981,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3617981,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.jpg":{"filename":"banner-1544x500.jpg","revision":3617989,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.jpg":{"filename":"banner-772x250.jpg","revision":3617989,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.10.0","1.10.1","1.10.10","1.10.11","1.10.2","1.10.3","1.10.4","1.10.5","1.10.6","1.10.7","1.10.8","1.10.9","1.11.0","1.11.1","1.11.2","1.11.3","1.11.4","1.11.5","1.11.6","1.11.7","1.12.0","1.13.0","1.14.0","1.18.0","1.19.0","1.20.0","1.22.0","1.22.1","1.22.2","1.28.0","1.29.0","1.30.0","1.31.0","1.32.0","1.33.0","1.34.0","1.35.0","1.36.0","1.37.0","1.40.0","1.43.0","1.44.0","1.44.1","1.44.2","1.44.3","1.44.5","1.44.6","1.45.0","1.46.0","1.46.1","1.46.2","1.47.0","1.48.0","1.49.0","1.49.1","1.49.2","1.49.3","1.49.4","1.49.5","1.49.6","1.49.7","1.49.8","1.49.9","1.50.0","1.50.1","1.50.10","1.50.11","1.50.12","1.50.2","1.50.3","1.50.9","1.51.1","1.51.4","1.52.0","1.53.0","1.53.2","1.53.3","1.54.0","1.54.1","1.54.2","1.54.3","1.54.4","1.54.5","1.54.7","1.54.8","1.54.9","1.55.0","1.55.1","1.55.2","1.55.3","1.55.4","1.55.5","1.55.6","1.55.7","1.55.8","1.56.0","1.57.0","1.57.1","1.57.10","1.57.11","1.57.12","1.57.13","1.57.2","1.57.3","1.57.4","1.57.5","1.57.6","1.57.7","1.57.8","1.58.0","1.58.1","1.58.2"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3625431,"resolution":"1","location":"assets","locale":"","width":1691,"height":816},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3625431,"resolution":"2","location":"assets","locale":"","width":1687,"height":807},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3625431,"resolution":"3","location":"assets","locale":"","width":1686,"height":820},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3625431,"resolution":"4","location":"assets","locale":"","width":1678,"height":826},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3625431,"resolution":"5","location":"assets","locale":"","width":1689,"height":770}},"screenshots":{"1":"Dashboard \u2014 one-click full, files-only or database backup; runs on your own server, no account needed.","2":"All backups \u2014 one-click restore or download, each with size and SHA-256 checksum.","3":"Built-in malware scanner \u2014 scan WordPress core, plugins and the active theme for injected code, web shells and backdoors.","4":"Settings \u2014 interface language and safe uninstall data handling.","5":"Optional Yedekalma Pro \u2014 connect to schedule off-site backups straight to your own cloud (Google Drive, S3, FTP) with client-side AES-256."}},"plugin_section":[],"plugin_tags":[151,274835,274836,274614,274615],"plugin_category":[59],"plugin_contributors":[271733],"plugin_business_model":[],"class_list":["post-332082","plugin","type-plugin","status-publish","hentry","plugin_tags-backup","plugin_tags-site-tasima","plugin_tags-virus-temizleme","plugin_tags-yedek-alma","plugin_tags-yedekleme","plugin_category-utilities-and-tools","plugin_contributors-kamkactemha","plugin_committers-kamkactemha"],"banners":{"banner":"https:\/\/ps.w.org\/yedekalma\/assets\/banner-772x250.jpg?rev=3617989","banner_2x":"https:\/\/ps.w.org\/yedekalma\/assets\/banner-1544x500.jpg?rev=3617989","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/yedekalma\/assets\/icon.svg?rev=3617981","icon":"https:\/\/ps.w.org\/yedekalma\/assets\/icon.svg?rev=3617981","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/yedekalma\/assets\/screenshot-1.png?rev=3625431","caption":"Dashboard \u2014 one-click full, files-only or database backup; runs on your own server, no account needed."},{"src":"https:\/\/ps.w.org\/yedekalma\/assets\/screenshot-2.png?rev=3625431","caption":"All backups \u2014 one-click restore or download, each with size and SHA-256 checksum."},{"src":"https:\/\/ps.w.org\/yedekalma\/assets\/screenshot-3.png?rev=3625431","caption":"Built-in malware scanner \u2014 scan WordPress core, plugins and the active theme for injected code, web shells and backdoors."},{"src":"https:\/\/ps.w.org\/yedekalma\/assets\/screenshot-4.png?rev=3625431","caption":"Settings \u2014 interface language and safe uninstall data handling."},{"src":"https:\/\/ps.w.org\/yedekalma\/assets\/screenshot-5.png?rev=3625431","caption":"Optional Yedekalma Pro \u2014 connect to schedule off-site backups straight to your own cloud (Google Drive, S3, FTP) with client-side AES-256."}],"raw_content":"<!--section=description-->\n<p>Yedekalma, <strong>WordPress yedekleme<\/strong> i\u015fini tek ekranda toplayan <strong>\u00fccretsiz bir yedek alma eklentisidir<\/strong>. Tek t\u0131kla sitenizin <strong>tam yede\u011fini<\/strong> al\u0131r \u2014 dosyalar <em>ve<\/em> veritaban\u0131 \u2014 ve ayn\u0131 ekrandan <strong>geri y\u00fckler<\/strong>. Ayr\u0131ca <strong>WordPress site ta\u015f\u0131ma<\/strong> (yeni sunucu veya yeni alan ad\u0131) yapar ve <strong>vir\u00fcs \/ zararl\u0131 yaz\u0131l\u0131m taramas\u0131<\/strong> ile bula\u015fm\u0131\u015f dosyalar\u0131 temizler. Yedekleme, geri y\u00fckleme, ta\u015f\u0131ma ve g\u00fcvenlik tek eklentide topland\u0131\u011f\u0131 i\u00e7in her i\u015f i\u00e7in ayr\u0131 bir araca ihtiyac\u0131n\u0131z olmaz.<\/p>\n\n<p>Her \u015fey kendi sunucunuzda \u00e7al\u0131\u015f\u0131r. Hesap, kay\u0131t veya API anahtar\u0131 gerekmez: kurun, etkinle\u015ftirin, <strong>Yedek Al<\/strong>'a bas\u0131n. <strong>Yedek dosyalar\u0131n\u0131z kendi hostingunuzda kal\u0131r<\/strong> ve diledi\u011finiz zaman ZIP olarak indirebilirsiniz.<\/p>\n\n<h4>Neler yapar?<\/h4>\n\n<ul>\n<li><strong>Site yedekleme<\/strong> \u2014 tema, eklenti ve y\u00fcklemeler dahil t\u00fcm dosyalar.<\/li>\n<li><strong>Veritaban\u0131 yedekleme<\/strong> \u2014 gzip s\u0131k\u0131\u015ft\u0131rmal\u0131 MySQL d\u00f6k\u00fcm\u00fc (<code>.sql.gz<\/code>), b\u00fcy\u00fck siteler i\u00e7in uygun.<\/li>\n<li><strong>Payla\u015f\u0131ml\u0131 hostingde \u00e7al\u0131\u015f\u0131r<\/strong> \u2014 <code>exec()<\/code> kapal\u0131 ve PHP limitleri dar olsa bile par\u00e7al\u0131 (zaman dilimli) \u00e7al\u0131\u015f\u0131p yede\u011fi tamamlar.<\/li>\n<li><strong>Art\u0131ml\u0131 yedekleme<\/strong> \u2014 dosyalar\u0131n ger\u00e7ek de\u011fi\u015fiklik zaman\u0131na bakar, de\u011fi\u015fen dosya asla atlanmaz.<\/li>\n<li><strong>Tek t\u0131kla geri y\u00fckleme<\/strong> \u2014 veritaban\u0131, eklentiler, temalar ve y\u00fcklemeler; ya da yaln\u0131zca se\u00e7ti\u011finiz par\u00e7a.<\/li>\n<li><strong>Elinizdeki ar\u015fivden geri y\u00fckleme<\/strong> \u2014 <code>.zip<\/code>, <code>.sql<\/code> veya <code>.sql.gz<\/code> dosyas\u0131n\u0131 s\u00fcr\u00fckleyip b\u0131rak\u0131n.<\/li>\n<li><strong>Site ta\u015f\u0131ma \/ alan ad\u0131 de\u011fi\u015ftirme<\/strong> \u2014 geri y\u00fckleme s\u0131ras\u0131nda site adresi veritaban\u0131nda otomatik g\u00fcncellenir.<\/li>\n<li><strong>Vir\u00fcs tarama<\/strong> \u2014 WordPress \u00e7ekirde\u011fi, eklentiler ve aktif temada kod enjeksiyonu, web shell ve arka kap\u0131 arar; bulunanlar\u0131 toplu silebilirsiniz.<\/li>\n<li><strong>Kendi bulutunuza g\u00f6nderim (iste\u011fe ba\u011fl\u0131)<\/strong> \u2014 Google Drive, Dropbox, OneDrive, Amazon S3 \/ S3 uyumlu, FTP \/ SFTP.<\/li>\n<li><strong>Zamanlanm\u0131\u015f otomatik yedekleme (iste\u011fe ba\u011fl\u0131)<\/strong> \u2014 g\u00fcnl\u00fck, haftal\u0131k, saatlik veya birka\u00e7 dakikada bir; saklama kural\u0131 ile.<\/li>\n<li><strong>AES-256 u\u00e7tan uca \u015fifreleme (BYOK)<\/strong> \u2014 parola sitenizden \u00e7\u0131kmaz.<\/li>\n<\/ul>\n\n<p>\u00dccretsiz bir <strong>yedekleme eklentisi<\/strong> ar\u0131yorsan\u0131z: geri y\u00fckleme, ta\u015f\u0131ma ve vir\u00fcs taramas\u0131 dahil hepsi \u00fccretsizdir; hi\u00e7biri \"premium\" kilidinin arkas\u0131nda de\u011fildir.<\/p>\n\n<h4>In English<\/h4>\n\n<p>Yedekalma is a free <strong>WordPress backup plugin<\/strong> that takes a one-click <strong>backup<\/strong> of your entire site \u2014 files <em>and<\/em> database \u2014 and <strong>restores<\/strong> it again from the same screen. It also <strong>migrates<\/strong> your WordPress site to a new host or domain and <strong>scans<\/strong> it for <strong>malware<\/strong>. One backup plugin covers backup, restore, migration and security, so you do not need a separate tool for each job.<\/p>\n\n<p>Everything runs on your own server. No account, no sign-up and no API key: install, activate, click <strong>Take Backup<\/strong>. Your backup archives stay on your hosting, and you can download them as a ZIP at any time.<\/p>\n\n<p>Looking for a <strong>free backup plugin<\/strong> that also does migration and malware scanning without a paywall? Yedekalma gives you a full <strong>WordPress backup<\/strong>, a <strong>database backup<\/strong>, one-click <strong>restore<\/strong>, site <strong>migration<\/strong> and a <strong>malware scanner<\/strong> in a single plugin \u2014 no premium unlock required for any of it.<\/p>\n\n<h4>Backup<\/h4>\n\n<ul>\n<li><strong>Full backup<\/strong> \u2014 every file (themes, plugins, uploads) plus the complete database.<\/li>\n<li><strong>Database backup<\/strong> \u2014 MySQL dump only, gzip compressed (<code>.sql.gz<\/code>) for large sites.<\/li>\n<li><strong>Files backup<\/strong> \u2014 site files only, without the database.<\/li>\n<li><strong>Works on shared hosting<\/strong> \u2014 chunked, time-sliced backup that finishes even when <code>exec()<\/code> is disabled and PHP limits are strict.<\/li>\n<li><strong>Incremental backup<\/strong> \u2014 compares real file modification times, so a changed file is never skipped.<\/li>\n<li><strong>Safe storage<\/strong> \u2014 local backups live in a hardened, non-browsable folder with unguessable file names.<\/li>\n<\/ul>\n\n<h4>Restore<\/h4>\n\n<ul>\n<li><strong>One-click restore<\/strong> of the database, plugins, themes and uploads straight from your dashboard.<\/li>\n<li><strong>Restore only what you need<\/strong> \u2014 pick just the database, just uploads, just plugins or the whole site.<\/li>\n<li><strong>Restore from an archive you already have<\/strong> \u2014 drag &amp; drop a <code>.zip<\/code>, <code>.sql<\/code> or <code>.sql.gz<\/code> file and restore from it.<\/li>\n<li><strong>Integrity checked<\/strong> \u2014 a truncated or corrupt archive is refused instead of half-applied, so a bad file can never damage a working site.<\/li>\n<li><strong>SHA-256 verification<\/strong> of every archive before a restore begins.<\/li>\n<\/ul>\n\n<h4>Migration<\/h4>\n\n<ul>\n<li><strong>Move your site to a new host<\/strong> \u2014 download the backup, install Yedekalma on the target server and restore.<\/li>\n<li><strong>Change domain safely<\/strong> \u2014 site URL and home URL are rewritten in the database automatically during the restore.<\/li>\n<li><strong>New database server<\/strong> \u2014 <code>wp-config.php<\/code> credentials can be updated as part of a restore.<\/li>\n<li><strong>Clone your website<\/strong> to a fresh install for disaster recovery or a redesign.<\/li>\n<\/ul>\n\n<h4>Malware scanner<\/h4>\n\n<ul>\n<li><strong>Security scan<\/strong> of PHP, JS and configuration files across WordPress core, your plugins and the active theme.<\/li>\n<li>Detects <strong>code injections, web shells and backdoors<\/strong> using malicious-pattern matching.<\/li>\n<li><strong>Persistent results<\/strong> \u2014 the scan report survives page reloads, so you can review it whenever you like.<\/li>\n<li><strong>Bulk clean<\/strong> \u2014 select detected files and delete them in one click.<\/li>\n<li><strong>Core protection<\/strong> \u2014 WordPress core files are shielded from accidental deletion while planted files can still be removed.<\/li>\n<\/ul>\n\n<h4>Optional cloud service \u2014 backup to your own cloud storage<\/h4>\n\n<p>Local backup, restore, migration and the malware scanner are complete on their own and never contact an external server. If you also want <strong>off-site backup<\/strong> copies, you can connect the optional Yedekalma cloud service (see <em>External services<\/em> below) to:<\/p>\n\n<ul>\n<li><strong>Backup to Google Drive<\/strong> \u2014 stream backups straight to your own Google Drive.<\/li>\n<li><strong>Backup to Dropbox and OneDrive<\/strong> \u2014 send archives to your own Dropbox or Microsoft OneDrive account.<\/li>\n<li><strong>Backup to Amazon S3<\/strong> and S3-compatible storage \u2014 Backblaze B2, Wasabi, Cloudflare R2 and MinIO.<\/li>\n<li><strong>Backup to FTP \/ SFTP<\/strong> \u2014 upload to any FTP or SFTP server you control.<\/li>\n<li>Run <strong>scheduled automatic backups<\/strong> \u2014 daily, weekly, hourly or as often as every few minutes for busy sites \u2014 with retention rules.<\/li>\n<li><strong>Table-level incremental database backup<\/strong> \u2014 only the database tables that actually changed are exported, so even very frequent backups stay small and fast; unchanged runs are skipped automatically.<\/li>\n<li>Encrypt archives with <strong>client-side AES-256 (BYOK)<\/strong> before they leave your server \u2014 the passphrase never leaves your site.<\/li>\n<\/ul>\n\n<h4>Languages<\/h4>\n\n<p>Yedekalma ships with English, Turkish (T\u00fcrk\u00e7e), German, Russian and Arabic translations.<\/p>\n\n<h3>External services<\/h3>\n\n<p>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 \u2014 all described below); the plugin's local backup, restore, migration and malware-scanner features work with no external connection at all.<\/p>\n\n<ul>\n<li><strong>Service URL:<\/strong> https:\/\/yedekalma.com<\/li>\n<li><strong>Terms of Service:<\/strong> https:\/\/yedekalma.com\/legal<\/li>\n<li><strong>Privacy Policy:<\/strong> https:\/\/yedekalma.com\/legal#privacy<\/li>\n<li><strong>Connect with Google (opt-in):<\/strong> 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.<\/li>\n<li><strong>Optional site registration (opt-in):<\/strong> 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.<\/li>\n<li><strong>Support form (opt-in, no account needed):<\/strong> The plugin has a <strong>Yedekalma \u2192 Support<\/strong> 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 \u2014 shown ticked, and you can untick it \u2014 additionally sends technical details of this installation: plugin, WordPress, PHP and MySQL versions, web server, site language, multisite flag, active theme name, the <em>number<\/em> of active plugins, PHP limits (<code>memory_limit<\/code>, <code>max_execution_time<\/code>, <code>upload_max_filesize<\/code>), whether ZipArchive and <code>exec()<\/code> 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.<\/li>\n<li><strong>Data Transmission:<\/strong> 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.<\/li>\n<\/ul>\n\n<!--section=installation-->\n<ol>\n<li>In your WordPress admin, go to <strong>Plugins \u2192 Add New<\/strong>.<\/li>\n<li>Search for <strong>Yedekalma<\/strong>.<\/li>\n<li>Click <strong>Install Now<\/strong>, then <strong>Activate<\/strong>.<\/li>\n<li>Open <strong>Yedekalma<\/strong> in the admin sidebar.<\/li>\n<li>Click <strong>Start without an account<\/strong> and take your first backup.<\/li>\n<\/ol>\n\n<p>Manual installation: upload the <code>yedekalma<\/code> folder to <code>\/wp-content\/plugins\/<\/code> and activate it from the Plugins screen.<\/p>\n\n<!--section=faq-->\n<dl>\n<dt id=\"wordpress%20sitemin%20yede%C4%9Fini%20nas%C4%B1l%20al%C4%B1r%C4%B1m%3F\"><h3>WordPress sitemin yede\u011fini nas\u0131l al\u0131r\u0131m?<\/h3><\/dt>\n<dd><p><strong>Yedekalma \u2192 Kontrol Paneli<\/strong>'ni a\u00e7\u0131n ve <strong>Yedek Al<\/strong>'a bas\u0131n. <strong>Tam Yedek<\/strong> (dosya + veritaban\u0131), <strong>Sadece Dosya<\/strong> veya <strong>Sadece Veritaban\u0131<\/strong> se\u00e7ebilirsiniz. Yedekleme kendi sunucunuzda par\u00e7a par\u00e7a \u00e7al\u0131\u015f\u0131r; bitti\u011finde ar\u015fivi ZIP olarak indirebilirsiniz.<\/p><\/dd>\n<dt id=\"veritaban%C4%B1%20yede%C4%9Fi%20nas%C4%B1l%20al%C4%B1n%C4%B1r%3F\"><h3>Veritaban\u0131 yede\u011fi nas\u0131l al\u0131n\u0131r?<\/h3><\/dt>\n<dd><p><strong>Yedek Al \u2192 Sadece Veritaban\u0131<\/strong> deyin. S\u0131k\u0131\u015ft\u0131r\u0131lm\u0131\u015f bir MySQL d\u00f6k\u00fcm\u00fc (<code>.sql.gz<\/code>) elde edersiniz; indirebilir veya daha sonra geri y\u00fckleyebilirsiniz.<\/p><\/dd>\n<dt id=\"yedek%20alma%20eklentisi%20%C3%BCcretsiz%20mi%3F\"><h3>Yedek alma eklentisi \u00fccretsiz mi?<\/h3><\/dt>\n<dd><p>Evet. Yedekleme, geri y\u00fckleme, ta\u015f\u0131ma ve vir\u00fcs taramas\u0131 hesap a\u00e7madan ve \u00fccret \u00f6demeden tam olarak \u00e7al\u0131\u015f\u0131r. \u0130ste\u011fe ba\u011fl\u0131 Yedekalma bulut hizmeti site d\u0131\u015f\u0131 (off-site) depolama ekler ve \u00fccretsiz bir ba\u015flang\u0131\u00e7 paketi vard\u0131r.<\/p><\/dd>\n<dt id=\"wordpress%20site%20ta%C5%9F%C4%B1ma%20nas%C4%B1l%20yap%C4%B1l%C4%B1r%3F\"><h3>WordPress site ta\u015f\u0131ma nas\u0131l yap\u0131l\u0131r?<\/h3><\/dt>\n<dd><p>Evet. Yede\u011fi indirin, yeni sunucuda Yedekalma'y\u0131 kurun ve ar\u015fivden geri y\u00fckleyin. Site adresi ve ana sayfa adresi veritaban\u0131nda otomatik olarak yeni alan ad\u0131na g\u00f6re g\u00fcncellenir.<\/p><\/dd>\n<dt id=\"yedekler%20nerede%20saklan%C4%B1yor%3F\"><h3>Yedekler nerede saklan\u0131yor?<\/h3><\/dt>\n<dd><p>Varsay\u0131lan olarak kendi hostingunuzda, d\u0131\u015far\u0131dan listelenemeyen korumal\u0131 bir klas\u00f6rde ve tahmin edilemez dosya adlar\u0131yla. \u0130sterseniz iste\u011fe ba\u011fl\u0131 bulut hizmetiyle kendi Google Drive, Dropbox, OneDrive, S3 veya FTP alan\u0131n\u0131za g\u00f6nderebilirsiniz \u2014 yede\u011fin i\u00e7eri\u011fi Yedekalma sunucular\u0131nda tutulmaz.<\/p><\/dd>\n<dt id=\"payla%C5%9F%C4%B1ml%C4%B1%20hostingde%20%C3%A7al%C4%B1%C5%9F%C4%B1r%20m%C4%B1%3F\"><h3>Payla\u015f\u0131ml\u0131 hostingde \u00e7al\u0131\u015f\u0131r m\u0131?<\/h3><\/dt>\n<dd><p>Evet. Yedekleme zaman dilimli par\u00e7alar halinde ilerler; <code>exec()<\/code> kapal\u0131 olsa ve PHP zaman\/bellek limitleri dar olsa bile tamamlan\u0131r. Sunucu yo\u011funluk nedeniyle iste\u011fi reddederse eklenti bekleyip kald\u0131\u011f\u0131 yerden devam eder.<\/p><\/dd>\n<dt id=\"wordpress%20vir%C3%BCs%20temizleme%20yapar%20m%C4%B1%3F\"><h3>WordPress vir\u00fcs temizleme yapar m\u0131?<\/h3><\/dt>\n<dd><p>Evet. <strong>Yedekalma \u2192 Zararl\u0131 Yaz\u0131l\u0131m Taramas\u0131<\/strong> ekran\u0131ndan tarama ba\u015flat\u0131n: WordPress \u00e7ekirde\u011fi, eklentiler ve aktif tema PHP\/JS ve yap\u0131land\u0131rma dosyalar\u0131 i\u00e7in kod enjeksiyonu, web shell ve arka kap\u0131 kal\u0131plar\u0131na kar\u015f\u0131 taran\u0131r. Bulunan dosyalar\u0131 tek t\u0131kla toplu silebilirsiniz; WordPress \u00e7ekirdek dosyalar\u0131 yanl\u0131\u015fl\u0131kla silinmeye kar\u015f\u0131 korunur. Vir\u00fcs temizleme \u00fccretsizdir, hesap a\u00e7man\u0131z gerekmez.<\/p><\/dd>\n<dt id=\"otomatik%20%28zamanlanm%C4%B1%C5%9F%29%20yedekleme%20var%20m%C4%B1%3F\"><h3>Otomatik (zamanlanm\u0131\u015f) yedekleme var m\u0131?<\/h3><\/dt>\n<dd><p>Evet, iste\u011fe ba\u011fl\u0131 bulut hizmetiyle. G\u00fcnl\u00fck, haftal\u0131k, saatlik ya da yo\u011fun siteler i\u00e7in birka\u00e7 dakikada bir otomatik yedekleme kurabilir, her biri i\u00e7in saklama kural\u0131 tan\u0131mlayabilirsiniz. Tek t\u0131kla manuel yedek her zaman \u00fccretsizdir ve zamanlama gerektirmez.<\/p><\/dd>\n<dt id=\"b%C3%BCy%C3%BCk%20siteleri%20%285%20gb%2C%2010%20gb%29%20yedekleyebilir%20mi%3F\"><h3>B\u00fcy\u00fck siteleri (5 GB, 10 GB) yedekleyebilir mi?<\/h3><\/dt>\n<dd><p>Evet. Yedekleme k\u00fc\u00e7\u00fck zaman dilimlerine b\u00f6l\u00fcnerek ilerler ve veritaban\u0131 do\u011frudan gzip s\u0131k\u0131\u015ft\u0131rmal\u0131 d\u00f6k\u00fcme ak\u0131t\u0131l\u0131r; b\u00f6ylece PHP s\u00fcre ve bellek limitlerine tak\u0131lmadan tamamlan\u0131r. \u00c7ok b\u00fcy\u00fck siteler i\u00e7in iste\u011fe ba\u011fl\u0131 bulut hizmetiyle ar\u015fivi hostinginizi doldurmadan do\u011frudan kendi Google Drive, S3 veya FTP alan\u0131n\u0131za g\u00f6nderebilirsiniz.<\/p><\/dd>\n<dt id=\"woocommerce%20ma%C4%9Fazam%C4%B1%20yedekler%20mi%3F\"><h3>WooCommerce ma\u011fazam\u0131 yedekler mi?<\/h3><\/dt>\n<dd><p>Evet. Tam yedek t\u00fcm WordPress veritaban\u0131n\u0131 i\u00e7erir \u2014 WooCommerce sipari\u015fleri, \u00fcr\u00fcnler, m\u00fc\u015fteriler ve ayarlar dosyalarla birlikte kaydedilir. Yo\u011fun ma\u011fazalarda iste\u011fe ba\u011fl\u0131 bulut hizmetiyle s\u0131k art\u0131ml\u0131 yedekleme kurup iki yedek aras\u0131ndaki yeni sipari\u015fleri de koruyabilirsiniz.<\/p><\/dd>\n<dt id=\"nas%C4%B1l%20destek%20alabilirim%3F%20%C3%9Cye%20olmam%20gerekiyor%20mu%3F\"><h3>Nas\u0131l destek alabilirim? \u00dcye olmam gerekiyor mu?<\/h3><\/dt>\n<dd><p>Hay\u0131r, \u00fcyelik gerekmez. WordPress y\u00f6netim panelinizde <strong>Yedekalma \u2192 Destek<\/strong> ekran\u0131n\u0131 a\u00e7\u0131n, sorununuzu yaz\u0131n ve g\u00f6nderin. Site adresiniz otomatik olarak eklenir; isterseniz PHP\/WordPress s\u00fcr\u00fcm\u00fc ve sunucu limitleri gibi teknik bilgileri de tek t\u0131kla iletebilirsiniz (ne g\u00f6nderilece\u011fini g\u00f6ndermeden \u00f6nce ekranda g\u00f6r\u00fcrs\u00fcn\u00fcz). Yan\u0131t, yazd\u0131\u011f\u0131n\u0131z e-posta adresine gelir \u2014 yedekalma.com hesab\u0131n\u0131z olmasa bile.<\/p><\/dd>\n<dt id=\"yedeklerimi%20google%20drive%27a%20g%C3%B6nderebilir%20miyim%3F\"><h3>Yedeklerimi Google Drive'a g\u00f6nderebilir miyim?<\/h3><\/dt>\n<dd><p>Evet, iste\u011fe ba\u011fl\u0131 Yedekalma bulut hizmetiyle. Ar\u015fiv sunucunuzdan do\u011frudan <strong>kendi<\/strong> Google Drive, Dropbox, OneDrive, Amazon S3 \/ S3 uyumlu veya FTP \/ SFTP alan\u0131n\u0131za aktar\u0131l\u0131r; Yedekalma bir kopyas\u0131n\u0131 saklamaz.<\/p><\/dd>\n<dt id=\"is%20this%20backup%20plugin%20free%3F\"><h3>Is this backup plugin free?<\/h3><\/dt>\n<dd><p>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.<\/p><\/dd>\n<dt id=\"is%20this%20a%20good%20free%20backup%20plugin%20for%20wordpress%3F\"><h3>Is this a good free backup plugin for WordPress?<\/h3><\/dt>\n<dd><p>Yedekalma is a free WordPress backup plugin that bundles full-site backup, database backup, one-click restore, site migration and a malware scanner \u2014 features that many plugins split between free and premium tiers. Everything runs on your own server and needs no account.<\/p><\/dd>\n<dt id=\"how%20do%20i%20back%20up%20my%20wordpress%20site%3F\"><h3>How do I back up my WordPress site?<\/h3><\/dt>\n<dd><p>Open <strong>Yedekalma \u2192 Dashboard<\/strong> and click <strong>Take Backup<\/strong>. Choose <strong>Full<\/strong> (files + database), <strong>Files Only<\/strong> or <strong>Database Only<\/strong>. The backup runs in time-sliced chunks on your own server and you can download the archive as a ZIP when it finishes.<\/p><\/dd>\n<dt id=\"how%20do%20i%20back%20up%20my%20wordpress%20database%3F\"><h3>How do I back up my WordPress database?<\/h3><\/dt>\n<dd><p>Open <strong>Yedekalma \u2192 Dashboard<\/strong>, click <strong>Take Backup<\/strong> and choose <strong>Database Only<\/strong>. You get a compressed MySQL dump (<code>.sql.gz<\/code>) that you can download or restore later.<\/p><\/dd>\n<dt id=\"can%20i%20back%20up%20a%20woocommerce%20store%3F\"><h3>Can I back up a WooCommerce store?<\/h3><\/dt>\n<dd><p>Yes. A full backup includes your entire WordPress database \u2014 WooCommerce orders, products, customers and settings \u2014 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.<\/p><\/dd>\n<dt id=\"can%20it%20back%20up%20large%20sites%20%285%20gb%2C%2010%20gb%20or%20more%29%3F\"><h3>Can it back up large sites (5 GB, 10 GB or more)?<\/h3><\/dt>\n<dd><p>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.<\/p><\/dd>\n<dt id=\"does%20it%20work%20on%20shared%20hosting%2C%20cpanel%2C%20plesk%20or%20directadmin%3F\"><h3>Does it work on shared hosting, cPanel, Plesk or DirectAdmin?<\/h3><\/dt>\n<dd><p>Yes. Yedekalma is a pure-PHP plugin with no server dependencies, so it works on any standard WordPress host \u2014 shared hosting, cPanel, Plesk, DirectAdmin or a managed platform. It does not need <code>exec()<\/code>, shell access or SSH.<\/p><\/dd>\n<dt id=\"does%20it%20work%20on%20litespeed%2C%20nginx%20and%20apache%3F\"><h3>Does it work on LiteSpeed, Nginx and Apache?<\/h3><\/dt>\n<dd><p>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.<\/p><\/dd>\n<dt id=\"can%20i%20use%20it%20to%20migrate%20my%20site%20to%20a%20new%20host%20or%20domain%3F\"><h3>Can I use it to migrate my site to a new host or domain?<\/h3><\/dt>\n<dd><p>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.<\/p><\/dd>\n<dt id=\"can%20i%20clone%20my%20website%20for%20disaster%20recovery%3F\"><h3>Can I clone my website for disaster recovery?<\/h3><\/dt>\n<dd><p>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.<\/p><\/dd>\n<dt id=\"where%20are%20my%20backups%20stored%3F\"><h3>Where are my backups stored?<\/h3><\/dt>\n<dd><p>In <code>wp-content\/uploads\/yedekalma-backups\/<\/code> 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.<\/p><\/dd>\n<dt id=\"can%20i%20back%20up%20to%20google%20drive%3F\"><h3>Can I back up to Google Drive?<\/h3><\/dt>\n<dd><p>Yes, through the optional Yedekalma cloud service. Backups stream directly from your server to <strong>your own<\/strong> Google Drive; Yedekalma never keeps a copy.<\/p><\/dd>\n<dt id=\"can%20i%20back%20up%20to%20dropbox%20or%20onedrive%3F\"><h3>Can I back up to Dropbox or OneDrive?<\/h3><\/dt>\n<dd><p>Yes. With the optional cloud service you can send scheduled backups to your own Dropbox or Microsoft OneDrive account.<\/p><\/dd>\n<dt id=\"does%20it%20support%20amazon%20s3%2C%20backblaze%20b2%20or%20wasabi%3F\"><h3>Does it support Amazon S3, Backblaze B2 or Wasabi?<\/h3><\/dt>\n<dd><p>Yes. The optional cloud service supports Amazon S3 and any S3-compatible storage \u2014 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.<\/p><\/dd>\n<dt id=\"can%20i%20back%20up%20to%20ftp%20or%20sftp%3F\"><h3>Can I back up to FTP or SFTP?<\/h3><\/dt>\n<dd><p>Yes. The optional cloud service can upload backups to any FTP or SFTP server you control. The credentials are encrypted on your own site.<\/p><\/dd>\n<dt id=\"does%20it%20support%20scheduled%20automatic%20backups%3F\"><h3>Does it support scheduled automatic backups?<\/h3><\/dt>\n<dd><p>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.<\/p><\/dd>\n<dt id=\"what%20is%20incremental%20backup%20and%20does%20it%20support%20it%3F\"><h3>What is incremental backup and does it support it?<\/h3><\/dt>\n<dd><p>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 \u2014 unchanged runs are skipped automatically.<\/p><\/dd>\n<dt id=\"can%20i%20encrypt%20my%20backups%3F\"><h3>Can I encrypt my backups?<\/h3><\/dt>\n<dd><p>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.<\/p><\/dd>\n<dt id=\"how%20does%20the%20malware%20scanner%20work%3F\"><h3>How does the malware scanner work?<\/h3><\/dt>\n<dd><p>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.<\/p><\/dd>\n<dt id=\"how%20do%20i%20restore%20a%20wordpress%20backup%20for%20free%3F\"><h3>How do I restore a WordPress backup for free?<\/h3><\/dt>\n<dd><p>Open <strong>Yedekalma \u2192 Backups<\/strong>, find the backup you want and click <strong>Restore<\/strong>. You can restore the database, plugins, themes and uploads separately or all at once. You can also drag &amp; drop a <code>.zip<\/code>, <code>.sql<\/code> or <code>.sql.gz<\/code> archive you already have and restore from it \u2014 no account and no payment required.<\/p><\/dd>\n<dt id=\"can%20i%20restore%20only%20the%20database%3F\"><h3>Can I restore only the database?<\/h3><\/dt>\n<dd><p>Yes. When restoring, pick the <strong>Database<\/strong> 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.<\/p><\/dd>\n<dt id=\"can%20i%20restore%20only%20the%20uploads%2C%20media%20or%20a%20single%20component%3F\"><h3>Can I restore only the uploads, media or a single component?<\/h3><\/dt>\n<dd><p>Yes. Restore offers each section your backup contains \u2014 database, plugins, themes and uploads \u2014 so you can restore just your media\/uploads, just plugins or any single part instead of the whole site.<\/p><\/dd>\n<dt id=\"is%20there%20a%20free%20wordpress%20migration%20plugin%20here%3F\"><h3>Is there a free WordPress migration plugin here?<\/h3><\/dt>\n<dd><p>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 <code>wp-config.php<\/code> credentials can be updated during the restore.<\/p><\/dd>\n<dt id=\"how%20can%20i%20scan%20wordpress%20for%20malware%20without%20a%20subscription%3F\"><h3>How can I scan WordPress for malware without a subscription?<\/h3><\/dt>\n<dd><p>The built-in malware scanner is completely free and needs no account. Open <strong>Yedekalma \u2192 Malware Scanner<\/strong> 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.<\/p><\/dd>\n<dt id=\"how%20often%20should%20i%20back%20up%20my%20wordpress%20site%3F\"><h3>How often should I back up my WordPress site?<\/h3><\/dt>\n<dd><p>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.<\/p><\/dd>\n<dt id=\"what%20happens%20to%20my%20backups%20if%20i%20delete%20the%20plugin%3F\"><h3>What happens to my backups if I delete the plugin?<\/h3><\/dt>\n<dd><p>Nothing. Local archives under <code>wp-content\/uploads\/yedekalma-backups\/<\/code> stay where they are unless you remove them yourself, and anything in your own cloud storage stays there too.<\/p><\/dd>\n<dt id=\"t%C3%BCrk%C3%A7e%20destekliyor%20mu%3F\"><h3>T\u00fcrk\u00e7e destekliyor mu?<\/h3><\/dt>\n<dd><p>Evet. Yedekalma tamamen T\u00fcrk\u00e7e aray\u00fcze sahiptir: site yedekleme, veritaban\u0131 yedekleme, yedekten geri y\u00fckleme, site ta\u015f\u0131ma ve vir\u00fcs\/zararl\u0131 yaz\u0131l\u0131m taramas\u0131 i\u015flemlerinin t\u00fcm\u00fcn\u00fc T\u00fcrk\u00e7e olarak yapabilirsiniz.<\/p><\/dd>\n<dt id=\"is%20multisite%20supported%3F\"><h3>Is Multisite supported?<\/h3><\/dt>\n<dd><p>Not in version 1 \u2014 a separate plugin instance per site is required. Full Multisite support is on the roadmap.<\/p><\/dd>\n<dt id=\"is%20it%20gdpr%20%2F%20kvkk%20compliant%3F\"><h3>Is it GDPR \/ KVKK compliant?<\/h3><\/dt>\n<dd><p>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.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<p>For the full history of older releases, see <code>changelog.txt<\/code> in the plugin folder.<\/p>\n\n<h4>1.58.2 \u2014 2026-08-22<\/h4>\n\n<ul>\n<li><strong>\"Pro \u00f6zelliklerini a\u00e7mak i\u00e7in ba\u011flan\u0131n\" ba\u015fl\u0131\u011f\u0131 yeniden en \u00fcstte.<\/strong> 1.58.1'de tan\u0131t\u0131m\nb\u00f6l\u00fcm\u00fc onay kutular\u0131n\u0131n \u00fcst\u00fcne al\u0131n\u0131rken ba\u015fl\u0131\u011f\u0131n da \u00fcst\u00fcne ge\u00e7mi\u015fti; ekran\u0131n ne i\u00e7in\noldu\u011funu s\u00f6yleyen \u00e7a\u011fr\u0131, uzun anlat\u0131m\u0131n alt\u0131nda kal\u0131yordu. S\u0131ra art\u0131k \u015f\u00f6yle:\n<strong>ba\u015fl\u0131k \u2192 k\u0131sa \u00f6zet \u2192 \"Yedekalma nedir \/ verim nereye gidiyor\" \u2192 onay \u2192 ba\u011flan.<\/strong>\nB\u00f6ylece hem \u00e7a\u011fr\u0131 ilk g\u00f6r\u00fcnen \u015fey oluyor, hem de ayd\u0131nlatma r\u0131zadan \u00f6nce geliyor.<\/li>\n<\/ul>\n\n<h4>1.58.1 \u2014 2026-08-22<\/h4>\n\n<ul>\n<li><strong>Ba\u011flanmadan \u00f6nce ne oldu\u011funu okuyorsunuz.<\/strong> \"Yedekalma nedir, yede\u011fim nerede\nhaz\u0131rlan\u0131yor, verim nereye gidiyor\" anlat\u0131m\u0131 art\u0131k onay kutular\u0131n\u0131n ve \"Google ile\nba\u011flan\" d\u00fc\u011fmesinin <strong>\u00fcst\u00fcnde<\/strong>. \u00d6nceden d\u00fc\u011fmenin alt\u0131ndayd\u0131; yani kullan\u0131c\u0131 \u00f6nce karar\nverip sonra okuyordu. Onay ancak bilgilendirmeden sonra anlaml\u0131d\u0131r \u2014 KVKK'da da\nayd\u0131nlatma, a\u00e7\u0131k r\u0131zadan \u00f6nce gelir.<\/li>\n<li>S\u00f6zle\u015fme bilgisi al\u0131namad\u0131\u011f\u0131nda art\u0131k <strong>\"Tekrar dene\"<\/strong> ba\u011flant\u0131s\u0131 var. \u00d6nceden tek \u00e7are\nkoca y\u00f6netim sayfas\u0131n\u0131 yeniden y\u00fcklemekti; ge\u00e7ici bir a\u011f hatas\u0131 gereksiz bir \u00e7\u0131kmaza\nsokuyordu.<\/li>\n<\/ul>\n\n<h4>1.58.0 \u2014 2026-08-22<\/h4>\n\n<ul>\n<li><strong>Yedekalma hesab\u0131 a\u00e7\u0131l\u0131rken art\u0131k a\u00e7\u0131k r\u0131za al\u0131n\u0131yor (KVKK).<\/strong> \"Google ile ba\u011flan\"\nd\u00fc\u011fmesi yaln\u0131z ba\u011flant\u0131 kurmuyor \u2014 yedekalma.com'da sizin ad\u0131n\u0131za bir <strong>m\u00fc\u015fteri hesab\u0131\na\u00e7\u0131yor<\/strong>. Panelden kay\u0131t olurken Kullan\u0131m Ko\u015fullar\u0131 ve KVKK ayd\u0131nlatma metni onay\u0131\nzorunluyken, bu yol onlar\u0131 hi\u00e7 sormuyordu. Art\u0131k iki onay kutusu i\u015faretlenmeden d\u00fc\u011fme\na\u00e7\u0131lm\u0131yor; onay\u0131n\u0131z tarih, s\u00fcr\u00fcm ve IP ile birlikte kaydediliyor.<\/li>\n<li>S\u00f6zle\u015fme ba\u011flant\u0131lar\u0131 yeni sekmede yedekalma.com \u00fczerinden a\u00e7\u0131l\u0131r. Metinler ve s\u00fcr\u00fcm\nbilgisi eklentiye g\u00f6m\u00fcl\u00fc DE\u011e\u0130L, panelden \u00e7ekilir \u2014 b\u00f6ylece belgeler g\u00fcncellendi\u011finde\neklentiyi yeniden yay\u0131nlamak gerekmez ve onay kayd\u0131n\u0131z her zaman ger\u00e7ekten okudu\u011funuz\nmetnin s\u00fcr\u00fcm\u00fcn\u00fc g\u00f6sterir.<\/li>\n<li>S\u00f6zle\u015fme bilgisi al\u0131namazsa ba\u011flant\u0131 <strong>ba\u015flat\u0131lmaz<\/strong> ve sebebi ekranda yaz\u0131l\u0131r. Bilin\u00e7li\nbir karar: hangi metne onay verildi\u011fi bilinmeden hesap a\u00e7mak, kayd\u0131 ba\u015ftan de\u011fersiz k\u0131lar.<\/li>\n<\/ul>\n\n<h4>1.57.13 \u2014 2026-08-21<\/h4>\n\n<ul>\n<li><strong>B\u00fcy\u00fck sat\u0131rl\u0131 veritabanlar\u0131nda yedek art\u0131k bellek yetmedi\u011fi i\u00e7in durmuyor.<\/strong> Veritaban\u0131\nd\u00f6k\u00fcm\u00fc partileri \u015fimdiye kadar SATIR SAYISIYLA \u00f6l\u00e7\u00fcl\u00fcyordu (sabit 500). Sat\u0131r say\u0131s\u0131\nbelle\u011fi \u00f6l\u00e7mez: \u015fi\u015fmi\u015f bir ayar kayd\u0131 ya da serile\u015ftirilmi\u015f b\u00fcy\u00fck bir meta de\u011feri tek\nba\u015f\u0131na megabaytlarca olabilir. B\u00f6yle bir sitede 500 sat\u0131r PHP bellek s\u0131n\u0131r\u0131n\u0131 a\u015f\u0131yor ve\nyedek her denemede ayn\u0131 noktada, birka\u00e7 saniye i\u00e7inde \u00f6l\u00fcyordu. Parti boyutu art\u0131k\ntablonun ortalama sat\u0131r b\u00fcy\u00fckl\u00fc\u011f\u00fcne g\u00f6re BAYT b\u00fct\u00e7esiyle belirleniyor; \u00f6l\u00e7\u00fcm al\u0131namazsa\neski davran\u0131\u015f aynen korunur (parti yaln\u0131zca k\u00fc\u00e7\u00fclt\u00fcl\u00fcr, asla b\u00fcy\u00fct\u00fclmez).<\/li>\n<li><strong>Her partiden sonra WordPress'in tuttu\u011fu ikinci kopya serbest b\u0131rak\u0131l\u0131yor.<\/strong> WordPress\nsorgu sonucunu ayr\u0131ca kendi i\u00e7inde saklar ve bir sonraki sorguya kadar b\u0131rakmaz; bu,\nd\u00f6k\u00fcm s\u0131ras\u0131nda tepe bellek kullan\u0131m\u0131n\u0131 gereksiz yere iki kat\u0131na \u00e7\u0131kar\u0131yordu. D\u00fczeltme\nyedekleme, d\u00f6k\u00fcm ve geri y\u00fckleme (ara\/de\u011fi\u015ftir) yollar\u0131n\u0131n \u00dc\u00c7\u00dcNE de uyguland\u0131.<\/li>\n<\/ul>\n\n<h4>1.57.12 \u2014 2026-08-20<\/h4>\n\n<ul>\n<li><strong>Yedek biletleri art\u0131k adres sat\u0131r\u0131nda ta\u015f\u0131nm\u0131yor.<\/strong> Y\u00fckleme\/indirme isteklerinde\nkullan\u0131lan tek kullan\u0131ml\u0131k bilet, sunucu eri\u015fim kay\u0131tlar\u0131na ve aradaki vekillere\nd\u00fc\u015fmesin diye yaln\u0131zca istek ba\u015fl\u0131\u011f\u0131nda g\u00f6nderiliyor. Eski s\u00fcr\u00fcm al\u0131c\u0131 mod\u00fcllerle\nuyum korunuyor: kar\u015f\u0131 taraf yeni bi\u00e7imi tan\u0131m\u0131yorsa \u00f6nceki y\u00f6ntem kullan\u0131lmaya devam eder.<\/li>\n<\/ul>\n\n<h4>1.57.11 \u2014 2026-08-20<\/h4>\n\n<ul>\n<li><strong>Yar\u0131m kalan y\u00fckleme art\u0131k kilitlenmiyor.<\/strong> B\u00fcy\u00fck bir yedek par\u00e7a par\u00e7a g\u00f6nderilirken\nson par\u00e7an\u0131n yan\u0131t\u0131 kaybolursa, eklenti \"her \u015fey kar\u015f\u0131da\" cevab\u0131n\u0131 al\u0131p g\u00f6nderimi\ntamamlanm\u0131\u015f saym\u0131yor; tamamlama sinyalini yeniden g\u00f6nderiyor. \u00d6nceden bu durumda ar\u015fiv\nhedefe hi\u00e7 ta\u015f\u0131nm\u0131yor, her yeni deneme ayn\u0131 noktada ba\u015far\u0131s\u0131z oluyor ve yedek\ntamamlanam\u0131yordu.<\/li>\n<li><strong>Yedek biletleri art\u0131k istek ba\u015fl\u0131\u011f\u0131nda da g\u00f6nderiliyor.<\/strong> Sunucu eri\u015fim kay\u0131tlar\u0131na ve\naradaki vekillere adres sat\u0131r\u0131yla birlikte d\u00fc\u015fmemesi i\u00e7in; eski s\u00fcr\u00fcm al\u0131c\u0131larla uyum\nkorunuyor.<\/li>\n<\/ul>\n\n<h4>1.57.10 \u2014 2026-08-20<\/h4>\n\n<ul>\n<li><strong>Yedek klas\u00f6r\u00fc art\u0131k kendi kendini yedeklemiyor.<\/strong> Klas\u00f6r ad\u0131 yeniden adland\u0131r\u0131lamay\u0131p\neskisi yerinde kald\u0131\u011f\u0131nda, eski klas\u00f6r yede\u011fin i\u00e7ine giriyordu \u2014 ar\u015fiv kendi eski\nar\u015fivlerini ta\u015f\u0131yor ve gereksiz yere b\u00fcy\u00fcyordu. Hari\u00e7 tutma art\u0131k t\u00fcm yedek klas\u00f6rlerini\ntan\u0131yor (yaln\u0131zca g\u00fcncel ad\u0131 de\u011fil).<\/li>\n<li><strong>Sa\u011flamas\u0131 olmayan katman art\u0131k geri y\u00fcklemede a\u00e7\u0131k onay ister.<\/strong> B\u00fct\u00fcnl\u00fck do\u011frulamas\u0131\nyap\u0131lamayan bir yedek katman\u0131 sessizce uygulanm\u0131yor; ne oldu\u011fu ekranda yaz\u0131yor ve\nkullan\u0131c\u0131 bilerek onaylamadan i\u015flem ba\u015flam\u0131yor.<\/li>\n<\/ul>\n\n<h4>1.57.9 \u2014 2026-08-20<\/h4>\n\n<ul>\n<li><strong>Par\u00e7al\u0131 yedekte kesik ar\u015fiv korumas\u0131.<\/strong> Ar\u015fiv, b\u00fcy\u00fck sitelerde birden \u00e7ok istekte\npar\u00e7a par\u00e7a yaz\u0131l\u0131r. Bir par\u00e7a yar\u0131da kesilirse (hosting zaman a\u015f\u0131m\u0131, bellek s\u0131n\u0131r\u0131)\nayn\u0131 dosya ikinci kez yaz\u0131labiliyor ve ar\u015fiv tutars\u0131z h\u00e2le gelebiliyordu. Yaz\u0131c\u0131 art\u0131k\nar\u015fivin yan kayd\u0131n\u0131 okuyup hangi dosyalar\u0131n ger\u00e7ekten TAM yaz\u0131ld\u0131\u011f\u0131n\u0131 do\u011fruluyor;\nyar\u0131m kalm\u0131\u015f bir girdi \"tamam\" say\u0131lm\u0131yor.<\/li>\n<li><strong>Vir\u00fcs tarama ekran\u0131nda dosya ad\u0131 ka\u00e7\u0131\u015f\u0131.<\/strong> Taranan bir dosyan\u0131n ad\u0131 ekrana\nka\u00e7\u0131r\u0131lmadan bas\u0131l\u0131yordu; siteye k\u00f6t\u00fcc\u00fcl adl\u0131 bir dosya b\u0131rakabilen biri, tarama\nekran\u0131n\u0131 a\u00e7an y\u00f6neticinin taray\u0131c\u0131s\u0131nda kod \u00e7al\u0131\u015ft\u0131rabilirdi.<\/li>\n<li><strong>Yedek klas\u00f6r\u00fc ad\u0131.<\/strong> Klas\u00f6r ad\u0131 yeniden olu\u015fturulurken tahmin edilebilir bir ada\nd\u00fc\u015febiliyordu; art\u0131k her durumda rastgele ad \u00fcretiliyor ve mevcut yedek kay\u0131tlar\u0131\n\u00f6ks\u00fcz kalm\u0131yor.<\/li>\n<li><strong>Manuel yedekte ge\u00e7ici dosya konumu.<\/strong> wp-admin \u00fczerinden al\u0131nan yedeklerde\nveritaban\u0131 d\u00f6k\u00fcm\u00fc ve ar\u015fiv, baz\u0131 sunucularda web'den eri\u015filebilen bir klas\u00f6re\nyaz\u0131labiliyordu; art\u0131k sertle\u015ftirilmi\u015f ge\u00e7ici klas\u00f6r kullan\u0131l\u0131yor.<\/li>\n<li><strong>Hari\u00e7 tutma listesi.<\/strong> Virg\u00fclle ayr\u0131lm\u0131\u015f sat\u0131rlar ve nicelik aral\u0131\u011f\u0131 i\u00e7eren d\u00fczenli\nifadeler (<code>\\d{1,3}<\/code> gibi) art\u0131k mod\u00fclle birebir ayn\u0131 bi\u00e7imde yorumlan\u0131yor \u2014 panelde\ng\u00f6r\u00fcnen kural say\u0131s\u0131 ile yede\u011fe ger\u00e7ekten uygulanan kural ayn\u0131.<\/li>\n<\/ul>\n\n<h4>1.57.8 \u2014 2026-08-19<\/h4>\n\n<ul>\n<li><strong>G\u00fcvenlik\/kararl\u0131l\u0131k: bozuk ya da k\u00f6t\u00fcc\u00fcl bir \u015fifreli yedek art\u0131k belle\u011fi t\u00fcketip\ngeri y\u00fcklemeyi \u00f6ld\u00fcremiyor.<\/strong> \u015eifreli ar\u015fivler \u00e7er\u00e7eve \u00e7er\u00e7eve okunur ve her \u00e7er\u00e7evenin\nba\u015f\u0131nda 4 baytl\u0131k bir uzunluk alan\u0131 vard\u0131r. Do\u011frulama ge\u00e7i\u015finde (HMAC) bu uzunluk i\u00e7in\nbir \u00fcst s\u0131n\u0131r YOKTU \u2014 dosya bozulmu\u015f ya da kasten de\u011fi\u015ftirilmi\u015fse tek bir \u00e7er\u00e7eve 4 GB'a\nkadar okuma istetebiliyor ve PHP \"Allowed memory size exhausted\" ile \u00f6l\u00fcyordu; WordPress\ntaraf\u0131nda bu, geri y\u00fcklemenin 500 ile d\u00fc\u015fmesi demek. \u00c7\u00f6zme ge\u00e7i\u015finde s\u0131n\u0131r zaten vard\u0131\nama do\u011frulama ge\u00e7i\u015fi ONDAN \u00d6NCE ko\u015ftu\u011fu i\u00e7in s\u0131ra ona hi\u00e7 gelmiyordu. S\u0131n\u0131r art\u0131k her\niki ge\u00e7i\u015fte de var (me\u015fru azami \u00e7er\u00e7eve 1 MB; s\u0131n\u0131r 5 MB).<\/li>\n<li>Not: bu, ayn\u0131 hatan\u0131n \u00fc\u00e7\u00fcnc\u00fc kopyas\u0131yd\u0131. Panel mod\u00fcl\u00fc ve sunucu taraf\u0131ndaki kopyalar ayn\u0131\ng\u00fcn d\u00fczeltilmi\u015fti; eklentideki kopyay\u0131 otomatik \"ikiz parite\" kap\u0131m\u0131z yakalad\u0131.<\/li>\n<\/ul>\n\n<h4>1.57.7 \u2014 2026-08-19<\/h4>\n\n<ul>\n<li><strong>Yeni: geri y\u00fcklemede \"sunucu yap\u0131land\u0131rma dosyalar\u0131n\u0131 da geri y\u00fckle\" se\u00e7ene\u011fi.<\/strong> 1.57.6'dan\nberi <code>wp-config.php<\/code>, <code>.htaccess<\/code> ve <code>.user.ini<\/code> geri y\u00fcklemede korunuyordu \u2014 do\u011fru varsay\u0131lan,\n\u00e7\u00fcnk\u00fc yedek al\u0131nd\u0131\u011f\u0131ndan bu yana veritaban\u0131 bilgileriniz ya da hosting sunucunuz de\u011fi\u015ftiyse eski\nayarlar\u0131n geri gelmesi siteyi ONARMAK yerine D\u00dc\u015e\u00dcR\u00dcR. Ama bu \u00fc\u00e7 dosyay\u0131 <em>bilerek<\/em> geri istemenin\nhi\u00e7bir yolu yoktu (sunucu ta\u015f\u0131mas\u0131ndan sonra eski <code>.htaccess<\/code> kurallar\u0131n\u0131 geri almak gibi).\nArt\u0131k geri y\u00fckleme penceresinde a\u00e7\u0131k bir onay kutusu var: i\u015faretlemedi\u011finiz s\u00fcrece davran\u0131\u015f\nayn\u0131 (dosyalar korunur), kutu her a\u00e7\u0131l\u0131\u015fta kapal\u0131 ba\u015flar ve \"Sadece Veritaban\u0131\" modunda hi\u00e7\ng\u00f6r\u00fcnmez.<\/li>\n<li><strong>Yeni uyar\u0131: geri y\u00fcklenen wp-config.php farkl\u0131 bir AUTH_KEY ta\u015f\u0131yorsa art\u0131k s\u00f6yl\u00fcyoruz.<\/strong>\nPanel ba\u011flant\u0131n\u0131z ve yedek \u015fifreleme (BYOK) parolan\u0131z bu sitede AUTH_KEY'den t\u00fcretilen bir\nanahtarla \u015fifreli saklan\u0131r. Eski bir sunucudan gelen wp-config.php geri y\u00fcklenirse ikisi de\nokunamaz h\u00e2le gelir \u2014 \u00f6nceden bunu hi\u00e7bir yerde g\u00f6remiyor, ancak bir sonraki yedek\nba\u015far\u0131s\u0131z olunca fark ediyordunuz. Art\u0131k dosya yaz\u0131lmadan \u00d6NCE \u00f6l\u00e7\u00fcl\u00fcyor ve sonu\u00e7 ekran\u0131nda\nne yapman\u0131z gerekti\u011fi yaz\u0131yor (paneli yeniden ba\u011flay\u0131n, \u015fifreleme parolan\u0131z\u0131 yeniden girin).<\/li>\n<li><strong>Geri y\u00fckleme sonucu art\u0131k ne oldu\u011funu S\u00d6YL\u00dcYOR.<\/strong> \"Ba\u015far\u0131yla tamamland\u0131\" mesaj\u0131n\u0131n alt\u0131nda\nyap\u0131land\u0131rma dosyalar\u0131n\u0131n korunup korunmad\u0131\u011f\u0131 ve \u2014 yedek bir sa\u011flama (SHA-256) kayd\u0131\nta\u015f\u0131m\u0131yorsa \u2014 ar\u015fivin yaln\u0131zca YAPISAL olarak do\u011fruland\u0131\u011f\u0131 yaz\u0131yor. Bu bilgiler 1.57.6'dan beri\n\u00fcretiliyordu ama ekrana hi\u00e7 gelmiyordu; \u00fcretilip g\u00f6sterilmeyen uyar\u0131, verilmemi\u015f uyar\u0131d\u0131r.<\/li>\n<li><strong>D\u00fczeltildi: \"Al\u0131c\u0131 Mod\u00fcl\" hedefine yedek y\u00fcklenemiyordu.<\/strong> Kendi sunucunuza kurdu\u011funuz\nAl\u0131c\u0131 Mod\u00fcl'\u00fc depolama hedefi olarak se\u00e7tiyseniz, WordPress eklentisi bu y\u00fckleme y\u00f6ntemini\nH\u0130\u00c7 uygulam\u0131yordu: yedek haz\u0131rlan\u0131yor, sonra y\u00fckleme ad\u0131m\u0131nda d\u00fc\u015f\u00fcyordu. (Panel mod\u00fcl\u00fc bu\ny\u00f6ntemi destekliyordu, eklenti desteklemiyordu.) Art\u0131k destekleniyor \u2014 b\u00fcy\u00fck ar\u015fivlerde\npar\u00e7al\u0131 ve kopan ba\u011flant\u0131da kald\u0131\u011f\u0131 yerden devam edebilen bi\u00e7imde.<\/li>\n<\/ul>\n\n<h4>1.57.6 \u2014 2026-08-19<\/h4>\n\n<ul>\n<li><strong>D\u00fczeltildi: wp-admin'den BULUT yede\u011fini geri y\u00fckleme her zaman \"403\" veriyordu.<\/strong> Yerel\n(bu sunucudaki) yedeklerden geri y\u00fckleme \u00e7al\u0131\u015f\u0131yordu, ama bulut hedefinizdeki (Google\nDrive\/S3\/FTP) yede\u011fi wp-admin'den geri y\u00fcklemeye \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131zda i\u015flem daima yetki hatas\u0131yla\nd\u00fc\u015f\u00fcyordu. Gerekli kimlik ba\u015fl\u0131\u011f\u0131 iki \u00e7a\u011fr\u0131 yerinden yaln\u0131z birine eklenmi\u015fti. Felaket an\u0131nda\nilk basaca\u011f\u0131n\u0131z d\u00fc\u011fme buydu; art\u0131k iki yol da TEK bir kap\u0131dan ge\u00e7iyor.<\/li>\n<li><strong>D\u00fczeltildi: sembolik ba\u011fl\u0131 site k\u00f6k\u00fcnde geri y\u00fckleme \"ba\u015far\u0131l\u0131\" diyor ama H\u0130\u00c7B\u0130R dosyay\u0131\nyazm\u0131yordu.<\/strong> Bir\u00e7ok payla\u015f\u0131ml\u0131 hostingde <code>public_html<\/code> ger\u00e7ek bir klas\u00f6r de\u011fil, ba\u015fka bir\nyola i\u015faret eden bir ba\u011fd\u0131r. Eklenti site k\u00f6k\u00fcn\u00fc \u00e7\u00f6z\u00fcmlemeden kar\u015f\u0131la\u015ft\u0131rd\u0131\u011f\u0131 i\u00e7in o\nsunucularda ar\u015fivdeki her dosya sessizce \"atland\u0131\" say\u0131l\u0131yor, i\u015flem yine de \"Geri y\u00fckleme\nba\u015far\u0131yla tamamland\u0131\" diyordu \u2014 site ONARILMAMI\u015e oluyordu ve bu ancak felaket g\u00fcn\u00fcnde\nanla\u015f\u0131l\u0131yordu. K\u00f6k art\u0131k \u00e7\u00f6z\u00fcmleniyor; ayr\u0131ca <strong>ar\u015fivde dosya varken hi\u00e7biri yaz\u0131lamad\u0131ysa\nbu art\u0131k bir HATADIR<\/strong>, ba\u015far\u0131 de\u011fil. Ayn\u0131 k\u00f6k neden Pro klas\u00f6r gezginini de o hostlarda\nkullan\u0131lamaz h\u00e2le getiriyordu; o da d\u00fczeldi.<\/li>\n<li><strong>Geri y\u00fckleme \u00f6ncesi ar\u015fiv do\u011frulamas\u0131 sertle\u015fti.<\/strong> Bir yedek katman\u0131 sa\u011flama (SHA-256)\nta\u015f\u0131m\u0131yorsa eskiden H\u0130\u00c7B\u0130R b\u00fct\u00fcnl\u00fck kontrol\u00fc yap\u0131lm\u0131yordu; indirmenin ba\u015far\u0131s\u0131 yaln\u0131zca\n\"dosya 22 bayttan b\u00fcy\u00fck m\u00fc\" ile \u00f6l\u00e7\u00fcl\u00fcyordu (22 bayt = bo\u015f bir zip). Art\u0131k indirilen boyut\nsunucunun bildirdi\u011fi boyutla kar\u015f\u0131la\u015ft\u0131r\u0131l\u0131yor (HTTP\/FTP\/SFTP), ar\u015fiv sitenizin \u00fczerine\nyaz\u0131lmadan \u00d6NCE i\u00e7erik tutarl\u0131l\u0131\u011f\u0131 denetleniyor ve yar\u0131m\/kesik aktar\u0131m \"ba\u015far\u0131l\u0131\" say\u0131lm\u0131yor.<\/li>\n<li><strong>D\u00fczeltildi: hari\u00e7 tutma kal\u0131plar\u0131 hostinga g\u00f6re FARKLI davran\u0131yordu.<\/strong> <code>logs[0-9]<\/code> gibi\nkarakter aral\u0131klar\u0131 ve b\u00fcy\u00fck\/k\u00fc\u00e7\u00fck harf duyarl\u0131l\u0131\u011f\u0131, PHP'nin <code>fnmatch<\/code> fonksiyonu bulunmayan\nsunucularda ba\u015fka t\u00fcrl\u00fc yorumlan\u0131yordu \u2014 yani ayn\u0131 eklenti, ayn\u0131 kal\u0131p, iki hostta \u0130K\u0130 FARKLI\nar\u015fiv i\u00e7eri\u011fi \u00fcretebiliyordu ve size hi\u00e7bir uyar\u0131 gitmiyordu. \u0130ki yol art\u0131k birebir ayn\u0131\nkarar\u0131 veriyor.<\/li>\n<li><strong>D\u00fczeltildi: geri y\u00fcklemede tam veritaban\u0131 d\u00f6k\u00fcm\u00fc sunucuda kalabiliyordu.<\/strong> \u0130\u015flem bir hata\nya da zaman a\u015f\u0131m\u0131yla yar\u0131da kesilirse, ge\u00e7ici olarak a\u00e7\u0131lan <code>.sql.gz<\/code> d\u00f6k\u00fcm\u00fc y\u00fckleme\nklas\u00f6r\u00fcnde kal\u0131yordu. Art\u0131k istek nas\u0131l biterse bitsin siliniyor.<\/li>\n<li><strong>Ek depolama hedefleri art\u0131k sessiz kalm\u0131yor.<\/strong> Birden \u00e7ok hedef tan\u0131mlad\u0131ysan\u0131z, ek\nhedeflerden birine y\u00fckleme ba\u015far\u0131s\u0131z oldu\u011funda hi\u00e7bir iz kalm\u0131yordu: panelde de,\nk\u00fct\u00fckte de. \u00d6dedi\u011finiz ikinci\/\u00fc\u00e7\u00fcnc\u00fc kopyan\u0131n yaz\u0131lmad\u0131\u011f\u0131n\u0131 \u00f6\u011frenemiyordunuz. Sonu\u00e7 art\u0131k\npanele raporlan\u0131yor ve ba\u015far\u0131s\u0131zl\u0131kta bildirim gidiyor. Ayr\u0131ca \"Sadece de\u011fi\u015fenler\" rejimi\na\u00e7\u0131kken WordPress kopyalar\u0131 da zincir klas\u00f6r\u00fcne d\u00fc\u015f\u00fcyor (\u00f6nceden yaln\u0131z mod\u00fcl kopyalar\u0131\nd\u00fc\u015f\u00fcyordu).<\/li>\n<li>G\u00fcvenlik: site anahtar\u0131n\u0131 (<code>pull_secret<\/code>) d\u00f6nd\u00fcren u\u00e7, karde\u015flerinde bulunan ikinci yetki\nkontrol\u00fcn\u00fc ta\u015f\u0131m\u0131yordu. Bug\u00fcn a\u00e7\u0131k bir kap\u0131 de\u011fildi; yine de eklendi.<\/li>\n<\/ul>\n\n<h4>1.57.5 \u2014 2026-08-18<\/h4>\n\n<ul>\n<li><strong>D\u00fczeltildi: baz\u0131 payla\u015f\u0131ml\u0131 hostinglerde yedek ilk saniyesinde \u00f6l\u00fcyordu.<\/strong> PHP'nin\n  set_time_limit, <code>ignore_user_abort<\/code>, <code>php_uname<\/code> ve <code>fsockopen<\/code> fonksiyonlar\u0131\nhostingler taraf\u0131ndan <code>disable_functions<\/code> ile kapat\u0131labilir. Kapal\u0131 olduklar\u0131nda\n  @ i\u015fareti KORUMAZ \u2014 PHP \u00f6l\u00fcmc\u00fcl hata verir ve yedekleme, geri y\u00fckleme ya da par\u00e7al\u0131\nyedek o anda durur. Ayn\u0131 s\u0131n\u0131f hata bu eklentide daha \u00f6nce <code>disk_free_space<\/code> i\u00e7in\nd\u00fczeltilmi\u015fti; bu s\u00fcr\u00fcm kalan 13 \u00e7a\u011fr\u0131y\u0131 da tek bir g\u00fcvenli kap\u0131ya ald\u0131.<\/li>\n<li><strong>D\u00fczeltildi: geri y\u00fckleme <code>wp-config.php<\/code> ve <code>.htaccess<\/code> dosyalar\u0131n\u0131 eziyordu.<\/strong>\nYedek al\u0131nd\u0131ktan sonra veritaban\u0131 bilgileriniz, sunucunuz ya da <code>.htaccess<\/code>\nkurallar\u0131n\u0131z de\u011fi\u015ftiyse, geri y\u00fckleme sitenizi ESK\u0130 yap\u0131land\u0131rmaya d\u00f6nd\u00fcr\u00fcyor ve\n\"Error establishing a database connection\" hatas\u0131na yol a\u00e7abiliyordu. Bu dosyalar\nart\u0131k geri y\u00fcklemede KORUNUR \u2014 kurtarma i\u015flemi sitenizi d\u00fc\u015f\u00fcrmez.<\/li>\n<li><strong>G\u00fcvenlik: y\u00fckleme s\u0131n\u0131r\u0131 ayar\u0131 yetki kontrol\u00fc olmadan \u00e7al\u0131\u015f\u0131yordu.<\/strong> Eklenti,\ny\u00fckleme s\u0131n\u0131rlar\u0131n\u0131 y\u00fckseltmek i\u00e7in site k\u00f6k\u00fcnde <code>.user.ini<\/code> olu\u015fturuyor; bu i\u015flem\nherhangi bir oturum a\u00e7m\u0131\u015f kullan\u0131c\u0131 (\u00f6r. Abone) taraf\u0131ndan tetiklenebiliyordu. Art\u0131k\nyaln\u0131zca y\u00f6neticiler tetikleyebilir.<\/li>\n<li><strong>D\u00fczeltildi: yedek klas\u00f6r\u00fcn\u00fcn yan\u0131ndaki benzer adl\u0131 klas\u00f6r sessizce yede\u011fe girmiyordu.<\/strong>\nKlas\u00f6r kar\u015f\u0131la\u015ft\u0131rmas\u0131 ayra\u00e7 s\u0131n\u0131r\u0131 kullanmad\u0131\u011f\u0131 i\u00e7in <code>yedekalma-backups<\/code> taban\u0131n\u0131n\nyan\u0131nda duran <code>yedekalma-backups-eski<\/code> gibi bir klas\u00f6r\u00fcn TAMAMI \"yedek klas\u00f6r\u00fc\"\nsay\u0131l\u0131yor ve yede\u011fin d\u0131\u015f\u0131nda kal\u0131yordu \u2014 hi\u00e7bir uyar\u0131 \u00e7\u0131kmadan.<\/li>\n<li><strong>D\u00fczeltildi: geri y\u00fcklemede bilinmeyen bile\u015fen se\u00e7imi \"her \u015feyi geri y\u00fckle\"ye\nd\u00fc\u015f\u00fcyordu.<\/strong> Art\u0131k ge\u00e7ersiz bir se\u00e7im sessizce en y\u0131k\u0131c\u0131 se\u00e7ene\u011fe \u00e7evrilmek yerine\nreddediliyor (REST ucunda zaten b\u00f6yleydi).<\/li>\n<li>G\u00fcvenlik\/sa\u011flaml\u0131k: arka plan yedek i\u015finin gizli anahtar\u0131 art\u0131k yaln\u0131zca POST\ng\u00f6vdesinden okunuyor (adres sat\u0131r\u0131ndan ge\u00e7ti\u011finde sunucu eri\u015fim k\u00fct\u00fc\u011f\u00fcne d\u00fc\u015f\u00fcyordu);\nyedek dosya ad\u0131 \u00e7\u00f6z\u00fcm\u00fcnde dizin d\u0131\u015f\u0131na \u00e7\u0131kma korumas\u0131; ar\u015fiv i\u00e7i dosya ad\u0131 e\u015flemeleri\nart\u0131k b\u00fcy\u00fck\/k\u00fc\u00e7\u00fck harfe duyars\u0131z (mod\u00fcldeki davran\u0131\u015fla e\u015fitlendi).<\/li>\n<\/ul>\n\n<h4>1.57.4 \u2014 2026-08-18<\/h4>\n\n<ul>\n<li><strong>D\u00fczeltildi: ta\u015f\u0131nm\u0131\u015f sitelerde wp-admin \"Yedekler\" listesi BO\u015e g\u00f6r\u00fcn\u00fcyordu.<\/strong> 1.57.3\nyedek klas\u00f6r\u00fcn\u00fcn yolunu tek bir do\u011frulanm\u0131\u015f kayna\u011fa ba\u011flam\u0131\u015ft\u0131, ama yaln\u0131zca panel\/REST\ntaraf\u0131nda. WordPress y\u00f6netim ekranlar\u0131 (yedek listesi, silme, indirme, i\u00e7e aktarma,\nklas\u00f6r gezgini, ge\u00e7ici dosya temizleyici, karantina ve destek tan\u0131lamas\u0131) h\u00e2l\u00e2 eski\ny\u00f6ntemle hesapl\u0131yordu. Sitesi ba\u015fka bir sunucuya ta\u015f\u0131nm\u0131\u015f kurulumlarda WordPress'in\nbildirdi\u011fi y\u00fckleme klas\u00f6r\u00fc yolu ESK\u0130 sunucuya ait olabildi\u011fi i\u00e7in bu ekranlar var\nolmayan bir klas\u00f6re bak\u0131yordu: yedekler diskte dururken listede g\u00f6r\u00fcnm\u00fcyor, temizlik\nyanl\u0131\u015f klas\u00f6r\u00fc hedefliyor, zamanlanm\u0131\u015f yedek sessizce kayboluyordu.<\/li>\n<li><strong>Sebebi s\u00f6ylemeyen hata kalkt\u0131:<\/strong> y\u00fckleme klas\u00f6r\u00fc ger\u00e7ekten kullan\u0131lam\u0131yorsa art\u0131k\n\"izinleri kontrol edin\" yerine ne yap\u0131lmas\u0131 gerekti\u011fi yaz\u0131yor (Ayarlar &gt; Medya'daki\ny\u00fckleme klas\u00f6r\u00fc yolunu bo\u015faltmak \u00e7o\u011fu ta\u015f\u0131nma sorununu \u00e7\u00f6zer).<\/li>\n<li>Destek tan\u0131lamas\u0131ndaki \"Yedek klas\u00f6r\u00fc\" sat\u0131r\u0131 eski sabit klas\u00f6r ad\u0131na bak\u0131yordu ve bu\ny\u00fczden her sitede \"hen\u00fcz olu\u015fmam\u0131\u015f\" diyordu; art\u0131k ger\u00e7ek klas\u00f6r\u00fc raporluyor. WordPress'in\nbildirdi\u011fi yol ile ger\u00e7ekte kullan\u0131lan yol farkl\u0131ysa bu da ayr\u0131ca g\u00f6steriliyor.<\/li>\n<li>Eklentiyi silerken \"yedekleri de sil\" se\u00e7ene\u011fi ta\u015f\u0131nm\u0131\u015f sitelerde ar\u015fivleri diskte\nb\u0131rak\u0131yordu; art\u0131k olas\u0131 t\u00fcm y\u00fckleme klas\u00f6r\u00fc konumlar\u0131 temizleniyor.<\/li>\n<\/ul>\n\n<h4>1.57.3 \u2014 2026-08-18<\/h4>\n\n<ul>\n<li><strong>D\u00fczeltildi: yedek ba\u015far\u0131yla al\u0131n\u0131yordu ama panel \"dosya bulunamad\u0131\" diyordu.<\/strong> Ar\u015fiv\ndo\u011fru klas\u00f6re yaz\u0131l\u0131yor, ancak indirme ve silme i\u015flemleri klas\u00f6r\u00fc BA\u015eKA bir kaynaktan\nhesapl\u0131yordu. Sitesi ba\u015fka bir sunucuya ta\u015f\u0131nm\u0131\u015f kurulumlarda WordPress'in bildirdi\u011fi\ny\u00fckleme klas\u00f6r\u00fc yolu ESK\u0130 sunucuya ait olabiliyor; yazma taraf\u0131 bunu 1.57.0'da\ndo\u011frulamaya ba\u015flam\u0131\u015ft\u0131 ama okuma\/silme taraf\u0131 ham de\u011feri kullanmaya devam ediyordu.\nSonu\u00e7: yedek 3-4 dakika boyunca paketleniyor, tamamlan\u0131yor, sonra panel dosyay\u0131\nbulamay\u0131p i\u015fi ba\u015far\u0131s\u0131z say\u0131yordu. Dosya asl\u0131nda YER\u0130NDEYD\u0130.<\/li>\n<li><strong>Ayn\u0131 hata yede\u011fin \u0130\u00c7ER\u0130\u011e\u0130N\u0130 de bozuyordu:<\/strong> yedek klas\u00f6r\u00fcn\u00fcn yeni ar\u015five dahil\nED\u0130LMEMES\u0130N\u0130 sa\u011flayan kural da ayn\u0131 yanl\u0131\u015f yoldan hesapland\u0131\u011f\u0131 i\u00e7in ta\u015f\u0131nm\u0131\u015f sitelerde\n\u00e7al\u0131\u015fm\u0131yordu \u2014 ar\u015fiv kendi \u00f6nceki ar\u015fivlerini i\u00e7ine al\u0131p gereksiz yere b\u00fcy\u00fcyordu.<\/li>\n<li>Art\u0131k yedek klas\u00f6r\u00fcn\u00fcn yolu tek bir do\u011frulanm\u0131\u015f kaynaktan geliyor: yazma, okuma, silme,\nge\u00e7ici dosya ve d\u0131\u015flama kural\u0131 ayn\u0131 yeri g\u00f6steriyor.<\/li>\n<\/ul>\n\n<h4>1.57.2 \u2014 2026-08-18<\/h4>\n\n<ul>\n<li><strong>D\u00fczeltildi: yedek %97'de \"kay\u0131t onay\u0131 bekleniyor\"da tak\u0131l\u0131p ba\u015far\u0131s\u0131z oluyordu.<\/strong>\nAr\u015fiv asl\u0131nda hedefe SORUNSUZ y\u00fcklenmi\u015f oluyordu; eklenti son ad\u0131mda panele kay\u0131t\nbilgisini yaln\u0131zca B\u0130R KEZ g\u00f6nderiyor, o tur tamamlanamazsa sonraki denemelerde bo\u015f\ng\u00f6nderiyordu. Panel de bunu \"bilgi gelmedi\" say\u0131p yede\u011fi ba\u015far\u0131s\u0131z i\u015faretliyordu.\nArt\u0131k kay\u0131t bilgisi saklan\u0131yor ve gerekti\u011finde tekrar g\u00f6nderiliyor.<\/li>\n<li>Bu durumda tak\u0131l\u0131 kalm\u0131\u015f eski bir oturum varsa art\u0131k otomatik temizleniyor; eskiden\no oturum sonraki her yede\u011fi de d\u00fc\u015f\u00fcr\u00fcyordu.<\/li>\n<\/ul>\n\n<h4>1.57.1 \u2014 2026-08-18<\/h4>\n\n<ul>\n<li><strong>D\u00fczeltildi: baz\u0131 hostinglerde yedek \"Call to undefined function disk_free_space()\"\nhatas\u0131yla d\u00fc\u015f\u00fcyordu.<\/strong> 1.57.0'daki yeni disk\/kota kontrol\u00fc, bu fonksiyonu kapatan\npayla\u015f\u0131ml\u0131 hostinglerde \u00f6l\u00fcmc\u00fcl hataya yol a\u00e7\u0131yordu. Art\u0131k fonksiyonun varl\u0131\u011f\u0131 tek bir\nyerden kontrol ediliyor; yoksa disk bilgisi \"\u00f6l\u00e7\u00fclemedi\" olarak ge\u00e7iliyor ve yedek\nnormal \u015fekilde devam ediyor.<\/li>\n<li>Not: ayn\u0131 s\u0131n\u0131f hata 1.53.x'te de ya\u015fanm\u0131\u015ft\u0131. Kontrol\u00fcn her \u00e7a\u011fr\u0131 yerinde elle\ntekrarlanmas\u0131 hatay\u0131 geri getirdi\u011fi i\u00e7in art\u0131k tek bir yard\u0131mc\u0131dan ge\u00e7iliyor ve\notomatik bir kontrol, korumas\u0131z \u00e7a\u011fr\u0131 eklenmesini engelliyor.<\/li>\n<\/ul>\n\n<h4>1.57.0 \u2014 2026-08-18<\/h4>\n\n<ul>\n<li><strong>Yedek art\u0131k BA\u015eLAMADAN \u00f6nce sistemi kontrol ediyor.<\/strong> Eskiden bir sorun varsa (klas\u00f6r\nyaz\u0131lam\u0131yor, disk dolu, veritaban\u0131na eri\u015filemiyor, ZipArchive yok) bunu ancak yedek %95'e\ngeldi\u011finde, 15-20 dakika sonra \u00f6\u011freniyordunuz. Art\u0131k yedek ba\u015flamadan \u00f6nce tek bayt\npaketlenmeden kontrol yap\u0131l\u0131yor ve sorun varsa saniyeler i\u00e7inde net bir mesajla duruyor.\nKontrol edilenler: PHP s\u00fcr\u00fcm\u00fc, gerekli eklentiler (ZipArchive, cURL), yedek klas\u00f6r\u00fcne\nGER\u00c7EK yazma testi, disk\/kota, veritaban\u0131 eri\u015fimi, bellek ve s\u00fcre limitleri, yar\u0131m kalm\u0131\u015f\nyedek art\u0131klar\u0131.<\/li>\n<li>Yazma testi bilerek ger\u00e7ek bir dosya yaz\u0131p siliyor: payla\u015f\u0131ml\u0131 hostingde izin bilgisi\n\"yaz\u0131labilir\" dese bile kota veya ba\u011flama sorunu y\u00fcz\u00fcnden yazma ba\u015far\u0131s\u0131z olabiliyor \u2014\nbug\u00fcn ya\u015fanan ar\u0131za tam olarak bu t\u00fcrdendi.<\/li>\n<li>Uyar\u0131lar yede\u011fi durdurmaz, yaln\u0131zca bildirilir; yedek yaln\u0131zca ger\u00e7ekten engelleyici bir\nsorun varsa ba\u015flat\u0131lmaz.<\/li>\n<\/ul>\n\n<h4>1.56.0 \u2014 2026-08-18<\/h4>\n\n<ul>\n<li><strong>Yedek klas\u00f6r\u00fc art\u0131k eklenti etkinle\u015ftirilirken olu\u015fturuluyor.<\/strong> Eskiden klas\u00f6r ilk yede\u011fin\nSONUNDA, ar\u015fiv paketlendikten sonra yarat\u0131l\u0131yordu. Bu y\u00fczden yaz\u0131lamayan bir klas\u00f6r ancak\nsaatler sonra, yedek %95'teyken hata veriyordu; o zamana kadar harcanan s\u00fcre bo\u015fa gidiyordu.\nArt\u0131k kurulumda deneniyor: klas\u00f6r olu\u015fturulup korumalar\u0131 (.htaccess, index.php) HEMEN\nuygulan\u0131yor. Bir sorun varsa y\u00f6netim panelinde net bir uyar\u0131 g\u00f6r\u00fcyorsunuz \u2014 yede\u011fin\nba\u015far\u0131s\u0131z olmas\u0131n\u0131 beklemenize gerek kalm\u0131yor.<\/li>\n<li><strong>Sorunu d\u00fczeltince uyar\u0131 kendili\u011finden kalk\u0131yor.<\/strong> Y\u00fckleme klas\u00f6r\u00fc yolunu d\u00fczeltti\u011finizde\neklentiyi yeniden etkinle\u015ftirmeniz gerekmez; panel her a\u00e7\u0131l\u0131\u015fta (saatte en fazla bir kez)\nyeniden deneyip klas\u00f6r\u00fc olu\u015fturur ve uyar\u0131y\u0131 kald\u0131r\u0131r.<\/li>\n<\/ul>\n\n<h4>1.55.8 \u2014 2026-08-18<\/h4>\n\n<ul>\n<li><strong>Sunucu ta\u015f\u0131mas\u0131 sonras\u0131 yedek al\u0131nam\u0131yordu (kritik).<\/strong> Site ba\u015fka bir sunucuya ta\u015f\u0131nd\u0131\u011f\u0131nda\nveritaban\u0131, ESK\u0130 sunucunun mutlak klas\u00f6r yolunu ta\u015f\u0131maya devam edebiliyor (Ayarlar &gt; Medya\nalt\u0131ndaki \"upload_path\" ayar\u0131). WordPress y\u00fckleme klas\u00f6r\u00fcn\u00fc oradan bildirdi\u011fi i\u00e7in eklenti,\nyeni sunucuda H\u0130\u00c7 VAR OLMAYAN bir yola yazmaya \u00e7al\u0131\u015f\u0131yor ve yedek her seferinde\n\"Hedef klas\u00f6r olu\u015fturulamad\u0131 \u2014 Permission denied\" ile \u00f6l\u00fcyordu. Diskte 30 GB bo\u015f yer olsa bile.\nEklenti art\u0131k bu yola k\u00f6r\u00fc k\u00f6r\u00fcne g\u00fcvenmiyor: kullan\u0131labilir oldu\u011funu (var + yaz\u0131labilir)\ndo\u011fruluyor, de\u011filse kurulumun ger\u00e7ek yap\u0131s\u0131ndan (WP_CONTENT_DIR, ard\u0131ndan ABSPATH) sa\u011flam bir\nklas\u00f6re d\u00fc\u015f\u00fcyor. Yol hi\u00e7bir \u015fekilde kullan\u0131lam\u0131yorsa hata mesaj\u0131 ne yapman\u0131z gerekti\u011fini\ns\u00f6yl\u00fcyor.<\/li>\n<\/ul>\n\n<h4>1.55.7 \u2014 2026-08-18<\/h4>\n\n<ul>\n<li><strong>\"Hedef klas\u00f6r olu\u015fturulamad\u0131\" hatas\u0131 art\u0131k sebebini \u00d6L\u00c7EREK s\u00f6yl\u00fcyor.<\/strong> \u00d6nceki s\u00fcr\u00fcm\n\"\u00fcst klas\u00f6rde yazma izni yok olabilir\" diyordu; \"olabilir\" sizi do\u011fru yere g\u00f6t\u00fcrmez, \u00e7\u00fcnk\u00fc\nbu hata hem izin, hem disk\/kota dolmas\u0131, hem de bir \u00fcst klas\u00f6r\u00fcn hi\u00e7 bulunmamas\u0131 y\u00fcz\u00fcnden\nolu\u015fur ve \u00e7\u00f6z\u00fcmleri birbirinden farkl\u0131d\u0131r. Art\u0131k mesaj \u015funlar\u0131 i\u00e7eriyor: en derin VAR OLAN\n\u00fcst klas\u00f6r hangisi, o klas\u00f6r yaz\u0131labilir mi, orada ne kadar bo\u015f alan var ve sistemin kendi\nhata mesaj\u0131. B\u00f6ylece disk mi dolu yoksa izin mi eksik, bakar bakmaz g\u00f6r\u00fcl\u00fcyor.<\/li>\n<\/ul>\n\n<h4>1.55.6 \u2014 2026-08-17<\/h4>\n\n<ul>\n<li><strong>\"Ne kadar yer kazand\u0131r\u0131r?\" \u00f6l\u00e7\u00fcm\u00fc ile yede\u011fin ger\u00e7ekte ald\u0131\u011f\u0131 dosya say\u0131s\u0131 ayr\u0131\u015f\u0131yordu.<\/strong>\n\u0130lerleme ekran\u0131 \"5717 dosya\" derken \u00f6l\u00e7\u00fcm paneli \"5724 dosya\" diyordu. Sebep: \u00f6l\u00e7\u00fcm, yede\u011fi\n\u00fcreten kodun iki elemesini yapm\u0131yordu \u2014 eklentinin kendi ge\u00e7ici art\u0131klar\u0131 ve okunamayan\ndosyalar. Yani panel, yede\u011fe girmeyecek dosyalar\u0131 \"girecek\" diye say\u0131yordu.\nArt\u0131k \u00fc\u00e7 yer de (par\u00e7al\u0131 yedek listesi, tam yedek ve \u00f6l\u00e7\u00fcm paneli) tek bir karar noktas\u0131n\u0131\nkullan\u0131yor; g\u00f6sterilen say\u0131 yede\u011fin ger\u00e7ekte yapt\u0131\u011f\u0131 i\u015fle ayn\u0131 olmak zorunda.<\/li>\n<li>\u00d6l\u00e7\u00fcm paneli art\u0131k yaln\u0131zca S\u0130Z\u0130N kal\u0131plar\u0131n\u0131z\u0131n eledi\u011fini \"kazan\u00e7\" olarak say\u0131yor; varsay\u0131lan\nolarak zaten hari\u00e7 olanlar (\u00f6nbellek, yedek klas\u00f6r\u00fc, okunamayan dosya) rakam\u0131 \u015fi\u015firmiyor.<\/li>\n<\/ul>\n\n<h4>1.55.5 \u2014 2026-08-17<\/h4>\n\n<ul>\n<li><strong>Ba\u015fka eklentilerin uyar\u0131lar\u0131 Yedekalma ekranlar\u0131nda g\u00f6r\u00fcnm\u00fcyor art\u0131k.<\/strong> WordPress uyar\u0131\nkancas\u0131n\u0131 t\u00fcm y\u00f6netim sayfalar\u0131nda \u00e7al\u0131\u015ft\u0131rd\u0131\u011f\u0131 i\u00e7in, teman\u0131z\u0131n \"\u015fu eklenti pasif\" uyar\u0131s\u0131\nveya ba\u015fka bir eklentinin \"veri toplamam\u0131za izin verir misiniz?\" kutusu Yedekalma ayar\nsayfas\u0131n\u0131n en \u00fcst\u00fcnde \u00e7\u0131k\u0131yordu; bir yedekleme ekran\u0131nda bunlar\u0131 g\u00f6rmek \"bu benim yede\u011fimle\nmi ilgili?\" kar\u0131\u015f\u0131kl\u0131\u011f\u0131 yarat\u0131yordu. Art\u0131k yaln\u0131zca KEND\u0130 ekranlar\u0131m\u0131zda \u00fc\u00e7\u00fcnc\u00fc taraf\nuyar\u0131lar\u0131 gizleniyor. WordPress \u00e7ekirde\u011finin uyar\u0131lar\u0131 (g\u00fcvenlik\/g\u00fcncelleme) KORUNUR ve\nsitenizin di\u011fer sayfalar\u0131na hi\u00e7 dokunulmaz.<\/li>\n<li><strong>Simge (dashicons) ba\u011f\u0131ml\u0131l\u0131\u011f\u0131 a\u00e7\u0131k\u00e7a beyan edildi.<\/strong> Aray\u00fczdeki simgeler \u00e7ekirde\u011fin\nstil dosyas\u0131n\u0131 zaten y\u00fcklemi\u015f olmas\u0131na dayan\u0131yordu; bir tema veya eklenti onu kald\u0131r\u0131rsa\nsimgelerin yerinde bo\u015f kutular kal\u0131yordu. Art\u0131k kendi stilimizin ba\u011f\u0131ml\u0131l\u0131\u011f\u0131 olarak\ny\u00fckleniyor.<\/li>\n<\/ul>\n\n<h4>1.55.4 \u2014 2026-08-17<\/h4>\n\n<ul>\n<li><strong>\"\u00d6nerilen gereksiz dosya ve klas\u00f6rleri hari\u00e7 tut\" \u00f6zelli\u011fi kald\u0131r\u0131ld\u0131.<\/strong> Tek t\u0131kla 35 kural\nuygulamak, yede\u011finizin i\u00e7eri\u011fini daraltan kararlar\u0131 g\u00f6rmeden kabul etmenize yol a\u00e7\u0131yordu.\nNeyin hari\u00e7 tutulaca\u011f\u0131na art\u0131k siz karar veriyorsunuz: sa\u011fdaki klas\u00f6r gezgininden istedi\u011finiz\nklas\u00f6r\u00fc se\u00e7ip hari\u00e7 tutabilir, kaydetmeden \u00f6nce \"Ne kadar yer kazand\u0131r\u0131r?\" ile etkisini\n\u00f6l\u00e7ebilirsiniz. \u00d6nbellek klas\u00f6rleri, .git, node_modules ve tan\u0131nan yedek eklentisi klas\u00f6rleri\nzaten varsay\u0131lan olarak hari\u00e7tir \u2014 onlar i\u00e7in bir \u015fey yapman\u0131z gerekmez.<\/li>\n<\/ul>\n\n<h4>1.55.3 \u2014 2026-08-17<\/h4>\n\n<ul>\n<li><strong>\"\u00d6nerilen gereksiz dosyalar\u0131 hari\u00e7 tut\" art\u0131k NEDEN gereksiz olduklar\u0131n\u0131 da g\u00f6steriyor.<\/strong>\nD\u00fc\u011fme 35 kal\u0131b\u0131 tek t\u0131kla ekliyordu ama her kal\u0131b\u0131n gerek\u00e7esi ayr\u0131 bir pencerede duruyor ve\nyaln\u0131zca ayr\u0131 bir ba\u011flant\u0131yla a\u00e7\u0131l\u0131yordu. Yani yede\u011finizin i\u00e7eri\u011fini daraltan 35 kural\u0131\ng\u00f6rmeden kabul etmi\u015f oluyordunuz. Art\u0131k kal\u0131plar eklendi\u011fi anda gerek\u00e7e listesi a\u00e7\u0131l\u0131yor:\nher sat\u0131rda kal\u0131p, ne oldu\u011fu ve neden yede\u011fe girmesine gerek olmad\u0131\u011f\u0131 yaz\u0131yor; eklenenler\n\"\u2713 eklendi\" olarak i\u015faretleniyor. Kat\u0131lmad\u0131\u011f\u0131n\u0131z sat\u0131r\u0131 kaydetmeden \u00f6nce kutudan silebilirsiniz.\nListede site i\u00e7eri\u011fi (y\u00fcklemeler, temalar, eklentiler, \u00e7eviriler, vendor\/) ASLA yer almaz.<\/li>\n<\/ul>\n\n<h4>1.55.2 \u2014 2026-08-17<\/h4>\n\n<ul>\n<li><strong>Yedek, kendi eski ar\u015fivini yedeklemeye \u00e7al\u0131\u015f\u0131yordu (kritik).<\/strong> Eklenti yede\u011fi ge\u00e7ici bir\ndosyada kurar (<code>wp-content\/uploads\/yedekalma_full_\u2026<\/code>). Bir yedek ko\u015fusu yar\u0131da kal\u0131rsa bu\nge\u00e7ici dosya diskte kal\u0131yor ve SONRAK\u0130 yedek onu normal bir site dosyas\u0131 san\u0131p ar\u015five\neklemeye \u00e7al\u0131\u015f\u0131yordu. Art\u0131k y\u00fczlerce MB olan bu art\u0131k tek bir ad\u0131ma s\u0131\u011fmad\u0131\u011f\u0131 i\u00e7in yedek\nilerleyemiyor, hosting iste\u011fi kesiyor ve yedek hi\u00e7 tamamlanm\u0131yordu. Ayn\u0131 \u015fey eski\nkurulumdan kalan <code>YedekAlmaBackup-\u2026<\/code> klas\u00f6rleri i\u00e7in de ge\u00e7erliydi.\nArt\u0131k eklentinin kendi ge\u00e7ici dosyalar\u0131 ve yedek klas\u00f6rleri her ko\u015fuda hari\u00e7 tutuluyor.\nBelirti: yede\u011fin sonlara do\u011fru t\u0131kan\u0131p saatlerce ayn\u0131 dosyada beklemesi, sitenizin ger\u00e7ekte\noldu\u011fundan \u00e7ok daha b\u00fcy\u00fck \u00f6l\u00e7\u00fclmesi.<\/li>\n<li>Not: diskte kalm\u0131\u015f eski <code>yedekalma_full_\u2026<\/code> dosyalar\u0131n\u0131 silmek yer kazand\u0131r\u0131r; yede\u011fe art\u0131k\ngirmiyorlar ama yer kaplamay\u0131 s\u00fcrd\u00fcr\u00fcrler.<\/li>\n<\/ul>\n\n<h4>1.55.1 \u2014 2026-08-17<\/h4>\n\n<ul>\n<li><strong>\"Y\u00fckleme ba\u015far\u0131s\u0131z\" art\u0131k SEBEB\u0130N\u0130 s\u00f6yl\u00fcyor.<\/strong> Yedek kendi sunucunuzda saklan\u0131rken (domain\ni\u00e7i depolama) bir sorun \u00e7\u0131karsa panelde yaln\u0131zca \"Y\u00fckleme ba\u015far\u0131s\u0131z: upload_failed\" yaz\u0131yordu;\ndisk mi doldu, klas\u00f6re yazma izni mi yok, hi\u00e7 belli olmuyordu. Bu ad\u0131mda be\u015f ayr\u0131 hata yolu\nvard\u0131 ve hi\u00e7biri gerek\u00e7e d\u00f6nd\u00fcrm\u00fcyordu. Art\u0131k disk bo\u015f alan\u0131 \u00f6l\u00e7\u00fcl\u00fcyor, yazma izni s\u0131nan\u0131yor\nve mesaj net: \"Diskte yeterli yer yok: ar\u015fiv 412,0 MB, bo\u015f alan 63,4 MB \u2014 eski yedekleri\nsilip yeniden deneyin.\" gibi.<\/li>\n<li><strong>Yar\u0131m yaz\u0131lan ar\u015fiv art\u0131k fark ediliyor.<\/strong> Disk yazma s\u0131ras\u0131nda dolarsa dosya eksik kal\u0131yor\nve bu sessizce \"ba\u015far\u0131l\u0131\" say\u0131labiliyordu. Art\u0131k yaz\u0131lan boyut beklenenle kar\u015f\u0131la\u015ft\u0131r\u0131l\u0131yor;\neksikse yar\u0131m dosya siliniyor ve durum a\u00e7\u0131k\u00e7a bildiriliyor.<\/li>\n<\/ul>\n\n<h4>1.55.0 \u2014 2026-08-17<\/h4>\n\n<ul>\n<li><strong>Yede\u011fe giremeyen dosyalar art\u0131k B\u0130LD\u0130R\u0130L\u0130YOR (kritik).<\/strong> Bir dosya izin hatas\u0131, a\u00e7\u0131lamayan\nklas\u00f6r ya da disk\/kota sorunu y\u00fcz\u00fcnden okunamazsa, eklenti onu SESS\u0130ZCE atl\u0131yordu: yedek\n\"tamamland\u0131\" damgas\u0131 al\u0131yor, o dosyalar ar\u015fivde bulunmuyordu. Daha k\u00f6t\u00fcs\u00fc, klas\u00f6r gezinmesi\nbir izin hatas\u0131yla kesilirse YARIM dosya listesi tam liste gibi kullan\u0131l\u0131yordu \u2014 yani b\u00fct\u00fcn\nbir klas\u00f6r sessizce yede\u011fin d\u0131\u015f\u0131nda kalabiliyordu. Bunu ancak geri y\u00fcklerken fark ederdiniz.\nArt\u0131k okunamayan her dosya\/klas\u00f6r say\u0131l\u0131yor ve yedekalma.com paneline bildiriliyor; panelde\nyede\u011fin yan\u0131nda \"\u26a0 N dosya ar\u015five eklenemedi \u2014 bu yedek EKS\u0130K\" uyar\u0131s\u0131 g\u00f6r\u00fcn\u00fcyor.<\/li>\n<li>Panel taraf\u0131 da ayn\u0131 g\u00fcn d\u00fczeltildi: bu bilgi eskiden g\u00f6nderiliyor ama panelde OKUNMUYORDU.<\/li>\n<\/ul>\n\n<h4>1.54.9 \u2014 2026-08-17<\/h4>\n\n<ul>\n<li><strong>Hari\u00e7 tutma kal\u0131plar\u0131nda karakter s\u0131n\u0131f\u0131 (<code>[0-9]<\/code>) uygulanm\u0131yordu.<\/strong> <code>logs[0-9]<\/code> ya da\n  20[12][0-9] gibi bir kal\u0131p yazd\u0131ysan\u0131z, ekranda \"hari\u00e7 tutulan yol\" olarak say\u0131l\u0131yor ama\nyede\u011fe G\u0130R\u0130YORDU. Ayn\u0131 kal\u0131p panelin PHP mod\u00fcl\u00fcnde do\u011fru \u00e7al\u0131\u015ft\u0131\u011f\u0131 i\u00e7in iki \u00fcr\u00fcnde farkl\u0131\nsonu\u00e7 do\u011fuyordu; art\u0131k ikisi birebir ayn\u0131 davran\u0131yor. Yaln\u0131z <code>*<\/code> ve <code>?<\/code> kulland\u0131ysan\u0131z\nbu sorundan etkilenmediniz.<\/li>\n<\/ul>\n\n<h4>1.54.8 \u2014 2026-08-17<\/h4>\n\n<ul>\n<li><strong>\"Diskte bulundu\" yedekleri silinemiyordu (kritik kullan\u0131labilirlik).<\/strong> Yedek listesi iki\nkayna\u011f\u0131 birle\u015ftirir: eklentinin kendi kayd\u0131 ve diskte tarama ile bulunan ar\u015fivler (sat\u0131rda\n\"Diskte bulundu\" etiketiyle g\u00f6r\u00fcn\u00fcr). \u0130kinci gruptaki bir yede\u011fi se\u00e7ip \"Sil\" dedi\u011finizde\ni\u015flem tamamlanm\u0131yor, sat\u0131r listede kal\u0131yordu. Sebep: bu sat\u0131rlar\u0131n kayd\u0131 olmad\u0131\u011f\u0131 i\u00e7in\neklenti onlar\u0131 bulut yede\u011fi san\u0131p yedekalma.com'a bilmedi\u011fi bir kimlikle silme iste\u011fi\ng\u00f6nderiyordu. Art\u0131k disk taramas\u0131nda bulunup dosya do\u011frudan siliniyor (yol g\u00fcvenlik\ndenetiminden ge\u00e7irilerek).<\/li>\n<li><strong>Ar\u015fivi elle sildiyseniz kay\u0131t art\u0131k temizlenebiliyor.<\/strong> Bir yedek dosyas\u0131n\u0131 FTP\/dosya\ny\u00f6neticisiyle kendiniz sildiyseniz, \"Sil\" i\u015flemi \"dosya bulunamad\u0131\" diyerek duruyor ve\nlisteyi hi\u00e7 temizleyemiyordunuz. Silme art\u0131k idempotent: dosya zaten yoksa istenen sonu\u00e7\nsa\u011flanm\u0131\u015f say\u0131l\u0131r ve kay\u0131t kald\u0131r\u0131l\u0131r. Dosya diskte VARSA ama silinemiyorsa (izin\/kilit)\nbu yine a\u00e7\u0131k\u00e7a hata olarak bildirilir \u2014 kayd\u0131n kalk\u0131p dosyan\u0131n kalmas\u0131 engellenir.\nAyn\u0131 kural bulut taraf\u0131nda da ge\u00e7erli: panelde kayd\u0131 bulunmayan bir yedek \"zaten silinmi\u015f\"\nsay\u0131l\u0131r.<\/li>\n<\/ul>\n\n<h4>1.54.7 \u2014 2026-08-17<\/h4>\n\n<ul>\n<li><strong>Sayfa \u00f6nbelle\u011fi panelin sitenizi okumas\u0131n\u0131 engelliyordu (kritik).<\/strong> LiteSpeed Cache,\nWP Rocket veya benzeri bir \u00f6nbellek eklentisi kullan\u0131yorsan\u0131z, eklentinin yedekalma.com\nile konu\u015ftu\u011fu <code>\/wp-json\/<\/code> yan\u0131tlar\u0131 \u00f6nbelle\u011fe al\u0131nabiliyordu. Sonucu: panelde \"Mod\u00fcl\ndurumu al\u0131namad\u0131 \u2014 eklentiyi g\u00fcncelleyin\" uyar\u0131s\u0131 \u00e7\u0131k\u0131yor, eklentiyi g\u00fcncellemek de bir\n\u015fey de\u011fi\u015ftirmiyordu; \u00e7\u00fcnk\u00fc sorun eklentide de\u011fil, araya giren \u00f6nbellekteydi.\nAyr\u0131ca ayn\u0131 \u00f6nbellek, yetkili bir iste\u011fe verilen yan\u0131t\u0131 yetkisiz bir ziyaret\u00e7iye\nsunabiliyordu \u2014 sitenizin dosya ve veritaban\u0131 boyutu bu yolla g\u00f6r\u00fcn\u00fcr h\u00e2le gelebiliyordu.\nEklenti art\u0131k kendi REST yan\u0131tlar\u0131n\u0131 a\u00e7\u0131k\u00e7a \u00f6nbelleklenemez olarak i\u015faretliyor\n(<code>no-store<\/code> + <code>DONOTCACHEPAGE<\/code> + LiteSpeed kontrol\u00fc). Yedeklemeniz bundan etkilenmiyordu;\netkilenen yaln\u0131zca panelin ayarlar\u0131n\u0131z\u0131 okumas\u0131 ve durum g\u00f6stergeleriydi.<\/li>\n<li><strong>S3 uyumlu depolamada \u00f6zel port kullanan hedeflerde imza hatas\u0131 (kritik).<\/strong> Kendi\nsunucunuzda \u00e7al\u0131\u015fan MinIO gibi, adresinde port bulunan (<code>https:\/\/depo.ornek.com:9000<\/code>)\nbir S3 hedefi tan\u0131mlad\u0131ysan\u0131z, eklentinin \u00fcretti\u011fi imza panelin \u00fcretti\u011finden FARKLI\nolabiliyordu ve y\u00fckleme <code>SignatureDoesNotMatch<\/code> hatas\u0131yla sessizce reddediliyordu.\nSebep: <code>Host<\/code> ba\u015fl\u0131\u011f\u0131 varsay\u0131lan portu (http'de 80, https'te 443) g\u00f6stermez; eklenti\nise portu her ko\u015fulda ekliyordu. Art\u0131k panelle birebir ayn\u0131 kural uygulan\u0131yor.\nAmazon S3, Google Cloud Storage, Wasabi gibi standart portlu hedefleri kullan\u0131yorsan\u0131z\nbu sorundan etkilenmediniz.<\/li>\n<\/ul>\n\n<h4>1.54.6<\/h4>\n\n<ul>\n<li>Bu s\u00fcr\u00fcm SAHAYA H\u0130\u00c7 \u00c7IKMADI. S\u00fcr\u00fcm numaras\u0131 deponun i\u00e7inde bir an i\u00e7in ayarland\u0131 ama\nyay\u0131nlanmadan \u00f6nce bir sonraki d\u00fczeltmeyle birle\u015ftirildi ve 1.54.7 olarak yay\u0131nland\u0131.\nKay\u0131t, \"1.54.6'ya ne oldu?\" sorusunun cevab\u0131 olarak burada duruyor.<\/li>\n<\/ul>\n\n<h4>1.54.5 \u2014 2026-08-17<\/h4>\n\n<ul>\n<li><strong>Hari\u00e7 tutma listesi yede\u011fe H\u0130\u00c7 uygulanm\u0131yordu (kritik).<\/strong> Dosya b\u00f6l\u00fcm\u00fcnde belirledi\u011finiz\nhari\u00e7 tutma kal\u0131plar\u0131 yaln\u0131zca ekranda \u00e7al\u0131\u015f\u0131yordu: rozet do\u011fru say\u0131y\u0131 g\u00f6steriyor,\n\"ne kadar yer kazand\u0131r\u0131r?\" \u00f6l\u00e7\u00fcm\u00fc do\u011fru sonucu veriyor, panele bildirilen liste de\ndo\u011fruydu \u2014 ama yede\u011fi \u00dcRETEN kod bu listeyi BA\u015eKA bir kay\u0131ttan okuyordu ve oraya hi\u00e7bir\nzaman bir \u015fey yaz\u0131lm\u0131yordu. Sonu\u00e7: liste daima bo\u015f say\u0131l\u0131yor ve hari\u00e7 tuttu\u011funuz her \u015fey\nar\u015five giriyordu. Ayn\u0131 hata boyut \u00f6l\u00e7\u00fcm\u00fcn\u00fc de etkiliyordu (site boyutu oldu\u011fundan b\u00fcy\u00fck\ng\u00f6r\u00fcn\u00fcyordu). Sahada \u00f6l\u00e7\u00fcld\u00fc: tahmin \"yede\u011fe giren 9.214 dosya\" derken yedek 16.669 dosya\ni\u015fliyordu \u2014 aradaki ~8,1 GB tam olarak hari\u00e7 tutulmu\u015f olmas\u0131 gereken veriydi. Art\u0131k\nliste tek bir kaynaktan okunuyor; eski kay\u0131tta de\u011fer b\u0131rakm\u0131\u015f kurulumlar i\u00e7in o kay\u0131t da\nbirle\u015ftiriliyor (hi\u00e7bir ayar kaybolmaz).<\/li>\n<\/ul>\n\n<h4>1.54.4 \u2014 2026-08-17<\/h4>\n\n<ul>\n<li><strong>Ayn\u0131 sitede iki yedek birden ba\u015flayabiliyordu (kritik).<\/strong> Eklentinin iki yedek yolu\nvard\u0131 ve her biri AYRI bir \u00e7al\u0131\u015fma kilidi kullan\u0131yordu: panelin s\u00fcrd\u00fcrd\u00fc\u011f\u00fc par\u00e7al\u0131\nyedek ile zamanlay\u0131c\u0131n\u0131n tetikledi\u011fi yedek birbirini hi\u00e7 g\u00f6rm\u00fcyordu. Panel bir yede\u011fi\npar\u00e7a par\u00e7a s\u00fcrd\u00fcr\u00fcrken gelen zamanl\u0131 tetik, ayn\u0131 sitede \u0130K\u0130NC\u0130 bir tam yedek\nba\u015flatabiliyordu \u2014 iki kat disk, iki kat CPU ve zaten s\u0131n\u0131rl\u0131 bir sunucuda ikisinin de\nbitememesi. Art\u0131k iki yol tek kilidi payla\u015f\u0131yor: hangisi \u00f6nce ba\u015flad\u0131ysa di\u011feri\nilerlemeyi bozmadan \"me\u015fgul\" deyip \u00e7ekiliyor.<\/li>\n<\/ul>\n\n<h4>1.54.3 \u2014 2026-08-17<\/h4>\n\n<ul>\n<li><strong>Eklentinin KEND\u0130 zamanlanm\u0131\u015f yede\u011fi b\u00fcy\u00fck sitelerde sonsuz d\u00f6ng\u00fcye giriyordu (kritik).<\/strong>\nPanelden tetiklenen yedek 1.49'da yeni ar\u015fiv motoruna ge\u00e7irilmi\u015fti; eklentinin kendi\nzamanlamas\u0131yla \u00e7al\u0131\u015fan yedek ise eski motorda (PHP ZipArchive) kalm\u0131\u015ft\u0131. Bu motor ar\u015fivi\nher kapan\u0131\u015fta BA\u015eTAN YAZAR \u2014 \u00fcstelik a\u00e7\u0131k dosya s\u0131n\u0131r\u0131 y\u00fcz\u00fcnden her 400 dosyada bir\nkapan\u0131\u015f yap\u0131l\u0131yordu. Sonu\u00e7: ar\u015fiv b\u00fcy\u00fcd\u00fck\u00e7e her tur, ar\u015fivin tamam\u0131n\u0131 yan\u0131na a\u00e7t\u0131\u011f\u0131\nge\u00e7ici bir dosyaya (<code>.part<\/code>) yeniden kopyal\u0131yor; payla\u015f\u0131ml\u0131 hosting iste\u011fi 60 saniyede\nkesti\u011fi i\u00e7in kopya hep yar\u0131m kal\u0131yor ve bir sonraki tur s\u0131f\u0131rdan ba\u015fl\u0131yordu. Ge\u00e7ici\nklas\u00f6rde b\u00fcy\u00fcy\u00fcp b\u00fcy\u00fcy\u00fcp s\u0131f\u0131rlanan bir dosya, s\u00fcrekli me\u015fgul bir sunucu ve hi\u00e7 bitmeyen\nbir yedek. Art\u0131k her iki yol da ayn\u0131 ak\u0131\u015f motorunu kullan\u0131yor: girdiler ar\u015fivin sonuna\neklenir, hi\u00e7bir a\u015famada yeniden yazma ve ge\u00e7ici kopya olmaz.<\/li>\n<\/ul>\n\n<h4>1.54.2 \u2014 2026-08-17<\/h4>\n\n<ul>\n<li><strong>B\u00fcy\u00fck sitelerde yedek asla bitmiyordu \u2014 ar\u015fiv art\u0131k kopyalanm\u0131yor, TA\u015eINIYOR (kritik).<\/strong>\n\"Domain i\u00e7i depolama\" hedefinde son ad\u0131m, tamamlanan ar\u015fivi ge\u00e7ici klas\u00f6rden yedek\nklas\u00f6r\u00fcne koymakt\u0131 ve bunu KOPYALAYARAK yap\u0131yordu. 7-9 GB'l\u0131k bir sitede bu kopya\ndakikalar s\u00fcrer; payla\u015f\u0131ml\u0131 hosting iste\u011fi 60 saniyede kesti\u011fi i\u00e7in kopya hep yar\u0131m\nkal\u0131yor ve bir sonraki tur AYNI kopyay\u0131 s\u0131f\u0131rdan ba\u015flat\u0131yordu. Sonu\u00e7: yedek klas\u00f6r\u00fcnde\nb\u00fcy\u00fcy\u00fcp b\u00fcy\u00fcy\u00fcp s\u0131f\u0131rlanan bir dosya, dolan disk ve hi\u00e7 tamamlanmayan bir yedek.\nKaynak ve hedef zaten ayn\u0131 disktedir; art\u0131k dosya ta\u015f\u0131n\u0131yor \u2014 i\u015flem an\u0131nda bitiyor,\nek disk alan\u0131 istemiyor ve yar\u0131da kalam\u0131yor. Ek bir yedek hedefiniz (mirror) varsa\nar\u015five h\u00e2l\u00e2 ihtiya\u00e7 duyuldu\u011fu i\u00e7in eski davran\u0131\u015f s\u00fcr\u00fcyor.<\/li>\n<li><strong>Ar\u015fivin SHA-256 \u00f6zeti her turda yeniden hesaplan\u0131yordu (kritik).<\/strong> Y\u00fckleme a\u015famas\u0131na\nbirden \u00e7ok kez girilir (izin iste \u2192 y\u00fckle \u2192 kay\u0131t onay\u0131) ve her giri\u015fte 7-9 GB'l\u0131k\nar\u015fivin tamam\u0131 ba\u015ftan sona okunup \u00f6zetleniyordu. Tek ge\u00e7i\u015f bile 60 saniyelik istek\npenceresine s\u0131\u011fmad\u0131\u011f\u0131 i\u00e7in yedek, ar\u015fiv \u00e7oktan haz\u0131rken %95'te tak\u0131l\u0131 kal\u0131yordu.\nAr\u015fiv o noktadan sonra de\u011fi\u015fmedi\u011fi i\u00e7in \u00f6zet art\u0131k bir kez hesaplan\u0131yor.<\/li>\n<li><strong>Yar\u0131m kalan yedeklerin GB'l\u0131k art\u0131klar\u0131 geride kalabiliyordu.<\/strong> Yar\u0131da kesilen bir\nyede\u011fin oturum bilgisi kaybolursa (nesne \u00f6nbelle\u011fi temizlenir, veritaban\u0131 budan\u0131r)\neklentinin elinde silinecek dosyan\u0131n yolu kalm\u0131yordu; sahada iki terk edilmi\u015f ar\u015fiv\n(9,0 GB + 7,6 GB) ayn\u0131 anda g\u00f6r\u00fcld\u00fc. Ge\u00e7ici dosya yollar\u0131 art\u0131k oturumdan ba\u011f\u0131ms\u0131z\nolarak da tutuluyor ve bir sonraki yedek ba\u015flarken \u00f6nceki ko\u015funun art\u0131klar\u0131 siliniyor.<\/li>\n<\/ul>\n\n<h4>1.54.1 \u2014 2026-08-17<\/h4>\n\n<ul>\n<li><strong>Ar\u015fiv yaz\u0131c\u0131s\u0131nda k\u0131sa yazma art\u0131k yakalan\u0131yor (yedek b\u00fct\u00fcnl\u00fc\u011f\u00fc).<\/strong> Disk ya da hosting\nkotas\u0131 doldu\u011funda i\u015fletim sistemi bir yazmay\u0131 YARIM tamamlayabilir. Yaz\u0131c\u0131 yaln\u0131zca \"yazma\ntamamen ba\u015far\u0131s\u0131z oldu mu\" diye bak\u0131yordu; yar\u0131m yazma ba\u015far\u0131 say\u0131l\u0131yor ve ar\u015fivde izlenen\nkonum ger\u00e7ek dosya boyutundan kay\u0131yordu. Bu kayma, o noktadan sonraki t\u00fcm dosya kay\u0131tlar\u0131n\u0131\nyanl\u0131\u015f yere i\u015faret ettirir \u2014 ar\u015fiv \"ge\u00e7erli\" g\u00f6r\u00fcn\u00fcr ama a\u00e7\u0131lamaz. Art\u0131k yar\u0131m yazmalar\ntamamlan\u0131yor, ger\u00e7ekten yaz\u0131lam\u0131yorsa paketleme durduruluyor. Ayn\u0131 bo\u015fluk 4 GB \u00fcst\u00fc\nar\u015fivlerin son kayd\u0131nda ve dosya k\u00fc\u00e7\u00fcld\u00fc\u011f\u00fcnde yaz\u0131lan dolguda da vard\u0131.<\/li>\n<li><strong>\u015eifreli yedekte \"yer yok\" hatas\u0131 art\u0131k do\u011fru s\u00f6yleniyor.<\/strong> \u015eifreleme ge\u00e7ici olarak\nar\u015fivin ~2 kat\u0131 bo\u015f alan ister; alan yetmedi\u011finde mesaj \"openssl yok ya da do\u011frulama\nba\u015far\u0131s\u0131z\" diyordu ve sorun yanl\u0131\u015f yerde aran\u0131yordu. Art\u0131k gereken\/mevcut alan yaz\u0131l\u0131yor\nve \u015fifreleme daha ba\u015flamadan kontrol ediliyor.<\/li>\n<\/ul>\n\n<h4>1.54.0 \u2014 2026-08-17<\/h4>\n\n<ul>\n<li><strong>Yedek b\u00fct\u00fcnl\u00fc\u011f\u00fc \u2014 ar\u015fiv art\u0131k y\u00fcklenmeden \u00d6NCE do\u011frulan\u0131yor (kritik).<\/strong> Eklenti, \u00fcretti\u011fi\nar\u015fivi bug\u00fcne kadar hi\u00e7 s\u0131nam\u0131yordu: yazma s\u0131ras\u0131nda bir hata olsa bile (disk dolu, hosting\nkotas\u0131, ge\u00e7ici I\/O hatas\u0131) paketleme sonuna kadar devam ediyor, dosya \"ge\u00e7erli bir zip\" gibi\ng\u00f6r\u00fcn\u00fcyor ve bulut alan\u0131n\u0131za \u00f6yle y\u00fckleniyordu. Bozukluk ancak GER\u0130 Y\u00dcKLEME g\u00fcn\u00fc ortaya\n\u00e7\u0131k\u0131yordu. Art\u0131k: (1) yazma hatas\u0131 oldu\u011fu anda paketleme durdurulur ve yar\u0131m ar\u015fiv silinir \u2014\nyanl\u0131\u015f bir \"ba\u015far\u0131l\u0131\" kayd\u0131 olu\u015fmaz; (2) tamamlanan her ar\u015fiv, y\u00fcklemeden ve \u015fifrelemeden\n\u00f6nce yap\u0131sal olarak do\u011frulan\u0131r; do\u011frulamay\u0131 ge\u00e7emeyen ar\u015fiv g\u00f6nderilmez.<\/li>\n<li><strong>Art\u0131ml\u0131 yedeklerde \"de\u011fi\u015fmemi\u015f dosyay\u0131 atla\" kural\u0131 d\u00fczeltildi.<\/strong> Kaynak s\u0131n\u0131r\u0131 olan\nhosting'lerde devreye giren par\u00e7al\u0131 yedekleme yolunda bu kural hesaplan\u0131yor ama\nUYGULANMIYORDU: yedek \"art\u0131ml\u0131\" olarak i\u015faretlense de her turda sitenin TAMAMI yeniden\npaketlenip y\u00fckleniyordu. Bu, gereksiz s\u00fcre, bant geni\u015fli\u011fi ve bulut alan\u0131 t\u00fcketiyordu.<\/li>\n<li><strong>Yedeklenemeyen dosya art\u0131k sessiz kalm\u0131yor.<\/strong> Bir dosya izin\/okuma hatas\u0131 y\u00fcz\u00fcnden ar\u015five\neklenemedi\u011finde eskiden hi\u00e7bir iz kalm\u0131yor, \u00fcstelik o dosya \"yedeklendi\" listesine yaz\u0131ld\u0131\u011f\u0131\ni\u00e7in SONRAK\u0130 art\u0131ml\u0131 yedeklerde de atlan\u0131yordu \u2014 yani bir daha hi\u00e7bir yede\u011fe girmiyordu.\nArt\u0131k yaln\u0131zca ger\u00e7ekten ar\u015five giren dosyalar listeye yaz\u0131l\u0131r ve eklenemeyen dosya say\u0131s\u0131\nilerleme ekran\u0131nda uyar\u0131 olarak g\u00f6sterilir.<\/li>\n<li><strong>Veritaban\u0131 olmadan \"tam yedek\" \u00fcretilmiyor.<\/strong> Do\u011frudan yedekleme yolunda veritaban\u0131 d\u00f6k\u00fcm\u00fc\nar\u015five eklenemese bile yedek ba\u015far\u0131l\u0131 say\u0131l\u0131yordu; i\u00e7inde veritaban\u0131 olmayan bu ar\u015fiv\nsaklama sayac\u0131na girip ger\u00e7ekten tam olan eski bir yede\u011fin silinmesine yol a\u00e7abiliyordu.\nArt\u0131k bu durumda yedek a\u00e7\u0131k\u00e7a ba\u015far\u0131s\u0131z olur.<\/li>\n<li><strong>E-posta yede\u011finde de ayn\u0131 koruma.<\/strong> Bir e-postan\u0131n ar\u015five yaz\u0131lmas\u0131 ba\u015far\u0131s\u0131z oldu\u011funda\nileti art\u0131k \"yedeklendi\" say\u0131lm\u0131yor.<\/li>\n<li>PHP s\u00fcr\u00fcm kap\u0131s\u0131 eklendi: eklenti, gerektirdi\u011fi PHP s\u00fcr\u00fcm\u00fcn\u00fcn alt\u0131ndaki sunucularda\ndosyalar\u0131n\u0131 y\u00fcklemeden \u00f6nce durur ve y\u00f6netici paneline a\u00e7\u0131klay\u0131c\u0131 bir uyar\u0131 basar.<\/li>\n<\/ul>\n\n<p><strong>Geri y\u00fckleme d\u00fczeltmeleri (ayn\u0131 s\u00fcr\u00fcmde):<\/strong><\/p>\n\n<ul>\n<li><strong>Geri y\u00fcklemede bile\u015fen se\u00e7imi art\u0131k UYGULANIYOR (kritik).<\/strong> Panelde \"Veritaban\u0131\" kutusunu\nkapat\u0131p yaln\u0131zca dosyalar\u0131 geri y\u00fckledi\u011finizde eklenti bu se\u00e7imi YOK SAYIYOR ve yedekteki\nveritaban\u0131 d\u00f6k\u00fcm\u00fcn\u00fc canl\u0131 veritaban\u0131n\u0131za uyguluyordu \u2014 a\u00e7\u0131k\u00e7a hari\u00e7 tuttu\u011funuz, geri d\u00f6n\u00fc\u015f\u00fc\nolmayan bir \u00fczerine yazma. Dosya, veritaban\u0131 ve e-posta se\u00e7imlerinin \u00fc\u00e7\u00fc de art\u0131k dikkate\nal\u0131n\u0131yor.<\/li>\n<li><strong>\"Bu dosyaya dokunma\" listesi art\u0131k S\u0130LME ad\u0131m\u0131nda da ge\u00e7erli.<\/strong> Hari\u00e7 tutma yaln\u0131zca yazma\ns\u0131ras\u0131nda uygulan\u0131yordu; art\u0131ml\u0131 geri y\u00fcklemenin \"silinenler\" listesinde yer alan korumal\u0131\nbir yol (tipik olarak <code>wp-config.php<\/code> veya <code>wp-content\/uploads<\/code> alt\u0131ndaki dosyalar) yine de\nsiteden siliniyordu \u2014 yani koruma tam tersine d\u00f6n\u00fcyordu.<\/li>\n<li><strong>Hi\u00e7bir dosya yaz\u0131lamad\u0131ysa silme ad\u0131m\u0131 art\u0131k \u00e7al\u0131\u015fm\u0131yor.<\/strong> Ar\u015fiv a\u00e7\u0131ld\u0131 ama izin\/disk\nsorunu y\u00fcz\u00fcnden tek bir dosya bile yaz\u0131lamad\u0131ysa, geri y\u00fckleme siteyi onarmak yerine yaln\u0131zca\nsilme uyguluyordu \u2014 kurtarma an\u0131nda ek veri kayb\u0131. Art\u0131k bu durumda silme atlan\u0131r ve sebebi\nraporlan\u0131r.<\/li>\n<li><strong>Yar\u0131m veritaban\u0131 d\u00f6k\u00fcm\u00fc art\u0131k uygulanmadan reddediliyor.<\/strong> S\u0131k\u0131\u015ft\u0131r\u0131lm\u0131\u015f (.sql.gz) d\u00f6k\u00fcmde\n\"tamamland\u0131\" i\u015fareti yaln\u0131zca t\u00fcm ifadeler \u00c7ALI\u015eTIRILDIKTAN sonra kontrol ediliyordu: yar\u0131m\nbir d\u00f6k\u00fcm canl\u0131 veritaban\u0131na zaten uygulanm\u0131\u015f oluyor, ard\u0131ndan \"k\u0131smi geri y\u00fckleme iptal\nedildi\" deniyordu \u2014 geri alma diye bir \u015fey yoktu. Art\u0131k d\u00f6k\u00fcm \u00f6nce taran\u0131yor; i\u015faret yoksa\nveritaban\u0131na tek bir ifade bile uygulanm\u0131yor.<\/li>\n<li><strong>Yar\u0131m yaz\u0131lan dosya art\u0131k sitede b\u0131rak\u0131lm\u0131yor.<\/strong> Geri y\u00fckleme s\u0131ras\u0131nda disk dolarsa kesik\nbir dosya yaz\u0131l\u0131p \"ba\u015far\u0131l\u0131\" say\u0131l\u0131yordu. Art\u0131k kesik dosya siliniyor, say\u0131l\u0131yor ve sonu\u00e7\n\"k\u0131smi\" olarak i\u015faretleniyor.<\/li>\n<li><strong>Geri y\u00fckleme art\u0131k eklentinin kendi dosyalar\u0131n\u0131n \u00fczerine yazm\u0131yor.<\/strong> Ar\u015fivdeki eski eklenti\ns\u00fcr\u00fcm\u00fc, i\u015flem s\u00fcrerken \u00e7al\u0131\u015fan eklentinin \u00fczerine yaz\u0131labiliyordu.<\/li>\n<li><strong>Kullan\u0131lmayan \u00fc\u00e7 geri y\u00fckleme u\u00e7 noktas\u0131 kald\u0131r\u0131ld\u0131<\/strong> (<code>\/restore-zip<\/code>, <code>\/restore-db<\/code>,\n  \/restore-wpconfig). Bunlar yukar\u0131daki korumalar\u0131n hi\u00e7birini uygulam\u0131yordu ve zaten\n\u00e7a\u011fr\u0131lm\u0131yorlard\u0131; ayr\u0131ca sitenizin k\u00f6k dizinindeki dosyalar\u0131 (<code>index.php<\/code>, <code>wp-config.php<\/code>,\n  .htaccess \u2026) sessizce atlayan bir hata i\u00e7eriyorlard\u0131.<\/li>\n<\/ul>\n\n<h4>1.53.3 \u2014 2026-08-16<\/h4>\n\n<ul>\n<li><strong>Geri y\u00fcklemede \"bu dosyay\u0131 koru\" se\u00e7imi art\u0131k UYGULANIYOR (\u00f6nemli).<\/strong> Panelde bir dosyay\u0131\nya da klas\u00f6r\u00fc geri y\u00fckleme d\u0131\u015f\u0131nda b\u0131rakt\u0131\u011f\u0131n\u0131zda, eklenti bu se\u00e7imi YOK SAYIYOR ve dosyan\u0131n\n\u00fczerine yaz\u0131yordu. Tipik olarak <code>wp-config.php<\/code>, <code>.htaccess<\/code> ve  &hellip;<\/li>\n<\/ul>","raw_excerpt":"WordPress yedekleme eklentisi: site ve veritaban\u0131 yedek alma, tek t\u0131kla geri y\u00fckleme, site ta\u015f\u0131ma ve vir\u00fcs temizleme. Tamamen \u00fccretsiz.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/yor.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/332082","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/yor.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/yor.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/yor.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=332082"}],"author":[{"embeddable":true,"href":"https:\/\/yor.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/kamkactemha"}],"wp:attachment":[{"href":"https:\/\/yor.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=332082"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/yor.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=332082"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/yor.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=332082"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/yor.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=332082"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/yor.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=332082"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/yor.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=332082"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}