Hello, not sure what this means but this is buggy for me. I install a new 8.x Head and post small content

sometimes i get this error

Warning: file_get_contents(http://example.com/core/modules/ckeditor/js/plugins/drupalimage/plugin.js): failed to open stream: HTTP request failed! HTTP/1.1 503 Service Unavailable in _locale_parse_js_file() (line 1184 of core/modules/locale/locale.module).
    Warning: file_get_contents(http://example.com/core/modules/ckeditor/js/plugins/drupalimagecaption/plugin.js): failed to open stream: HTTP request failed! HTTP/1.1 503 Service Unavailable in _locale_parse_js_file() (line 1184 of core/modules/locale/locale.module).
    Warning: file_get_contents(http://example.com/core/modules/ckeditor/js/plugins/drupallink/plugin.js): failed to open stream: HTTP request failed! HTTP/1.1 503 Service Unavailable in _locale_parse_js_file() (line 1184 of core/modules/locale/locale.module).

so something cant GET the plugins i look also to my logs and here he say me this

xxx.xxx.xx.xx - - [26/Sep/2013:20:15:03 +0200] "GET /core/modules/ckeditor/js/plugins/drupalimage/plugin.js HTTP/1.1" 444 0 "-" "-"
xxx.xxx.xx.xx - - [26/Sep/2013:20:15:03 +0200] "GET /core/modules/ckeditor/js/plugins/drupalimage/plugin.js HTTP/1.1" 444 0 "-" "-"
xxx.xxx.xx.xx - - [26/Sep/2013:20:15:03 +0200] "GET /core/modules/ckeditor/js/plugins/drupalimagecaption/plugin.js HTTP/1.1" 444 0 "-" "-"
xxx.xxx.xx.xx - - [26/Sep/2013:20:15:03 +0200] "GET /core/modules/ckeditor/js/plugins/drupalimagecaption/plugin.js HTTP/1.1" 444 0 "-" "-"
xxx.xxx.xx.xx - - [26/Sep/2013:20:15:03 +0200] "GET /core/modules/ckeditor/js/plugins/drupallink/plugin.js HTTP/1.1" 444 0 "-" "-"

xxx.xxx.xx.xx is the server IP
The request can´t successfully because i restrict my server to not allow "bots" without a User-Agent.
is this a bug by Drupal???

Comments

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

catch’s picture

catch
he/him
Primary language English
commented
Status: Active » Closed (duplicate)
Issue tags: +Bug Smash Initiative

This looks like a server configuration issue, but also should be fixed (or at least improved), by #2607376: Remove on-demand JavaScript translation parsing and do everything on rebuild. Marking duplicate.