Ошибка обновления ответ не является допустимым ответом json gutenberg

You are creating content in the WordPress editor but the document fails to update. In fact, you see an error message that says “Updating failed. Error message: The response is not a valid JSON response.” Before you panic, let me assure you that this error can be resolved easily so you don’t lose your hard work.

This error is one of the common WordPress errors that users encounter on their sites.

Why does “the response is not a valid JSON response” error occur?

There could be multiple reasons why this error occurs. This post delves into each reason and offers multiple solutions to solve the problem.

1. Reset the permalinks

Before you try anything else, you should try resetting your permalinks to resolve the invalid JSON response error. Navigate to Settings > Permalinks in your WordPress dashboard. Then ensure that the correct permalink setting is selected and click the Save Changes button.

Now try updating a page. The error should be fixed but if it still occurs, try out the solutions below.

2. Disable the Block editor and switch back to Classic editor

The error “Updating failed. Error message: The response is not a valid JSON response.” is overwhelmingly seen in the new Block editor called Gutenberg.

The easiest way to resolve the updating error is by disabling Gutenberg and switching back to the Classic editor. As they say, old is Gold.

You can install the Classic Editor plugin for this. Once you have activated the plugin, try to save your posts. You should not see any error message now.

But what if you still want to use the block editor?

Nice question. It could be that reverting to the classic editor is not an option for you. In that case, you should follow what we are doing on PassionWP. With the classic editor plugin installed and activated, navigate to Settings>Writing.

Now select the Classic Editor as the “default editor for all users” option, save your changes, and clear your website cache. Right after this, select the Block Editor as the default editor and again save the changes.

Now try editing an existing post or create a new post with the block editor. You should not encounter the JSON response error. However, it could be that the editor fails to automatically save your changes.

In this event, press Ctrl + S (Cmd + S for Mac) to manually save your changes. This solution works for us and we are using the block editor without encountering the JSON response error.

3. Mixed content error due to the use of SSL certificate

Another common reason for this error is the use of a secure socket layer (SSL) certificate (HTTPS) on your WordPress site. Using an SSL certificate can result in some content being delivered non-securely on HTTP protocol even while the rest of the content is delivered in a secure manner over HTTPS protocol.

This results in a mixed content error in which both https and https content is transmitted at the same time to the web browser, usually Google Chrome.

How to solve the Mixed Content Error in WordPress?

We investigated the mixed content error and noticed that it is linked to the use of the Really Simple SSL plugin that is used by over 3 million WordPress users to configure HTTPS on their websites.

To resolve the “the response is not a valid JSON response” or mixed content error, navigate to Settings > SSL. This will open the plugin’s settings. Now click on the Settings tab.

You should do the following two things here:

1. Ensure that the “Mixed content fixer” option is turned on. This prevents mixed content problems on your website that we discussed above.
2. Next, you should turn on the “Use an alternative method to fix the mixed content” option. This will ensure that “the response is not a valid JSON response” error does not erupt abruptly while editing.

After saving the changes, go back to the post you were working on and try saving your post or page. You should no longer experience the response is not a valid JSON response error.

ad

4. Plugin conflict

The more plugins you use on your WordPress site, the higher the chances of conflict between plugins. Some of these conflicts can result in invalid JSON response errors as well.

I have witnessed this issue on websites running a high number of plugins, say more than 40. But it’s not just the number of plugins that matter. Rather, some plugin files might be causing the JSON bug on your website.

For instance, on a client’s site, the Yoast SEO plugin was causing the JSON response error.

So, in order to rule out any plugin conflict, you should deactivate all the plugins on your website. If required, use the Health Check and Troubleshooting plugin to deactivate the plugins in the backend while the front end remains the same for your visitors.

If the JSON response error disappears when you deactivate all the plugins means that one of the plugins was causing the error. Now, you should activate the plugins one by one. If the error recurs on activating a particular plugin implies that this plugin was the culprit.

5. WordPress REST API conflict

The WordPress admin backend uses the REST API to communicate with the server. If there is any conflict with this API, WordPress won’t be able to connect with the server and will instead display the JSON response error.

In order to identify if the REST API problem is indeed causing the problem, try editing one of your posts and saving it. Once the invalid JSON error is displayed, right-click the mouse button and then click Inspect to open Chrome’s dev tools.

Now under the Console tab, check whether any REST API error is displayed. If it is, then the REST API conflict is indeed the cause.

The best solution to this is to contact your web host since REST API errors are mostly caused at the server level. If you’re using a cache plugin like LiteSpeed Cache, you should disable the setting to cache the REST API and try saving the post again.

6. Alternative solutions to the response is not a valid JSON response error

Deactivate all the plugins on your site and edit the content normally. If you’re using the Really Simple SSL plugin then deactivate this plugin first. Subsequently, try saving the document. If you are able to save it without facing any errors, re-activate the plugins one by one to check which plugin was causing the error.

There is another solution you can try to fix the response is not a valid JSON response error in WordPress.

Navigate to Settings > Permalinks. Change the permalink structure from post-name or the current structure to Plain i.e. https://yoursite.com/?p=123. Now try saving your post/page. The problem should have been resolved.

But try this solution if all other methods fail as changing the permalinks will result in huge SEO issues on a live website and you will also need to add multiple redirects.

We discussed 6 possible solutions to the response is not a valid JSON response error in WordPress. I hope one of these methods worked for you. If it did, let me know in the comments below. If it didn’t, post your specific problem so others can suggest different solutions.

You can also check out our WordPress Error Fixing Service to fix the invalid JSON response error for you.

Почему возникает эта ошибка?

Причин возникновения этой ошибки множество, но самая распространенная — отключение событий REST API. Но мы не будем останавливаться только на ней и рассмотрим все возможные способы решения этой проблемы.

Кстати, так выглядит сама ошибка обновления, возникающая при публикации или обновлении записи в WordPress.

Как я решил эту проблему? Изначально я создавал сайт на хостинге Beget, после завершения работы требовалось выгрузить сайт на хостинг Namecheap. И сразу после публикации сайта я обнаружил, что больше могу обновлять или создавать новые записи/страницы. Особо никаких действий предпринимать мне не хотелось, поэтому я просто написал в техподдержку, и там решили мою проблему.

Если же техподдержка вашего хостинга не очень отзывчивая, то я рекомендую перейти на Beget и обязательно указать мой код партнера 1486766 при регистрации! 😀

А если серьезно, то попробуйте каждый из описанных ниже методов, и один из них вам наверняка поможет!

Способ 1. Обновите постоянные ссылки

Перейдите в консоль вашего сайта, затем в Настройки и найдите там пункт Постоянные ссылки.

Здесь вам требуется просто нажать на кнопку Обновить. После этого можно проверить изменения.

Способ 2. Установка классического редактора WordPress

