Xallinta ciladaha Zinnector®

Khaladaadka ay dadku dhab ahaan kala kulmaan Zinnector® CLI, waxa mid kastaa la micno yahay, iyo xalka. Qodob kasta waxa uu magacaabayaa qoraalka saxda ah ee aad arki doonto, si aad boggan uga dhex raadiso. Haddii kaagu aanu halkan ku jirin, ku socodsii amarka fashilmaya ZINNECTOR_DEBUG=1 oo arrin ka fur github.com/Zinn-Digital/zinnector/issues adiga oo raacinaya natiijada soo baxday, noocaaga node --version iyo nidaamkaaga hawlgalka.

"spawn EINVAL" isla markii la aqbalo rakibaadda runtime-ka (Windows)

Khalad ku jira Zinnector® 0.1.0 iyo 0.1.1. Dhanka Windows rakibaha runtime-ku waxa uu magac ahaan ku socodsiin jiray npm.cmd, Node-na waxa uu diiday in uu socodsiiyo fayl .cmd ah bilaa shell tan iyo xallintii CVE-2024-27980 — sidaa darteed rakibaaddu waxay burburtay hal ilbiriqsi ka dib markii aad kaga jawaabtay Y. Lagu xalliyay 0.1.2: npm hadda waxa loo socodsiiyaa sidii node npm-cli.js, kaas oo isku mid ka ah barxad kasta oo aan u baahnayn shell. Socodsii npm install -g zinnector@latest, ka dibna zinnector dev mar kale.

"npm WARN EBADENGINE" inta lagu jiro rakibaadda, ama "Zinnector® needs Node 24 or newer"

Node-kaagu waxa uu ka weyn yahay 24. npm waxa uu daabacayaa digniinta sababtoo ah xidhmadu waxay caddaynaysaa engines: >=24.18.1; rakibaaddu si kastaba ha ahaatee way dhammaystirmaysaa, laakiin zinnector ayaa markaas diidaya in uu bilaabmo (exit code 78) intii uu meel dambe oo wareer leh ku fashilmi lahaa. Ka rakibo LTS-ka hadda jira nodejs.org — winget install OpenJS.NodeJS.LTS marka ay tahay Windows, brew install node@24 marka ay tahay macOS — xaqiiji in node --version ay daabacayso v24 ama ka sarreeya, oo mar kale rakibo Zinnector®.

"gyp ERR!", "Building from source with node-gyp", ama "You need to install Visual Studio"

Runtime-ka WordPress waxa uu leeyahay module native ah kaas oo binary-yadiisa hore loo dhisay ay u jiraan Node 24 iyo 25 keliya. Node ka cusub dushiisa (26 iyo wixii ka sarreeya, laga bilaabo Sebtembar 2026) rakibihiisu waxa uu dib ugu noqonayaa samaynta laga soo bilaabo source-ka, taas oo kombuyuutarka caadiga ah ee Windows ku dambaysa codsi loogu jiro Visual Studio. Lagu xalliyay 0.1.2: Zinnector® waxa uu tan ogaadaa ka hor inta aanu waxba soo dejin waxana uu soo qaadaa Node 24 oo runtime-ka oo keliya loogu talagalay — qiyaastii 30 MB, oo lagu xaqiijiyay checksum-yada nodejs.org — sidaa darteed waxba waligood lama habeeyo (compile). Haddii aad weli aragto ka dib cusboonaysiinta, socodsii zinnector dev --reset-runtime si rakibaaddii hore ee qabyada ahayd marka hore loo tuuro.

Digniinaha "EPERM" ee ka yimaada npm inta uu nadiifinta wado (Windows)

Ku dhowaad had iyo jeer waa scan-gareeyaha fayraska ama search indexer fayl furan ku haysta hoosta runtime-ka node_modules inta npm uu isku dayayo in uu ka saaro. Rakibaadda waxa lagaga soo ceshadaa gal nadiif ah markasta oo la isticmaalo zinnector dev; haddii ay sii socoto, zinnector dev --reset-runtime ayaa marka hore galka runtime-ka oo dhan meesha ka saaraysa oo mar kale rakibaysa.

"the local playground runtime could not be installed"

Fariintu waxay caddaynaysaa khadadka u dambeeya ee npm laftiisa iyo amarka saxda ah ee Zinnector® uu socodsiiyay, si aad adigu laftaadu u socodsiiso oo aad u aragto waxa oo dhan ee soo baxay. Sababaha caadiga ahi waa dhibaato dhanka xidhiidhka ah ama proxy-ga — runtime-ka waxa lagu soo qaadaa npm-kaaga gaarka ah, markaa npm config set proxy … iyo muraayadda diiwaanka (registry mirror) way khuseeyaan — ama rakibaad hore oo qabyo ahayd, taas oo --reset-runtime ay nadiifinayso.

"the local playground exited before it was ready", ama waligii ma noqonayo mid diyaar ah

Socodsii zinnector dev --verbose si aad u aragto waxa kasoo baxaya runtime-ka laftiisa. Port mar hore la isticmaalay ayaa ah midka caadiga ah: zinnector dev --port 9401, ama ku dhex deji port gudaha zinnector.json. Runtime rakibmay laakiin aan kici doonin: zinnector dev --reset-runtime. Kicitaanka koowaad waxa kale oo uu soo dejiyaa WordPress laftiisa, markaa xidhiidhka daciifka ah sii dhowr daqiiqo; CLI-gu waxa uu sugayaa ilaa shan daqiiqo ka hor inta aanu soo sheegin in wakhtigii dhammaaday (timeout) intii uu iska xayirnaan lahaa.

"this project is not a git repository" marka la samaynayo push

Kicinta hawlgelinta (deploys) waxa laga maamulaa kayd (repository), markaa zinnector push waxay u baahan tahay mid leh meel fog (remote) oo barxaddu gaadhi karto. git init && git add -A && git commit -m initial, ku dar remote-kaaga GitHub ama GitLab, ka dibna zinnector link si aad ugu xidho goobta.

Goobtu way caddahay ka dib markii deploy la sameeyay

Socodsii zinnector check. Sagaal jeer tobankii jeerba waa farqi u dhexeeya nooca PHP — waxaad ku dhistay PHP ka cusub kan uu slot-ku socodsiiyo — warbixintuna waxay sheegaysaa nooca loo beddelayo slot-ka iyada oo la isticmaalayo zinnector php <version>, ama midka lagu horumarinayo iyada oo la adeegsanayo zinnector dev --php <version>. zinnector logs --error waxay muujinaysaa khaladka dilaaga ah (fatal) laftiisa.

La xidhiidha

• Bilaabashada · Horumarinta maxalliga ah · Hawlgelinta · Tixraaca amarka