{"id":141,"date":"2023-02-14T00:00:00","date_gmt":"2023-02-13T23:00:00","guid":{"rendered":"https:\/\/helloblog.io\/lv\/labaka-wordpress-atkludosana-ar-acorn\/"},"modified":"2026-01-20T06:38:47","modified_gmt":"2026-01-20T05:38:47","slug":"labaka-wordpress-atkludosana-ar-acorn","status":"publish","type":"post","link":"https:\/\/helloblog.io\/lv\/labaka-wordpress-atkludosana-ar-acorn\/","title":{"rendered":"Lab\u0101ka WordPress atk\u013c\u016bdo\u0161ana ar Acorn: p\u0101rskat\u0101m\u0101kas k\u013c\u016bdas, maz\u0101k min\u0113\u0161anas"},"content":{"rendered":"\n

Ja WordPress projekts s\u0101k mest notice<\/code>, warning<\/code> vai fat\u0101las k\u013c\u016bdas, pirmais solis parasti ir iesl\u0113gt WP_DEBUG<\/code>. Probl\u0113ma \u2014 WordPress noklus\u0113juma k\u013c\u016bdu izdruka bie\u017ei vien ir gr\u016bti las\u0101ma: teksts \u201cpa virsu lapai\u201d, minim\u0101ls konteksts un stack trace, kas ne vienm\u0113r pal\u012bdz \u0101tri saprast, kur tie\u0161i viss sal\u016bza.<\/p>\n\n\n\n

Roots ekosist\u0113m\u0101 (Bedrock + Acorn) \u0161o pieredzi var b\u016btiski uzlabot. Acorn ir Roots komponents, kas ienes WordPress projekt\u0101 Laravel stila iesp\u0113jas (piem\u0113ram, helperus) un ar\u012b modern\u0101ku error handling (k\u013c\u016bdu apstr\u0101di). Rezult\u0101ts: tu redzi k\u013c\u016bdas lapu, kas vair\u0101k atg\u0101dina m\u016bsdien\u012bgu PHP framework nek\u0101 klasisku WordPress.<\/p>\n\n\n\n

K\u0101p\u0113c WP_DEBUG<\/code> ir j\u0101b\u016bt iesl\u0113gtam lok\u0101li<\/h2>\n\n\n\n

WP_DEBUG<\/code> ir WordPress ieb\u016bv\u0113ts \u201cdebug mode\u201d \u2014 to aktiviz\u0113 ar konstanti WP_DEBUG<\/code> konfigur\u0101cij\u0101. Lok\u0101laj\u0101 izstr\u0101d\u0113 tas ir praktiski oblig\u0101ts: \u0101tr\u0101k pamani nepareizus main\u012bgos, deprecations, k\u013c\u016bdainus hook izsaukumus un citas nianses, kas v\u0113l\u0101k staging\/production vid\u0113 var p\u0101rv\u0113rsties par re\u0101l\u0101m probl\u0113m\u0101m.<\/p>\n\n\n\n

Ja str\u0101d\u0101 ar Bedrock (m\u016bsdien\u012bgs WordPress boilerplate ar Composer), izstr\u0101des vid\u0113 WP_DEBUG<\/code> parasti jau ir iesl\u0113gts p\u0113c noklus\u0113juma, t\u0101p\u0113c bie\u017ei vien atliek tikai sak\u0101rtot to, k\u0101<\/em> k\u013c\u016bdas tiek r\u0101d\u012btas.<\/p>\n\n\n\n

WordPress noklus\u0113juma WP_DEBUG<\/code> izvade: darbojas, bet nav \u0113rta<\/h2>\n\n\n\n

Noklus\u0113juma scen\u0101rij\u0101 WordPress vienk\u0101r\u0161i izvada pazi\u0146ojumu vai k\u013c\u016bdu tie\u0161i lap\u0101. Tas ir lab\u0101k nek\u0101 klusums, ta\u010du, ja tev j\u0101atrisina sare\u017e\u0123\u012bt\u0101ks iz\u0146\u0113mums (exception) ar dzi\u013cu izsaukumu \u0137\u0113di (stack trace), \u0161\u012b izdruka \u0101tri k\u013c\u016bst par \u201catrodi adatu siena kaudz\u0113\u201d uzdevumu.<\/p>\n\n\n\n

\"WordPress
Noklus\u0113juma WP_DEBUG<\/code> zi\u0146ojumi WordPress lap\u0101 ir minim\u0101listiski un bie\u017ei vien gr\u016bti las\u0101mi. \u2014 Forr\u00e1s: Roots.io<\/em><\/figcaption><\/figure>\n\n\n\n

Ko dara Acorn: sakar\u012bga k\u013c\u016bdu lapa, kad WP_DEBUG<\/code> ir iesl\u0113gts<\/h2>\n\n\n\n

Acorn uzlabo WP_DEBUG<\/code> pieredzi gad\u012bjum\u0101, kad ir akt\u012bvi WP_DEBUG<\/code> un WP_DEBUG_DISPLAY<\/code>. B\u016btisk\u0101 doma: nevis izdruk\u0101t pliku tekstu, bet izmantot m\u016bsdien\u012bgu exception handler (iz\u0146\u0113mumu apstr\u0101d\u0101t\u0101ju), kas par\u0101da k\u013c\u016bdu struktur\u0113ti.<\/p>\n\n\n\n

Acorn noklus\u0113juma k\u013c\u016bdu apstr\u0101de ar Symfony exception handler<\/h3>\n\n\n\n

P\u0113c noklus\u0113juma Acorn izmanto Symfony exception handler. Praktiski tas noz\u012bm\u0113: p\u0101rskat\u0101m\u0101ka k\u013c\u016bdas lapa, lab\u0101ks stack trace att\u0113lojums un \u0101tr\u0101ka orient\u0113\u0161an\u0101s, kur\u0101 fail\u0101\/rind\u0101 probl\u0113ma radusies.<\/p>\n\n\n\n

\"Acorn
Acorn p\u0113c noklus\u0113juma izmanto Symfony exception handler, kas k\u013c\u016bdas par\u0101da struktur\u0113ti. \u2014 Forr\u00e1s: Roots.io<\/em><\/figcaption><\/figure>\n\n\n\n

Ignition WordPress projekt\u0101: Laravel l\u012bme\u0146a debug lapa<\/h3>\n\n\n\n

Ja tev ir Laravel pieredze, visticam\u0101k paz\u012bsti Ignition \u2014 t\u0101 ir Laravel noklus\u0113juma k\u013c\u016bdu lapa kop\u0161 Laravel v9. No Acorn v3 puses ir pieejams Laravel routing atbalsts, un l\u012bdz ar to WordPress projektos ar Acorn var izmantot ar\u012b Ignition. Tas parasti dod vispat\u012bkam\u0101ko k\u013c\u016bdu diagnostikas pieredzi: bag\u0101t\u012bg\u0101ks konteksts, skaidr\u0101ka navig\u0101cija, \u0113rt\u0101ks stack trace.<\/p>\n\n\n\n

\"Acorn
Ar Ignition WordPress k\u013c\u016bdu lapa izskat\u0101s un uzvedas \u013coti l\u012bdz\u012bgi Laravel pieredzei. \u2014 Forr\u00e1s: Roots.io<\/em><\/figcaption><\/figure>\n\n\n\n

Lai s\u0101ktu lietot Ignition, to var pievienot ar Composer k\u0101 izstr\u0101des atkar\u012bbu (no t\u0101s pa\u0161as mapes, kur instal\u0113ts Acorn):<\/p>\n\n\n\n

<\/circle><\/circle><\/circle><\/g><\/svg><\/span>