Далеко не самый идеальный способ решения проблемы, потому что вам придется отказаться от удобного современного блочного редактора и начать пользоваться его давно устаревшей версией.

Скачайте плагин Классический редактор с официального репозитория WordPress. Затем перейдите в Настройки — Написание. Здесь вам нужно найти параметр Классический редактор для всех пользователей и выбрать значение Для всех.

Можно проверить изменения. Если не помогло, переходим к следующему способу!

Способ 3. Отсутствие SSL сертификата или его некорректная настройка

Зачастую многие регистраторы и хостинг-провайдеры предлагают слишком дорогие SSL-сертификаты, цена на которые порой превышает 5 000 рублей за год. Далеко не все готовы платить столько денег и ищут возможность подключить бесплатный SSL-сертификат.

Зачастую эти попытки заканчиваются неудачами, некорректными настройками сайта, что приводит к ряду ошибок.

Если вы новичок, то крайне рекомендую использовать хостинг Beget в своей работе. Он не только предоставляет бесплатный пробный период на 30 дней для любого тарифа, но и выдает бесплатные рабочие SSL-сертификаты. Я уже как-то писал обзор на хостинг Beget, рекомендую к прочтению!

Способ 4. Устранение ошибки смешанного содержимого

Данное решение поможет, если ошибка возникла после подключения SSL-сертификата. Для начала перейдите в раздел настроек вашего сайта и проверьте, чтобы URL WordPress Address (Адрес WordPress) и URL Site Address (Адрес сайта) начинались с протокола безопасного соединения https.

Затем перейдите в раздел плагинов, скачайте и установите Really Simple SSL. После активации плагина появится уведомление Almost Ready to migrate SSL. Нажмите на синюю кнопку Activate SSL.

Затем идем в Настройки, находим раздел SSL. Проконтролируйте, чтобы первые три пункта (Mixed content fixer, Enable WordPress 301 Redirection to SSL, Enable 301 .htaccess redirect) были активны. По окончанию настройки проверяем изменения.

Способ 5. Проверка тем и плагинов

Если ошибка «Обновление не удалось. Ответ не является допустимым ответом JSON» появилась после установки какой-то темы или плагина, то не сложно догадаться, в чем может быть причина ее возникновения.

Попробуйте переключиться на другую тему и проверить изменения. Затем отключите все плагины и снова проверьте изменения. Если же проблема решена, то остается только выяснить, какой из плагинов вызывает эту ошибку. Включайте их по очереди и проверяйте, появилась ли снова эта проблема.

Способ 6. Удостоверьтесь, что вы не отключили Rest API и wp-json

В самом начале этого материала я сказал, что это одна из самых частых причин возникновения ошибки обновления записей и страниц.

Перейдите в редактор вашей темы и найдите файл functions.php. А теперь внимательно изучите его содержимое. Если проблема кроется в отключении REST API и wp-json вы найдете примерно следующее:

// Отключаем сам REST API
add_filter('rest_enabled', '__return_false');

// Отключаем фильтры REST API
remove_action( 'xmlrpc_rsd_apis',            'rest_output_rsd' );
remove_action( 'wp_head',                    'rest_output_link_wp_head', 10, 0 );
remove_action( 'template_redirect',          'rest_output_link_header', 11, 0 );
remove_action( 'auth_cookie_malformed',      'rest_cookie_collect_status' );
remove_action( 'auth_cookie_expired',        'rest_cookie_collect_status' );
remove_action( 'auth_cookie_bad_username',   'rest_cookie_collect_status' );
remove_action( 'auth_cookie_bad_hash',       'rest_cookie_collect_status' );
remove_action( 'auth_cookie_valid',          'rest_cookie_collect_status' );
remove_filter( 'rest_authentication_errors', 'rest_cookie_check_errors', 100 );

// Отключаем события REST API
remove_action( 'init',          'rest_api_init' );
remove_action( 'rest_api_init', 'rest_api_default_filters', 10, 1 );
remove_action( 'parse_request', 'rest_api_loaded' );

// Отключаем Embeds связанные с REST API
remove_action( 'rest_api_init',          'wp_oembed_register_route'              );
remove_filter( 'rest_pre_serve_request', '_oembed_rest_pre_serve_request', 10, 4 );
remove_action( 'wp_head', 'wp_oembed_add_discovery_links' );

// Отключаем wp-json
add_filter('rest_enabled', '__return_false');
remove_action( 'xmlrpc_rsd_apis', 'rest_output_rsd' );
remove_action( 'wp_head', 'rest_output_link_wp_head', 10, 0 );
remove_action( 'template_redirect', 'rest_output_link_header', 11, 0 );
remove_action( 'auth_cookie_malformed', 'rest_cookie_collect_status' );
remove_action( 'auth_cookie_expired', 'rest_cookie_collect_status' );
remove_action( 'auth_cookie_bad_username', 'rest_cookie_collect_status' );
remove_action( 'auth_cookie_bad_hash', 'rest_cookie_collect_status' );
remove_action( 'auth_cookie_valid', 'rest_cookie_collect_status' );
remove_filter( 'rest_authentication_errors', 'rest_cookie_check_errors', 100 );
remove_action( 'init', 'rest_api_init' );
remove_action( 'rest_api_init', 'rest_api_default_filters', 10, 1 );
remove_action( 'parse_request', 'rest_api_loaded' );
remove_action( 'rest_api_init', 'wp_oembed_register_route' );
remove_filter( 'rest_pre_serve_request', '_oembed_rest_pre_serve_request', 10, 4 );
remove_action( 'wp_head', 'wp_oembed_add_discovery_links' );
remove_action( 'wp_head', 'wp_oembed_add_host_js' );

Если у вас есть похожий код, то удаляем его. Затем переходим в Настройки, находим раздел «Постоянные ссылки» и нажимаем «обновить».

Способ 7. Узнать ответ у техподдержки вашего хостинга

Иногда проблема может возникнуть не из-за вашего сайта, а некорректных настроек сервера. Попробуйте обратиться в техподдержку вашего хостинга с просьбой решить вашу проблему.

Кстати, а вам рассказать, у какого хостинга самая лучшая техподдержка? 😀 Конечно же у Beget! А вы думали, я какой-то другой хостинг здесь посоветую? (Не забывайте при регистрации указывать мой партнерский код 1486766, так я заработаю много денег и больше не буду писать статьи).

Вам понравился материал? Интересует разработка сайтов? Тогда обязательно подпишитесь на нашу группу ВКонтакте! Так вы всегда будете в курсе событий и никогда не пропустите новые материалы. А еще у нас есть беседа с активными участниками, где мы бесплатно помогаем новичкам с решением любых вопросов! 🙂

Fix the annoying WordPress error Publishing failed. The response is not a valid JSON response., Updating failed. The response is not a valid JSON response., or The response is not a valid JSON response.

