WordPress Block Editor Load Nahi Ho Raha? Aise Karein Fix

Zyadatar mamlon mein, jo WordPress block editor load nahi hota uska kaaran ek JavaScript error hota hai — kisi plugin ya theme ka ek toota hua script poore React app ko rok deta hai, aur editor kabhi render hi nahi ho paata. Apne browser ka developer console kholein (F12, ya Mac par Cmd+Option+I), edit screen ko reload karein, aur laal (red) error padhein. Woh lagbhag hamesha us file ka naam bata deta hai jisne error phenka. Wahi ek line aapko bata deti hai ki kaunsa plugin disable karna hai, aur aap aksar paanch minute ke andar wapas likhne laayak ho jaate hain. WordPress ko dobara install karna, PHP memory limit badhaana, aur Classic Editor par switch karna — internet par milne waale ye teen sabse aam sujhav hain, aur teenon aksar galat kadam hote hain.

Editor jis tarah se toota hai, uska kaaran

Block editor (Gutenberg) ek single-page React application hai jo wp-admin/post.php aur post-new.php ke andar chalti hai. WordPress kai script packages enqueue karta hai — wp-blocks, wp-element, wp-editor, wp-edit-post — aur app wp.domReady() ke zariye bootstrap hota hai. JavaScript pehle uncaught exception par hi chalna band kar deta hai. To agar koi bhi enqueue kiya gaya script editor initialize hote samay error phenkta hai, to uske baad ka sab kuch uske saath hi mar jaata hai. Aapka dhyaan se likha gaya post area ek khaali safed pane mein badal jaata hai ya “The editor has encountered an unexpected error.” message dikhta hai.

Default roop se WordPress admin scripts ko kam requests mein concatenate bhi karta hai. Iska matlab hai ki ek plugin ki tooti hui JS usi bundle mein load hone waale bilkul unrelated scripts ko bhi neeche kheench sakti hai, isiliye sirf behavior se hi asli mujrim hamesha saaf nahi hota. Console se hota hai.

Doosra failure mode alag dikhta hai: editor to load ho jaata hai, lekin save karte samay “Updating failed. The response is not a valid JSON response.” aata hai. Yeh JavaScript ki samasya nahi hai. Editor /wp-json/wp/v2/ par REST API se baat karta hai, aur wapas saaf JSON ki umeed karta hai. Agar koi plugin ya aapki theme ki functions.php JSON se pehle koi PHP notice, warning, ya fatal nikaalti hai — ya koi security plugin REST route block kar deta hai, ya koi redirect plugin URL ko rewrite kar deta hai — to response gadbad ho jaata hai aur editor use parse nahi kar paata.

Ise kaise fix karein, sabse tez pehle

1. Console padhein. DevTools khula rakhkar failure ko dobara reproduce karein. Uncaught TypeError ... some-plugin/build/index.js jaisa error seedha us dosh waale plugin ki taraf ishara karta hai. Yeh akela kadam zyadatar mamlon ko suljha deta hai aur aapko andhaadhundh bisecting se bacha leta hai.

2. Browser ko rule out karein. Hard-refresh karein (Cmd/Ctrl+Shift+R), phir extensions band karke ek incognito window try karein. Ad blockers aur privacy extensions kabhi-kabhi admin scripts ko hata dete hain. Agar incognito mein kaam karta hai, to samasya browser extension ya purani cache hai, aapki site nahi.

3. REST API ko seedhe check karein agar aapko “not a valid JSON” message dikha ho. Browser mein https://yoursite.com/wp-json/ par jaayein. Aapko JSON ki ek deewar milni chahiye. Agar aapko HTML, ek 500, ya login redirect milta hai, to wahi aapka bug hai — koi plugin REST response ko tod raha hai, khud editor nahi.

4. Apne plugins ko bisect karein. Sab ko deactivate karein, confirm karein ki editor load hota hai, phir ek-ek karke tab tak reactivate karein jab tak woh dobara na toote. Agar aap wp-admin se poori tarah locked out hain, to SFTP par folder ka naam badalkar yeh karein:

mv wp-content/plugins wp-content/plugins_off

Folder gaayab hone par WordPress sab kuch deactivate kar deta hai. Ise wapas rename karein, phir plugins ko ek-ek karke andar-bahar karein.

5. Theme test karein. Twenty Twenty-Four par switch karein. Jo theme toothi editor JS enqueue karti hai ya functions.php mein PHP error phenkti hai, woh wahi symptoms paida karti hai.

6. Log on karein aur asli error padhein. REST/JSON failures ke liye khaaskar, wp-config.php mein debugging enable karein:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Fatal error wp-content/debug.log mein exact file aur line number ke saath likh diya jaata hai. Agar woh stack trace ghana ho — namespaced class names, require chains, das line ke trace ke neeche daba hua ek fatal — to use hamare WordPress error log decoder mein paste karein, taaki saaf shabdon mein dekh sakein ki asal mein kaunsa plugin aur line ise trigger kar rahi hai. Yahi “kuch toota hai” aur “iss khaas plugin ki line 214 tooti hai” ke beech ka farak hai.

Agar aapko lagta hai ki script concatenation asli mujrim ko chhupa raha hai, to har script ko alag load hone ke liye force karein taaki console error thik ek file par ishara kare:

define( 'SCRIPT_DEBUG', true );
define( 'CONCATENATE_SCRIPTS', false );

Kya nahi karna chahiye

Classic Editor plugin install karke ise fix mat samajhiye. Yeh kuch fix nahi karta — yeh sirf block editor ko chhupa deta hai taaki aapko error dikhna band ho jaaye. Tooti hui JavaScript ya toota hua REST response abhi bhi wahin hai, aur woh aapko site editor mein, widgets mein, ya agli baar update karte samay phir se kaatega. Pehle diagnose karein; Classic par tabhi jaayein jab aapne soch-samajhkar blocks ka istemaal band karne ka faisla kiya ho.

PHP memory limit ko aadat se mat badhaayein. Yeh internet ka pasandida copy-paste fix hai, lekin khaali editor kabhi-kabhaar hi memory khatm hone ki wajah se hota hai. Asli memory exhaustion ek khaas fatal phenkta hai — “Allowed memory size of N bytes exhausted” — jo aapko debug.log mein dikhega. Agar woh line wahaan nahi hai, to zyada memory kuch nahi badalti.

WordPress core ko dobara install mat karein. Har install par core files byte-ke-byte ek jaisi hoti hain. Agar core hi samasya hoti, to duniya ki har WordPress site ka editor abhi toota hua hota. Galti lagbhag hamesha aapke plugins ya theme mein hoti hai, aur core ko reinstall karne se cheezein overwrite hone ka khatra hota hai jabki kuch fix nahi hota.

Apne cache plugin ko andhaadhundh clear ya disable mat karein pehle kadam ke roop mein. Aggressive JS minification aur concatenation editor ko tod sakti hai, isliye test karna theek hai — lekin cache ko bina soche flush karne se pehle console check karein. Andaaza lagaana hi woh tarika hai jisse paanch minute ka fix ek poori dopahar mein badal jaata hai.

Abhi bhi atke hue hain?

Agar console saaf hai, REST API valid JSON deta hai, aur poora plugin-aur-theme bisect karne ke baad bhi editor mara hua hai, to jawaab lagbhag hamesha debug.log mein baitha hota hai. WP_DEBUG_LOG enable karein, failure ko ek baar reproduce karein, aur nikle hue fatal ko error log decoder ke zariye chalayein. Stack trace file ka naam bata deta hai — wahin se shuru karein.