Opened 6 years ago
Last modified 6 years 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)
Change History (12)
#2
follow-up:
↓ 3
@
6 years ago
- Keywords reporter-feedback removed
Steps to reproduce:
- Leave domain in "default" with NoScript, using Firefox 59 on Win 10
- Install fresh WordPress (I used 4.9.5).
- Open Plugins - Installed plugins. Click on "Delete" next to "Hello Dolly".
- A dialog appears "Are you sure..." - Click "OK"
- 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)
#3
in reply to:
↑ 2
;
follow-up:
↓ 4
@
6 years 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:
- Leave domain in "default" with NoScript, using Firefox 59 on Win 10
- Install fresh WordPress (I used 4.9.5).
- Open Plugins - Installed plugins. Click on "Delete" next to "Hello Dolly".
- A dialog appears "Are you sure..." - Click "OK"
- 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:
↓ 5
@
6 years 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
@
6 years 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
@
6 years 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).
- Marked my own site untrusted. Screenshot
untrusted-site.png
.
- I could not see the error message you mentioned. Please see screenshot
error-filer-result.png
- Screenshot
content-security-policy.png
- list of console errors and earning.
- 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:
↓ 8
@
6 years 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
@
6 years 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!
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?