You may have seen these errors when trying to publish or update your WordPress posts or pages. You may even have see this error when trying to upload an image in your WordPress website.

If you don’t deal with this error right away, you may lose all the changes that you have made for the past few hours (yes, we humans still go by hours without saving our work). This article is about rescuing you from that.

There are many reasons for why these errors can occur to your WordPress site. It can be related to your web server, .htaccess file, SSL certificate, a plugin, a theme, or for another reason. So depending on your specific scenario, a different solution may work for you.

Here, I have outlined all the methods that will help you solve this error. Be it Publishing failed. Error message: The response is not a valid JSON response., Updating failed. Error message: The response is not a valid JSON response., or just The response is not a valid JSON response.

Try using the following methods one by one and you should find the one that works for you. But in order not to lose your work progress, open your WordPress dashboard in a new window and try the solutions there.

Update Permalink

Warning: Updating permalink structure may change the URL of all your website pages and posts so the previous URLs to access your pages and posts won’t work. Your website’s SEO will also be affected by this. Therefore, if keeping your original URL is important, you may either not want to try this one or revert back to the original permalink structure as soon as the test is completed. But if your website is brand new, you don’t have to worry about it.

The most common solution for publishing or updating failed the response is not a valid JSON response error is to update your permalink structure.

From your WordPress dashboard, go to Settings and then Permalinks. Then you can click on the Save Changes button to re-save or update the current permalink structure. Then check to see if the error is fixed.

If it doesn’t fix the error then you can go back to the permalink page and then select Plain from under the Custom Settings heading to change the permalink structure. Then click on Save Changes. Now check again to see if the error has been solved.

If the error hasn’t resolved, then you can try changing to all the other permalink structures and check if the error gets solved for any of them.

If this solution doesn’t work for you try the next one.

Use Classic Editor

In December 2018 WordPress updated their Classic Editor with the new Gutenberg/Block Editor. And since then many have faced this “Publishing failed. The response is not a valid JSON response.” and “Updating failed. The response is not a valid JSON response.” error.

So, by going back to the Classic Editor many have been able to solve the error. In order to use Classic Editor, you will need to install and activate the Classic Editor plugin on your WordPress website.

However, if you use Classic Editor, this will replace the new Block Editor of WordPress with its old Classic Editor. This will change how you are used to editing your pages and posts. This may also affect the formatting and layout of your existing pages and posts that have been previously edited using the Block editor. So, you should safeguard your site first by changing a setting in the Classic Editor before you start using it.

So, to safeguard from affecting your existing pages, after you activate the Classic Editor plugin, go to Settings and then Writing from the WordPress dashboard. This will show you the settings for the Classic Editor plugin. From here, select “Yes” for the option “Allow users to switch editors”. Then click on Save Changes. This will let you use the Gutenberg/Block editor for your existing pages and posts so you won’t have to be concerned about losing existing work in case you want to edit any existing pages or posts on your site. This will also give you the option to edit any new pages or posts with either Block editor or the Classic editor.

Then try creating a new page or post using the Classic Editor and check if the JSON response error has been fixed.

From the plugin’s settings page, you can also select “Block Editor” as the option for “Default editor for all users” if you would like to make the Block Editor your default WordPress editor while using the Classic Editor plugin.

Using the Classic Editor might solve the JSON response error for you while updating or publishing your pages and posts. But if it doesn’t solve the error, then you can just deactivate the plugin and try out the next solution.

Configure SSL

Your website always needs to have TLS/SSL enabled or web browsers will show a warning message whenever someone tries to visit your website. That warning will make your site look dangerous so you will lose lots of your website visitors. That’s why properly setting up SSL certificate for your website is an important thing to do regardless of it solving “The response is not a valid JSON response” error.

In this part, I will tell you how you can properly set up your WordPress website to use SSL certificate which is also a very common solution to the JSON response error.

Use SSL Certificate

You can check if your site is using SSL certificate by looking at the URL of your website. After your website is loaded in a web browser, you can click on your website’s URL to see if the URL starts with HTTPS or HTTP. If it starts with HTTPS and if you see a padlock icon without a cross sign beside the URL, then your site is already configured with SSL certificate. So, you will just need to ensure that your website is using it properly.

For instance, if your website is example.com then it will look like https://example.com and it will be marked with a padlock icon after it loads in your web browser if it is properly set up with SSL certificate.

However, having no padlock icon doesn’t always mean that an SSL certificate hasn’t been issued or your website. Instead, the reason might be that your website hasn’t been configured to automatically redirect all HTTP traffic to the HTTPS version of your website. To check if that is the case, change your website URL’s HTTP to HTTPS on the web browser and press enter. If the browser now shows a padlock icon beside the URL, then an SSL certificate has been issued for your site but it isn’t configured properly. So, we will need to configure it properly.

But if changing HTTP to HTTPS doesn’t work, then that it is probably because an SSL certificate hasn’t been issued for your website. And if that is the case, then you will first need to issue an SSL certificate for your website. If you are using cPanel, Plesk, DirectAdmin, CyberPanel or any other web hosting control panel, then you can easily issue an SSL certificate for your website from that web hosting control panel. See their guide on how to do that.

Additionally, the validity of SSL certificates expires after a certain period so you may also check if your SSL certificate is still valid. If it is not valid then you should first renew the SSL certificate to fix the SSL related issues. Once a valid SSL certificate is installed on your WordPress site, you can follow the next steps here to solve Publishing failed. The response is not a valid JSON response. or Updating failed. The response is not a valid JSON response. error.

Force HTTPS Redirect

Using your web hosting control panel like cPanel, Plesk, CyberPanel, etc., you can easily redirect all HTTP traffic to the HTTPS version of your website. The process of doing this will differ based on the hosting control panel you are using but you should easily find an option to do that in the SSL settings or in the domain settings option on the control panel. Look for settings that say something like force HTTPS redirect, redirect HTTP to HTTPS, and so on. See their guide on how to do that.

If you aren’t using a hosting control panel or if this doesn’t work for you then you can use the Really Simple SSL plugin to do that. I have described it further in the next step «Solve Mixed Content Error» which is also very important to solve SSL related issues for your WordPress site. So, even if this step solves the error, you should still follow the next step to solve the mixed content error on your website.

Solve Mixed Content Error

Your webpages will generally require linking multiple files like CSS, JS, images, etc. to display and function properly. And the links for these files may contain HTTP or HTTPS. If your website is configured to use HTTPS but if some of those links are using HTTP instead of HTTPS, there will be a mixed content error.

To solve this problem you can install the Really Simple SSL plugin on your WordPress site. It will modify all links on your website to use HTTPS and therefore solve the mixed content error.

After you install and activate the Really Simple SSL plugin, you will get a notification to activate SSL. So, click on the “Go ahead, activate SSL!” button on the notification. But if you don’t see the notification then from your WordPress dashboard, go to Settings and select SSL.

