WordPress.org

Make WordPress Core

Opened 8 weeks ago

Last modified 8 weeks ago

#43900 new defect (bug)

Add hint about blocked Javascript as possible error reason in script-loader.php

Reported by: tobifjellner Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version:
Component: Script Loader Keywords: needs-patch
Focuses: Cc:

Description

When trying to do various things with a new site, I got the same error message over and over: Connection lost or the server is busy. Please try again later.

I even reinstalled, but the error didn't go away. When I revisited the issue next day, finally realized what silly mistake i had made.

In order to help other people with same issue, we only need to change the string above in /wp-includes/script-loader.php (around row 840) into: Connection lost, the server is busy, or you may have blocked JavaScript. Please try again later.

Attachments (4)

untrusted-site.png (7.1 KB) - added by subrataemfluence 8 weeks ago.
error-filter-result.png (7.7 KB) - added by subrataemfluence 8 weeks ago.
content-security-policy.png (15.0 KB) - added by subrataemfluence 8 weeks ago.
dashicons-not-appearing.png (4.8 KB) - added by subrataemfluence 8 weeks ago.

Download all attachments as: .zip

Change History (12)

#1 @SergeyBiryukov
8 weeks ago

  • Keywords reporter-feedback added

I tried editing a post or leaving a tab in background for a while with JavaScript disabled in Opera dev tools, but could not reproduce this message. Could you clarify the steps to trigger it by disabling JavaScript?

#2 follow-up: @tobifjellner
8 weeks ago

  • Keywords reporter-feedback removed

Steps to reproduce:

  1. Leave domain in "default" with NoScript, using Firefox 59 on Win 10
  2. Install fresh WordPress (I used 4.9.5).
  3. Open Plugins - Installed plugins. Click on "Delete" next to "Hello Dolly".
  4. A dialog appears "Are you sure..." - Click "OK"
  5. An admin notice appears (immediately): Deletion failed: Connection lost or the server is busy. Please try again later.

Alternatively 3a. Tools-import 4a. Click on any "Install Now" (I used import tool for WordPress) 5a. An admin notice appears (immediately): Installation failed: Connection lost or the server is busy. Please try again later.

(Edit: corrected chosen state for NoScript)

Last edited 8 weeks ago by tobifjellner (previous) (diff)

#3 in reply to: ↑ 2 ; follow-up: @subrataemfluence
8 weeks ago

I would like to test this at my end. Would you mind telling me how to "Leave domain in default with NoScript..."? Although I am on Ubuntu, I believe if its a bug in WP core it should popup irrespective of operating system!

Replying to tobifjellner:

Steps to reproduce:

  1. Leave domain in "default" with NoScript, using Firefox 59 on Win 10
  2. Install fresh WordPress (I used 4.9.5).
  3. Open Plugins - Installed plugins. Click on "Delete" next to "Hello Dolly".
  4. A dialog appears "Are you sure..." - Click "OK"
  5. An admin notice appears (immediately): Deletion failed: Connection lost or the server is busy. Please try again later.

Alternatively 3a. Tools-import 4a. Click on any "Install Now" (I used import tool for WordPress) 5a. An admin notice appears (immediately): Installation failed: Connection lost or the server is busy. Please try again later.

(Edit: corrected chosen state for NoScript)

#4 in reply to: ↑ 3 ; follow-up: @tobifjellner
8 weeks ago

Replying to subrataemfluence:

I would like to test this at my end. Would you mind telling me how to "Leave domain in default with NoScript..."? Although I am on Ubuntu, I believe if its a bug in WP core it should popup irrespective of operating system!

When I check Firefox extension Noscript seems to be available on Linux, too. So yes, it would be nice if you could test and confirm this situation.

If I recall correctly, the default setting in Noscript, when you activate the add-on, all domains will be "untrusted", until you mark them as trusted.

You may test this the other way around: Activate NoScript and configure it to trust everyone, but mark the domain of your website as "untrusted".

Next: try to delete some unneded plugin. Or try to add some import tool. In both these cases I got this error message, which solely talked about server and/or connectivity issues, when the real culprit was that I still hadn't whitelisted my new domain in NoScript. :)

I'll be eagerly waiting for your comments. If you need a hand during testing, you may DM me on Slack, too. Same username.

#5 in reply to: ↑ 4 @subrataemfluence
8 weeks ago

Thanks so much! I will be into this tomorrow since its almost midnight here! :)

Replying to tobifjellner:

Replying to subrataemfluence:

I would like to test this at my end. Would you mind telling me how to "Leave domain in default with NoScript..."? Although I am on Ubuntu, I believe if its a bug in WP core it should popup irrespective of operating system!

When I check Firefox extension Noscript seems to be available on Linux, too. So yes, it would be nice if you could test and confirm this situation.

If I recall correctly, the default setting in Noscript, when you activate the add-on, all domains will be "untrusted", until you mark them as trusted.

You may test this the other way around: Activate NoScript and configure it to trust everyone, but mark the domain of your website as "untrusted".

Next: try to delete some unneded plugin. Or try to add some import tool. In both these cases I got this error message, which solely talked about server and/or connectivity issues, when the real culprit was that I still hadn't whitelisted my new domain in NoScript. :)

I'll be eagerly waiting for your comments. If you need a hand during testing, you may DM me on Slack, too. Same username.

#6 @subrataemfluence
8 weeks ago

Hi @tobifjellner I installed NoScript and tried to reproduce the issue. Here are my observations (I am on Ubuntu with FireFox 59.0.2 (64-bit).

  1. Marked my own site untrusted. Screenshot untrusted-site.png.
  1. I could not see the error message you mentioned. Please see screenshot error-filer-result.png
  1. Screenshot content-security-policy.png - list of console errors and earning.
  1. What I noticed is no dashicon is appearing for native WordPress menu items (this is out of the scope of this discussion though)

#7 follow-up: @tobifjellner
8 weeks ago

Thanks a lot, @subrataemfluence So it seems that on Linux one will end up with other error than the one I encountered. Interesting!

#8 in reply to: ↑ 7 @subrataemfluence
8 weeks ago

Yes! And since JS is disabled, the action goes along in server-side way without hampering the workflow of plugin deletion method.

Replying to tobifjellner:

Thanks a lot, @subrataemfluence So it seems that on Linux one will end up with other error than the one I encountered. Interesting!

Note: See TracTickets for help on using tickets.