{"id":1172,"date":"2026-03-23T08:43:36","date_gmt":"2026-03-23T05:43:36","guid":{"rendered":"https:\/\/allinonewpsettings.com\/blog\/?p=1172"},"modified":"2026-08-04T21:56:30","modified_gmt":"2026-08-04T21:56:30","slug":"wordpress-kalici-baglanti-404-hatasi","status":"publish","type":"post","link":"https:\/\/allinonewpsettings.com\/blog\/tr\/wordpress-kalici-baglanti-404-hatasi\/","title":{"rendered":"WordPress Kal\u0131c\u0131 Ba\u011flant\u0131lar\u0131 404 Veriyor: Nedenler ve \u00c7\u00f6z\u00fcmler"},"content":{"rendered":"

Deneme ortam\u0131ndan \u00fcretime ta\u015f\u0131nan bir sitede ana sayfa ve wp-admin<\/code> \u00e7al\u0131\u015f\u0131yor, ancak b\u00fct\u00fcn yaz\u0131 adresleri web sunucusunun 404 sayfas\u0131na d\u00fc\u015f\u00fcyor. Kal\u0131c\u0131 Ba\u011flant\u0131 Ayarlar\u0131n\u0131 kaydetmek k\u0131sa s\u00fcreli \u00e7\u00f6z\u00fcm gibi g\u00f6r\u00fcnse de ikinci sunucuya giden istekler yine ba\u015far\u0131s\u0131z oluyor.<\/p>\n

Bu tablo eksik i\u00e7erikten \u00e7ok rota yap\u0131land\u0131rmas\u0131na i\u015faret eder. Yeni y\u00f6nlendirmeler eklemeden veya kal\u0131c\u0131 ba\u011flant\u0131lar\u0131 tekrar tekrar kaydetmeden \u00f6nce 404 yan\u0131t\u0131n\u0131 hangi katman\u0131n \u00fcretti\u011fini belirleyin; ard\u0131ndan b\u00fct\u00fcn sunucularda ayn\u0131 web k\u00f6k dizininin ve rewrite kurallar\u0131n\u0131n etkin oldu\u011funu do\u011frulay\u0131n.<\/p>\n

\n\u0130\u00e7indekiler<\/strong><\/p>\n
    \n
  1. Bu konu ne anlama gelir?<\/a><\/li>\n
  2. Ger\u00e7ek\u00e7i bir WordPress \u00f6rne\u011fi<\/a><\/li>\n
  3. Neden \u00f6nemlidir ve ne zaman kullan\u0131l\u0131r?<\/a><\/li>\n
  4. Yeni ba\u015flayanlar i\u00e7in anla\u015f\u0131l\u0131r yol<\/a><\/li>\n
  5. \u0130leri teknik yol<\/a><\/li>\n
  6. Riskler, s\u0131k hatalar, yedek ve geri d\u00f6n\u00fc\u015f<\/a><\/li>\n
  7. AIOWS Y\u00f6nlendirme Y\u00f6neticisi<\/a><\/li>\n
  8. \u0130lgili AIOWS yaz\u0131lar\u0131<\/a><\/li>\n
  9. Sonu\u00e7 ve \u00f6nerilen yol<\/a><\/li>\n
  10. Resm\u00ee kaynaklar<\/a><\/li>\n<\/ol>\n<\/div>\n

    Bu konu ne anlama gelir?<\/h2>\n

    Kal\u0131c\u0131 ba\u011flant\u0131 404 hatas\u0131, okunabilir adresin WordPress\u2019in front controller\u2019\u0131 olan index.php<\/code> dosyas\u0131na ula\u015fmamas\u0131 veya olu\u015fan sorgunun i\u00e7erikle e\u015fle\u015ftirilememesidir. Web sunucusu kurallar\u0131, sanal sunucu ayar\u0131, multisite yollar\u0131, \u00f6zel yaz\u0131 t\u00fcrlerinin kayd\u0131, u\u00e7 nokta \u00e7ak\u0131\u015fmalar\u0131 ve tek bir i\u00e7eri\u011fin durumu ya da slug\u2019\u0131 bu hataya yol a\u00e7abilir.<\/p>\n

    Sunucunun kendi 404 sayfas\u0131 ile WordPress temas\u0131n\u0131n 404 \u015fablonu farkl\u0131 ipu\u00e7lar\u0131 verir. B\u00fct\u00fcn okunabilir adreslerin bozulmas\u0131 da yaln\u0131z bir yaz\u0131n\u0131n bulunamamas\u0131ndan ayr\u0131d\u0131r. Hedef y\u00f6nlendirmesi, bozuk WordPress rotas\u0131n\u0131 onarmaz.<\/p>\n

    Ger\u00e7ek\u00e7i bir WordPress \u00f6rne\u011fi<\/h2>\n

    \u00d6rnekte \/?p=123<\/code> gibi do\u011frudan sorgu adresi yaz\u0131y\u0131 a\u00e7arken \/ornek-yazi\/<\/code> 404 veriyor. Ana sayfa ve statik dosyalar da \u00e7al\u0131\u015f\u0131yor. Y\u00fck dengeleyicinin arkas\u0131ndaki sunuculardan biri do\u011fru front controller kural\u0131n\u0131, di\u011feri ise eski sanal sunucu ayar\u0131n\u0131 kullan\u0131yor.<\/p>\n

    Kal\u0131c\u0131 \u00e7\u00f6z\u00fcm, etkin rewrite yap\u0131land\u0131rmas\u0131n\u0131 b\u00fct\u00fcn sunuculara ayn\u0131 \u015fekilde da\u011f\u0131t\u0131p g\u00fcvenli bi\u00e7imde yeniden y\u00fcklemektir. Ard\u0131ndan WordPress rewrite kurallar\u0131 desteklenen y\u00f6ntemle bir kez yenilenebilir; bu i\u015flem sunucular aras\u0131ndaki fark\u0131 gizleyen rutin bir \u00e7\u00f6z\u00fcm olmamal\u0131d\u0131r.<\/p>\n

    Neden \u00f6nemlidir ve ne zaman kullan\u0131l\u0131r?<\/h2>\n

    Bozuk kal\u0131c\u0131 ba\u011flant\u0131lar, y\u00f6netim paneli normal g\u00f6r\u00fcn\u00fcrken sitenin neredeyse b\u00fct\u00fcn genel i\u00e7eri\u011fini eri\u015filemez h\u00e2le getirebilir. Do\u011fru te\u015fhis, ger\u00e7ekten silinmi\u015f bir sayfay\u0131 sistem genelindeki rota hatas\u0131ndan ay\u0131rmay\u0131 da sa\u011flar.<\/p>\n

    Ana sayfa, bir yaz\u0131, bir sayfa, ar\u015fiv, do\u011frudan sorgu adresi, REST yolu ve statik dosyadan olu\u015fan k\u00fc\u00e7\u00fck bir listeyi s\u0131nay\u0131n. Durum kodu ve 404 sayfas\u0131n\u0131n g\u00f6r\u00fcn\u00fcm\u00fc, iste\u011fin web sunucusunda m\u0131 kald\u0131\u011f\u0131n\u0131 yoksa WordPress\u2019e mi ula\u015ft\u0131\u011f\u0131n\u0131 g\u00f6sterir.<\/p>\n

    Yeni ba\u015flayanlar i\u00e7in anla\u015f\u0131l\u0131r yol<\/h2>\n
      \n
    1. Etkin web sunucusu yap\u0131land\u0131rmas\u0131n\u0131 yedekleyin ve nas\u0131l geri y\u00fcklenece\u011fini do\u011frulay\u0131n.<\/li>\n
    2. WordPress Adresini, Site Adresini ve se\u00e7ili kal\u0131c\u0131 ba\u011flant\u0131 yap\u0131s\u0131n\u0131 kontrol edin.<\/li>\n
    3. Bozulan okunabilir adresi do\u011frudan sorgu kar\u015f\u0131l\u0131\u011f\u0131yla k\u0131yaslay\u0131p 404\u2019\u00fc sunucunun mu WordPress\u2019in mi \u00fcretti\u011fini belirleyin.<\/li>\n
    4. Her sunucuda etkin sanal sunucu ayar\u0131n\u0131, web k\u00f6k dizinini ve Apache ya da Nginx\u2019in WordPress isteklerini index.php<\/code> dosyas\u0131na ileten kural\u0131n\u0131 inceleyin.<\/li>\n
    5. Sunucu ayar\u0131 d\u00fczeltildikten sonra WordPress rewrite kurallar\u0131n\u0131 desteklenen y\u00f6ntemle bir kez yenileyin ve \u00f6rnek rotalar\u0131 yeniden s\u0131nay\u0131n.<\/li>\n<\/ol>\n

      \u0130leri teknik yol<\/h2>\n

      Apache\u2019de ger\u00e7ekten kullan\u0131lan sanal sunucu ve .htaccess<\/code> i\u00e7in ge\u00e7erli AllowOverride<\/code> ayar\u0131 \u00f6nemlidir. Nginx\u2019te etkin try_files<\/code> kural\u0131n\u0131 inceleyin. Kapsay\u0131c\u0131 veya cluster yap\u0131s\u0131nda b\u00fct\u00fcn d\u00fc\u011f\u00fcmlerin ayn\u0131 s\u00fcr\u00fcm ve yap\u0131land\u0131rmay\u0131 kulland\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n.<\/p>\n

      Yaln\u0131z \u00f6zel bir yaz\u0131 t\u00fcr\u00fc, taksonomi, dil \u00f6neki veya multisite yolu bozuksa rewrite kayd\u0131n\u0131n ne zaman y\u00fcklendi\u011fini ve ba\u015fka bir u\u00e7 noktayla \u00e7ak\u0131\u015f\u0131p \u00e7ak\u0131\u015fmad\u0131\u011f\u0131n\u0131 ara\u015ft\u0131r\u0131n. Normal yaz\u0131lar \u00e7al\u0131\u015f\u0131rken sorun dar bir alanda kalabilir.<\/p>\n

      Riskler, s\u0131k hatalar, yedek ve geri d\u00f6n\u00fc\u015f<\/h2>\n

      Bar\u0131nd\u0131rma ve g\u00fcvenlik kurallar\u0131n\u0131 yedeklemeden .htaccess<\/code> dosyas\u0131n\u0131n \u00fczerine yazmay\u0131n. Rota hatas\u0131n\u0131 geni\u015f y\u00f6nlendirmelerle gizlemek d\u00f6ng\u00fc veya yan\u0131lt\u0131c\u0131 soft 404 sayfalar\u0131 olu\u015fturabilir. Kal\u0131c\u0131 ba\u011flant\u0131lar\u0131 s\u00fcrekli kaydetmek de yaln\u0131z bir sunucuyu ge\u00e7ici olarak d\u00fczeltebilir.<\/p>\n

      Y\u00f6netim paneli, REST, beslemeler veya statik dosyalar bozulursa, sunucu ayar\u0131 yeniden y\u00fcklenemezse ya da d\u00f6ng\u00fc olu\u015fursa \u00f6nceki yap\u0131land\u0131rmaya d\u00f6n\u00fcn. D\u00fczeltme b\u00fct\u00fcn d\u00fc\u011f\u00fcmlerde, \u00f6nbellek s\u00fcresi dolduktan ve hizmet yeniden ba\u015flat\u0131ld\u0131ktan sonra da \u00e7al\u0131\u015fmal\u0131d\u0131r.<\/p>\n

      \n

      AIOWS nas\u0131l yard\u0131mc\u0131 olur?<\/p>\n

      AIOWS Y\u00f6nlendirme Y\u00f6neticisi<\/h2>\n

      AIOWS Y\u00f6nlendirme Y\u00f6neticisi, WordPress i\u00e7indeki a\u00e7\u0131k y\u00f6nlendirme kurallar\u0131n\u0131 g\u00f6r\u00fcn\u00fcr tutarak bu katman\u0131 kal\u0131c\u0131 ba\u011flant\u0131 rotas\u0131ndan ay\u0131rmaya yard\u0131mc\u0131 olur. \u0130nceleme s\u0131ras\u0131nda 404 yan\u0131t\u0131n\u0131 WordPress kural\u0131n\u0131n m\u0131 yoksa daha \u00f6nce devreye giren CDN ya da web sunucusunun mu \u00fcretti\u011fi anla\u015f\u0131labilir.<\/p>\n

      Sunucudaki rewrite kural\u0131 ve WordPress kal\u0131c\u0131 ba\u011flant\u0131 durumu netle\u015fene kadar y\u00f6nlendirmeleri de\u011fi\u015ftirmeyin. Yaln\u0131z belirli bir eski adres ger\u00e7ekten yay\u0131ndaki ilgili bir i\u00e7eri\u011fe ta\u015f\u0131nd\u0131ysa y\u00f6netilen y\u00f6nlendirme ekleyin; site genelindeki rota ar\u0131zas\u0131n\u0131 bununla kapatmay\u0131n.<\/p>\n

      Mod\u00fcl Apache veya Nginx ayarlar\u0131n\u0131 onaramaz, cluster d\u00fc\u011f\u00fcmlerini e\u015fitleyemez ve eksik i\u00e7eri\u011fi geri getiremez. Bu yaz\u0131daki rol\u00fc, WordPress y\u00f6nlendirme katman\u0131n\u0131 tan\u0131 s\u0131ras\u0131nda denetlenebilir tutmakt\u0131r.<\/p>\n

      AIOWS Y\u00f6nlendirme Y\u00f6neticisi \u00f6zelli\u011fini inceleyin<\/a>AIOWS planlar\u0131n\u0131 kar\u015f\u0131la\u015ft\u0131r\u0131n<\/a><\/p>\n<\/section>\n

      \u0130lgili AIOWS yaz\u0131lar\u0131<\/h2>\n