Then you will see the same button saying “Go ahead, activate SSL!”. Once you click on the button it will activate SSL and set HTTPS redirect for your website.

Then it will give you will see a warning that says “WordPress 301 redirect enabled. We recommend to enable the 301 .htaccess redirect option on your specific setup”. Beside that warning, you will see a link saying “Enable”. Clicking on the link will take you to the Settings tab on the plugin. You can also go to the same page from your WordPress dashboard by going to Settings then SSL and then by selecting the Settings tab.

Here, you will see an option saying “Enable 301 .htaccess redirect”. Turn on the button beside that to activate HTTPS redirect from your .htaccess file. Before enabling the button you can also read the warning on how to regain access to your site in case of a redirect loop issue. Then after enabling the button click on Save.

Also, from your WordPress dashboard, you can go to Settings then General. This will show you “WordPress Address (URL)” and “Site Address (URL)”. Make sure that these URLs are using HTTPS and not HTTP.

After doing this, check if the JSON response error has been fixed. If it doesn’t get fixed, you can also go to Settings > SSL > Settings and then turn on the button beside the “Use alternative method to fix mixed content” option and then save the change.

Now, check if the JSON response error has been fixed. If it hasn’t, then turn off the button beside the “Use alternative method to fix mixed content” option and save the change again then follow the next solution.

Check Themes and Plugins

If the previous methods don’t work for you then you can try to find out if it is any theme or plugin that is causing the problem. So, first, go to Appearance and then Themes from your WordPress dashboard. Then activate the default WordPress theme (as of now it is Twenty Twenty) and check if the error is fixed. If not, then revert back to your original theme.

The error may also cause by a plugin and in that case you can deactivate all the plugins on your website and then check again to see if the error occurs. If the error doesn’t occur then it is probably a plugin that is causing the issue. So, to find out which plugin is causing the problem, turn on one plugin at a time and check if the error occurs. And if the error occurs after enabling a certain plugin, then you will know that is the one causing the problem. So, you can just deactivate that plugin and activate the rest of the plugins that you need.

Restart OpenLiteSpeed

If you are using OpenLiteSpeed web server, then there is a very high chance that a restart will solve your problem.

OpenLiteSpeed is the open source or free version of the LiteSpeed Web Server (also known as LIteSpeed Enterprise). One of the major differences between LiteSpeed Enterprise and OpenLiteSpeed is that LiteSpeed Enterprise autodetects changes in .htaccess file and adjusts as necessary in realtime but OpenLiteSpeed can’t do that so it requires restarting for any changes in the .htaccess file to take place. And because WordPress uses the .htaccess file for many operations, those inactive .htaccess changes in the OpenLiteSpeed server may also cause The response is not a valid JSON response error. If you see this error after adding a new website on your OpenLiteSpeed server, this may also be the reason.

So, if you are using OpenLiteSpeed web server, a restart of the OpenLiteSpeed server can solve the error for you.

If you are using CyberPanel web hosting panel with OpenLiteSpeed, then you can open your CyberPanel dashboard then go to Server Status then LiteSpeed Status. Then you can click on the Reboot LiteSpeed button to restart your OpenLIteSpeed server.

But if you are using a different web hosting panel or if you aren’t using any web hosting panel at all, then you will need to find out how to restart the OpenLIteSpeed server for your specific setup.

Update .htaccess

If none of the previous methods work then you can try configuring your .htaccess file.

In order to ensure that you can revert back to your original .htaccess file in case anything goes wrong, you can keep a backup of it by downloading it in your computer. If you know how to use an FTP client or the file manager of your web hosting control panel like cPanel, CyberPanel, etc., then you can download the .htaccess file from your website’s “public_html” folder.

If you want an easy solution and want to do everything from WordPress dashboard then install and activate a file manager plugin like Advanced File Manager on your WordPress website.

Then from your WordPress dashboard, go to File Manager then Settings. From here put a checkmark beside the Display .htaccess? option then click on Save Changes.

Now click on File Manager to see all the folders and files for your website. Here, in the “public_html” folder of your website, you will see the “.htaccess” file. Right-click on the file and click Download to keep a backup of it.

So, now you will be able to easily re-upload the original .htaccess file to the same location in case anything goes wrong.

Now, disable all the plugins on your WordPress site. Then delete the .htaccess file so that we can start from the beginning.

Now, go to Settings and then Permalinks from your WordPress dashboard. Then, make sure the permalink option of your choice is selected and then click on Save Changes. This will create a new .htaccess file for your website.

Now you need to check if “The response is not a valid JSON response” error is fixed or not.

If the error has been fixed, then you can turn on one plugin at a time and check if the error occurs again. If the error occurs after enabling a certain plugin then you can just deactivate that one and activate the other plugins as you need.

But if the error isn’t fixed after saving your permalink, then you can select the other permalink structures one after another and check if the JSON response has been fixed. Remember to change your permalink structure to the original one after your testing with different permalink structures is finished if you want to keep your previous URL structure.

But if that doesn’t fix “The response is not a valid JSON response” error, then you will need to follow the previously mentioned steps for Force HTTPS Redirect and Solve Mixed Content Error one more time. Do these steps while all your plugins are still deactivated.

This should solve the error for your website. And if the problem is solved, then activate all your plugins again one by one and check if any of them cause any problem. If the error doesn’t occur again, then the problem has been fixed but if the problem occurs after installing any specific plugin then just deactivate that plugin and activate the other ones.

After you activate the plugins, the .htaccess rules associated with the plugins should automatically be created to your new .htaccess file based on the existing plugin settings. So, you shouldn’t lose any configurations this way. But if something doesn’t work properly, then you can open both the .htaccess files in the editor or in a text document and compare the rules in both the .htaccess files. Then you can update the new .htaccess file with the changes you found. You can even delete the new .htaccess file and then upload the original one to go back to the previous state.

Check Site Health

From your WordPress dashboard, if you go to Tools and then select Site Health, then under the Status tab on that page, WordPress will show you any improvement recommendations that could help your website.

An issue related to Rest API could also cause the JSON response error on your website. Moreover, if you find any issue there, solving the issue might also fix the JSON response error for your website.

Fix Image Upload Error

If you have tried the previous methods but “The response is not a valid JSON response” error still occurs when you try to upload images on your WordPress website, then you can follow the instructions in this section.

Use Media Library Instead of Direct Upload

If you are trying to upload images in an Image block using the Upload button, then you might get the JSON response error but surprisingly many people have found that if they first select Media Library then go to the Upload Files tab and then upload images from there then the error doesn’t occur.

This might be a temporary workaround but it can be helpful if you are in the middle of writing a post or if any other methods don’t work for you.

Remove Invalid Characters

You may also get “The response is not a valid JSON response” error if you try to upload images with unsupported characters in the image name. So, you can rename your image using only English letters, numbers, and supported symbols like hyphens. Then you can upload that renamed image to see if the error has been fixed.

