{"id":213,"date":"2026-01-20T00:00:00","date_gmt":"2026-01-19T23:00:00","guid":{"rendered":"https:\/\/helloblog.io\/ro\/woocommerce-10-5-schimbari-pentru-dezvoltatori\/"},"modified":"2026-01-20T00:00:00","modified_gmt":"2026-01-19T23:00:00","slug":"woocommerce-10-5-schimbari-pentru-dezvoltatori","status":"publish","type":"post","link":"https:\/\/helloblog.io\/ro\/woocommerce-10-5-schimbari-pentru-dezvoltatori\/","title":{"rendered":"WooCommerce 10.5: schimb\u0103rile care conteaz\u0103 pentru dezvoltatori (import Analytics, taxe, UI Checkout, API \u0219i performan\u021b\u0103)"},"content":{"rendered":"\n<p>WooCommerce 10.5 intr\u0103 \u00een linie dreapt\u0103, iar pentru noi, cei care dezvolt\u0103m extensii sau oper\u0103m magazine cu volum mare de comenzi, versiunea asta nu e una \u201ede rutin\u0103\u201d. Sunt c\u00e2teva modific\u0103ri care ating direct performan\u021ba (\u00een special pe partea de Analytics), compatibilitatea (date de taxe legacy\/corupte), dar \u0219i comportamentul UI (Checkout block, pagini de produs variabil) \u0219i zona de API.<\/p>\n\n\n\n<p>Mai jos ai o trecere \u00een revist\u0103, cu accent pe ce impact poate avea \u00een proiecte \u0219i ce merit\u0103 testat \u00een beta \u00eenainte de release.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Calendar de release (\u0219i cum testezi beta-urile)<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Feature Freeze: 12 ianuarie 2026<\/li>\n\n\n<li>WooCommerce 10.5 Beta 1: 19 ianuarie 2026<\/li>\n\n\n<li>WooCommerce 10.5 Beta 2: 26 ianuarie 2026<\/li>\n\n\n<li>Release final WooCommerce 10.5: programat pentru 4 februarie 2026<\/li>\n\n<\/ul>\n\n\n\n<p>Pentru testare, echipa WooCommerce recomand\u0103 pluginul oficial <a href=\"https:\/\/woocommerce.com\/products\/woocommerce-beta-tester\/\">WooCommerce Beta Tester<\/a>, care \u00ee\u021bi permite s\u0103 instalezi \u0219i s\u0103 rulezi u\u0219or versiunile beta \u00eentr-un mediu de staging.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Ce aduce WooCommerce 10.5 (pe scurt, dar tehnic)<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1) Schimbare fundamental\u0103: importul datelor de comenzi \u00een tabelele de Analytics<\/h3>\n\n\n\n<p>Cea mai important\u0103 schimbare din 10.5 este felul \u00een care WooCommerce import\u0103 (sau regenereaz\u0103) datele de comenzi \u00een tabelele folosite de Analytics. P\u00e2n\u0103 acum, la fiecare eveniment relevant de comand\u0103, WooCommerce pornea un job de import prin ActionScheduler. De\u0219i era asincron, pe magazine ocupate genera backlog-uri uria\u0219e (10.000+ ac\u021biuni), cu efecte concrete: degradare sever\u0103 de performan\u021b\u0103, contenden\u021b\u0103 pe baza de date \u0219i \u00eencetiniri vizibile ale site-ului.<\/p>\n\n\n\n<p>\u00cen 10.5, comportamentul implicit se schimb\u0103: WooCommerce trece la <strong>Scheduled Imports<\/strong> (import programat), adic\u0103 o regenerare \u00een batch-uri, la intervale regulate.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Frecven\u021b\u0103 implicit\u0103: la fiecare <strong>12 ore<\/strong><\/li>\n\n\n<li>Dimensiune batch implicit\u0103: <strong>100 comenzi per batch<\/strong><\/li>\n\n\n<li>Configurabil prin filtre noi: <code>woocommerce_analytics_import_interval<\/code> \u0219i <code>woocommerce_analytics_regenerate_batch_size<\/code><\/li>\n\n\n<li>Beneficii: mult mai pu\u021bine ac\u021biuni programate, \u00eenc\u0103rcare mai mic\u0103 pe DB, plus vizibilitate mai clar\u0103 a statusului importului \u0219i posibilitatea de a declan\u0219a manual importuri oric\u00e2nd<\/li>\n\n<\/ul>\n\n\n\n<p>Detalii tehnice \u00een PR: <a href=\"https:\/\/github.com\/woocommerce\/woocommerce\/pull\/61603\">#61603<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2) Checkout block: op\u021biuni de livrare mai clare \u00een scenarii cu multiple pachete (mai ales subscriptions)<\/h3>\n\n\n\n<p>\u00cen Checkout block, UI-ul pentru op\u021biunile de livrare este \u00eembun\u0103t\u0103\u021bit: c\u00e2nd exist\u0103 multiple pachete (un scenariu \u00eent\u00e2lnit mai des la produse de tip subscription), op\u021biunile vor afi\u0219a <strong>thumbnail-uri de produs<\/strong> \u0219i <strong>containere cu bordur\u0103<\/strong>, ca s\u0103 fie mai u\u0219or de \u00een\u021beles ce se livreaz\u0103 \u0219i cum.<\/p>\n\n\n\n<p>\u00cen acela\u0219i pachet de schimb\u0103ri se rezolv\u0103 \u0219i un bug: metodele de livrare nu se sincronizau corect c\u00e2nd utilizatorul comuta \u00eentre op\u021biunile de tip <strong>Ship<\/strong> \u0219i <strong>Pickup<\/strong>.<\/p>\n\n\n\n<p>Referin\u021b\u0103: <a href=\"https:\/\/github.com\/woocommerce\/woocommerce\/pull\/61625\">#61625<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3) Comenzi cu taxe legacy\/corupte: handling mai robust (float\/string vs array)<\/h3>\n\n\n\n<p>O alt\u0103 zon\u0103 care a creat probleme \u00een practic\u0103: comenzi vechi (sau alterate) unde valorile de tax\u0103 au fost salvate gre\u0219it, de exemplu ca float-uri sau string-uri, \u00een loc de structuri de tip array. \u00cen 10.5 apare un fix care adaug\u0103 handling <strong>backwards-compatible<\/strong> pentru toate tipurile de order item (produse, shipping, fees).<\/p>\n\n\n\n<p>\u00cen plus, logica \u00eencearc\u0103 s\u0103 infereze inteligent tax rate IDs din contextul comenzii, iar pentru cazurile speciale exist\u0103 \u0219i un filtru dedicat pentru conversie custom.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Acoperire: order item types pentru products, shipping \u0219i fees<\/li>\n\n\n<li>Inferen\u021b\u0103 tax rate IDs pe baza contextului comenzii<\/li>\n\n\n<li>Filtru nou: <code>woocommerce_order_item_legacy_tax_conversion<\/code> (pentru logic\u0103 de conversie personalizat\u0103)<\/li>\n\n<\/ul>\n\n\n\n<p>Referin\u021b\u0103: <a href=\"https:\/\/github.com\/woocommerce\/woocommerce\/pull\/62271\">#62271<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">4) Select2 CSS: stilurile WooCommerce sunt \u201escoped\u201d ca s\u0103 nu afecteze interfe\u021bele altor pluginuri<\/h3>\n\n\n\n<p>WooCommerce \u00eencarc\u0103 stiluri pentru Select2 (biblioteca de UI pentru select-uri avansate), iar uneori CSS-ul \u201ecurgea\u201d \u0219i \u00een alte zone din admin, afect\u00e2nd interfe\u021be din alte pluginuri. \u00cen 10.5, stilurile sunt acum sc\u0103pate \u00een mod controlat folosind <code>:where(.woocommerce)<\/code>.<\/p>\n\n\n\n<p>Un detaliu important: pseudo-clasa <code>:where()<\/code> are specificitate zero, ceea ce \u00eenseamn\u0103 c\u0103 override-urile custom existente ar trebui s\u0103 continue s\u0103 func\u021bioneze, dar f\u0103r\u0103 efectele secundare \u00een afara contextului WooCommerce.<\/p>\n\n\n\n<p>Referin\u021b\u0103: <a href=\"https:\/\/github.com\/woocommerce\/woocommerce\/pull\/61956\">#61956<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">5) Filtru nou pentru taxe la shipping: <code>woocommerce_shipping_tax_class<\/code><\/h3>\n\n\n\n<p>WooCommerce introduce un filtru nou, <code>woocommerce_shipping_tax_class<\/code>, care permite calculul dinamic al taxelor pentru shipping \u00een func\u021bie de con\u021binutul co\u0219ului, datele clientului \u0219i loca\u021bie. Practic, \u00ee\u021bi d\u0103 un punct clar de extensie pentru scenarii fiscale mai complicate.<\/p>\n\n\n\n<p>Un exemplu de logic\u0103 posibil\u0103 men\u021bionat\u0103 explicit: calcularea taxei de shipping folosind <strong>rata predominant\u0103 de tax\u0103 din co\u0219<\/strong>, ceea ce poate fi necesar \u00een anumite jurisdic\u021bii (de exemplu, \u00een Olanda) unde regulile pot cere astfel de abord\u0103ri.<\/p>\n\n\n\n<p>Referin\u021b\u0103: <a href=\"https:\/\/github.com\/woocommerce\/woocommerce\/pull\/62040\">#59512<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">API Changes &#038; advisories (lucruri de verificat \u00een extensii)<\/h2>\n\n\n\n<p>Pe l\u00e2ng\u0103 func\u021bionalit\u0103\u021bi, 10.5 vine \u0219i cu schimb\u0103ri de API\/comportament documentate separat \u00een developer advisories. Dac\u0103 ai integr\u0103ri pe REST API sau folose\u0219ti intern clase\/trait-uri \u201einterne\u201d, merit\u0103 s\u0103 le parcurgi.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>WC REST API: handling corect pentru <strong>decodarea caracterelor speciale<\/strong> \u00een atributele varia\u021biilor de produs. Detalii: https:\/\/developer.woocommerce.com\/2026\/01\/14\/wc-rest-api-fixes-for-product-variation-attributes-with-special-characters-in-woocommerce-10-5\/<\/li>\n\n\n<li>Se elimin\u0103 trait-ul <strong>AccessiblePrivateMethods<\/strong>. Era \u00een namespace-ul <code>Internal<\/code> (semnal clar c\u0103 nu e destinat consumului public), dar poate afecta extensii care l-au folosit gre\u0219it. Detalii: https:\/\/developer.woocommerce.com\/2026\/01\/15\/removal-of-the-accessibleprivatemethods-trait-in-woocommerce-10-5\/<\/li>\n\n\n<li>Schimb\u0103ri la <strong>product permalinks bazate pe categorii<\/strong>: se prioritizeaz\u0103 categoria cea mai \u201ead\u00e2nc\u0103\u201d (deepest category) pentru SEO \u0219i consisten\u021b\u0103 \u00een URL-uri; afecteaz\u0103 doar anumite structuri de permalink. Detalii: https:\/\/developer.woocommerce.com\/2026\/01\/13\/product-permalink-changes-coming-in-woocommerce-10-5\/<\/li>\n\n\n<li>Pe paginile de produse variabile, butonul <strong>Add to Cart<\/strong> este acum <strong>dezactivat p\u00e2n\u0103 c\u00e2nd scriptul de varia\u021bii s-a \u00eenc\u0103rcat complet<\/strong>. Motiv: pe conexiuni lente, utilizatorii puteau click-ui \u00eenainte de ini\u021bializarea logicii de selec\u021bie, duc\u00e2nd la submit e\u0219uat. Detalii: https:\/\/developer.woocommerce.com\/2026\/01\/16\/add-to-cart-button-disabled-by-default-in-variable-products-in-woocommerce-10-5\/<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">\u00cembun\u0103t\u0103\u021biri de performan\u021b\u0103 \u00een WooCommerce 10.5<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">REST API cache (experimental) pentru orice endpoint<\/h3>\n\n\n\n<p>10.5 introduce un <strong>REST API cache experimental<\/strong> care poate fi aplicat oric\u0103rui endpoint din WC REST API. \u00cen anun\u021b, echipa precizeaz\u0103 c\u0103 vor veni detalii suplimentare despre cum se testeaz\u0103 aceast\u0103 func\u021bionalitate \u00eenainte de release. Ideea e clar\u0103: reducerea timpilor de r\u0103spuns \u0219i a \u00eenc\u0103rc\u0103rii, mai ales c\u00e2nd API-ul este lovit frecvent de integr\u0103ri, dashboard-uri sau aplica\u021bii headless.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">\u00cembun\u0103t\u0103\u021biri pentru cached variation prices + utilitar pentru callbacks<\/h3>\n\n\n\n<p>Sistemul de caching pentru pre\u021burile varia\u021biilor prime\u0219te optimiz\u0103ri suplimentare, \u00eempreun\u0103 cu introducerea unei clase utilitare pentru lucrul cu callbacks (utile c\u00e2nd ai mult\u0103 logic\u0103 \u00eenregistrat\u0103 dinamic). Detalii: https:\/\/developer.woocommerce.com\/2026\/01\/08\/variation-prices-caching-improvements-in-woocommerce-10-5\/<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Product Object Caching (experimental): cache pe instan\u021be de produs \u00een cadrul aceluia\u0219i request<\/h3>\n\n\n\n<p>Apare \u0219i o func\u021bionalitate experimental\u0103 numit\u0103 <strong>Product Object Caching<\/strong>: \u00een loc s\u0103 \u00eencarce acela\u0219i produs din DB de mai multe ori \u00eentr-un singur request, WooCommerce poate p\u0103stra \u00een cache instan\u021bele de produs pe durata request-ului, evit\u00e2nd load-uri duplicate.<\/p>\n\n\n\n<p>Referin\u021be: PR https:\/\/github.com\/woocommerce\/woocommerce\/pull\/62041 \u0219i articol cu context: https:\/\/developer.woocommerce.com\/2026\/01\/19\/experimental-product-object-caching-in-woocommerce-10-5\/<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Fix pentru Product Filters: cache data setat\/\u00eenc\u0103rcat corect + cleanup transients<\/h3>\n\n\n\n<p>Dac\u0103 ai magazine cu cataloage mari \u0219i folose\u0219ti Product Filters block, exist\u0103 o optimizare punctual\u0103: \u00een 10.5 se repar\u0103 un caz \u00een care cache data pentru filtre nu era setat \u0219i \u00eenc\u0103rcat corect. Problema putea duce la \u201einundarea\u201d bazei de date cu date de cache pentru filtre \u0219i, implicit, la degradarea performan\u021bei.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Cache-ul pentru Product Filters este setat \u0219i \u00eenc\u0103rcat corect, reduc\u00e2nd presiunea pe DB<\/li>\n\n\n<li>Tool-ul de cleanup pentru WooCommerce transients a fost actualizat ca s\u0103 \u0219tearg\u0103 \u0219i cache-ul de filter data c\u00e2nd ruleaz\u0103<\/li>\n\n\n<li>Dac\u0103 exist\u0103 \u00een continuare probleme de performan\u021b\u0103 cu Product Filters block, cauza poate fi cache-ul r\u0103mas, iar solu\u021bia indicat\u0103 este rularea cur\u0103\u021b\u0103rii de WooCommerce transients<\/li>\n\n<\/ul>\n\n\n\n<p>Referin\u021b\u0103: <a href=\"https:\/\/github.com\/woocommerce\/woocommerce\/pull\/62575\">#62575<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Changelog complet (pentru diff-uri fine)<\/h2>\n\n\n\n<p>Pentru lista complet\u0103 de modific\u0103ri, vezi changelog-ul din readme: https:\/\/github.com\/woocommerce\/woocommerce\/blob\/10.5.0-beta.1\/plugins\/woocommerce\/readme.txt<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Ce merit\u0103 testat concret \u00eenainte de 10.5 (checklist pentru staging)<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Magazine cu volum mare de comenzi: verific\u0103 impactul noului <strong>Scheduled Imports<\/strong> asupra ActionScheduler (num\u0103r de ac\u021biuni, timpi, load DB) \u0219i confirm\u0103 c\u0103 Analytics se actualizeaz\u0103 conform a\u0219tept\u0103rilor<\/li>\n\n\n<li>Checkout block cu subscriptions \/ multiple packages: verific\u0103 UI-ul (thumbnails + containere) \u0219i sincronizarea corect\u0103 c\u00e2nd comu\u021bi Ship \u2194 Pickup<\/li>\n\n\n<li>Comenzi istorice\/importate: caut\u0103 edge-case-uri cu taxe salvate ca float\/string \u0219i testeaz\u0103 dac\u0103 ai integr\u0103ri care depind de structura veche; dac\u0103 e nevoie, folose\u0219te <code>woocommerce_order_item_legacy_tax_conversion<\/code><\/li>\n\n\n<li>\u00cen admin, \u00een ecrane unde folose\u0219ti Select2 din alte pluginuri: verific\u0103 dac\u0103 scoping-ul <code>:where(.woocommerce)<\/code> elimin\u0103 conflictele f\u0103r\u0103 s\u0103-\u021bi strice override-urile<\/li>\n\n\n<li>Logici fiscale custom: evalueaz\u0103 dac\u0103 <code>woocommerce_shipping_tax_class<\/code> \u00ee\u021bi simplific\u0103 implementarea (de exemplu, tax\u0103 de shipping calculat\u0103 pe rata predominant\u0103 din co\u0219)<\/li>\n\n\n<li>REST API consumers: verific\u0103 endpoint-urile pentru produse variabile\/atribute cu caractere speciale; confirm\u0103 c\u0103 decodarea e corect\u0103<\/li>\n\n\n<li>Front-end pe produse variabile: confirm\u0103 comportamentul nou al butonului Add to Cart (dezactivat p\u00e2n\u0103 se \u00eencarc\u0103 scriptul) \u0219i c\u0103 nu ai JS custom care presupune alt flow<\/li>\n\n\n<li>Performan\u021b\u0103: dac\u0103 folose\u0219ti Product Filters block, ruleaz\u0103 cleanup la transients \u0219i monitorizeaz\u0103 DB; urm\u0103re\u0219te \u0219i func\u021biile experimentale de caching (REST API cache, Product Object Caching) \u00een func\u021bie de compatibilitatea proiectului<\/li>\n\n<\/ul>\n\n\n<div class=\"references-section\">\n                <h2>Referin\u021be \/ Surse<\/h2>\n                <ul class=\"references-list\"><li><a href=\"https:\/\/developer.woocommerce.com\/2026\/01\/20\/woocommerce-10-5-whats-coming-for-developers\/\" target=\"_blank\" rel=\"noopener noreferrer\">WooCommerce 10.5: What\u2019s coming for developers Release Posts<\/a><\/li><li><a href=\"https:\/\/developer.woocommerce.com\/2026\/01\/14\/wc-rest-api-fixes-for-product-variation-attributes-with-special-characters-in-woocommerce-10-5\/\" target=\"_blank\" rel=\"noopener noreferrer\">WC REST API fixes for product variation attributes with special characters in WooCommerce 10.5<\/a><\/li><li><a href=\"https:\/\/developer.woocommerce.com\/2026\/01\/15\/removal-of-the-accessibleprivatemethods-trait-in-woocommerce-10-5\/\" target=\"_blank\" rel=\"noopener noreferrer\">Removal of the AccessiblePrivateMethods trait in WooCommerce 10.5<\/a><\/li><li><a href=\"https:\/\/developer.woocommerce.com\/2026\/01\/13\/product-permalink-changes-coming-in-woocommerce-10-5\/\" target=\"_blank\" rel=\"noopener noreferrer\">Product permalink changes coming in WooCommerce 10.5<\/a><\/li><li><a href=\"https:\/\/developer.woocommerce.com\/2026\/01\/16\/add-to-cart-button-disabled-by-default-in-variable-products-in-woocommerce-10-5\/\" target=\"_blank\" rel=\"noopener noreferrer\">Add to cart button disabled by default in variable products in WooCommerce 10.5<\/a><\/li><li><a href=\"https:\/\/developer.woocommerce.com\/2026\/01\/08\/variation-prices-caching-improvements-in-woocommerce-10-5\/\" target=\"_blank\" rel=\"noopener noreferrer\">Variation prices caching improvements in WooCommerce 10.5<\/a><\/li><li><a href=\"https:\/\/developer.woocommerce.com\/2026\/01\/19\/experimental-product-object-caching-in-woocommerce-10-5\/\" target=\"_blank\" rel=\"noopener noreferrer\">Experimental product object caching in WooCommerce 10.5<\/a><\/li><li><a href=\"https:\/\/github.com\/woocommerce\/woocommerce\/pull\/61603\" target=\"_blank\" rel=\"noopener noreferrer\">woocommerce\/woocommerce pull request #61603<\/a><\/li><li><a href=\"https:\/\/github.com\/woocommerce\/woocommerce\/pull\/61625\" target=\"_blank\" rel=\"noopener noreferrer\">woocommerce\/woocommerce pull request #61625<\/a><\/li><li><a href=\"https:\/\/github.com\/woocommerce\/woocommerce\/pull\/62271\" target=\"_blank\" rel=\"noopener noreferrer\">woocommerce\/woocommerce pull request #62271<\/a><\/li><li><a href=\"https:\/\/github.com\/woocommerce\/woocommerce\/pull\/61956\" target=\"_blank\" rel=\"noopener noreferrer\">woocommerce\/woocommerce pull request #61956<\/a><\/li><li><a href=\"https:\/\/github.com\/woocommerce\/woocommerce\/pull\/62040\" target=\"_blank\" rel=\"noopener noreferrer\">woocommerce\/woocommerce pull request #62040<\/a><\/li><li><a href=\"https:\/\/github.com\/woocommerce\/woocommerce\/pull\/62041\" target=\"_blank\" rel=\"noopener noreferrer\">woocommerce\/woocommerce pull request #62041<\/a><\/li><li><a href=\"https:\/\/github.com\/woocommerce\/woocommerce\/pull\/62575\" target=\"_blank\" rel=\"noopener noreferrer\">woocommerce\/woocommerce pull request #62575<\/a><\/li><li><a href=\"https:\/\/github.com\/woocommerce\/woocommerce\/blob\/10.5.0-beta.1\/plugins\/woocommerce\/readme.txt\" target=\"_blank\" rel=\"noopener noreferrer\">plugins\/woocommerce\/readme.txt (10.5.0-beta.1 changelog)<\/a><\/li><\/ul>\n            <\/div>","protected":false},"excerpt":{"rendered":"<p>WooCommerce 10.5 vine cu un upgrade major pentru importul datelor \u00een tabelele de Analytics, plus ajust\u0103ri importante \u00een REST API, Checkout block \u0219i caching. Dac\u0103 ai extensii sau magazine cu trafic mare, merit\u0103 s\u0103 \u0219tii ce se schimb\u0103 \u00eenainte de release.<\/p>\n","protected":false},"author":30,"featured_media":212,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[18],"tags":[111,29,110,42,10],"class_list":["post-213","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ecosistem-wordpress","tag-dezvoltare-pluginuri","tag-performanta","tag-rest-api","tag-woocommerce","tag-wordpress"],"_links":{"self":[{"href":"https:\/\/helloblog.io\/ro\/wp-json\/wp\/v2\/posts\/213","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/helloblog.io\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/helloblog.io\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/helloblog.io\/ro\/wp-json\/wp\/v2\/users\/30"}],"replies":[{"embeddable":true,"href":"https:\/\/helloblog.io\/ro\/wp-json\/wp\/v2\/comments?post=213"}],"version-history":[{"count":0,"href":"https:\/\/helloblog.io\/ro\/wp-json\/wp\/v2\/posts\/213\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/helloblog.io\/ro\/wp-json\/wp\/v2\/media\/212"}],"wp:attachment":[{"href":"https:\/\/helloblog.io\/ro\/wp-json\/wp\/v2\/media?parent=213"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/helloblog.io\/ro\/wp-json\/wp\/v2\/categories?post=213"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/helloblog.io\/ro\/wp-json\/wp\/v2\/tags?post=213"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}