{"id":506,"date":"2018-08-21T21:05:42","date_gmt":"2018-08-21T19:05:42","guid":{"rendered":"https:\/\/blog.nav.ro\/?p=506"},"modified":"2021-11-22T12:20:54","modified_gmt":"2021-11-22T10:20:54","slug":"remedierea-erorii-500-internal-server-error-in-wordpress","status":"publish","type":"post","link":"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/","title":{"rendered":"Remedierea erorii 500 Internal Server Error \u00een WordPress"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" class=\" wp-image-2243 aligncenter\" src=\"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2018\/08\/500server-300x141.png\" alt=\"\" width=\"513\" height=\"241\" srcset=\"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2018\/08\/500server-300x141.png 300w, https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2018\/08\/500server.png 523w\" sizes=\"auto, (max-width: 513px) 85vw, 513px\" \/><\/p>\n<p>Va aminti\u021bi de momentul \u00een care a\u021bi \u00eencercat s\u0103 v\u0103 conecta\u021bi la WordPress, acest proces dur\u00e2nd foarte mult? \u0218i, c\u00e2nd \u00een sf\u00e2r\u0219it a\u021bi crezut c\u0103 s-a \u00eenc\u0103rcat, a ap\u0103rut o maimu\u021bic\u0103 cu un ciocan \u0219i o \u0219urubelni\u021b\u0103 care \u00eencearc\u0103 s\u0103 repare ceva? A\u021bi ghicit bine! Vorbim despre eroarea 500 Internal Server Error.<\/p>\n<p>\u00cen acest articol, v\u0103 voi ar\u0103ta care sunt cauzele acestei erori \u0219i cum s\u0103 o remedia\u021bi \u00een cazul site-ului dvs. WordPress!<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\" wp-image-2247 aligncenter\" src=\"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2018\/08\/500-internal-server-error-300x225.png\" alt=\"\" width=\"547\" height=\"410\" srcset=\"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2018\/08\/500-internal-server-error-300x225.png 300w, https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2018\/08\/500-internal-server-error-1024x768.png 1024w, https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2018\/08\/500-internal-server-error-768x576.png 768w, https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2018\/08\/500-internal-server-error-1536x1152.png 1536w, https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2018\/08\/500-internal-server-error-1200x900.png 1200w, https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2018\/08\/500-internal-server-error.png 1956w\" sizes=\"auto, (max-width: 547px) 85vw, 547px\" \/><\/p>\n<p>Dup\u0103 cum pute\u021bi vedea, numele \u00een sine arat\u0103 c\u0103 a ap\u0103rut o eroare la nivelul serverului, din cauza c\u0103reia pagina solicitat\u0103 nu poate fi \u00eenc\u0103rcat\u0103. Exist\u0103 mai multe motive pentru aceasta. Cu toate acestea, nu exist\u0103, \u00een special, nimic care ar fi putut s\u0103 o determine.<\/p>\n<p>Cele 3 cauze probabile care provoac\u0103 de obicei aceast\u0103 eroare \u00een WordPress sunt:<\/p>\n<p>1. Corup\u021bia sau o eroare sintactic\u0103 \u00een fi\u0219ierul .htaccess<br \/>\n2. Atingerea limitei de memorie PHP<br \/>\n3. O eroare sau o defec\u021biune \u00een codul unui plugin instalat<\/p>\n<p>Pentru a sc\u0103pa de aceast\u0103 eroare a site-ului dvs. WordPress, trebuie s\u0103 remedia\u021bi problemele de mai sus. S\u0103 vedem cum pute\u021bi s\u0103 le rezolva\u021bi.<\/p>\n<p><strong>1. Verifica\u021bi fi\u0219ierul .htaccess<\/strong><\/p>\n<p>Pentru a accesa fi\u0219ierul .htaccess, trebuie s\u0103 v\u0103 conecta\u021bi la panoul de g\u0103zduire a site-ului dvs. adic\u0103 cPanel sau s\u0103 \u00eel accesa\u021bi prin FTP. Fi\u0219ierul .htaccess poate fi accesat urm\u00e2nd ace\u0219ti pa\u0219i:<\/p>\n<p>1. Conecta\u021bi-v\u0103 la panoul de control<br \/>\n2. Accesa\u021bi domeniul site-ului WordPress<br \/>\n3. Accesa\u021bi cPanel<br \/>\n4. \u00cen cPanel, c\u0103uta\u021bi File manager \u2192 public_html \u2192 fi\u0219ier .htaccess<\/p>\n<p>Odat\u0103 ce a\u021bi g\u0103sit fi\u0219ierul .htaccess, trebuie s\u0103 verific\u0103\u021bi dac\u0103 acesta este corupt. \u00cenainte de a \u00eencepe verificarea, redenumi\u021bi fi\u0219ierul \u0219i desc\u0103rca\u021bi-l. De asemenea, crea\u021bi o copie de rezerv\u0103 a acestui fi\u0219ier.<\/p>\n<p>Acum, dup\u0103 ce a\u021bi desc\u0103rcat fi\u0219ierul .htaccess, deschide\u021bi-l cu orice editor HTML (Notepad, Notepad ++, Sublime etc.) \u0219i \u00eenlocui\u021bi textul cu codul disponibil pe site-ul oficial WordPress. \u00cen func\u021bie de versiunea WordPress instalat\u0103, codul se modific\u0103 astfel, asigura\u021bi-v\u0103 c\u0103 ve\u021bi copia codul corect.<\/p>\n<p>Salva\u021bi fi\u0219ierul .htaccess \u0219i \u00eenc\u0103rca\u021bi-l pe server. Re\u00eenc\u0103rca\u021bi site-ul dvs. WordPress \u0219i verifica\u021bi dac\u0103 eroarea este corectat\u0103.<\/p>\n<p>Dac\u0103 eroarea este corectat\u0103, felicit\u0103ri dac\u0103 nu, merge\u021bi mai departe pentru a vedea solu\u021bia pentru urm\u0103toarea cauz\u0103 probabil\u0103 a erorii. Dar, \u00eenainte de asta, merge\u021bi la WordPress Admin Panel \u2192 face\u021bi clic pe Settings \u2192 Permalinks \u0219i face\u021bi clic pe Save, pentru a v\u0103 asigura c\u0103 un nou fi\u0219ier .htaccess este generat automat \u0219i c\u0103 eroarea 404 nu apare.<\/p>\n<p><strong>2. Cre\u0219te\u021bi limita de memorie PHP<\/strong><\/p>\n<p>Mai departe vom discuta despre urm\u0103toarea cauz\u0103 posibil\u0103 a erorii 500 Internal Server Error &#8211; atingerea limitei de memorie PHP. Limita de memorie PHP este de obicei configurat\u0103 de furnizorul dvs. de g\u0103zduire \u0219i de WordPress. S\u0103 spunem c\u0103 limita este setat\u0103 la &#8222;X&#8221; \u0219i, de \u00eendat\u0103 ce exist\u0103 aceast\u0103 limita este atins\u0103, serverul afi\u0219eaz\u0103 automat o eroare de 500 Internal Server Error c\u0103 semn pentru remedierea acesteia. Cea mai simpl\u0103 modalitate de a rezolva aceast\u0103 problema este prin cre\u0219terea limitei de memorie PHP a site-ului dvs. WordPress.<\/p>\n<p>S\u0103 vedem dou\u0103 moduri prin care pute\u021bi cre\u0219te limita de memorie PHP.<\/p>\n<p>&#8211; Edita\u021bi fi\u0219ierul .htaccess:<\/p>\n<p>\u00cen fi\u0219ierul .htaccess, accesa\u021bi sec\u021biunea \u0219i introduce\u021bi urm\u0103torul cod:<\/p>\n<p>php_value upload_max_filesize 64M<br \/>\nphp_value post_max_size 64M<\/p>\n<p>&#8211; Crea\u021bi un fi\u0219ier PHP.ini:<\/p>\n<p>Un mod mai simplu de a cre\u0219te limita de memorie PHP este crearea unui fi\u0219ier PHP.ini. \u00cen zona de administrare, g\u0103si\u021bi wp-admin \u0219i crea\u021bi un fi\u0219ier php.ini \u0219i introduce\u021bi urm\u0103torul cod:<\/p>\n<p>memory_limit = 64M<br \/>\nupload_max_filesize = 64M<br \/>\npost_max_size = 64M<br \/>\nfile_uploads = Activat<\/p>\n<p>Re\u00eenc\u0103rca\u021bi-v\u0103 site-ul dup\u0103 ce a\u021bi crescut limita de memorie PHP. Pentru majoritatea site-urilor web, aceasta este cauza erorii 500 Internal Server Error. Merge\u021bi la pasul urm\u0103tor, \u00een cazul \u00een care totu\u0219i problema dvs. nu s-a rezolvat \u00eenc\u0103.<\/p>\n<p><strong>3. Dezactiva\u021bi pluginurile<\/strong><\/p>\n<p>Dac\u0103 cele dou\u0103 solu\u021bii de mai sus nu au func\u021bionat pentru dvs., eroarea ar putea fi din cauza unui plugin defect.<\/p>\n<p>Primul pas este s\u0103 verifica\u021bi dac\u0103 pluginurile sunt actualizate, un plugin cu o versiune dep\u0103\u0219it\u0103 ar putea fi un motiv pentru aceast\u0103 eroare. Dac\u0103 ave\u021bi un plugin \u00eenvechit, elimina\u021bi-l \u0219i re\u00eenc\u0103rca\u021bi site-ul. Dac\u0103 nici acest lucru nu rezolv\u0103 problema, singur\u0103 modalitate de a verifica este dezactivarea tuturor pluginurilor.<\/p>\n<p>Accesa\u021bi panoul de administrare WordPress \u2192 Selecta\u021bi Plugins \u2192 Face\u021bi clic pe Dezactivare<\/p>\n<p>Re\u00eenc\u0103rca\u021bi site-ul dvs. din nou. Dac\u0103 eroarea se rezolv\u0103, atunci ura! Dar care dintre acestea a fost pluginul defect? Nu exist\u0103 nici o modalitate de a vedea acest lucru \u00een afar\u0103 de a reactiva un c\u00e2te un singur plugin pe r\u00e2nd \u0219i a verifica site-ul dvs. \u00cen momentul \u00een care acesta \u00ee\u0219i revine, a\u021bi g\u0103sit pluginul defect.<\/p>\n<p>P\u00e2n\u0103 \u00een acest punct, sper\u0103m c\u0103 problema dvs. este rezolvat\u0103 \u0219i c\u0103 site-ul dvs. este online. Cu toate acestea, dac\u0103 problema persist\u0103, singura solu\u021bie este contactarea furnizorului de servicii de g\u0103zduire.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Va aminti\u021bi de momentul \u00een care a\u021bi \u00eencercat s\u0103 v\u0103 conecta\u021bi la WordPress, acest proces dur\u00e2nd foarte mult? \u0218i, c\u00e2nd \u00een sf\u00e2r\u0219it a\u021bi crezut c\u0103 s-a \u00eenc\u0103rcat, a ap\u0103rut o maimu\u021bic\u0103 cu un ciocan \u0219i o \u0219urubelni\u021b\u0103 care \u00eencearc\u0103 s\u0103 repare ceva? A\u021bi ghicit bine! Vorbim despre eroarea 500 Internal Server Error. \u00cen acest articol,<\/p>\n","protected":false},"author":1,"featured_media":1117,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[150],"tags":[],"class_list":["post-506","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-gazduire"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.1.1 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Remedierea erorii 500 Internal Server Error \u00een WordPress - NAV.RO Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/\" \/>\n<meta property=\"og:locale\" content=\"ro_RO\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Remedierea erorii 500 Internal Server Error \u00een WordPress - NAV.RO Blog\" \/>\n<meta property=\"og:description\" content=\"Va aminti\u021bi de momentul \u00een care a\u021bi \u00eencercat s\u0103 v\u0103 conecta\u021bi la WordPress, acest proces dur\u00e2nd foarte mult? \u0218i, c\u00e2nd \u00een sf\u00e2r\u0219it a\u021bi crezut c\u0103 s-a \u00eenc\u0103rcat, a ap\u0103rut o maimu\u021bic\u0103 cu un ciocan \u0219i o \u0219urubelni\u021b\u0103 care \u00eencearc\u0103 s\u0103 repare ceva? A\u021bi ghicit bine! Vorbim despre eroarea 500 Internal Server Error. \u00cen acest articol,\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/\" \/>\n<meta property=\"og:site_name\" content=\"NAV.RO Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/nav6718\" \/>\n<meta property=\"article:published_time\" content=\"2018-08-21T19:05:42+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-11-22T10:20:54+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2019\/01\/wordpress_eroare_500.png\" \/>\n\t<meta property=\"og:image:width\" content=\"825\" \/>\n\t<meta property=\"og:image:height\" content=\"432\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"NAV.RO\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@nav6718\" \/>\n<meta name=\"twitter:site\" content=\"@nav6718\" \/>\n<meta name=\"twitter:label1\" content=\"Scris de\" \/>\n\t<meta name=\"twitter:data1\" content=\"NAV.RO\" \/>\n\t<meta name=\"twitter:label2\" content=\"Timp estimat pentru citire\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minute\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/\"},\"author\":{\"name\":\"NAV.RO\",\"@id\":\"https:\/\/www.nav.ro\/blog\/#\/schema\/person\/c0271febcae717bbdbc3b2c6dbdec20e\"},\"headline\":\"Remedierea erorii 500 Internal Server Error \u00een WordPress\",\"datePublished\":\"2018-08-21T19:05:42+00:00\",\"dateModified\":\"2021-11-22T10:20:54+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/\"},\"wordCount\":904,\"publisher\":{\"@id\":\"https:\/\/www.nav.ro\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2019\/01\/wordpress_eroare_500.png\",\"articleSection\":[\"G\u0102ZDUIRE\"],\"inLanguage\":\"ro-RO\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/\",\"url\":\"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/\",\"name\":\"Remedierea erorii 500 Internal Server Error \u00een WordPress - NAV.RO Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.nav.ro\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2019\/01\/wordpress_eroare_500.png\",\"datePublished\":\"2018-08-21T19:05:42+00:00\",\"dateModified\":\"2021-11-22T10:20:54+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/#breadcrumb\"},\"inLanguage\":\"ro-RO\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"ro-RO\",\"@id\":\"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/#primaryimage\",\"url\":\"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2019\/01\/wordpress_eroare_500.png\",\"contentUrl\":\"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2019\/01\/wordpress_eroare_500.png\",\"width\":825,\"height\":432},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Prima pagin\u0103\",\"item\":\"https:\/\/www.nav.ro\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Remedierea erorii 500 Internal Server Error \u00een WordPress\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.nav.ro\/blog\/#website\",\"url\":\"https:\/\/www.nav.ro\/blog\/\",\"name\":\"NAV.RO Blog\",\"description\":\"Stiri IT\u2705 de actualitate si noutati din domeniul Hosting \u279c Gazduire Web \u279c Servere Dedicate \/ VPS \u279c DATA CENTER \u279c Domenii \u2b50 Actualizare zilnica de la expertii NAV.RO\",\"publisher\":{\"@id\":\"https:\/\/www.nav.ro\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.nav.ro\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ro-RO\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.nav.ro\/blog\/#organization\",\"name\":\"NAV Communications\",\"url\":\"https:\/\/www.nav.ro\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ro-RO\",\"@id\":\"https:\/\/www.nav.ro\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2022\/09\/nav_logo.png\",\"contentUrl\":\"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2022\/09\/nav_logo.png\",\"width\":1120,\"height\":800,\"caption\":\"NAV Communications\"},\"image\":{\"@id\":\"https:\/\/www.nav.ro\/blog\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/nav6718\",\"https:\/\/x.com\/nav6718\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.nav.ro\/blog\/#\/schema\/person\/c0271febcae717bbdbc3b2c6dbdec20e\",\"name\":\"NAV.RO\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ro-RO\",\"@id\":\"https:\/\/www.nav.ro\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/93c42d768fb29d2b7c2c9b94595b1770ec8dbbda107bfb5e6759247e857c9cda?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/93c42d768fb29d2b7c2c9b94595b1770ec8dbbda107bfb5e6759247e857c9cda?s=96&d=mm&r=g\",\"caption\":\"NAV.RO\"},\"sameAs\":[\"https:\/\/www.nav.ro\"],\"url\":\"https:\/\/www.nav.ro\/blog\/author\/useradmin\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Remedierea erorii 500 Internal Server Error \u00een WordPress - NAV.RO Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/","og_locale":"ro_RO","og_type":"article","og_title":"Remedierea erorii 500 Internal Server Error \u00een WordPress - NAV.RO Blog","og_description":"Va aminti\u021bi de momentul \u00een care a\u021bi \u00eencercat s\u0103 v\u0103 conecta\u021bi la WordPress, acest proces dur\u00e2nd foarte mult? \u0218i, c\u00e2nd \u00een sf\u00e2r\u0219it a\u021bi crezut c\u0103 s-a \u00eenc\u0103rcat, a ap\u0103rut o maimu\u021bic\u0103 cu un ciocan \u0219i o \u0219urubelni\u021b\u0103 care \u00eencearc\u0103 s\u0103 repare ceva? A\u021bi ghicit bine! Vorbim despre eroarea 500 Internal Server Error. \u00cen acest articol,","og_url":"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/","og_site_name":"NAV.RO Blog","article_publisher":"https:\/\/www.facebook.com\/nav6718","article_published_time":"2018-08-21T19:05:42+00:00","article_modified_time":"2021-11-22T10:20:54+00:00","og_image":[{"width":825,"height":432,"url":"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2019\/01\/wordpress_eroare_500.png","type":"image\/png"}],"author":"NAV.RO","twitter_card":"summary_large_image","twitter_creator":"@nav6718","twitter_site":"@nav6718","twitter_misc":{"Scris de":"NAV.RO","Timp estimat pentru citire":"4 minute"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/#article","isPartOf":{"@id":"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/"},"author":{"name":"NAV.RO","@id":"https:\/\/www.nav.ro\/blog\/#\/schema\/person\/c0271febcae717bbdbc3b2c6dbdec20e"},"headline":"Remedierea erorii 500 Internal Server Error \u00een WordPress","datePublished":"2018-08-21T19:05:42+00:00","dateModified":"2021-11-22T10:20:54+00:00","mainEntityOfPage":{"@id":"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/"},"wordCount":904,"publisher":{"@id":"https:\/\/www.nav.ro\/blog\/#organization"},"image":{"@id":"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/#primaryimage"},"thumbnailUrl":"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2019\/01\/wordpress_eroare_500.png","articleSection":["G\u0102ZDUIRE"],"inLanguage":"ro-RO"},{"@type":"WebPage","@id":"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/","url":"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/","name":"Remedierea erorii 500 Internal Server Error \u00een WordPress - NAV.RO Blog","isPartOf":{"@id":"https:\/\/www.nav.ro\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/#primaryimage"},"image":{"@id":"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/#primaryimage"},"thumbnailUrl":"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2019\/01\/wordpress_eroare_500.png","datePublished":"2018-08-21T19:05:42+00:00","dateModified":"2021-11-22T10:20:54+00:00","breadcrumb":{"@id":"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/#breadcrumb"},"inLanguage":"ro-RO","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/"]}]},{"@type":"ImageObject","inLanguage":"ro-RO","@id":"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/#primaryimage","url":"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2019\/01\/wordpress_eroare_500.png","contentUrl":"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2019\/01\/wordpress_eroare_500.png","width":825,"height":432},{"@type":"BreadcrumbList","@id":"https:\/\/www.nav.ro\/blog\/remedierea-erorii-500-internal-server-error-in-wordpress\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Prima pagin\u0103","item":"https:\/\/www.nav.ro\/blog\/"},{"@type":"ListItem","position":2,"name":"Remedierea erorii 500 Internal Server Error \u00een WordPress"}]},{"@type":"WebSite","@id":"https:\/\/www.nav.ro\/blog\/#website","url":"https:\/\/www.nav.ro\/blog\/","name":"NAV.RO Blog","description":"Stiri IT\u2705 de actualitate si noutati din domeniul Hosting \u279c Gazduire Web \u279c Servere Dedicate \/ VPS \u279c DATA CENTER \u279c Domenii \u2b50 Actualizare zilnica de la expertii NAV.RO","publisher":{"@id":"https:\/\/www.nav.ro\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.nav.ro\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ro-RO"},{"@type":"Organization","@id":"https:\/\/www.nav.ro\/blog\/#organization","name":"NAV Communications","url":"https:\/\/www.nav.ro\/blog\/","logo":{"@type":"ImageObject","inLanguage":"ro-RO","@id":"https:\/\/www.nav.ro\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2022\/09\/nav_logo.png","contentUrl":"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2022\/09\/nav_logo.png","width":1120,"height":800,"caption":"NAV Communications"},"image":{"@id":"https:\/\/www.nav.ro\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/nav6718","https:\/\/x.com\/nav6718"]},{"@type":"Person","@id":"https:\/\/www.nav.ro\/blog\/#\/schema\/person\/c0271febcae717bbdbc3b2c6dbdec20e","name":"NAV.RO","image":{"@type":"ImageObject","inLanguage":"ro-RO","@id":"https:\/\/www.nav.ro\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/93c42d768fb29d2b7c2c9b94595b1770ec8dbbda107bfb5e6759247e857c9cda?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/93c42d768fb29d2b7c2c9b94595b1770ec8dbbda107bfb5e6759247e857c9cda?s=96&d=mm&r=g","caption":"NAV.RO"},"sameAs":["https:\/\/www.nav.ro"],"url":"https:\/\/www.nav.ro\/blog\/author\/useradmin\/"}]}},"_links":{"self":[{"href":"https:\/\/www.nav.ro\/blog\/wp-json\/wp\/v2\/posts\/506","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.nav.ro\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.nav.ro\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.nav.ro\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.nav.ro\/blog\/wp-json\/wp\/v2\/comments?post=506"}],"version-history":[{"count":8,"href":"https:\/\/www.nav.ro\/blog\/wp-json\/wp\/v2\/posts\/506\/revisions"}],"predecessor-version":[{"id":2249,"href":"https:\/\/www.nav.ro\/blog\/wp-json\/wp\/v2\/posts\/506\/revisions\/2249"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.nav.ro\/blog\/wp-json\/wp\/v2\/media\/1117"}],"wp:attachment":[{"href":"https:\/\/www.nav.ro\/blog\/wp-json\/wp\/v2\/media?parent=506"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.nav.ro\/blog\/wp-json\/wp\/v2\/categories?post=506"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.nav.ro\/blog\/wp-json\/wp\/v2\/tags?post=506"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}