Use Default to GD plugin

Some people were also able to solve The response is not a valid JSON response error by using the Default to GD plugin. This plugin isn’t available on WordPress so you will need to download it from the Default to GD GitHub link.

To download the plugin click on the «Code” button on the page. Then select Download ZIP. This will download the plugin on your computer.

Then go to your WordPress dashboard then Plugins then Add New. Now click on Upload Plugin button then upload the plugin you just downloaded by clicking on the Choose File button. Then click on Install Now. After the installation is completed, click on Activate Plugin. It doesn’t require any set up so you can now check if the JSON response error occurs while uploading images to your WordPress site. And if the error still occurs, then you can just deactivate and then delete the plugin.

These methods for solving “The response is not a valid JSON response” error works for most people but if it doesn’t work for you then you may have a specific problem in your WordPress settings or in your web server setup. This error can also cause because of an issue related to the REST API, misconfiguration in NGINX server, security plugins like Wordfence or for security rules like WAF or Web Application Firewall. In these cases, you can look for solutions specific to those areas.

I hope one of these methods works for you and if works let me and others know which one worked for you. And if you found any other solution tell us in the comments section so that it can help others.

Грёбаная ошибка, которая отняла весь вечер. Уточню, ошибка выскакивала когда я пытался включить/разрешить комментарии к странице. При простом обновлении WordPress, данная ошибка не выскакивала.

Гугл  и Яндекс молчит по этому поводу, нигде никакой информации по «Ошибка обновления ответ не является допустимым ответом json».

Обновление страницы начало работать, только после того как я выполнил несколько действий, которые напишу ниже. Причину исправления я таки не понял. Так как мне  было надо вывести собаку на улицу.

Гуляли около часа. Вернулся,  решил повторить процесс, поставил галочку на «разрешить комментарии», и о чудо, страница обновилась без ошибок. Такой же процесс повторил ещё на пяти страницах, всё работает без сбоев.

Перед этим, делал несколько манипуляций, какая из них помогла, могу только догадываться. Уточню мои некоторые параметры моего хостинга и сайта: WordPress 5.4.2–ru_RU, CPanel, PHP 7.2,  бесплатный сертификат Let’s Encrypt SSL.

• Искал ответ в поисковых системах, нашел ряд рекомендаций.
• Переобновил версию WP
• Включал выключал настройки постоянных ссылок в админке, с  ?p=123 на читабельные ЧПУ
• Поставил плагин Really Simple SSL
• Менял версии PHP на 7.3, 7.0. Вернулся PHP к 7.2
• Деактивировал плагин для ЧПУ Webcraftic Cyrlitera. И  активировал снова.
• Переустановил сертификат Let’s Encrypt SSL в Cpanel. Сработало на один раз, страница корректно обновилась, но на других страницах снова ошибка.
• Погулял с собакой, около часа, пришёл, и всё заработало.

Скорее всего, проблема была в сертификате Let’s Encrypt SSL, только надо было дать  некоторое время.  Посмотрим что будет дальше.

Забыл. Ставил и удалял код в файле functions.php, который рекомендовали в сети.

// ОТКЛЮЧАЕМ САМ REST API
add_filter(‘rest_enabled’, ‘__return_false’);

// ОТКЛЮЧАЕМ ФИЛЬТРЫ REST API
remove_action( ‘xmlrpc_rsd_apis’, ‘rest_output_rsd’ );
remove_action( ‘wp_head’, ‘rest_output_link_wp_head’, 10, 0 );
remove_action( ‘template_redirect’, ‘rest_output_link_header’, 11, 0 );
remove_action( ‘auth_cookie_malformed’, ‘rest_cookie_collect_status’ );
remove_action( ‘auth_cookie_expired’, ‘rest_cookie_collect_status’ );
remove_action( ‘auth_cookie_bad_username’, ‘rest_cookie_collect_status’ );
remove_action( ‘auth_cookie_bad_hash’, ‘rest_cookie_collect_status’ );
remove_action( ‘auth_cookie_valid’, ‘rest_cookie_collect_status’ );
remove_filter( ‘rest_authentication_errors’, ‘rest_cookie_check_errors’, 100 );

// ОТКЛЮЧАЕМ СОБЫТИЯ REST API
remove_action( ‘init’, ‘rest_api_init’ );
remove_action( ‘rest_api_init’, ‘rest_api_default_filters’, 10, 1 );
remove_action( ‘parse_request’, ‘rest_api_loaded’ );

// ОТКЛЮЧАЕМ EMBEDS СВЯЗАННЫЕ С REST API
remove_action( ‘rest_api_init’, ‘wp_oembed_register_route’);
remove_filter( ‘rest_pre_serve_request’, ‘_oembed_rest_pre_serve_request’, 10, 4 );

remove_action( ‘wp_head’, ‘wp_oembed_add_discovery_links’ );

Were you trying to upload a file or edit a piece of content on your WordPress site only to be met by a scary red message saying something like, «Updating failed. The response is not a valid JSON response?»

The WordPress invalid JSON response error happens in the new Block Editor (AKA Gutenberg) when something goes wrong on your site. Because it appears when you’re working on content, it can be a frustrating error because it can get in the way of whatever task you’re trying to accomplish.

Thankfully, there are some straightforward steps that you can take to fix this problem and get your site working properly again.

In this post, we’ll briefly explain what the invalid JSON response error means. Then, we’ll share a number of troubleshooting steps you can implement to fix the problem.

If you see «Updating failed. The response is not a valid JSON response,» it will typically appear when you’re working on content in the WordPress Block Editor. In some cases, it can also appear when you’re trying to upload a media file to your site, especially if you’re trying to upload the file directly to a block in the Block Editor.

So, why does it happen?

When you’re working in the Block Editor, the editor is in constant communication with your WordPress site’s server. This «communication» happens behind the scenes, but it’s important to the editor.

One of the «languages» of this communication is JSON, short for JavaScript Object Notation. If something goes wrong with this communication, WordPress will show the «The response is not a valid JSON response» message. It means that the editor failed to get a response to the server or the response wasn’t in a valid JSON format.

Basically, if the editor can’t communicate with the server, it will show this error message instead.

To fix the problem, you essentially need to fix whatever is getting in the way of the communication.

How to Fix the WordPress Invalid JSON Response Error

Now that you know what the JSON response error message means, let’s dig into some troubleshooting steps to fix this problem.

We’ll try to put these in a logical order, so that the first troubleshooting steps are the most likely to fix the problem.

For that reason, we recommend trying these processes in the order that we’ve written them.

Fix your site’s permalinks and .htaccess file.

One of the most common causes of the invalid JSON response error is an issue with your site’s .htaccess file and/or WordPress permalinks.

