Opened 6 years ago
Last modified 3 years ago
#44447 reopened defect (bug)
Failed to load resource: net::ERR_FILE_NOT_FOUND
Reported by: | Benjamin_Zekavica | Owned by: | |
---|---|---|---|
Milestone: | Awaiting Review | Priority: | normal |
Severity: | normal | Version: | |
Component: | General | Keywords: | reporter-feedback |
Focuses: | Cc: |
Attachments (1)
Change History (6)
#1
@
6 years ago
- Keywords reporter-feedback added; needs-patch removed
- Resolution set to invalid
- Status changed from new to closed
#2
follow-up:
↓ 4
@
6 years ago
- Resolution invalid deleted
- Status changed from closed to reopened
I think its a WP Bug, look: https://wordpress.org/plugins/contact-form-7/
Its also on WP.org :(
I have appended some screenshots.
blob:https://wordpress.org/70b682e3-6d0d-4d35-8043-29017af10fd9
Screenshot:
https://www.imagebanana.com/s/1099/RYqApBRn.html
#3
@
6 years ago
I hope to publish a patch for this. More and more WP Installation of different website get this error message.
It was so fantastic to correct this bug.
#4
in reply to:
↑ 2
@
6 years ago
Replying to Benjamin_Zekavica:
I think its a WP Bug, look: https://wordpress.org/plugins/contact-form-7/
Its also on WP.org :(
I have appended some screenshots.
blob:https://wordpress.org/70b682e3-6d0d-4d35-8043-29017af10fd9
Hi @Benjamin_Zekavica, welcome to WordPress Trac! Thanks for the report.
I don't see the issue on that page, the HTML source doesn't have that URL either. Which browser are you using? Does it still happen with all browser extensions disabled, or in another browser?
Google search for 70b682e3-6d0d-4d35-8043-29017af10fd9
only shows this ticket.
It is clear from the error message that the file in question could not be found in referenced path. This I don't think a core WordPress issue. I tried to reproduce on a clean WordPress install with no addition plugin activated. I used WordPress bundled theme
twentyseventeen
.Can you please double check what file is giving this error. The filename is listed at the right of the error message in gray color. To my understanding it is related to some theme / plugin being active in the system.
Please reopen this ticket if you can reproduce the bug with the following configuration:
Thank you.