Thankfully, this is also one of the simplest debugging steps. Here’s all you need to do:

1. Go to Settings → Permalinks in your WordPress dashboard.
2. Verify that the correct permalink structure is selected — If the correct structure is already selected, you don’t need to change anything.
3. Click the Save Changes button. Even if you didn’t change anything, you should still click the save changes button because it will force WordPress to regenerate its rewrite rules.

Now, go back to the editor and see if that fixed the invalid JSON response error.

If you’re still experiencing issues, you can guarantee that your .htaccess file is clean by deleting it and forcing WordPress to generate a new one. Here’s how:

1. Connect to your server using an FTP client or cPanel File Manager.
2. Find your .htaccess file (it should be in the root folder).
3. Download a copy of the file to your computer as a backup (just in case).
4. Delete the file from your server.
5. Go to Settings → Permalinks in your WordPress dashboard and click Save Changes. This will force WordPress to generate a new, clean .htaccess file.
6. Check if the problem is fixed.

Finally, there’s one last potential fix, but it really only applies to advanced WordPress users.

If you’re working in a local development environment via a tool such as XAMPP, you’ll also want to make sure that you’ve properly configured the .htaccess file permissions and enabled mod_rewrite in Apache’s settings. Make sure to restart Apache once you’ve made the changes.

Check your WordPress site URL.

Another common cause of the invalid JSON response error is a problem with your WordPress site URLs.

The problem can arise if your site URLs aren’t correct or if you accidentally put HTTP instead of HTTPS (assuming your site is using an SSL certificate).

To fix this problem, go to Settings → General in your WordPress dashboard.

You’ll want to verify two things here:

1. Make sure that the URLs are correct. On the vast majority of WordPress sites, your WordPress Address and Site Address should be the same.
2. Make sure that both URLs start with https if you’re using an SSL certificate on your site.

Then, save your changes.

In very rare cases, your site’s URLs might have been hard-coded into your wp-config.php file. If this is so, any changes that you make via your WordPress dashboard won’t apply because those hard-coded changes will override the dashboard settings.

Again, this is very rare because you need to manually add those hard-coded changes, but it can happen so it might be worth checking. For example, your WordPress developer might have done this for you without letting you know.

Here’s how to check if this is the case:

1. Connect to your site’s server using FTP or cPanel File Manager.
2. Edit the wp-config.php file.
3. Search for define( ‘WP_HOME’ OR define( ‘WP_SITEURL’

Here’s an example of what it might look like:

If you do find these code snippets, you can either:

1. Verify that both site URLs are correct and leave the code snippets in your wp-config.php file.
2. Remove the code snippets, which will tell your site to use the URLs that you set in your WordPress dashboard.

Check for a mixed content warning (HTTPS issue).

If your site is using an SSL certificate (which most sites do nowadays), issues with mixed HTTP and HTTPS content can trigger the invalid JSON response error.

In order for your website to benefit from the security of your SSL certificate, you need to use HTTPS to load every resource on your site. If you still have some resources loading over HTTP, this can trigger something called a mixed content warning and which causes problems with the invalid JSON response error.

In the previous section, you made sure that your WordPress site URLs both start with HTTPS (if you’re using an SSL certificate), which should fix many problems with mixed content already.

However, there could still be issues, especially if you’re using a plugin to handle migrating an older site from HTTP to HTTPS.

If you’re using a plugin, make sure that you’ve fully enabled its mixed content fixer features. You can do this by going to Settings → SSL and enabling both the Mixed content fixer and the Fire mixed content fixer with different method toggles:

If you’re not using an SSL plugin, many hosts now offer tools to force HTTPS, which you can find in your hosting dashboard or by consulting your host’s documentation.

Finally, if you’re using Cloudflare on your site, make sure that you’ve set its Encryption Mode to Full (Strict) or Full. Try the Strict option first and then switch to just Full if you experience any issues.

Disable your security firewall.

If you use a firewall to protect your WordPress site, this can sometimes interfere with the editor’s connection to your server and trigger the invalid JSON response error.

This is especially common with ModSecurity rules from your web host, though it also might be triggered by popular security plugins.

To troubleshoot this, try deactivating your firewall or security plugin and see if that fixes the problem. If the editor starts working, you know that something is going wrong with your firewall.

Of course, leaving the firewall disabled isn’t a viable long-term strategy, but you at least now know what’s causing the problem and you can start fixing things.

If your firewall is implemented at the hosting level, you can ask your WordPress host to investigate and whitelist the editor to avoid having it trigger the firewall. That way, you can maintain the protection of your site’s firewall while still avoiding the invalid JSON response error.

If you’re using a WordPress security or firewall plugin, you have two options:

1. You can replace your existing firewall plugin with a different plugin that protects your site without causing problems.
2. You can reach out to the plugin’s developer to ask them about whitelisting to avoid future problems.

If you’re using Wordfence (or another plugin that has a «learning mode»), you can also try reactivating learning mode to reset its firewall rules.

Use a classic editor plugin.

Some people report being able to fix the invalid JSON response error by activating and deactivating the Classic Editor (WordPress’ old, TinyMCE-based editor).

It only takes a couple of minutes, so it’s worth seeing if this trick can fix your problems.

Here’s all you need to do:

1. Install the official Classic Editor plugin from WordPress.org.
2. Go to Settings → Writing and use the drop-down to select the Classic Editor as the default editor for all users.
3. Save your changes.
4. Use the same drop-down to change the default editor back to the Block Editor.
5. Save your changes again.

Now, try creating or editing a new post and see if it works.

Deactivate your WordPress plugins.

Debugging WordPress errors can be tricky because the plugins that you’re using introduce a lot of variables to the equation. With 58,000+ plugins at WordPress.org, that’s a lot of edge cases that could be triggering the invalid JSON response error.

One easy way to figure out if a plugin is causing the problem is to deactivate all of your plugins.

If you’re still seeing the invalid JSON response error after deactivating everything, you can be confident that it’s not an issue with your plugins and you can reactivate them.

On the other hand, if the error goes away after deactivating your plugins, you know that there’s a problem with one of the plugins that you’re using.

To find the problematic plugin, you can reactivate your plugins one by one, making sure to test the editor after each plugin. If you activate a plugin and see the error appear right after that, you’ve found the issue.

From there, you can either replace that plugin with an alternative that doesn’t cause a problem or you can reach out to the plugin’s developer for help and a potential fix.

Upload media files via the Media Library.

If you’re seeing the «The response is not a valid JSON response» when you try to upload media files via the Block Editor, one fix is to upload these images directly to your Media Library instead of via the block interface.

When you add an image block (or the block for another type of media file), click on the Media Library option and upload files that way instead of just clicking the Upload button.

When you do that, you’ll see the regular WordPress Media Library uploader interface, which should let you bypass the invalid JSON response error.

Check the console and debug log.

For more advanced users, you can try digging into your browser’s console or various debug logs to find a more specific problem. This isn’t really a solution for casual users, though, as you’ll need some technical knowledge to accomplish anything here.

First off, you can use the Network tab in Chrome Developer Tools to find issues with Ajax calls.

In the Network tool, select FETCH/XHR to filter out Ajax calls and debug issues with the REST API.

You can also view some REST API issues from your WordPress dashboard. Go to Tools → Site Health and look for a heading such as «The REST API encountered an unexpected result».

Use the Classic Editor as a short-term fix.

This last method isn’t a permanent fix, but it is a workaround that can help you publish content in a pinch.

Earlier, we told you about the Classic Editor trick where you switch your site to the Classic Editor but then switch back to the Block Editor.

Well, if none of the other tips have worked for you, one way to continue publishing content is to just leave the Classic Editor enabled and use that to create content for the time being.

This isn’t an actual «fix» because you’ll lose all of the functionality that the Block Editor adds. However, it will give you the ability to work on content while you continue debugging the «The response is not a valid JSON response» message.

Additionally, once you get the Block Editor working again, you’ll be able to convert your Classic Editor content into blocks with just a few clicks.

Fixing the WordPress Invalid JSON Response Error

Seeing a «Updating failed. The response is not a valid JSON response» message can be frustrating because it appears while you’re trying to work in the WordPress editor.

Thankfully, for most sites, debugging this error shouldn’t be too painful.

In most situations, simply re-saving your WordPress permalinks should fix the problem. If that doesn’t work, you might need to dig into other fixes such as checking your site URLs, fixing mixed content warnings with HTTPS, adjusting your firewall, and more. Implement these troubleshooting steps and you should have your site functioning properly again in no time.

I am getting the error message «Updating failed.» Without any further explanation.
When deactivating every plugin, the message says «Updating failed. Error message: The response is not a valid JSON response.»

The solution I have found online was to use the old editor, which solves the error message, but it is unusable, makes everything very slow.

Here is what the Site Health Plugin says about the site:

wp-core

version: 5.3.2
site_language: en_US
user_language: en_US
permalink: /%postname%/
https_status: true
user_registration: 0
default_comment_status: open
multisite: false
user_count: 4
dotorg_communication: true

wp-paths-sizes

wordpress_path: /var/www/virtual/fraestreik.lu/htdocs
wordpress_size: 50.83 MB (53302243 bytes)
uploads_path: /var/www/virtual/fraestreik.lu/htdocs/wp-content/uploads
uploads_size: 605.88 MB (635308697 bytes)
themes_path: /var/www/virtual/fraestreik.lu/htdocs/wp-content/themes
themes_size: 34.04 MB (35695117 bytes)
plugins_path: /var/www/virtual/fraestreik.lu/htdocs/wp-content/plugins
plugins_size: 84.07 MB (88149952 bytes)
database_size: 17.98 MB (18857984 bytes)
total_size: 792.80 MB (831313993 bytes)

wp-active-theme

name: Divi (Divi)
version: 3.29.3 (latest version: 4.2.2)
author: Elegant Themes
author_website: http://www.elegantthemes.com
parent_theme: none
theme_features: custom-background, automatic-feed-links, post-thumbnails, menus, title-tag, post-formats, woocommerce, wc-product-gallery-zoom, wc-product-gallery-lightbox, wc-product-gallery-slider, customize-selective-refresh-widgets, editor-style, widgets
theme_path: /var/www/virtual/fraestreik.lu/htdocs/wp-content/themes/Divi

wp-themes-inactive (4)

Twenty Nineteen: version: 1.4, author: the WordPress team
Twenty Seventeen: version: 2.2, author: the WordPress team
Twenty Sixteen: version: 2.0, author: the WordPress team
Twenty Twenty: version: 1.1, author: the WordPress team

wp-plugins-active (8)

Give — Donation Plugin: version: 2.5.13, author: GiveWP
Head, Footer and Post Injections: version: 3.1.6, author: Stefano Lissa
Health Check & Troubleshooting: version: 1.4.2, author: The WordPress.org community
Really Simple SSL: version: 3.2.9, author: Rogier Lankhorst, Mark Wolters
Smash Balloon Instagram Feed: version: 2.1.5, author: Smash Balloon
The Events Calendar: version: 5.0.0.1, author: Modern Tribe, Inc.
WP Statistics: version: 12.6.12, author: VeronaLabs
Yoast SEO Premium: version: 12.9.2, author: Team Yoast

wp-plugins-inactive (3)

Akismet Anti-Spam: version: 4.1.3, author: Automattic
Classic Editor: version: 1.5, author: WordPress Contributors
Polylang: version: 2.6.9, author: WP SYNTEX

wp-media

image_editor: WP_Image_Editor_Imagick
imagick_module_version: 1687
imagemagick_version: ImageMagick 6.9.7-4 Q16 x86_64 20170114 http://www.imagemagick.org
imagick_limits:
imagick::RESOURCETYPE_AREA: 122 MB
imagick::RESOURCETYPE_DISK: 1073741824
imagick::RESOURCETYPE_FILE: 768
imagick::RESOURCETYPE_MAP: 512 MB
imagick::RESOURCETYPE_MEMORY: 256 MB
imagick::RESOURCETYPE_THREAD: 12
gd_version: 2.2.5
ghostscript_version: unknown

wp-server

server_architecture: Linux 4.15.0-72-generic x86_64
httpd_software: Apache
php_version: 7.0.33-15+ubuntu18.04.1+deb.sury.org+1 64bit
php_sapi: fpm-fcgi
max_input_variables: 10000
time_limit: 30
memory_limit: 128M
max_input_time: 60
upload_max_size: 19M
php_post_max_size: 20M
curl_version: 7.58.0 OpenSSL/1.1.1d
suhosin: false
imagick_availability: true
server-headers:
date: Sun, 02 Feb 2020 16:25:23 GMT
server: Apache
expires: Wed, 11 Jan 1984 05:00:00 GMT
cache-control: no-cache, must-revalidate, max-age=0
link: https://www.fraestreik.lu/wp-json/; rel=»https://api.w.org/», https://www.fraestreik.lu/; rel=shortlink
x-tec-api-version: v1
x-tec-api-root: https://www.fraestreik.lu/wp-json/tribe/events/v1/
x-tec-api-origin: https://www.fraestreik.lu
x-frame-options: SAMEORIGIN
strict-transport-security: max-age=0; includeSubDomains
vary: Accept-Encoding
content-encoding: gzip
x-xss-protection: 1; mode=block
content-type: text/html; charset=UTF-8
htaccess_extra_rules: true

wp-database

extension: mysqli
server_version: 10.1.43-MariaDB-0ubuntu0.18.04.1
client_version: mysqlnd 5.0.12-dev — 20150407 — $Id: b5c5906d452ec590732a93b051f3827e02749b83 $

wp-constants

WP_HOME: undefined
WP_SITEURL: undefined
WP_CONTENT_DIR: /var/www/virtual/fraestreik.lu/htdocs/wp-content
WP_PLUGIN_DIR: /var/www/virtual/fraestreik.lu/htdocs/wp-content/plugins
WP_MAX_MEMORY_LIMIT: 128M
WP_DEBUG: false
WP_DEBUG_DISPLAY: true
WP_DEBUG_LOG: false
SCRIPT_DEBUG: false
WP_CACHE: false
CONCATENATE_SCRIPTS: undefined
COMPRESS_SCRIPTS: undefined
COMPRESS_CSS: undefined
WP_LOCAL_DEV: undefined

wp-filesystem

wordpress: writable
wp-content: writable
uploads: writable
plugins: writable
themes: writable

I am getting the error message «Updating failed.» Without any further explanation.
When deactivating every plugin, the message says «Updating failed. Error message: The response is not a valid JSON response.»

The solution I have found online was to use the old editor, which solves the error message, but it is unusable, makes everything very slow.

Here is what the Site Health Plugin says about the site:

wp-core

version: 5.3.2
site_language: en_US
user_language: en_US
permalink: /%postname%/
https_status: true
user_registration: 0
default_comment_status: open
multisite: false
user_count: 4
dotorg_communication: true

wp-paths-sizes

wordpress_path: /var/www/virtual/fraestreik.lu/htdocs
wordpress_size: 50.83 MB (53302243 bytes)
uploads_path: /var/www/virtual/fraestreik.lu/htdocs/wp-content/uploads
uploads_size: 605.88 MB (635308697 bytes)
themes_path: /var/www/virtual/fraestreik.lu/htdocs/wp-content/themes
themes_size: 34.04 MB (35695117 bytes)
plugins_path: /var/www/virtual/fraestreik.lu/htdocs/wp-content/plugins
plugins_size: 84.07 MB (88149952 bytes)
database_size: 17.98 MB (18857984 bytes)
total_size: 792.80 MB (831313993 bytes)

wp-active-theme

name: Divi (Divi)
version: 3.29.3 (latest version: 4.2.2)
author: Elegant Themes
author_website: http://www.elegantthemes.com
parent_theme: none
theme_features: custom-background, automatic-feed-links, post-thumbnails, menus, title-tag, post-formats, woocommerce, wc-product-gallery-zoom, wc-product-gallery-lightbox, wc-product-gallery-slider, customize-selective-refresh-widgets, editor-style, widgets
theme_path: /var/www/virtual/fraestreik.lu/htdocs/wp-content/themes/Divi

wp-themes-inactive (4)

Twenty Nineteen: version: 1.4, author: the WordPress team
Twenty Seventeen: version: 2.2, author: the WordPress team
Twenty Sixteen: version: 2.0, author: the WordPress team
Twenty Twenty: version: 1.1, author: the WordPress team

wp-plugins-active (8)

Give — Donation Plugin: version: 2.5.13, author: GiveWP
Head, Footer and Post Injections: version: 3.1.6, author: Stefano Lissa
Health Check & Troubleshooting: version: 1.4.2, author: The WordPress.org community
Really Simple SSL: version: 3.2.9, author: Rogier Lankhorst, Mark Wolters
Smash Balloon Instagram Feed: version: 2.1.5, author: Smash Balloon
The Events Calendar: version: 5.0.0.1, author: Modern Tribe, Inc.
WP Statistics: version: 12.6.12, author: VeronaLabs
Yoast SEO Premium: version: 12.9.2, author: Team Yoast

wp-plugins-inactive (3)

Akismet Anti-Spam: version: 4.1.3, author: Automattic
Classic Editor: version: 1.5, author: WordPress Contributors
Polylang: version: 2.6.9, author: WP SYNTEX

wp-media

image_editor: WP_Image_Editor_Imagick
imagick_module_version: 1687
imagemagick_version: ImageMagick 6.9.7-4 Q16 x86_64 20170114 http://www.imagemagick.org
imagick_limits:
imagick::RESOURCETYPE_AREA: 122 MB
imagick::RESOURCETYPE_DISK: 1073741824
imagick::RESOURCETYPE_FILE: 768
imagick::RESOURCETYPE_MAP: 512 MB
imagick::RESOURCETYPE_MEMORY: 256 MB
imagick::RESOURCETYPE_THREAD: 12
gd_version: 2.2.5
ghostscript_version: unknown

wp-server

server_architecture: Linux 4.15.0-72-generic x86_64
httpd_software: Apache
php_version: 7.0.33-15+ubuntu18.04.1+deb.sury.org+1 64bit
php_sapi: fpm-fcgi
max_input_variables: 10000
time_limit: 30
memory_limit: 128M
max_input_time: 60
upload_max_size: 19M
php_post_max_size: 20M
curl_version: 7.58.0 OpenSSL/1.1.1d
suhosin: false
imagick_availability: true
server-headers:
date: Sun, 02 Feb 2020 16:25:23 GMT
server: Apache
expires: Wed, 11 Jan 1984 05:00:00 GMT
cache-control: no-cache, must-revalidate, max-age=0
link: https://www.fraestreik.lu/wp-json/; rel=»https://api.w.org/», https://www.fraestreik.lu/; rel=shortlink
x-tec-api-version: v1
x-tec-api-root: https://www.fraestreik.lu/wp-json/tribe/events/v1/
x-tec-api-origin: https://www.fraestreik.lu
x-frame-options: SAMEORIGIN
strict-transport-security: max-age=0; includeSubDomains
vary: Accept-Encoding
content-encoding: gzip
x-xss-protection: 1; mode=block
content-type: text/html; charset=UTF-8
htaccess_extra_rules: true

wp-database

extension: mysqli
server_version: 10.1.43-MariaDB-0ubuntu0.18.04.1
client_version: mysqlnd 5.0.12-dev — 20150407 — $Id: b5c5906d452ec590732a93b051f3827e02749b83 $

wp-constants

WP_HOME: undefined
WP_SITEURL: undefined
WP_CONTENT_DIR: /var/www/virtual/fraestreik.lu/htdocs/wp-content
WP_PLUGIN_DIR: /var/www/virtual/fraestreik.lu/htdocs/wp-content/plugins
WP_MAX_MEMORY_LIMIT: 128M
WP_DEBUG: false
WP_DEBUG_DISPLAY: true
WP_DEBUG_LOG: false
SCRIPT_DEBUG: false
WP_CACHE: false
CONCATENATE_SCRIPTS: undefined
COMPRESS_SCRIPTS: undefined
COMPRESS_CSS: undefined
WP_LOCAL_DEV: undefined

wp-filesystem

wordpress: writable
wp-content: writable
uploads: writable
plugins: writable
themes: writable